OS 3.9 installation issues

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

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

[Oldsmobile_Mike]

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

Can you adjust your boot priorities of any other devices (hard drive partitions, etc.) to be lower, so you don't have to do this?

*SetPatch does make changes to the Early Startup Control screen that if you're having to go back into it each time, might be throwing something off...

*I vaguely seem to recall someone having a problem a long time ago where it would start to boot off the floppy, then incorrectly pull some of the files of the hard disk instead

*I wonder if they even considered the possibility that someone might try to install 3.9 off an external DF2:?  I'll have to skim one of my ERD's later to see if there's anything off-hand that might have an issue with this...

TL;DR.  I wonder if you shouldn't focus on getting all your hardware issues resolved before starting on software stuff?  AFAIK I think you can still buy new internal floppy drives from AmigaKit; they won't match your faceplate but they'd work in a pinch.  

[Oldsmobile_Mike]

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.

Okay, you know you're not supposed to do that, right?  

You need to reboot - boot off the ERD floppy disk.  I'd get all your 3.1 partitions off there, clean slate.  Or make them a lower boot priority so the system automatically goes to the floppy drive first.

[Oldsmobile_Mike]

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?

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

[Oldsmobile_Mike]

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?

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)

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

[Oldsmobile_Mike]

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

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

[Oldsmobile_Mike]

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?

I would try to eliminate as many variables as possible.  At one point was even thinking to suggest just getting that WarpEngine out of there and using the A3000's built-in 68030 and SCSI.  

*Although* having all the devices on the same chain probably wouldn't hurt. Does your WarpEngine use scsi.device?  Or something else?  (i.e., my GVP uses gvpscsi.device that's on a ROM on the board)

Edit:  This page lists an optional external SCSI connector.  Is that what you have?

[dschallock]

I would try to eliminate as many variables as possible.  At one point was even thinking to suggest just getting that WarpEngine out of there and using the A3000's built-in 68030 and SCSI.  

*Although* having all the devices on the same chain probably wouldn't hurt. Does your WarpEngine use scsi.device?  Or something else?  (i.e., my GVP uses gvpscsi.device that's on a ROM on the board)

Edit:  This page lists an optional external SCSI connector.  Is that what you have?

Warpengine uses warpdrive.device.  My Hardrive is connected to it.
I don't have the official Macrosystems adpater, at least I don't think so.  I have an adapter Software hut sold me in the 90s along with an external drive case.  I used to run all the hard drives and cdrom and zip drive in an external mini tower.  Then the cdrom died.  I tried to move the whole system into a mirage elbox mediator tower and that whole set up never worked well, so I eventually put my amiga back together in the original case.  said to heck with the mediator angle and now I am working towards a xsurf set up.  I only recently purchased the external scsi cdrom drive I am using now. I think I will take pictures of everything this afternoon and post those too just so there is a clear picture of the set up.