I can think of one thing. When talking TMSCP, you are using a mapping to
SCSI. The question is which SCSI unit number you are mapped to. Might
not match the unit number set on the DAT. If so, the device you are
trying to talk with through TMSCP might very well be offline, since it
don't exist. :-)
By convention, SCSI tapes usually use unit number 5 or 6 (I think it
is). If you have a TMSCP-SCSI only, it might very well think that TMSCP
unit #0 will match to SCSI unit #0, and not #5.
By the way, are you really sure about the HVD? Since your cabling seems
to work, this is more of an academic question. But many connectors are
actually backwards compatible with SE SCSI.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: b...@softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
If you did that, you probably have toasted at least some of the SCSI bus
drivers/receivers on your drive and/or your controller.
Christian
I don't think so. As I said, now with the HVD adapter I can access the
DAT sending a standard INQUIRY command, and it answers as it should...
I read the inquiry answer string that I could also obtain on a linux
box.