#corel scsi/WORM/AIC6360
6 messages in this thread
Hi,
i have a severe problem with my RF5010 WORM drive and an adaptec AIC 6360
SCSI controller. The controller is installed ON-Board in my docking station for
my 486dx notebook.
Now my problem: I have an internal seagate scsi disk in the docking station and
an external WORM drive (940mb). The notebook is equiped with an 250 MB AT-Bus
HD.
The adaptec controller detects the scsi-hd and the WORM drive and reports that
there are no errors when booting up. I use version 3.22 of adaptec 1520/22 and
AIC 6360 aspi driver and corel scsi 1.2.
There are no problems accessing the internal scsi hd. All works fine.
If i try to access the WORM drive (e.g. format a new cartridge), i receive the
following error:
THE DRIVE REPORTS HARDWARE ERROR.
If i run DVRSTAT i get:
Last error: check conditions 0x305
driver reports: Hardware error, error (0x04)
sense code (0x09)
no module is mounted.
The module is inserted, definitly. The WORM drive is ok. it works fine with an
1542 adaptec. The terminators are on internal scsi disk and on external WORM.
There are no one on the internal on board controller card.
Please help
best regards
P. Heimbuch
This may be too basic and, if so, apologies, but check that the ID number
does not conflict with any others on the chain and also check terminations. I
have a 7010 rather than a 5010 but I know that either by jumpers or switches
they all have a termination on/off, a terminator power on/off, and a parity
on/off. Mine is not at the end of the chain yet it wanted term power on and
parity on with terminator off. You might just have to experiment with these
settings. If you can get a read/format, you can get a setting.
Also, did you patch the notebook to read/write 1024 byte sectors with
PATCH.EXE? Often this causes all sorts of problems. I just had to repatch when
changing from DOS6 to 6.2….
Hi Jack,
many thanks for your fast reply. I was this weekend on vacation and so i am
answering now not earlier.
I already patched my dos, german version 6.0
I think if there is a problem with the termination the internal hard disk will
also not work. but it does. only the external worm won't run.
Any other ideas?
best regards peter
It definitely sounds like a termination problem. The usual applies–only
the first and last device in a SCSI chain should be terminated (and, remember,
the card is a device so it, too, has terminators) and all the ID numbers should
be unique. Bootable hard disks are always ID0; a second hard disk should be 1.
The card is almost always 7 but not always, so you might check and make sure
that some other device isn't set to the card ID.
Beyond these, the next suspect is cabling, which can cause real problems
if it's not well shielded.
Peter,
With the 1520/22 chip set the card defaults to syncronous communication. This
may hinder the capability of the controller to talk to the drive. On the ASPI
line in the config.sys add a /U-. This disables host initiated synchronous
communication.
Now, for the error message. It is hard to ignore something like that! <grin>
Now, you'll have to take my word on this as improbable as it may seem, but we
have been writing drivers for this drive for about 3-5 years.
04 is a hardware error. The 09 is a 'Tracking Servo Spindle Failure'. What
this means is that the drive's servo (motor) that moves the read head back and
forth across the surface of the cartridge is unable to 'track' the media. The
problem is probably dust !!!! Unlikey as it may seem. If the cartride or
drive lens is dusty the mechanism that tracks can't find the marks on the
surface of the cartridge. Clean the cartridge and drive lens and all will be
well. If that doesn't solve and the /U- doesn't solve it, then the SERVO
MECHANISM may be bad after all. (I've never seen this though in all the calls
that I have handled on this error message)
I hope this helps…
Laszlo
Hi Bryan
many thinks for the hints. I will try to clean the lense (i rub it with my
fingers, oK 🙂 ?)
I will inform you if i have any success.
Greetings
Peter