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

[Sandman]

Whether I try to install 3.9 directly to my A3000-040 or install thru Winuae and then transfer via CF card to the A3000, it never seems to render a working install.

When I install thru Winuae, it works great on the PC side but when I transfer the contents of the working installation to the CF card and try to boot the A3000 with it - Problems galore.  I have tried following every online guide and follow their instructions exactly but the problem persist.  The only way that I have even gotten close to a good install was the manually copy libs, etc. from the OS3.9 cd to the cf boot partition but even then it seems broken.

What do you guys find that you manually have to copy to your boot partition to get this thing to turn over.

WB3.1 is a breeze but for a novice like me os3.9 makes Windows 3.1 look like a walk in the park!  

I will post more details after another install attempt on this end....

[Sandman]

Well, sorry for not getting back sooner with my results but real life gets in the way sometimes.

Anyways, I have spent numerous hours on this and still haven't made any progress.  I am not sure if it is a sporadic hardware issue or what but I just can't get OS3.9 installed.  I am literally ready to pitch my Amiga gear onto the trash-heap of time.

I set up 3.9 in WinUAE and it works flawlessly on a CF card.  I move it to the real amiga and it won't boot up.  It just loads up to a black screen and sits there.

So, I figured that I would follow Cammy's advise and do a .lha archive on WinUAE and then transfer the good OS3.9 install to my A3000 that way.  I create the .lha archive fine on uae with no problem.  I then transfer the CF card to my A3000 and everytime I try to unarchive the backup.lha it fails with a 'Failed CRC Check' at a different spot everytime.

So.... Back to installing OS3.0 of off the CDROM the old way.

* I install 3.1 onto the boot drive of the A3000...... no problem.
* Move CD0: to Devs, double-click it and my CDROM shows up fine.
* Reboot, CD0: causes a suspend message and locks up workbench.
* Reboot with bootdisk, move CD0: out of Devs, reboot 3.1 install fine.
* manual mount CD0: again, to access OS3.9 CD, fine.
* Proceed to make Emergency-Disk, install fails with c/installer crash.
* Reboot, CDROM drive not recognized.
* Reboot, CDROM shows up, try to make Emergency-Disk again, installer abruptly quits back to workbench about half-way thru making e-disk.
*Boot E-disk, flashes something about iprefs:bad loadfile hunk but gets to workbench
*WB3.1 install on internal SCSI HD now showing checksum errors.
*Start OS3.9 installer from CDROM, Installer crashes with c/installer program failed.
* Reboot E-disk, now it crashes with a datatypes error.
etc.

Memories come flooding back why I dumped the Amiga for PC back in 1992!

Ready to give up.......

[Sandman]

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.

I did finally get the CDROM to cooperate more by installing AsimCDFS, but now when I go to make an Emergency-Disk it gets farther but  crashes with.

Sorry... an Error Has Occured
Unable to perform operation -- not enough memory in line 2568.

Reboot, try again.  Copy correct installer from c: on OS3.9 cd to c: of boot drive.  Start OS3.9 e-disk installation and it crashes because of c/installer.

Could there be a problem on my SCSI chain causing data corruption?

Stupid computer.....

[Sandman]

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!

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

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