Hi,

I have a Tandberg SDLT600 drive and an Adaptec 29160 SCSI card on a
win 2000 platform. I cannot get the SCSI card to recognise the SDLT
drive. The SCSI ID is set correctly on the back of the drive at ID 5
and I am using a self terminating SCSI cable. I can swop the SDLT600
drive for a DAT drive and it is picked up straight away. I have tried
changing machines, cables and cards and I am yet to have the SDLT600
drive recognised. I have however managed to get the drive working on a
solaris box with no problems, simply just plugging into the SCSI
connector.

Has anyone had any issues with this hardware before.

Thanks in advance.

[ Post a follow-up to this message ]

GEvans wrote:
>
> Hi,
>
> I have a Tandberg SDLT600 drive and an Adaptec 29160 SCSI card on a
> win 2000 platform. I cannot get the SCSI card to recognise the SDLT
> drive. The SCSI ID is set correctly on the back of the drive at ID 5
> and I am using a self terminating SCSI cable. I can swop the SDLT600
> drive for a DAT drive and it is picked up straight away. I have tried
> changing machines, cables and cards and I am yet to have the SDLT600
> drive recognised. I have however managed to get the drive working on a
> solaris box with no problems, simply just plugging into the SCSI
> connector.

The 29160 card is a LVD SCSI card.  Is the SDLT drive an LVD/SE drive or
is it Differential or HVD?  It is possible that the drive and controller
on the Solaris box are HVD. What is the exact model number of the SDLT
drive?

--
 ________________________________________
______________________________
Steve Cousins, Ocean Modeling Group    Email: cousins@umit.maine.edu
Marine Sciences, 208 Libby Hall        http://rocky.umeoce.maine.edu
Univ. of Maine, Orono, ME 04469        Phone: (207) 581-4302

[ Post a follow-up to this message ]

There's three possibilities I can think of:
1. The cabling/termination you're using in the Windows machine is
defective. Replace it and make sure you have Termpower.
2. There have been issues with buggy domain validation code in some
29160s. Disable all SCSI features, set the HA to the slowest speed and
see if the drive is recognized. If yes, work your way up from there. If
not, you have a hardware problem.
3. And, just in case, make sure there's no jumpers on the library
connector.

Hope this helps,
Ralf-Peter

[ Post a follow-up to this message ]