hyc@math.lsa.umich.edu (Howard Chu) (02/19/90)
In article <11021@stag.math.lsa.umich.edu> dc@dcpc.UUCP (Don Curtis) writes:
%Original-posting-by: dc@dcpc.UUCP (Don Curtis)
%Original-subject: Conner CP340 specs
%Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti)
% I got the Conner Technical Manual today...here's the official
% word on both drive parameters and jumper settings:
[deleted]
% While the drive DID show up as SCSI 0 with E2-4 OUT, it was VERY
% flakey. It would only boot when it felt like it, and would go
% off-line at odd times for no apparent reason. Also, doing an
% ASSIGN command (NOT info command) showed DH2: thru DH8: as
% existing (with only 1 drive attached to the SCSI bus). Two drives
% on the cable would not work at all...either neither of them showed
% up...or both showed up as the same drive. Yes, they were jumpered
% for different ID numbers.
%
This sounds familiar, but I'm surprised that a mere jumper change fixed the
problem. I'd heard that when the controller on the Conner drive picked up
a query for any device other than its own number, it would park itself. I'd
also heard that the fix required replacing the conner scsi controller.
% Based on the message by Darrin (???) earlier...I reversed the sense
% of the above SELECT settings (that is...changed the "out" to "in"
% and vice versa) and put all jumpers IN. Drive again showed up as
% SCSI ID 0 and this time, ASSIGN only showed DH2: as existing. The
% flakieness was GONE...the drive works perfectly. Adding a 2nd drive
% works fine also.
Thanks for the info. These are really great articles, guys.
--
-- Howard Chu @ University of Michigan