stu@gtisqr.UUCP (Stu Donaldson) (02/07/89)
I bought the StarDrive for my Microbotics, and also bought a Seagate ST-296N
80 Mb drive. The problem I have, is that no matter how I have the mountlist
configured, the best I can get out of it, is that the drive select light
will flash during an access, (format, park, copy, dir, etc...) and the
driver will return with an error code -1. The diagnostic software that
came with the StarDrive consistently fails saying that it was unable to
open StarDrive.Device. The PARK command which came with the StarDrive
will fail the first time with a opendevice failure, (The drive select
light flashes). The third time through the park command is issued, the
drive actually parks.
jdow responded to an earlier plea for help with some suggestions for my
Mountlist, I tried those, and all other examples I could think of.
All I can think of now, is that there is something slightly different
about the SCSI interface to the ST-296N, as opposed to the other Seagate
SCSI drives.
After 5 weeks, Microbotics finally says that they won't be able to do
anything about it until the next re-write of the driver software, which
isn't scheduled for several more months.
Does anyone out there have a SCSI device driver that I could hack to work
with the Microbotics Stardrive? How about a RAMdisk device driver that
could be similarly hacked. Does anyone know of some diagnostic software
for the Microbotics StarDrive which talks directly to the device, bypassing
the driver?
Any suggestions would be much appreciated...
Please respond by email, since our News Disk has been having some problems
lately, and I don't know if I will get a news article.
Thanks in advance.
--
Stu Donaldson UUCP: uw-beaver!uw-nsr!uw-warp!gtisqr!stu
ARPA: uw-nsr!uw-warp!gtisqr!stu@beaver.cs.washington.edu
Bell: (206) 742-9111
PS: use one of the above return addresses, the From field is probably hosed.