SystemPatch does not work anymore.

Leandro Jardim · 28 April 2013, 00:27

For some reason SystemPatch (tested 2.99+) seems to not work on 2.6.0 betas. It simply shows that the patches are installed and immediatelly lock-up Workbench or shell. I have tested it with an "A1200 + 4MB Fast"; configuration and Kickstart/Workbench 3.1 and with a shell window from Early Setup.

Toni Wilen · 28 April 2013, 08:59

I think you missed some very important information: last working version and make sure you re-test previous official version because it is suspicious that program like systempatch just stops working..

daxb · 28 April 2013, 12:19

Did you tried SystemPatch V3.3? Do you have all patches installed? You may compare changelog/history of winuae with SystemPatch patches. You can find out if a special patch is resposible by deactivate single patches and/or patch groups (NOEXEC, NOGFX, ...). If you find the causer Toni could tell you more.

Leandro Jardim · 03 May 2013, 09:02

I found the problem. Somebody hacked my AmigaOS executables... I had problem with this before, at first was the newicon executables, after the fblit ones, the systempatch and the datatypes. But I fixed that ones. And now I guess are the RDB and maybe even the anti-virus.

The only thing remaining to check is the RDB, I think. Does VirusZ would not be able to check the RDB of the hard disk and tell any anomalies with it?

PS. daxb, are you not the same guy of the ngemu forums and the chip8/chip16 threads? Nice to talk with you, I think very interesting that threads on ngemu.

daxb · 03 May 2013, 13:16

Quote:

Originally Posted by Leandro Jardim

PS. daxb, are you not the same guy of the ngemu forums and the chip8/chip16 threads?

No.

28 April 2013, 00:27	#1
Leandro Jardim Registered User Join Date: Nov 2009 Location: Legoland Age: 45 Posts: 1,461	SystemPatch does not work anymore. For some reason SystemPatch (tested 2.99+) seems to not work on 2.6.0 betas. It simply shows that the patches are installed and immediatelly lock-up Workbench or shell. I have tested it with an "A1200 + 4MB Fast"; configuration and Kickstart/Workbench 3.1 and with a shell window from Early Setup. Last edited by Leandro Jardim; 28 April 2013 at 09:02. Reason: added version.

03 May 2013, 09:02	#4
Leandro Jardim Registered User Join Date: Nov 2009 Location: Legoland Age: 45 Posts: 1,461	I found the problem. Somebody hacked my AmigaOS executables... I had problem with this before, at first was the newicon executables, after the fblit ones, the systempatch and the datatypes. But I fixed that ones. And now I guess are the RDB and maybe even the anti-virus. The only thing remaining to check is the RDB, I think. Does VirusZ would not be able to check the RDB of the hard disk and tell any anomalies with it? PS. daxb, are you not the same guy of the ngemu forums and the chip8/chip16 threads? Nice to talk with you, I think very interesting that threads on ngemu. Last edited by Leandro Jardim; 03 May 2013 at 12:23.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Vsync does not work anymore with 2.4.0	Clark Kent	support.WinUAE	36	24 May 2012 20:30
Rom 1.2 doesn't work anymore	hitchhikr	support.WinUAE	4	24 April 2010 15:05
Many WHDLoad games don't work anymore.	alkis21	project.WHDLoad	19	26 August 2009 11:51
Loom CD doesn't work anymore with scummvm 0.9.0?	hexaae	support.Games	1	03 August 2006 18:51
PinballFantasies CD32 (HD) doesn't work anymore with R6	Leo42	support.WinUAE	0	02 May 2003 03:20

28 April 2013, 08:59	#2
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,570	I think you missed some very important information: last working version and make sure you re-test previous official version because it is suspicious that program like systempatch just stops working..

28 April 2013, 12:19	#3
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,307	Did you tried SystemPatch V3.3? Do you have all patches installed? You may compare changelog/history of winuae with SystemPatch patches. You can find out if a special patch is resposible by deactivate single patches and/or patch groups (NOEXEC, NOGFX, ...). If you find the causer Toni could tell you more.

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