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

[mechy]

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

No offense but why do you blame the machine for your problems when you dont even know if the scsi is setup right. Stupid human

are you using a bootleg os3.9 cd burned from a pc? it may have corrupted all the files/icon info?

Seriously Though, if you don't take the time to learn a bit about your stuff you will cause yourself nothing but trouble. I kind of wonder if the amiga didn't dump you back then LOL

First set your scsi chain right. If this is wrong it probably will never work reliably.

I have made a emergency disk with asim before and it never works right.the emergency disk doesn't copy all the asim stuff because asim does a screwball install putting stuff in silly places. this MAY be your trouble. It could also be max transfer issues.

Getting a scsi cdrom working on a A3000 is easy with os3.1 and 3.1 roms.. you simply copy CD0 from storage/dos drivers to devs/dos drivers then edit the cd0 icon info for UNIT number and DEVICE where your cdrom is,then save it. reboot and it should see the cdrom.
i have been doing this for a 15+ years now and it works everytime. after you do that you can install the better os3.9 cd filesystem.

Mech

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

This may be a clue as to some problem. It does sound like you may either have a ram problem,the scsi chain is not terminated properly or some chip somewhere is making bad contact on a pin or somewhere.

What does the scsi chain look like? i.e. what devices are terminated and what is not terminated. are there termination resistors on the motherboard?

As for using the os3.1 cd filesystem, its not the greatest,but it should allow you to read a cd like os3.9. I have worked on about 60+ A3000's over 20 years the owners claimed it would not work and made this work every single time barring a bad cd drive or bad cables which i fixed regardless of the scsi chip. Don't give up, you will get there.

[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