I have a issue to recognize the ide cdrom on AmigaOs 3.2, on 3.1 work good with IDEFix (atapi.device) but with 3.2 IDEFix hang… I know the 3.2 scsi.device handle the ide cdrom but on my config don’t work! I have the A4091 scsi board (with hdd and jaz) and cdrom on ide port, the scsi.device is mapped on A4091 and 2nd.scsi.device do not exist! (on boot the cdrom is not recognized and the 2nd.scsi.device is not loaded in menory) How I can use the new scsi.device if the device not exist? Any suggestion?

@marmotta

Using kick 3.1 and loading scsi.device from disk? Sounds like LoadModule figuring your system to be A4000T with just SCSI and so it never loads the A4000D scsi.device, and instead just replace the kickstart one with new one for just SCSI. I don’t know if it is possible for LoadModule to load both the two scsi.device drivers at once - the one to know would be Thomas Richter, aka ThoR.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@kolla

Yes, kick 3.1 and softkick 3.2, when I have installed the 3.2 I have selected A4000D as “machine type”. My system always have only one scsi.device (a4091) with 3.2 or with 3.1. I think the 2nd.scsi.device appears only if I connect a ide hdd.

@marmotta

What do you mean by “softkick”? Do you load the entire OS 3.2.1 kickstart and reboot, or do you use LoadModule to replace kickstart modules?

With kickstart 3.1 for A4000, the built in scsi.device is for IDE, and the scsi.device for the A4091 is on the firmware/ROM of the A4091 itself.

To update both of them with new scsi.device v47 from OS 3.2.1, you need to load both the scsi.device for A4000D and the one for A4000T.

LoadModule tries to detect what amiga model you have, but may not be bugfree, and perhaps ends up guessing you have an A4000T (it shares same scsi controller chip as a4091 iirc) and loads DEVS:A4000T/scsi.device, and not DEVS:A4000D/scsi.device (I may remember the paths wrongly here).

An alternative would of course be updated rom/firmware on the a4091 with new scsi.device, no idea if that’s a supported possibility.

Last edited by kolla on 01-Aug-2022 at 11:32 PM.
Last edited by kolla on 01-Aug-2022 at 11:31 PM.

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

I had no problem at all. I have a physical 3.2.1 rom and running AOS 3.2.1 on my A4000 with CDROM on 2nd IDE cable. I did a minimal manual install by added atapi.device from IDEfix to DEVs and CacheCDFS to L and a proper CD0 mountlist. Works without a problem.

@kolla

The kickstart is loaded from default installer startup-sequence, the installation is clear. If I run “version scsi.device” I see the version from kickstart 3.2.1… I tried to load the scsi.device from devs:a4000d/scsi.device (loadmodule devs:a4000d/scsi.device) but nothing change. I remember, with ide hdd, the onboard ide is scsi.device and a4091 is 2nd.scsi.device. But without ide hdd the kickstart don’t load a device for ide (cdrom is not recognized at boot) and I have only scsi.device for the A4091. I need to force loading of ide device, but I don’t know how to do.

@spud101

You have a ide hdd?

Idefix work good with 3.1. With 3.2 it hangs when c:idefix is loaded from startup-sequence

Last edited by marmotta on 02-Aug-2022 at 09:08 AM.

@marmotta

I have an IDE CF on first IDE cable
I have a CDROM on second IDE cable

Don't put IDEfix on your computer and not in your startup-sequence.

just pick these files from the IDEfix package (e.g. extract to RAM):
put atapi.scsi in DEVS
put CacheCDFS in L
Put CD0 in & CD0.info in DEVS/DOSDrivers
No edits in startup-sequence needed.

After install of these files you may still get a register IDEfix popup.
You can register, after you make sure CDROM works, by extracting the IDEfix package to RAM: again (Assuming it was gone after a reboot)
Then run: RAM:IDEfix/register/register
You can use the registration details that is provided in AmigaForever if you own a copy of that. Otherwise, google is your friend for a serial.

@spud101

Without idefix on startup-sequence, atapi.device don’t work (not find any device)

Another strange thing, if I load a idefix executable on 3.2 (without cd0 on devs) the 2nd.scsi.device appears! But if I query it the system hangs, same as I query atapi.device.

And another… if I load idefix and cd0 on 3.1 then reboot on 3.2 I can use Idefix and the cdrom work! I think the idefix can’t initialize the cdrom on 3.2… but when it is initialized it work on 3.2. At least until poweroff.

Problem solved!!!

In the past, for have a faster boot (no delay for ide) I have set the cdrom as “slave”! (I forgot it) now I have set the cdrom as “master” and all is as aspected! The 2nd.scsi.device are present and the ide is on scsi.device. All ok!

I have to get used to the slow boot :-p

@marmotta

Good!! So how did you do it, totally without idefix, atapi, etc and only with scsi.device? If so, I would like to know how you got the 2nd IDE working without idefix.

I have tried with atapimagic, but didn't get it working.

@spud101

Yes, work good without idefix! I only use a scsi.device and os3.2 mountlist. The A4091 now is 2nd.scsi.device

@marmotta

I am curious, what does "version full 2nd.scsi.device" say?

_________________
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC

@kolla

Say 40.13 (old version…)