Yep, shouldn't need the BoingBag updates at this stage, leave them for now.
During the install, you would have been required to create an emergency disk and reboot, thus booting from the emergency disk.
The idea is that when you boot from the emergency disk, it runs OS3.9 setpatch which then applies the ROM update (all from the floppy disk).
You should then see the computer do a soft reset by itself in order to actually run the new ROM code, so now it'll be using the updated scsi.device, etc, which means the CDROM drive will be operational, no IDEfix required.
The system then proceeds to boot WB from the OS3.9 CD once the drive has been mounted.
Not sure why it's not playing ball for you, it's generally not caused many issues on the countless OS3.9 machines I've set up over the last few years.
Try this:
1. Boot from emergency disk
2. Wait until it loads the new ROM image then reboots itself (takes about 20-30 seconds)
3. Hold down both mouse buttons, boot with no startup
4. Providing "version" is on the emergency disk, you'll be able to check the kickstart version is 45.xx
5. Entering "mount CD0:" should immediately mount the CDROM, so you should be able to then browse files, etc, on it using the CLI
If all works fine from the emergency disk, it suggests something wrong with the new OS3.9 install on the hard drive.
