OS 3.9 installation issues

[dschallock]

First, thank you for helping me with this.
OldsmobileMike has already been helping me a ton with some private messages with advice, but I don't want to abuse his time either!

My System:
A3000 Super Buster 11.  GAL chips recently replaced fixed garbled graphics.
Battery has been replaced with coin cell upgrade.
3.1 Roms
OS 3.1 Installed
Warpengine 3040 with 32 megs of Ram installed.
2 megs of chip.  No zip ram on motherboard.
750 Meg Scsi hard drive attached to Warpdrive.device (the warpengine fast scsi II).
External Lacie CDROM Scsi attached externally to scsi.device (a3000 onboard scsi).
Currently I don't own a working internal floppy drive so I have an external Amiga floppy drive plugged into the external floppy port (DF2 on my system.  works good)
PicassoIV graphics card.
AD516 Sound card
Personal Animation Recorder with IDE hard drive attached.

The Goal:  3.9 installation with all the boing bags successfully installed!

The Method: I was planning on following OldsmobileMike's awesome videos on doing this install but I have already run into some hickups.

What I did:
1) I inserted the 3.9 CD and first thing attempted to make a emergency install disk.  Program returned successful creation message.
2) I try to boot with the emergency disk and I get a crash saying something about "setpatch" and string of numbers 00012020021 or something.
3) I make a backup of my entire Workbench partition to a folder on my Work partition.
4) I boot from the install disk of 3.1 and format the workbench partition.
5) I do a fresh install of of 3.1
6) I mount 3.1's CD0 with my appropriate scsi drive and unit number.
7) I insert the 3.9 install disk and run the installation "upgrade from 3.1 or blank partition".  When it finishes, I install the internet software from the CD as well.
I reboot and insert a CD I have burned from my PC with the latest Picasso96 software as well as the Boingbag1, boingbag2, and boingbag3/4 combo.  First thing I notice is that the files names on the CD are all truncated to names like boing~1.  I was hoping the 3.9 install was going to fix this filename shortening issue but apparently not.
*** I also notice at this reboot that Amidock is crashing on reboot and not loading, but I click suspend instead of reboot and I can still access the system***
9) I attempt to unarc the picasso drivers and I get errors for some of the files as corrupt. If I click past the error messages most of it decompresses fine but some of it definitely had a problem.
10) worried about this corruption above, I opt to use my original picasso96 install disk and install the software so I can run a larger RTG screen mode.  The software seems to install fine and I am on a larger screen mode.  Amidock is still crashing.
11) I attempt to unarc the first boingbag 1 archive which of course is listed as boing~1 or something shortened like that.  I run into the same issue getting system messages of some of the files being corrupted.  Pressing "ok" through the process what I am left with is enough to launch the boingbag1 installer but it asks me for the 3.9 cd to be inserted and as soon as I insert it the installer crashes and says there is something wrong with my install files (I'm sure its the corrupted files).

So, now I am not sure what to do.  I can't install 3.9 on a freshly formatted partition because the disk fails to make an emergency install disk crashing on setpatch.  Installing over a fresh 3.1 doesn't seem to be a good option either as I have amidock crashing right out the gate.  My CD Rom has been working flawlessly in the past when installing Amiga software (like photogenics for instance... I installed that last week and got no errors), but CD's that I burn on the PC with amiga files I need seem to all get their names messed up and files seem to be corrupted on all the archives I burn.  Not sure if this is related to the filename issue, or something else entirely.   I apologize for typing so much but I wanted to give as much information as possible.

Thank you again for any help you can offer to help me get through this OS upgrade.
-Dan

[dschallock]

Thomas, Thanks for the tip on the warp engine 68040 library, I will definitely check that.

In terms of the Hard disk install Vs. CD.  I never tried to boot from the CD and had that fail.  I tried to create an emergency boot floppy and that failed.  I didn't assume that meant that entire OS3.9 install CD was flawed, should I have?

[dschallock]

Thanks for the great reply Mechy.  Couple of questions to your comments.

make sure the max transfer setting on the 3000 is set properly for the hd partitions.If its wrong larger archives may get corrupted when copied to the 3000.

Is the max transfer a value determined by the CDROM drive itself?  Once I know that value do I add that to the CD0 Tooltype?  I think it currently has ACTIVATE=1 DEVICE=SCSI.DEVICE UNIT=1

Scsi termination and term power must be working/correct or you will have endless problems. Also double check warp engine jumpers.

So I am working with 2 scsi controllers.  The WARPDRIVE.DEVICE which has 1 hard drive attached, which is partitioned into WORK and WORKBENCH, and SCSI.DEVICE which is the CDROM attached externally.  That CDROM has its own power supply, and scsi terminator attached.  I assume that's all I need and all should be good..... I assume.

to stop amidock from crashing, just remove it from wbstartup for now.

Ok, will do.

are you using a legit os3.9 cd or some junk you found on the net?
note that the initial install may be a tad flakey until at least boing bag 1 is installed, this is a known thing.

Absolutely.  I have real OS 31 disks, and 100% real OS 3.9 disk.

I was re-reading through my own process and one thing I think I should try again is to get a fresh solid 3.1 installation with the correct 040 library and the latest picasso96 software and then try to make my emergency disk from that.

2 unknown issues that are still freaking me out is:
1) Why was my emergency boot disk crashing because of SETPATCH?  What is the setpatch thing even about, I never understood it, I don't know what could be going wrong or how to fix that.
2) Why am I getting corrupted files off my CD?

