Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*3583\s+LTO\s+library\s+and\s+drives\s+in\s+Windows\s+2000\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*3583\s+LTO\s+library\s+and\s+drives\s+in\s+Windows\s+2000\s*$/: 8 ]

Total 8 documents matching your query.

1. 3583 LTO library and drives in Windows 2000 (score: 1): Author: Dallas Gill <Dallas.Gill AT AVENTIS DOT COM>; Date: Thu, 23 May 2002 17:35:53 -0500; Can anybody out there help, I have a windows 2000 server currently running TSM 4.2(going to be upgraded to 5.1). I have just connected up to it, our 3583 LTO library. I have defined the library and t; /lists/html/ADSM-L/2002-05/msg01047.html (9,764 bytes)
2. Re: 3583 LTO library and drives in Windows 2000 (score: 1): Author: Samiran Das <sdas AT COSMOS.DCMDS.CO DOT IN>; Date: Fri, 24 May 2002 09:35:11 +0530; Gill, I will suggest you to do the following - Your drive definition shows you are using \\.\tape0 device, which means you are using windows driver for tape drive. You should install TSM device drive; /lists/html/ADSM-L/2002-05/msg01055.html (11,214 bytes)
3. Re: 3583 LTO library and drives in Windows 2000 (score: 1): Author: "Kelly J. Lipp" <lipp AT STORSOL DOT COM>; Date: Fri, 24 May 2002 01:35:09 -0700; You probably have the drives and elements switched. Try deleting the drives and redefining switching the element numbers between the two drives. Kelly J. Lipp Storage Solutions Specialists, Inc. PO B; /lists/html/ADSM-L/2002-05/msg01058.html (9,470 bytes)
4. Re: 3583 LTO library and drives in Windows 2000 (score: 1): Author: "Kelly J. Lipp" <lipp AT STORSOL DOT COM>; Date: Fri, 24 May 2002 01:36:23 -0700; I wouldn't do this. Use the native device drivers rather than the tsmscsi driver for these drives. You are probably ok for the driver, but since the elements are switched, TSM is putting the tape in; /lists/html/ADSM-L/2002-05/msg01059.html (9,676 bytes)
5. Re: 3583 LTO library and drives in Windows 2000 (score: 1): Author: "Peter Pijpelink - P.L.C.S. BV Storage Consultants" <tsm AT PLCS DOT NL>; Date: Fri, 24 May 2002 09:51:01 +0200; Better use the tsmscsi for the library and the native LTO drivers, (there is certified driver on the ftp.software.ibm.com choose storage and look for the drivers) Make use you use at least tsm server; /lists/html/ADSM-L/2002-05/msg01060.html (12,834 bytes)
6. Re: 3583 LTO library and drives in Windows 2000 (score: 1): Author: "Kelly J. Lipp" <lipp AT STORSOL DOT COM>; Date: Fri, 24 May 2002 02:55:48 -0700; Also, there is a special Adaptec driver for use with the IBM LTO drives. This is called out in the readme file. Be sure and download this driver from the website. This driver will dramatically improv; /lists/html/ADSM-L/2002-05/msg01062.html (9,696 bytes)
7. Re: 3583 LTO library and drives in Windows 2000 (score: 1): Author: Hunny Kershaw <hunnychka AT US.IBM DOT COM>; Date: Fri, 24 May 2002 11:50:41 -0700; Hello, The TSM device driver does not support IBM LTO (3580) drives. You will have to use the IBM device driver for the drives ( ftp://ftp.software.ibm.com/storage/devdrvr/Win2000). The device name w; /lists/html/ADSM-L/2002-05/msg01095.html (10,745 bytes)
8. Re: 3583 LTO library and drives in Windows 2000 (score: 1): Author: Gianluca Mariani1 <gianluca_mariani AT IT.IBM DOT COM>; Date: Fri, 24 May 2002 22:48:15 +0200; I would use the IBM LTO drivers for the drives and TSM drivers for the medium changer. then check the SCSI chain and be sure of which drive will have element 256 and which element 257. there may be a; /lists/html/ADSM-L/2002-05/msg01104.html (14,626 bytes)

Current List: 1 - 8
Page: [1]