OS 3.9 installation issues

[dschallock]

Gah, I'm confused again.  So are you installing a fresh 3.9?  Or 3.9 on top of 3.1?

I did do a fresh install, it wasn't over 3.1... however the emergency disk I created was made on a fresh 3.1 install which meant the CD driver was the 3.1 CD0 driver in Devs/dosdrivers/.  That was necessary just to get the system to boot and recognize the CD to be able to install 3.9.  But the 3.1 CDROM driver has problems not the least of which is the truncated file names, so I installed the CDROM software from the 3.9 install which is improved. Does that make sense or am I explaining it wonky?

Also, from your screenshot, "BufMemType = 513".  I wish Thomas was here, but as far as I know there's only supposed to be a single digit there, 0 through 5:

Buffer Type: 0,1=Any, 2,3=Chip, 4,5=Fast RAM

Try changing that field to a 1 and see what happens.

Next try changing your MaxTransfer to 0x1fe00.

Try increasing the number of buffers from 50 to say, 200.

Make these changes one-at-a-time, and note if anything changes.  

Awesome tips, Thank you.  I will try these one at a time.  I guess the test after each change is to try and install boingbag1.

[dschallock]

Yes, but you need a little Hardware-Hack to get it working in the A3000 !

It is incompatible with the A3000's motherboard SCSI controller - replacing the A3000's SCSI chip to rev. 08 solves the problem.

And the device is called warpdrive.device

Hi Rotzloeffel, Thanks for the feedback.  I understand what your saying and yes I know its warpdrive.device (I was being lazy and typing short hand).  What I meant by attaching the cd to the warp chain was to plug it in to the end of the scsi chain I already have coming off the warpdrive.device now.  And I know that does work as I used to have a cdrom attached to it.  I am only using the amiga 3000 scsi.device for it now is because it is a an external drive with the 25 pin external plug and it was just easier for me to plug it directly into the back of the A3000 rather than hacking a port for the internal warp ribbon to end in an external 25 pin plug.

[dschallock]

Gah, I'm confused again.  So are you installing a fresh 3.9?  Or 3.9 on top of 3.1?

Also, from your screenshot, "BufMemType = 513".  I wish Thomas was here, but as far as I know there's only supposed to be a single digit there, 0 through 5:

Buffer Type: 0,1=Any, 2,3=Chip, 4,5=Fast RAM

Try changing that field to a 1 and see what happens.

Next try changing your MaxTransfer to 0x1fe00.

Try increasing the number of buffers from 50 to say, 200.

Make these changes one-at-a-time, and note if anything changes.  

Well I tried these. Nothing stopped working but it did fix anything either.  What program do you to burn Amiga stuff to disk?  Also what cd rom software are you using on your Amiga?

[Oldsmobile_Mike]

Well I tried these. Nothing stopped working but it did fix anything either.  What program do you to burn Amiga stuff to disk?  Also what cd rom software are you using on your Amiga?

Well, crud.  Gotta get that CD drive onto your WarpEngine SCSI chain and see if that makes any difference.  

I use Nero "Multimedia Suite" 10, Nero 12, and even the Windows built-in CD burning software, all have written discs just fine and read them back on my Amiga.  On the Amiga-side, I use the standard CD0: setup that comes with 3.9.  Literally the only thing I have to change is from scsi.device to gvpscsi.device, and the device # to match the # on my chain.

I've used MakeCD (on the Amiga) in the past to burn CD's that I can read back on my PC, but that is some of the most un-user-friendly software I've ever seen.  Like Windows 8, you might call it outright user-hostile.  

You don't happen to have a different CD drive you can try, do you?

[dschallock]

Just an update.  I moved the CDRom from the scsi.device to the warpdrive.device.  Unfortunately it didn't allow me install the boingbags successfully (same errors as before), however it did seem to alleviate some of the read errors I was getting on the CD when extracting archives off CDs.  It's a long shot, but I am hoping that maybe my 3.9 is a a flawed install even though it seems to be working fine, and that if I reinstalled from the CD now connected to the warpdrive it would solve my problems.  Like I said, a long shot, but I am running out of ideas.

[dschallock]

UPDATE 10-7-15

I obtained another copy of the 3.9 disk. (I assure you I own a real pink copy by the way).  I wanted to rule out something amiss with my copy.  I also now have the cdrom drive connected to the warpdrive.device instead of the 3000's scsi.device.

I have had complete success through boingbag2.
Here was my procedure.
1) format workbench -clean slate
2) install 3.1 fresh and mount CD0 to get access to the CDdrive.
3) insert new copy of 3.9 disk and create EBD (emergency boot disk)
4) reboot from boot disk
5) re-format workbench -clean slate
6) install 3.9
7) install 3.9 internet software
install 3.9 cdrom driver (to replace the 3.1 driver in DEVS)
9) reboot
10) insert a cd burned on a PC (using windows 10 normal burning) with the boingbag updates (1-4) already decompressed (using winrar).
11) copy boingbag1 folder to RAM:
12) swap CD for new 3.9 disk
13) install boingbag1
14) reboot
15) repeat step #10 through #14 with boingbag2

Everything in the above steps works 100% including using the ROM updates with my warpengine.  No problems, no errors, everything good!
Thanks to everyone for the help and education that got to this point.  I hope this thread helps others get at least this far in in the future should they run into similar problems.

********************

I did attempt (and succeed) moving beyond and installing the boingbag3&4 combo (which by the way does not require the 3.9 disk inserted).  The install seems to work fine however on restart I get messed up colors on my screen and various commodities return errors on startup.  I will continue to try and discern the nature of those problems but I am happy I succeeded through boingbag2 at this point with a stable system.