[dschallock]

UPDATE.

After watching all of Oldsmobilemike's videos on the install (thanks for making those by the way... super helpful), I restarted the process.  I hit a snag again, but it happened at a very specific moment and so I thought I would post it as an update.

1) I reformatted partition workbench
2) I reinstalled os 3.1
3) I installed picasso96 and warpengine 68040 library. Got the screen resolution set correctly.
4) mounted CD0 correctly.
5) created the emergency boot disk from 3.9 CD and it worked!  It boots.  Everything great so far!
6) I reboot via the emergency disk. (no problems still).
7) I format partition workbench again so I could install 3.9 on a totally blank partition.
I reboot via the emergency disk as before and this time BOOM crash SETPATCH.

So something happened right there at that step that threw something off kilter.  Any ideas?

Thanks!

[dschallock]

When I stopped using os 3.1's CD0 and installed the 3.9 CDROM software the CD started showing full file names which is great, but I can't seem to be able to properly extract any of the boingbags.  Each one says the file "AmigaOS-Update" is corrupt and fails CRC check or something like that.

Thanks for the screen shots Mike, I am going to try using Nero and burning boing bag 1 already decompressed and see if it can read it that way.

Mechy, Yea I am using the warpengine 68040 library on the emergency boot disk.

oh.... so I tried 3 times to recreate the working emergency boot disk and I never got it to work again even though I followed the same steps.  No matter what it always crashes on bootup on the Setpatch.  I ended up just installing 3.9 over the fairly fresh 3.1 which worked mostly fine.  I had to move amidock out of wbstartup cause it didn't like that.  I want to try installing the boingbags now but I can't get a non-corrupted version off the CD.  I'm gonna have to break down and buy a xsurf just to get this install going.

[dschallock]

Ok, so I switched to using nero on the pc to burn the CD and it solved the corrupt file problem.
I was able to decompress boingbag1 with no corrupt errors.
Now the problem is I start to run the update and I get XAD password errors.  Unable to depack XAD missing password.
Any idea whats up with that?

[dschallock]

I can't find the xadmaster key file anywhere on the OS 3.9 CD nor can I find it on my system. hmmmmm.....

[dschallock]

Try this one.  Second link from the top.  Freely released by the author.  It might not be "the" problem but it's certainly "a" problem.

http://www.vht-dk.dk/amiga/diverse/unsorted.htm

Thanks Mike, I downloaded it.  I will try it when I get home from work today. Around 4pm California time.

If that doesn't work I can send you a copy of mine in the morning.  Go to sleep.  :p

Dude, you are so right, and I finally did go to sleep :insane:.  Pounding my head against against my miggie till 2 in the morning and then having to be up at 5am for work. :rofl: hahaha... took me back to the 90's when I would work on my Amiga all night.   Man, I never remember having so much trouble installing a version of Amiga OS though. I think I'm getting close.  I wish I knew what was causing the setpatch error early on.  My gut feeling is that setpatch thing is a root of some problem.

I could be mistaken, but I seem to remember reading that the WarpEngine  is incompatible with the standard SCSI chip on the A3000, but will work  with a .08 version SCSI chip.

