Error: 0100 0003 Task: 002223C0 on boot

[a94marbo]

Hi
I am probably pushing my Amiga 500 a bit too much, but I am so close now so I would like to know if anyone have encountered this before.

I have an 1 MEG ECS Amiga 500 pimped with a ACA500Plus and a ACA1221lc and X-Surf-500.

I have made a clean AmigaOS3.9 hdf and upgraded it to ClassicWB3.9. Works fine in WinUAE, but when I move to CF-card to the Amiga I get this yellow message:

Recoverable Alert Error: 0100 0003 Task: 002223C0, twice. Then ClassicWB starts and everything seems fine.

If I edit the startup-sequence ROM update part:

IF EXISTS SYS:Prefs/Env-Archive/NOSCSIUPDATE
Set SCSIUpdate 0
EndIF
IF @SCSIUpdate EQ 1
C:SetPatch QUIET
ELSE
C:SetPatch SKIPROMUPDATES "scsi.device" QUIET
EndIF
Unset SCSIUpdate


With a ";" before the "Set SCSIUpdate 0" - row
It boot with no error, but I get this message instead when it has booted:

"Cannot open "workbench.library", version 45. Unable to run "AmiDock"

, and all icons are gone and AmiDock....

Any ideas?

[Saghalie]

Yellow - The CPU encountered an error before the system's error-trapping
code (the code the calls up the Guru) was in place.

Which more than likely means that you don't have the correct hardware for
the CPU to operate correctly.

you will need to copy the workbench.library to your Libs: directory. I think
Cloanto has a down load for it somewhere. Look for it on their FAQ web site.

Hope this helps!

[a94marbo]

Thanks for your answer.
The workbench.library exist in Libs, thats not the problem.

Its just not finding it if I remove the "C:SetPatch QUIET" line in startup-sequence.

I am starting to believe that this error is connected to the CF cards I have as harddrives.

When I removed the CF card from the AUX port in the ACA500plus, the task number in the error message changed to "00216C18" instaed of "002223C0".
They are both 4 GB CF cards, and there are alot of fixes and patches in the "My Files" folder in the ClassicWB distrubution.
The question is which patch to try out?

[Toni Wilen]

#define AN_LibChkSum 0x01000003 /* Library checksum failure */

Most likely usual max transfer bug. Do you get same crash in WinUAE if you go to harddrives panel, open your HDF and set ATA mode to "ATA 2+ Strict"?

ACA500plus already has never IDE driver in flash ROM that does not have max transfer bug but it is possible (?) setpatch will overwrite it with older version.

[a94marbo]

Originally Posted by Toni Wilen

Most likely usual max transfer bug. Do you get same crash in WinUAE if you go to harddrives panel, open your HDF and set ATA mode to "ATA 2+ Strict"?

ACA500plus already has never IDE driver in flash ROM that does not have max transfer bug but it is possible (?) setpatch will overwrite it with older version.

If I set the controller to "IDE (auto)" in WinUEA, it does not boot at all, stops at kickstartstart logo. It only boots if I have it set to "UAE (uaehf.device)".

[Toni Wilen]

Originally Posted by a94marbo

If I set the controller to "IDE (auto)" in WinUEA, it does not boot at all, stops at kickstartstart logo. It only boots if I have it set to "UAE (uaehf.device)".

If you use A500 config, you need to manually enable IDE in advanced chipset panel (or simply change chipset extra to A600)

[a94marbo]

Originally Posted by Toni Wilen

Most likely usual max transfer bug. Do you get same crash in WinUAE if you go to harddrives panel, open your HDF and set ATA mode to "ATA 2+ Strict"?

ACA500plus already has never IDE driver in flash ROM that does not have max transfer bug but it is possible (?) setpatch will overwrite it with older version.

If I disable the patch ClassicWB cannot open workbench.library, version 45. (it is in libs), but the yellow error message disappears.

Originally Posted by Toni Wilen

If you use A500 config, you need to manually enable IDE in advanced chipset panel (or simply change chipset extra to A600)

Upps, sorry.
With IDE enabled it boots both from HDF file and from the actual CF card in WinUAE, without any 0100 0003 yellow message.

[Thomas Richter]

Originally Posted by Toni Wilen

Most likely usual max transfer bug.

That - or which version of the scsi.device is this? The 3.9 versions allocate one critical structure too small and then trash memory of whatever is allocated close to it.

[a94marbo]

Originally Posted by Thomas Richter

That - or which version of the scsi.device is this? The 3.9 versions allocate one critical structure too small and then trash memory of whatever is allocated close to it.

I have scsi.device version 52.511.
That version seems to be inserted from the ACA500plus.

In ClassicWb 3.1 no error occurs at boot and the same scsi.device version is used, i.e. 52.511.