OS 3.9 installation issues

[Oldsmobile_Mike]

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!  

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

[Oldsmobile_Mike]

It's a decompressor library that works with many types of compressed file formats.  They secured a license to include it with 3.9, but honestly the only thing I've ever used it with is the 3.9 Unarc program, and the "AmigaOS-Update" files for 3.9. Everybody else just uses LHA.

[SACC-guy]

Okay then...
I went back and read the entire thread because this last entry really lost me.

Maybe if you start (as Mike suggested) by using the Keep it simple idea?
My first question is do you have the red(1st) 3.9 cd or the pink (2nd and corrected) 3.9 cd.
It seems that everything is good from 3.1 (very good) but when you created the ER disk to boot 3.9 the items copied are getting in the way of a correct boot.

Our overall experience says to watch for well known issues. one of the first issues was the mistakes made on the install script on the red cd...
another was that some hardware was not good with the "newer" setpatch
another issue was that the cd driver was imcomplete sometimes...
sometimes the problems are from issues like the "scsi.device" instead of "warpscsi.device"

There's more... so start as simply as possible and keep it simple by keeping track of the changes you created with the hardware and software choices you made.

My fav problem was the asimware cdfs issue (grin)

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

[SACC-guy]

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?

[Oldsmobile_Mike]

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?

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

setpatch SKIPROMUPDATES console.device,scsi.device QUIET

[Oldsmobile_Mike]

A screenshot of the decompressed BB2, for reference:

[Oldsmobile_Mike]

Vacaville..to Washington DC..to Sacramento

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

At this point I could probably install this sucker in 15 minutes if I had it in front of me.  And had a good DF0: floppy drive.  And some known-good floppy disks.  And a known-good 3.9 CD.  :lol:

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

[SACC-guy]

At this point I could probably install this sucker in 15 minutes if I had it in front of me.  And had a good DF0: floppy drive.  And some known-good floppy disks.  And a known-good 3.9 CD.  :lol:

Yes, i see that (really big grin)

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

[Oldsmobile_Mike]

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

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.  

[SACC-guy]

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

@dschallock
Yes, that's idea. IN order to get a complete 3.9 install, it requires booting from the er disk.

Do you have BoingBag 1 and BoingBag 2?

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