ClassicWB with systempatch

rare_j · 04 April 2006, 11:50

I installed the latest version of systempatch2 to classicWB and some strange things happened -

1. When opening lha files in voodoox a black screen popped up with an orange flashing box telling me Xvs.Library is corrupted or hacked or something
2. So I started janoeditor to remove the patch fron the user startup the amiga did a guru. In the end I had to use ed which wasn't pleasant. Then all was back to normal.

Is there some option I should have specified to systempatch or should I not use systempatch at all with scalos?

mr_a500 · 04 April 2006, 15:08

This latest version of SystemPatch (2.96) has problems with xvs.library. I sent an email to the program's author the day this new version was released explaining this problem, but he hasn't replied.

You can either do without SystemPatch or use version 2.95.

rare_j · 04 April 2006, 17:36

I tried the 2.95a version with the NOEXEC option. It works much better now.

mr_a500 · 04 April 2006, 17:56

I suggest you also use the NOINTUITION option. Otherwise you'll have problems with programs using custom file requesters - like DigiPaint3, DSS, PageRender.

rare_j · 04 April 2006, 18:36

I wondered why that was in there by default. Thanks, I put it back in just in case.

PeterK · 04 April 2006, 19:13

Yes, SystemPatch 2.96 has indeed a problem with the new
LoadSeg() patch for dos.library, which causes the error with
xvs.library. I've already reported this to the author Sante, but
no reply and no changes of SystemPatch yet

For my own system with WinUAE and P96, I switched back to
version 2.95a again calling it with these options:
SystemPatch >NIL: NOLAYERS -BltClear

If you want to use v2.96, then add the NoDOS option to fix the bug.
Unfortunately, that would disable the faster file access, too.

mr_a500 · 04 April 2006, 22:36

Quote:

I wondered why that was in there by default. Thanks, I put it back in just in case.

What?

The NOINTUITION option is in the ClassicWB startup-sequence? I don't use the ClassicWB packs, just my own setup on my A500. Even Sante couldn't help me fix the Digipaint 3 and DSS file requester problems. I had to find that out with lots of tedious testing. Gee - I could have just looked at the ClassicWB setup.

rare_j · 05 April 2006, 00:34

Systempatch isnt part of classicwb as far as I know, that's why I was adding it myself. The systempatch installation script adds the NOINTUITION switch to user-startup by default, without any explaination in the docs. I took it out but you gave me a good reason to leave that switch in.

mr_a500 · 05 April 2006, 00:51

Ah ha! I've just been copying over the new versions of SystemPatch without using the installer. Maybe Sante put that in as default after my problems and forgot to tell me.

Bloodwych · 08 April 2006, 15:17

Scalos, being a workbench replacement, has many performance patches already included. What is so good about SystemPatch?

It seems to cause more issues than perceivable benefits? Or am I being ignorant since I haven't truly tested it. Let me know peeps just what benefits you notice after installing this patch!

rare_j · 10 April 2006, 14:25

As far as I can tell it patches some system libraries for better performance and perhaps some chipram savings. I don't know if the patches in systempatch overlap with the stuff Scalos does.

04 April 2006, 11:50	#1
rare_j Zone Friend Join Date: Apr 2005 Location: London Posts: 1,176	ClassicWB with systempatch I installed the latest version of systempatch2 to classicWB and some strange things happened - 1. When opening lha files in voodoox a black screen popped up with an orange flashing box telling me Xvs.Library is corrupted or hacked or something 2. So I started janoeditor to remove the patch fron the user startup the amiga did a guru. In the end I had to use ed which wasn't pleasant. Then all was back to normal. Is there some option I should have specified to systempatch or should I not use systempatch at all with scalos?

08 April 2006, 15:17	#10
Bloodwych Moderator Join Date: Jun 2001 Location: I'm behind you! Posts: 3,763	Scalos, being a workbench replacement, has many performance patches already included. What is so good about SystemPatch? It seems to cause more issues than perceivable benefits? Or am I being ignorant since I haven't truly tested it. Let me know peeps just what benefits you notice after installing this patch! Last edited by Bloodwych; 08 April 2006 at 19:06.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
SystemPatch 3.1	ziosante	News	32	30 August 2018 14:08
SystemPatch 3.x	tolkien	request.Apps	2	02 April 2013 00:03
SystemPatch 3.3	Leandro Jardim	request.Apps	2	22 May 2010 03:56
SystemPatch 3.0	ziosante	News	11	02 January 2008 00:50
New release of SystemPatch!	Paul	News	0	04 January 2005 12:59

04 April 2006, 15:08	#2
mr_a500 Amiga-based Cyborg Join Date: Dec 2004 Location: Canada Posts: 808	This latest version of SystemPatch (2.96) has problems with xvs.library. I sent an email to the program's author the day this new version was released explaining this problem, but he hasn't replied. You can either do without SystemPatch or use version 2.95.

04 April 2006, 17:36	#3
rare_j Zone Friend Join Date: Apr 2005 Location: London Posts: 1,176	I tried the 2.95a version with the NOEXEC option. It works much better now.

04 April 2006, 17:56	#4
mr_a500 Amiga-based Cyborg Join Date: Dec 2004 Location: Canada Posts: 808	I suggest you also use the NOINTUITION option. Otherwise you'll have problems with programs using custom file requesters - like DigiPaint3, DSS, PageRender.

04 April 2006, 18:36	#5
rare_j Zone Friend Join Date: Apr 2005 Location: London Posts: 1,176	I wondered why that was in there by default. Thanks, I put it back in just in case.

04 April 2006, 19:13	#6
PeterK Registered User Join Date: Apr 2005 Location: digital hell, Germany, after 1984, but worse Posts: 3,366	Yes, SystemPatch 2.96 has indeed a problem with the new LoadSeg() patch for dos.library, which causes the error with xvs.library. I've already reported this to the author Sante, but no reply and no changes of SystemPatch yet For my own system with WinUAE and P96, I switched back to version 2.95a again calling it with these options: SystemPatch >NIL: NOLAYERS -BltClear If you want to use v2.96, then add the NoDOS option to fix the bug. Unfortunately, that would disable the faster file access, too.

05 April 2006, 00:34	#8
rare_j Zone Friend Join Date: Apr 2005 Location: London Posts: 1,176	Systempatch isnt part of classicwb as far as I know, that's why I was adding it myself. The systempatch installation script adds the NOINTUITION switch to user-startup by default, without any explaination in the docs. I took it out but you gave me a good reason to leave that switch in.

05 April 2006, 00:51	#9
mr_a500 Amiga-based Cyborg Join Date: Dec 2004 Location: Canada Posts: 808	Ah ha! I've just been copying over the new versions of SystemPatch without using the installer. Maybe Sante put that in as default after my problems and forgot to tell me.

10 April 2006, 14:25	#11
rare_j Zone Friend Join Date: Apr 2005 Location: London Posts: 1,176	As far as I can tell it patches some system libraries for better performance and perhaps some chipram savings. I don't know if the patches in systempatch overlap with the stuff Scalos does.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)