OS 3.9 installation issues

[PanterHZ]

SetPatch is one thing, but what about the "AmigaOS ROM Update" file it uses, is it present in the Devs drawer of the Emergency Disk, and does it have the correct name? Also, I don't think using a different version of SetPatch is such a good idea, since it might lead to a conflict when SetPatch is run for the third time (from the CD) upon booting.

I have a feeling that using the default OS3.1 CD file system might be the root of your problems, since this will only use the 8.3 file & dir naming method, which leads to certain file names being truncated (and the extensions as well). This file system is only to be considered as a "better than nothing" type of solution. So after making sure that it's possible to access your AmigaOS 3.9 CD, you should have just copied the CacheCDFS file to the Devs drawer on your Workbench partition, and then tried to configure a proper mount file which uses it.

[PanterHZ]

I suggest that you leave picasso96 for now. The main priority should be to create a working Emergency Disk, and then make a working AmigaOS 3.9 install.

[PanterHZ]

I think he's using a 3.1 SetPatch in there, in conflict with a 3.9 SetPatch, or something.  He mentioned "one he downloaded from the web", which could be anything, who knows?  

I remember having similar problems years ago, where certain files was copied directly from the harddisk instead of the CD when creating the Emergency Disk. It might be possible that 3.1 SetPatch gets copied to the disk.

[PanterHZ]

Once the emergency disk is created I should be able to check the version of the setpatch on the floppy version the version on the os 3.9 cd.  I assume it should be the newer 44.17 version I want the emergency disk, yes?

Yes that's true. Do also check that the Libs/68040.library and "Devs/AmigaOS ROM Update" files are present on the disk as well.

[PanterHZ]

Mike is probably right, it's the AmigaOS3.9:OS-Version3.9/Emergency-Disk/C/SetPatch file you want.

[PanterHZ]

Just a thought I had. You mention that your CD-ROM uses scsi.device, isn't it possible that this some way conflicts with the scsi.device versions present in the OS3.9 ROM update? (which are meant for IDE controllers only)

When you boot with no startup sequence, what happens when you enter the following: SetPatch SKIPROMUPDATES "scsi.device"

[PanterHZ]

Edit: I suppose you could also try "setpatch NOROMUPDATE" and then just add the updates back in one-by-one?  But that would be a real PITA.  

Yes that sounds like a tedious task indeed

I'm still going back to your second screenshot in this post, however.

Can you tell us exactly what was happening there?  You say you were trying to boot off your ERD? Because it says "SetPatch V40.16 already installed".  40.16 is a 3.1 SetPatch.  Then it's giving a checksum failure on console.device 44.6, which a 3.9 update.  No way are these two files going to play nice together...

Maybe he was trying to run the EDisk SetPatch from within Workbench 3.1 instead of booting the floppy with no Startup-Sequence?

[PanterHZ]

After some googling, I came across this thread which explains what ERROR #80000004 means: http://www.amiga.org/forums/showthread.php?t=11743

In Post #3 Piru mentions the following:

"Error 80000004 means CPU has executed illegal instruction (instruction is not identified by the CPU). The reason for this error can be numerous. In simplest case it's just some single program misbehaving, in worst case it's indication of a failing hardware."


I also found this thread which sounds a bit familiar (although it's an A4000): http://www.amiga.org/forums/showthread.php?t=49805

My guess is that you really need to copy the 68040.library from your WarpEngine disk to your Emergency Disk, because even though the version numbers are the same, the library might have been patched in order to work with the WarpEngine.

Try this first, and if it fails, you might consider following the instructions by Thomas in the above mentioned thread.