OS 3.9 installation issues

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

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

[dschallock]

@dschallock
SACC had a replacement floppy drive waiting for you at our last meeting...as discussed and as requested...sigh

BTW, our next meeting is this sunday 27th at 3pm (but some of us are meeting at 1pm)

Hi Sacc-guy, thank for writing, and for having a drive I could try at the last meeting.  I'm sorry I wasn't able to attend that meeting.  I will try to attend this Sunday.  Thanks again for your support!

[dschallock]

Oh heck, just bring your mess of stuff there, I'm sure they'll be able to get you sorted in no-time.  Sometimes 15 minutes hands-on is way better than 3 days back-and-forth on the forums.  :roflmao:

Actually Mike this has been a great learning experience for me.  Sometimes the hard way is a great way to learn a lot and I super appreciate your help!

[dschallock]

(2) disable the existing partitions or lower their priority to force the system to boot straight off DF2: with an ERD disk in the drive

I think I see OP's future, and it involves burning a few more ERD disks, just to make sure to get a good one.  
[/QUOTE]

I made 2 ERD disks.  I made sure both have the 68040.library from the original warpdrive disk.  I went into HDToolbox and made workbench not bootable.  Both ERD disks are still crashing on startup citing the "setpatch" error.
Not sure what to try next.

[dschallock]

I'd look into these suggestions first.

Hi Paul, I am very grateful for your feedback.  I read through the whole thread you indicated and it seems the original member who was having the problem on that thread turned out his whole problem was bad ram sims.  I suppose I shouldn't rule that out completely, but I have never had any other issues  that would lead me to believe I have bad ram sims.

[dschallock]

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

Thomas, Thanks for your input too.  I'm not sure where to get a proper Rom-updates file.  The 3.9 disk doesn't have a non corrupt version when creating a Emergency boot disk?

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

Mike, I just wanted to report back on this request.  I think I must be typing it wrong because I get a error. here is a screenshot.



Although just to recap.  When I boot with no startup sequence all the setpatch versions work.  The stock 3.1 one, the one on my 3.9 disk (44.17) and also the version you uploaded for me (44.38). They all work if I boot with no startup sequence.  The whole checksum error thing was real, but that seems to be solved with the new floppy disk.  The setpatch crashes I get now are any version on a floppy disk that I boot from. (and I have confirmed that I am booting from the floppy by disabling the workbench partition).
Ideas?

[dschallock]

On the bright side, there's a copy of "AmigaOS ROM Update" inside BoingBag2.  So even if your CD is scratched or degraded, you could get it from there as an alternate source.  The downside is to extract that file from the BoingBag archive you need your Xad decompressors working.  And that's a whole other can of worms for you already.  It's a catch-22 at this point.  You need that file, but no way of getting it from either your CD or your BoingBags.  

I'm assuming the xad thing is like a lha decompressor but with security measures built in?  And I assuming me having my xad working is necessary because it confirms I actually have my purchased 3.9 cd in the drive at the time of unarchiving said boingbag?

[dschallock]

Actually, edit the Startup-Sequence on the ERD and add those two items, if they aren't already in the line.

C:Ed text editor should be on there?  Of course now I'm home and left all my disks at the office, ugh!  

Add this:

 setpatch SKIPROMUPDATES console.device,scsi.device REVERSE NOREBOOT

To the startup-sequence on the ERD? ok, I can do that.

[dschallock]

in the startup-sequence on the ERD there is list of if statements.  The last one says something like:
IF $scsiupdate EQ 1
   setpatch QUIET

Are you saying I would modify this line to
IF $scsiupdate EQ 1
   setpatch SKIPROMUPDATES console.device,scsi.device REVERSE NOREBOOT

Or am I placing this line somewhere else in the startup-sequence?

[dschallock]

Okay, if that's what it says (I left all my disks at the office), try:

setpatch SKIPROMUPDATES console.device,scsi.device QUIET

That worked.  It booted from the ERD.  What does this mean, and should I proceed with a 3.9 install from here?

[dschallock]

Vacaville..to Washington DC..to Sacramento

How many amigas does it take to install an OS???

The boingbag1 and 2 do correct somethings but still need a booting 3.9 with a working cd reader.
I can't remember...is the cd connected to the 3000 scsi.device or the warpscsi.device?

the CD is connected the scsi.device and it is working. The external floppy drive is also working (I believe).  The culprit I was having before is the fact that all my floppies are old and unreliable media at this point although I think I found a good one I working from now.

[dschallock]

It means exactly what it sounds like.  That big "AmigaOS ROM Update" file in DEVS: contains updates to many of the files that are in your actual, physical ROM.  Device drivers, handlers, libraries, stuff like that.  By Default it tries to use the versions in the file on disk instead of the ones in your (older) ROM.  SKIPROMUPDATES is telling it to use the versions in the ROM rather than the newer versions on the disk.

And, yes!  What the heck, at this point.  Proceed!  Although keep in mind you may need to edit any startup-sequences it creates (S-S is updated with each BoingBag update, also), to keep adding those two commands.  

But did I understand you correctly before that perhaps the Rom update in boingbag2 might be a fix that I won't need to SKIP?

[dschallock]

At this point you've booted off the ERD with the 3.9 CD in the drive and gotten the "Boing ball" background screen and whatnot, correct?  Here's where you'd prep a partition with HDToolbox, if you haven't already, and start the install.  Go go go!  

3.9 has been installed successfully, along with the internet software and the cdrom software.

I am loading up the cd with the boingbags now....

[dschallock]

I'm backing up the workbench partition before installing anything else so I have a good save point in this game.