OS 3.9 installation issues

[giZmo350]

OMG, it just occurred to me.  Are you using the same floppy disk for all of this?  Is it some old disk you pulled out of a box that's 20+ years old?  Try a different floppy and report back.  

Also try booting with no Startup-Sequence and just run the setpatch command.

Way to hustle Mike!
Holy Sheet! What made you think of that?!!!
Must be on the hard stuff tonight eh!!!! :lol:


Wait a minute!!!!!
Did you go see the Pope today?
Did you get your Miggy Blessed!!!!!
:angel:

[Oldsmobile_Mike]

:laughing:

[Oldsmobile_Mike]

Two other thoughts: In your second screenshot it says 40.16.  If you're booting off the 3.9 ERD It should be 44.16.  Or 44.38, if you use the version I posted earlier.

Also here's what mine does.  Just 'cause we're on the subject, not that it's very relevant.  I hacked the sh*# out of mine though, with a string of LoadResident & LoadModule commands, and a lengthy "SKIPROMUPDATES" string, as well.  One of these days I'll get around to joining the exclusive club of "I burn my own 3.9 ROM's too", but in the meantime that double-reboot doesn't bother me too much.  

[dschallock]

Ok, I'm back.  I'm going to get another floppy from my collection and see if we can get a different result.  I still may have a xad key file issue when I get there, but... one thing at a time. :laugh1:

[dschallock]

ok, new floppy.
Made another emergency boot disk.
This time when I boot with no startup sequence and then execute setpatch I don't get any more checksum errors.  I looks like it works fine.
However....
Upon trying to boot from it, it still crashes on setpatch.
It has setpatch version 44.17 so maybe I'll try the version Mike sent me on this new floppy now.

[dschallock]

nope.  copied 44.38 version of the setpatch onto the emergency-disk floppy.  Now when I boot I get a yellow recovery crash, I click the left mouse button, it continues and then I get the setpatch crash. :pissed:

I think someone mentioned checking romupdate files, I'm going to back read a little and try checking that I guess.

[dschallock]

You know I'm going to ask you another dumb question here.  You definitely have 3.1 ROM's, right?  Not 3.0?

Yes, Definitely have 3.1 roms.

[dschallock]

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.

I just checked and both these are present on the disk.

(sigh)... I'm not sure what to try next honestly.  I guess I could download the 44.16 version of setpatch and give that a go instead of the 44.38?

[Oldsmobile_Mike]

Are you sure your floppy drive is working okay?  Did I read somewhere you mentioned something about your internal drive being toast, and that you are trying to do all this off an external DF2:?

You have any game disks or anything else you can try booting off of, just to give the drive a workout?

[Oldsmobile_Mike]

FYI here is the output of a straight SetPatch with no additional options or config changes.  What it should look like, anyway.  

Yours crashed at console.device.  Try this:

C:SetPatch SKIPROMMODULES console.device

Does it get past it then?

[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"

[Oldsmobile_Mike]

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

Ha, was just going to post something about that, too.    Maybe his multiple SCSI controllers aren't playing nice with the updates?

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.  

[Oldsmobile_Mike]

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...

[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.

[guest11527]

I just checked and both these are present on the disk.

(sigh)... I'm not sure what to try next honestly.  I guess I could download the 44.16 version of setpatch and give that a go instead of the 44.38?

The version of SetPatch is at this point irrelevant - the problem is that your ROM-Updates file is corrupt. The thing in DEVS: This needs replacement with a version with a proper checksum. (-: