OS 3.9 installation issues

[dschallock]

Emergency boot disk gives me this on boot attempt.  I will now try the version of setpatch you added Mike and report back. Thanks!

[dschallock]

Ok, new version of setpatch gave me a recoverable error (the yellow one) first, and then booted to the same setpatch error crash as in the previous picture.

mike... hahahha... yes, of course I pulled that 20 year old floppy out of a box! :roflmao:. ok, I'll try a new floppy, and I'll also try the boot with no startup sequence thing too.

Ugh... I had to run out of the house for about an hour to drop someone off.  If anyone is around in an hour, I will report the new findings out here. Thanks!

[dschallock]

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.

Real quick  thought I better post this.
This is the boot with no startup sequence.  tested set patch from the os 3.1 currently installed.


And this is the same test trying to run setpatch from the floppy emergency disk.



That um... checksum error thing.... :rofl: I suppose that is the old floppy thing you might be talking about Mike? :laughing:

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

[dschallock]

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?

Yes Mike, your correct.  I have 2 different internal floppy drives that were both acting very buggy so I removed them.  I am still on the hunt for a good internal replacement for DF0.  In the mean time I have an external plugged into the the external floppy port, DF2.  The boot priority is less on DF2 so when I try to boot from it I have to do the "hold down both mouse buttons on restart" and select DF2 as the boot device.  I can certainly try booting from some games today when I get home.  I have booted from some games off that drive in the past without a problem, but its good to rule everything out I agree.

[dschallock]

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?

The picture of the setpatch crash you are referring to was when I was using the buggy floppy disk.  Once I changed the floppy disk to a better one and I boot with no startup sequence and run the setpatch it doesn't crash.  But it DOES crash when I try to boot from it (Which makes no sense to me).
Having said all that, I will certainly try typing what you said and report the results.

[dschallock]

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"

Ok, that is a good thought... I will try this too.

[dschallock]

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

Hi Mike, ok, here is what produced these two screen shots.
I had a fresh install of 3.1 and had created an emergency boot disk.
I booted the amiga with no startup sequence
In the first picture I had typed workbench:c/setpatch
Immediately after typing that (no reboot) I typed df2:c/setpatch The results were the 2nd screenshot.
Thanks again for all the help with this!

[dschallock]

So to reiterate: ERD floppy in DF2:.  3.9 CD in CD0:.  Either lower the priority on all your other partitions so the system doesn't try to boot off them, or just go into HDToolbox and check the box to make them non-bootable.  Power on.  Don't touch anything.  What happens?

Ok, but in terms of wiping out the 3.1 partition completely, I can't do that until I have made an emergency disk based on a fresh 3.1 install that has CD0 mounted... .yes?  Then I can go into HDtoolbox and change the bootable thing, yes?

[dschallock]

Yes.  You mean you don't have like 20 ERD's made, already?  

Just to make sure before you do that, you do have a working 3.1 Install disk with a copy of HDToolbox on  it, right?  (this is so you'll be able to change it back, if the other process doesn't work)

Yes, I have my original 3.1 disks in the original 3.1 box I bought from an actual Amiga store in the 90s!  I have been putting those disks through a work out this week.  I have probably reinstalled 3.1 at least 12 times this week. :roflmao:

The Amiga store was Applied Computer Systems in Sacramento for history sake.  I think the owners name was Jim if I remember correctly.

[dschallock]

Man, now you've got me making ERD's, just for the hell of it.  Just made one on my A500, worked fine.  Good practice, I guess.  Maybe I should mail you one, haha.  :p

Hahahaha... :lol: I'm putting you on the pay roll till I get this solved.  I promise to pay this forward to the community all jokes aside though.

[dschallock]

I was just thinking... (dangerous I know). I think I have an adapter (its an adapter that goes from internal scsi 50 pin ribbon to external 25 scsi plug like my cdrom uses) that would allow me to get my external cd rom on the warpengine chain.  Do you think I should do that if possible, or should I not add another variable at this point?