Thanks for the feedback.  I used to have issues using the standard scsi.device along side the warpengine.device but I thought those problems went away when I upgraded the superbuster chip.  In any case, I don't think I'm getting any device errors from the 2 scsi controllers now.  I was getting corrupted files from the CD, but I switched burning software on the pc and the corrupted files went away... so makes me believe the controllers are working ok on the Amiga.

[dschallock]

OldsmobileMike, looks like the Xad keyfile didn't do the trick.  Same errors saying I'm missing the password or key.  Not sure if you have one I could try?

I'm still unable to make an emergency boot disk that I can actually boot from.  It always crashes on the setpatch.  I tried replacing the setpatch file and the 68040 file on the emergency floppy disk to see if that would help, but alas... nothing.

I'm starting to wonder if I will ever get a stable 3. install.

Thanks for the help all.

[dschallock]

What version of SetPatch? Did you see note above about trying different versions 44.13, 44.16, and 44.38?

Could you post a screenshot of the exact xad message you're getting?

Yeah, when I get home today I am going to start over and this time I am going to stop at the first problem and post the screen shot and not move on until that problem is solved.

I downloaded a setpatch from the web yesterday along with what I believe to be the latest 68040 library, plus the latest picasso96 software.  All of it was giving me problems last night. :eek:. The frustrating thing is that the problems don't seem to be consistent either.  One time I did a fresh install of 3.1 over a freshly formatted workbench partition and then I installed the original floppy disk version of picasso96 and the original warpengine 68040 library and immediately made an emergency boot disk at that point.  And it worked (meaning it booted without a setpatch error).  But I have never been able to recreate that sequence again.  I always get a setpatch error ever since.  The one time it did work, I reformatted the workbench partition so I could do the 3.9 install on a fresh reformat and anyway after the format when I tried to double click on the install icon for 3.9 it asked me to re-insert the workbench drive. :madashell:.  
I remember when I bought 3.9 when it first came out, I remember installing it as an update over my working 3.1 system and I don't remember things not working.  I remember even amidock working out the gate.  Now I do as clean an install as I can (over a fresh 3.1 install since I can't get a boot disk to work) and amidock is crashing right off the bat.  Half the time I try to relaunch the 3.9 installer so I can install in the internet software too (Cause I watched your video and I know I need it so the boingbag updates can update it) and anway, half the time it gives me an "c/installer" crash.  It's all pretty frustrating, and it probably doesn't help anything that I am still shaking the rust off my Amiga savvy-ness.
** I am super grateful to everyone here is helping me through this though!  I think it would be too daunting to do this alone. **
I'll restart this afternoon after work, and I'll post exactly the first step.  Versions I am using, and I'll include a screen shot of what is going on.

[dschallock]

OK... LETS DO THIS!
I reformatted Workbench.

I am now in installing 3.1

When that completes should I install the original picasso96 software and copy the 68040.library from the original warpengine disk before attempting to make a emergency boot disc?

I know we want to know setpatch version and to do the boot with no startup sequence and type setpatch and see what happens, so I will do that too and I will be specific!

[dschallock]

ok, we have a fresh 3.1 install

Here are the current versions installed presently.

Kickstart 40.68
workbench 40.42
setpatch 40.16
68040.library 37.30

I checked on the original warpengine floppy and the 68040.library is also version 37.30 so there is no point in copying since it appears the 3.1 install already has that version.

I mounted CD0 and from the shell checked some versions on the 3.9 install disc in CD0:EMERGENCY-BOOT/
setpatch 44.17
and apparently there is no 68040.library, at least not in the EMERGENCY-BOOT/LIBS/ folder.

So where should I go from here?  Should I install the picasso96 software? Or should I go right to trying to create an emergency boot disc?

[dschallock]

ok, so I'll insert the 3.9 and attempt to make an emergency boot disk.
Here we go.

[dschallock]

I remember having similar problems years ago, where certain files was copied directly from the harddisk instead of the CD when creating the Emergency Disk. It might be possible that 3.1 SetPatch gets copied to the disk.

Once the emergency disk is created I should be able to check the version of the setpatch on the floppy version the version on the os 3.9 cd.  I assume it should be the newer 44.17 version I want the emergency disk, yes?

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