A3000 SCSI issues.

[x56h34]

OK, I've got a rev 9/01 A3000D, 3.1Roms, 2MB Chip, 1MB Fast. There was a Hard Drive inside when I bought the system, I think it was the originally included Quantum 50 Meg. No termination on the mobo.

It was installed with OS3.1 and it let me boot to it fine. HD Toolbox reported 5 Quantum drives connected though! Weird.

Anyways, I removed it and installed an IBM 4.5GB SCSI-2 Hard Drive (actively terminated and providing term power) and the machine won't boot anymore from the HD. It just defaults to kickstart disk insert menu. I don't think it's the time-out issue, as the drive spins fast. I reset, and I get the same results. I've heard that A3000 SCSI is very flakey. WD SCSI 08 and Buster 11 are on their way to me, so I'll update them ASAP, however at the moment I am running WD 04, DMAC 2, Ramsey 4, Buster 7.

I've also tried connecting an external CD-ROM (actively terminated) however this doesn't let the system work at all (permanent freeze on boot). I just get a black screen.

All you A3000 experts out there...HELP! :-)

[x56h34]

Thanks for replying guys.

I have an IBM UltrastarXP DFHS S4F, 4.5GB in size. I have real 3.1 Roms for A3000, no software crap. It's the real thing.

I will try everything if I have to from your suggestions guys, and see what happens. Perhaps it could be due to the particular IBM drive, perhaps not. Maybe the soon to arrive rev. 08 SCSI chip will make a difference, who knows.

This IBM drive worked fine with Blizzard 1230-IV SCSI and A4000 w/ CSMKII 060 SCSI, so it's definitely not faulty.

I've emediately replaced the old battery on the mobo with a new one, as I've noticed that time was not being saved correctly, and I feared leakage, so I'll definitely try the SetBatt archive and see if there' some NVRam corruption due to this. Now time works fine (it is being saved correctly after shutdown).

I should also mentione that there is INT2 fix on the mobo.

[x56h34]

@melott:

The WD SCSI chip shipped with A3000 was usually of a lower revision, like 04. The updated 08 version supposedly solves a lot of SCSI problems due to better compatibility with newer type devices in your chain. I've never had a chance to test this theory out, but I will soon. :-)

[x56h34]

@Castellen:

Jusy to let you know that your suggestion about using SetBatt worked! :-)

I've played around with its settings and managed to get the IBM drive to work.

Thanks dude! :-)