zrh@amdahl.uts.amdahl.com (Zealand R. Hatch) (11/24/88)
I have a StarBoard II with 2Meg installed. I've recently added a StarDrive
module and connected it to a Seagate ST-138N SCSI drive. For two days it
work with DOS 1.3 and FFS. Until I tried to show it off to a friend.
With someone watching it claimed the drive was not a DOS disk. It's
been down hill since then.
The drive now regularly gets DMA Transfer timeouts, SCSI sense codes
3 or 4. Does not want to lowlevel format or DOS format. I've tried the
drive on another computer, it works fine. I've even talked my dealer
in to giving me another StarDrive module, same problems.
Does anyone have any clues?
Thanks,
Zealand
--
----
Zealand Hatch - 408 746-8720 - {where_ever}!amdahl!zrh
Amdahl Corporation -or- zrh@amdahl.amdahl.com
[ The opinions expressed are mine and do not reflect the opinions or
policies of Amdahl Corp. ]GregM@cup.portal.com (Greg Scott Miller) (11/25/88)
I have a suggestion .. Check out your SCSI cable. I had a bad connection in my 50 pin ribbon cable between my hard drive controller and the StarDrive interface that only failed under rare conditions. Drove me NUTS looking for it. I had a HECKUVA time with that StarDrive interface. I originally tried to use it with an Adaptec 4000 controller, and had no luck. Chatting with the Microbotics folks revealed that they had a bit of a problem with the driver software, and they'd fix it, and ship me out an updated driver .. It took them over 4 months to do that, and when I got the new driver, it didn't help me a bit. The author of the driver wrote it using the extended command set of SCSI, that the Adaptec 4000 didn't offer. (The 4000A did offer them, but I didn't OWN a 4000A ..) Suffice to say I got tired of the entire thing and wrote my own driver for it. Has worked great ever since. - Greg GregM@cup.portal.com