OS 3.2 Amiga 4000D IDE spliter AtapiMagic

[Laine]

HW: Amiga 4000D/3660 16megs fast Onboard, ZZ9000 Bios 1.8, 4 way splitter for an Amiga 4000D

Installed 3.2 on formatted CF card,
(installed the drivers for the ZZ9000/P06/roadshow and AExplorer to move files)

move CD0 from Storage\DOSDrivers to DevsOSDrivers

Downloaded AtapiMagic followed the instruction of editing startup-sequence and moving the atapimagic file to LIBS:modules
dir this edit to the start chaning the 46 to 47 like it says

If Exists C:LoadModule
C:Version exec.library version 47 >NIL:
If Warn
C:LoadModule LIBS:modules/AtapiMagic ROMUPDATE
Else
C:LoadModule LIBS:modules/AtapiMagic
EndIf
EndIf

rebooted and the amiga gurus, used WinUAE recover startup- sequence

So to make it work Change tooltype to from scsi.device to atapi.device
find an atapi.device place in devs:

edited the startup-sequence to leaving what was there and add

C:LoadModule LIBS:modules/AtapiMagic


what mine looks like


;Version exec.library version 47 >NIL:
;If Warn
LoadModule L:System-Startup ROMUPDATE
EndIf

C:LoadModule LIBS:modules/AtapiMagic

SetPatch >NIL:




reboot CD roms read fine, hope this helps someone

[thomas]

atapi.device is part of IDEfix. It handles IDE splitters out of the box, it does not need AtapiMagic.

[Laine]

Thank you Thomas,

I wasn't sure if the IDEFix was compatible with 3.2 so used what I read in the FAQ

I'll make an other install using IDEFix and see how that goes

[thomas]

You don't need IDEfix to run a CD drive. You can use atapi.device with 3.2's CD file system. IDEfix will undo the improvements introduced with 3.2.

[Laine]

So using Thomas's advice I removed the 'C:LoadModule LIBS:modules/AtapiMagic'

just using the atapi.device from IDEfix (with the tooltype change of CD0)

it all works fine

Thanks again Thomas

[Dege]

I have the same problem with my 4000D. If I have the loadmodule atapimagic in the SS, I'll get a guru. Interestingly if I click through the guru, my Amiga goes to the Workbench and I can see atapimagic is loaded with loadmodule list. Not the best way to arrive at it! Still haven't pinpointed the problem. It seems that if SOME machines with 3.2 go to 3.2.1 and beyond, it will black screen and eventually guru. It could be a conflict in 3.2.1 and up. I'll keep working at it.