Request for help to actually get OS3.9 to install!

[matthey]

Yes, I have 3.1 roms (KS ver. 40.68) and 16mb of ZIP's, and all of the custom chips have been upgraded including the WD-08.

Have the DMAC and Ramsey been upgraded also? Which 040 accelerator do you have? I have had random checksum errors on the SCSI bus with these chips and some accelerators. If I remember correctly, replacing the old DMAC only solved the problem despite the rumor that the new Ramsey and DMAC should be upgraded together. The new Buster and SCSI chip are good upgrades in my experience.

The 68040.library could be the other problem. You could try to remove the 040 accelerator (with needed jumper changes too). I bet the SCSI errors will go away and this will narrow the problem down. I very much doubt that the SCSI maxtransfer or mask are your problems as the 3000 is not picky about them. The 3000 SCSI is usually not picky about termination as long as 1 end of the SCSI bus is terminated (worth checking though). The reversed diodes on the earliest 3000 motherboards can cause problems.

[Boot_WB]

Never mind, missed your post regarding updating all chips including the scsi rev8.

EDIT: Learned to read.

[mechy]

Well, I can tell you for certain on THIS A3000 w/os3.1 and 3.1 rom you do not just simply copy cd0: from storage/dos drivers to devs/dosdrivers and then edit cd0: for UNIT 3 (scsi cdrom id #) and set device for scsi.device because it always crashes on either cold/warm reboot with cd0: in devs/dosdrivers.  This IS with using default 3.1 cd filesystem (no asimcdfs).

I've never had this problem on any of my A4000's but something is screwy with this A3000.  Maybe maxtrans may be an issue but I have tried different values here to no avail.  The problems don't seem to be consistent.  I can try to make an emergency-disk and the first time the installer fails, I reboot changing nothing and next time it gets past the installer and into the install just to guru half-way through preparing the disk..

Even when I can get the emergency-disk to install, I get a different error everytime I go to boot from it.... somethin' ain't right!

Something else just came to me, are you running static column ram with the 040? or have you mixed SC zips and pagemode zips??
Static column will have a part # ending in 402 and page mode 400.
It is a known problem with the old chips that when using a A3640 with the 3000 you MUST have a pagemode zip in the first ram bank. the 3640 doesn't like a static column zip there(it cant use burst).

Also check your 3.9 startup sequence and make sure if setpatch is loaded it has the NOBURST added to the line(again this is assuming you have static column ram).

Mech

[Sandman]

Well, I have made some progress but not in the expected way.

I have never been able to make a proper, working emergency-disk.  I didn't write down exactly all of the problems but I had random issues making the disk but if I did get one made it seemed to be either incomplete or for some reason always failed for one reason or the other.

Maybe the version of the 68040.lib or scsi.device had something to do with it.

I ended up installing 3.9 and BB1 and BB2 thru WinUAE, made a LHA archive of the result using Filemaster3 on my Amiga911.adf thru WinUAE and then used the same when transfering back to my real Amiga 3000.  Result, this time it booted with no crashes or system requesters showing and 'about' showed OS3.9 correctly whereas before even after 3.9 install, 'about' still showed OS3.1.

When I had previously installed OS3.9 thru WinUAE without the BoingBags, the install would never work when transfered to my real A3000 not matter what I tried.

Something in the BoingBags must have fixed the issue.  Sadly, if it wasn't for WinUAE I would have never been able to get this far.....  Very difficult process to say the least... at least for a novice like me.

THANK YOU EVERYONE FOR THE HELP, as you could tell I was beyond frustrated for which I apologize.

[marcfrick2112]

Oh boy, I bet it was the file 'AmigaOS ROM Update', that caused issues, maybe? IIRC, BB1+2 have updated files... That's the system I use, OS 3.9 with BoingBag's 1+2 ...

Under 3.5, on my system, I had to skip the ROM update all together...

[Sandman]

I spent 14 hours, yes 14, troubleshooting this thing last Saturday and this is what I think that I have found.

The A3640 just creates too many problems with my A3000's SCSI.  No matter what I tried with the A3640 attached I had numerous crashes, guru's and glitches and nothing repeated in a consistent manner.  This was with known working, original 3.1 roms and the page mode ZIP. I am unsure why some have success with the A3640 in their 3000 but mine just won't work.  I read that it might have to do with the fact that I have a DMAC -02 and not the much sought after DMAC -04.  

Sooooo......

I switched back to the stock '030 and the static column ZIP's and a basic set up (200mb SCSI hard-drive and Internal SCSI CDROM only) seems to work and OS3.9 sets up fine.  If I try to add and SCSI-IDE adapter to use a IDE-CF card or a LVD SCSI HD (using an adapter), things break again and get flakey..... go figure.

I REALLY wanted to get this sorted out but this looks as if this is the best it can get.

Thanks again for all the help.