It is called "Billy-Bob knows best OS". Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180
-----Original Message----- From: Cowperthwaite, Eric [mailto:eric.cowperthwaite@;EDS.COM] Sent: Thursday, October 17, 2002 1:14 PM To: [EMAIL PROTECTED] Subject: Re: Win2K, Fiber and I/O problem What seems to have worked is to disable the Win2K drivers and set the TSM driver to BOOT. Why isn't this like UNIX where I can decide what drivers load? When I tried just uninstalling the Win2K drivers the system promptly reinstalled them when the system rebooted. What a pain. Anyhow, we'll monitor the system for the next week or so and see if the problem is resolved. Thanks to Paul and Norbert for the advice. Eric W. Cowperthwaite EDS Operations Solutions Desk - 916-636-1929 Cell - 916-919-6271 [EMAIL PROTECTED] -----Original Message----- From: Seay, Paul [mailto:seay_pd@;NAPTHEON.COM] Sent: Wednesday, October 16, 2002 9:11 PM To: [EMAIL PROTECTED] Subject: Re: Win2K, Fiber and I/O problem Been there, seen this, solved this. For some reason the TSM Boot ADSMSCSI driver does not pickup the drives first. What you have to do is disable the drives in device manager and reboot. Make sure the ADSMSCSI driver service (BOOT) is setup in the configuration. Otherwise, the drives will not get picked up by TSM. We have seen if you get the (BOOT) driver installed from TSM correctly and delete the drives from device manager the TSM boot driver will pick them up correctly. Our case was Magstar tape drives but the symptoms were exactly the same. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Cowperthwaite, Eric [mailto:eric.cowperthwaite@;EDS.COM] Sent: Tuesday, October 15, 2002 7:45 PM To: [EMAIL PROTECTED] Subject: Win2K, Fiber and I/O problem I have an interesting problem. One of my TSM servers is running on Win2K Server. The server is connected to a Brocade FC switch and the FC switch is connected to an FC-SCSI bridge. The library is an HP SureStore 6/60 with DLT8000 drives. Every once in a while I get I/O error on a tape drive and the server resets the drive. When it does the drive renames from the TSM Driver name to the NT Driver name (i.e. from mtx.x.x.x to \\..\tape0 <\\..\tape0> ). Has anyone else had this sort of problem and what did you do to resolve it? Thanks, Eric W. Cowperthwaite EDS Operations Solutions Desk - 916-636-1929 Cell - 916-919-6271 [EMAIL PROTECTED] <mailto:eric.cowperthwaite@;eds.com>