IBM LTO device driver update - Windows 2003(32 and 64 bit) **************************************************************** | | | | | Build ID: 6.0.6.3 | | Revision: a | | | | (C) Copyright International Business Machines Corporation | | xxxx, 2004. All rights reserved. | | | | US Government Users Restricted Rights -- Use, duplication | | or disclosure restricted by GSA ADP Schedule Contract with | | IBM Corp. | | | | Note: Before using this information and the product it | | supports, read the general information under "NOTICES AND | | TRADEMARKS" in this document. | | | | Updated: 11/05/2004 | | | **************************************************************** CONTENTS: 1.0 Overview 2.0 Change history 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 HBA Restrictions 6.0 Web sites and phone support 6.1 Web sites 6.2 Software service and support 6.3 Hardware service and support 7.0 Notices and trademarks 8.0 Disclaimer 1.0 Overview: The IBM LTO device driver download contains a level of the device driver with its associated resource files and utilities. This driver will be installed in the IBM LTO directory. 2.0 Change History: Version Description ------- ----------- 6.0.6.3a Eliminate false "Drive needs cleaning" messages in W2K (10/20/04) 6.0.6.3 Fix blue screen crash (bug check 0x1E, 0xA and others) in call to TSM's ExtendedInquiry in Windows 2000 (10/09/04) 6.0.6.2 Change default block size to 64K for LTO (RSM) (09/29/04) (Note: this change was made in V5.0.5.3 of the 5.0.x.x series) 6.0.6.0 Fix for barcode reporting in NTUTIL (09/22/04) 6.0.5.9 3490 supported in coinstaller (09/21/04) 6.0.5.8 Fix blue screen crash (bug check 0xA and others) that occurred at sporadic times, usually on reboot or shutdown (09/10/04) 6.0.5.7 Remove INSTALLFLAG_FORCE in coinstaller (09/07/04) 6.0.5.6 Install on Windows XP disallowed (08/25/04) 6.0.5.3 64-bit ntutil code load fix for 3584 (08/09/04) 6.0.5.1 Fix for LogSense (now sets PC field correctly) (07/28/04) 6.0.5.0 Ntutil fix for return code in library inventory (07/27/04) 6.0.4.9 Microcode load fix in ntutil (07/15/04) 6.0.4.7 Eliminate unnecessary reboot in coinstaller (06/23/04) 6.0.4.6 Change "ERROR_SUCCESS" to "SUCCESS" in ntutil status reporting (06/17/04) 6.0.4.5 Support for 3581 barcode scanning in ntutil (06/09/04) 6.0.4.4 Integration with Windows 2000 driver (06/04/04) 6.0.4.3 GetMediaTypes now returns 3590 type for 3592 (05/25/04) 6.0.4.2 New rc for block sequence error (sense 0x3/14/04) (04/28/04) 6.0.4.1 Fix for coinstaller problem introduced in 6.0.4.0 Remove restriction on position after EOD new ntutil with inquiry p. 0x83 support (04/22/04) 6.0.4.0 New ntutil with serial number in inq data (04/14/04) 6.0.3.9 New coinstaller for enhanced device discovery Support for 3592 WORM/3592 in 3584 (04/09/04) 6.0.3.5 Capacity scaling enhancement (3592) (03/13/04) 6.0.3.4 Suppress Read Element Status overrun logging (03/09/04) 6.0.3.3 GetTapeStatus now returns error when tape not present (02/03/04) 6.0.3.2 Cancel IRP routine 3581 2U support (02/02/04) 6.0.2.9 Suppress reporting of "drive needs cleaning" status (12/18/03) 6.0.2.8 Fix XDRIVE_INVENTORY (RES) for the 3582 Support for xSeries HBA feature code 71P8594 (Ultra 320) 6.0.2.7 Support for 3592, 3590 Tape Drive Support for 3594 Library Remove event logging for all inquiry overruns Take out MT as a valid destination element for MS cert. Rollback reserve code from V6.0.1.5 (10/17/03) 6.0.2.6 Fix that prevented 3582 from configuring with Win code 10 6.0.2.5 Return 8-character barcodes for Ultrium products 6.0.2.4 Fix for barcode reading in the 3582 6.0.2.3 Remove WriteFilemarks(0) on readposition after read (08/01/03) 6.0.2.0 Fix open-close-open sequence (07/10/03) 6.0.1.9 Make exclusivity optional (TSM) (7/02/03) 6.0.1.7 Add 64-bit support to uninstall and ntutil (6/4/02) Update timeout value for 3592 erase to 15000 6.0.1.6 Support for 16-frame 3584 library (5/2/03) Support for all Ultrium products with Ultrium Gen I and Gen II drives 6.0.1.5 Support for 3582 and 3583 with Ultrium Generation II drives (4/22/03) ------ 3.0 Installation and setup: This section describes a procedure for installing or updating a Windows 2000, Server 2003 tape device driver for the IBM DAT tape drive. The procedure assumes previous tape drive hardware installation. That is, the tape drive is connected to a controller appropriate for the tape drive model. In addition, the drive must be powered. Login with administrator privilege. For Windows 2000/2003, the 'Found New Hardware Wizard' may appear on the first boot after tape drive hardware is connected. In this case, skip directly to either the 'Windows 2000 Hardware Wizard' or 'Windows 2003 Hardware Wizard' section below. Otherwise -- 1. Right click on 'My Computer', then select 'Properties'. 2. In 'System Properties', click the 'Hardware' tab. 3. In 'System Properties', click the 'Driver Signing' button. 4. In 'Driver Signing Options', select either the 'Warn' or 'Ignore' radio button. (The driver may not install if 'Block' is selected.) 5. Click 'OK' to close the 'Driver Signing Options' dialog. 6. In 'System Properties', click the 'Device Manager' button. 7. In 'Device Manager', open one of these tree branches -- 'Other devices' (the driver is not yet installed), or 'Tape drives' (the driver was previously installed), and find the IBM LTO Tape identifier. For example: 'IBM ULTRIUM-TD1 SCSI Sequential Device'. Right click the above identifier, then select Properties. Note. If the tape drive identifier is not present, Windows likely did not detect the drive during boot. Power down the system and verify the power and data cables are correctly oriented and securely connected. Also if two or more devices are attached to the SCSI bus ribbon cable, verify that the device's SCSI IDs do not conflict (see SCSI Hardware Configuration). You may be able to verify whether the BIOS is detecting the tape drive by enabling and observing the BIOS's hardware detection display during system boot. 8. In 'IBM ULTRIUM-TD1 SCSI Sequential Device Properties', select the 'Driver' tab, then click the 'Update Driver...' button. Proceed to either the 'Windows 2000 Hardware Wizard' or 'Windows 2003 Hardware Wizard' section below as appropriate. Windows 2000 Hardware Wizard ---------------------------- 9. In 'Found New Hardware Wizard' or 'Upgrade Device Driver Wizard', 'Welcome' ..., click 'Next'. 10. In 'Install Hardware Device Drivers', select the top radio button -- (x) Search for a suitable driver for my device (recommended), then click 'Next' 11. In 'Locate Device Drivers', check the appropriate box -- [ ] Floppy disk drives -- if the IBM driver files are on floppy, then insert the driver floppy, or [ ] CD-ROM drives -- if the IBM driver files are on CD, then insert the driver CD, or [ ] Specify a location -- if the IBM driver files are on your hard disc or a network server. then click 'Next'. 12. If you see a sub-dialog with the prompt -- 'Copy manufacturer's files from:', type the full pathname of the folder containing magtape.inf, then click 'OK'. Note: One way to locate the folder containing the file magtape.inf, is to right click 'Start', select 'Search...' then 'Look in: My Computer' for the file 'magtape.inf'. 13. In 'Driver Files Search Results'... If you see the following check box at the bottom of the dialog, '[x] Install one of the other drivers' then check it, then click 'Next'. Otherwise, if no check box appears, you should see 'Windows found a driver for this device...' \magtape.inf', then click 'Next', and skip to step 15. 14. In 'Driver Files Found', select (click to highlight) the driver -- 'IBM LTO (magtape.sys)' then click 'Next'. 15. In 'Completing the Found New/Upgrade Device Driver Wizard', you should see 'The wizard has finished installing the software for: IBM LTO (magtape.sys)', then click 'Finish'. Windows 2003 Hardware Wizard ------------------------------- 9. In 'Found New Hardware Wizard' or 'Hardware Update Wizard': 'Welcome ...', select BOTTOM radio button -- (x) Install from a list or specific location (Advanced) then click 'Next' 10. In 'Please choose your search and installation options.' select the BOTTOM radio button -- (x) Don't search. I will chose the driver to install. then click 'Next'. 11. If the 'Hardware Type.' dialog appears, select 'Tape drives' near the end of the list, then click 'Next'. 12. In 'Select the device driver you want to install for this hardware', click the 'Have Disk...' button. 13. In 'Install From Disk' 'Copy manufacturer's files from:', type the floppy disk drive letter (e.g., A:\), or the full pathname of the folder containing magtape.inf, then click 'OK'. Note: Optionally, 'Browse' can be used to select the folder containing the file magtape.inf. One way to locate the folder containing magtape.inf, is to right click 'Start', select 'Search...' then 'Look in: My Computer' for the file magtape.inf. 14. Now back in 'Select the device driver you want to install ...' select (click to highlight) the driver -- 'IBM LTO (magtape.sys)', then click 'Next'. 15. If you see the dialog -- 'Hardware Installation ! The software you are installing for this hardware IBM LTO (magtape.sys) has not passed Windows Logo testing ...' click 'Continue Anyway'. 16. The wizard then shows 'Please wait while the wizard installs the software ...' and proceeds to install the driver. 17. In 'Completing the Found New/Update Hardware Wizard', you should see 'The wizard has completed installing the software for: IBM LTO (magtape.sys)' then click 'Finish'. 4.0 Configuration Information: If the driver is being re-installed or updated you may be asked to reboot for the driver to take effect. Otherwise no reboot should be needed. The IBM LTO tape drive is now installed and ready to use. Windows 2000 and Server 2003 uses two programs to manage tape backups -- 'Removable Storage Manager' and 'Backup'. Note: Windows XP Home does not currently supply a tape backup application. Removable Storage Manager, at a lower level, recognizes removable storage devices (such as tape drives) and their media (such as tapes). Removable Storage Manager maintains a data base of tapes which is organized by 'allocating' tapes to various media 'pools'. The Backup program, at a higher level, backs up and restore system files. Backup uses services of Removable Storage Manager to gain access to tapes. To verify that Removable Storage Manager has recognized the tape drive -- Right click 'My Computer' and select 'Manage'. In 'Computer Management', follow the tree Computer Management (local) - Storage - Removable Storage -> - Physical Locations [for Windows 2000], - Libraries [for Windows XP, Server 2003], In this tree, you should see an entry similar to: 'IBM DDS Gen5 SCSI Sequential Device'. For help on on Removable Storage, click the help icon and open the 'Removable Storage' book. For Windows 2000, XP Professional (not XP Home), or Server 2003, you can use the Start -> Programs -> Accessories -> System Tools -> Backup applet to verify correct tape drive operation. There are two sections: General Items and HBA Restrictions ***************** * General Items * ***************** 1) Beginning with version 6.0.4.4, the IBMTape device drivers for Windows 2000 and Windows 2003 have been converged into a single install package with common inf files. Use this single package to install a driver on either operating system. The system will detect which version of the driver binary files to install. For Windows 2000 users, the Magstar and Ultrium drivers have also been converged. 2) Attention users of 3570 and 3575 devices: Support for these devices has been dropped in the converged Windows 2000/2003 driver. If you use Windows 2000 you may use the IBMMag.Win2K_5080.zip install package to support these devices. 3) Levels of the Win/200x Device Driver 6.0.1.1 through 6.0.1.6 permit multiple opens on a single tape drive. This change was made to enable the use of RSM on Win/200x. For those levels of the device drivers, system administrators are responsible to ensure that a single tape drive is never accessed by more than one application at a time to prevent potential data loss. With the introduction of driver level 6.0.2.4 and thereafter, two versions of the device driver are made available, one that prohibits multiple opens on a single tape drive and one that will allow multiple opens on a single tape drive. Drivers that prohibit multiple opens on a single tape drive are indicated (when presented by the Windows Plug and Play Device Manager during device configuration) with the text string '(for Tivoli Storage Manager)' in them. These drivers will use the file exctape.inf from the install package during installation. Drivers that allow multiple opens on a tape drive do not have the text string '(for Tivoli Storage Manager)' in them. These drivers will use the file magtape.inf from the install package during the installation. For example, if you have attached a IBM Ultrium II tape drive to your server, you will see the following: IBM ULTRIUM II TAPE DRIVE (for Tivoli Storage Manager) IBM ULTRIUM II TAPE DRIVE IBM strongly recommends that you use the "for Tivoli Storage Manager" drivers whether or not you are a Tivoli customer to prevent a tape drive from being accessed by more than one process and potentially causing data to be corrupted or lost. However, if you are a customer that uses RSM, you will need to use the other driver and take steps to ensure that multiple uncoordinated opens to a tape drive do not occur. If you are using driver version 6.0.2.4 or later, the "Driver Files Search Results" screen will prompt you to choose between drivers during installation. This screen will present you with a default driver choice and a check box labeled "Install one of the other drivers." Select this check box and click "Next." Then choose the driver from the list that best suits your needs. 4) All files with the zip extension need to be downloaded to your workstation in binary mode. 5) A limitation has been found with certain IBM 3582 and 3583 libraries running older versions of library microcode. To determine if you are affected by this limitation, answer questions a, b, c, and d. a) If you are running an IBM 3582 library, do you have microcode level less than 215B.GY001 running on your library? b) If you are running an IBM 3583 library, do you have microcode level less than 5.14.0001 running on your library? c) Have you partitioned your library into logical libraries? d) Have you attached more than one logical library of the same physical library to the same host? If your answers to questions a, c, and d are yes, you are affected by this limitation for your 3582 library. If your answers to questions b, c, and d are yes, you are affected by this limitation for your 3583 library. The limitation is that under these conditions, a unique library serial number is not properly associated with each logical library and sometimes invalid data is returned to applications running library inventory operations. You have two options to avoid the limitation: Option 1 involves upgrading to a level of the library microcode which does not have this limitation and redoing the logical partitioning in the library after the new microcode has been activated. Note, that just upgrading the microcode in a library that is already partitioned does not solve the limitation. Perform the following steps to implement option 1: For an IBM 3583 library: a. Goto the Operator Panel b. From the front choose more c. Select Setup d. Select Library e. Select Partions f. Select option 2 g. After library reboots load new level of ucode h. Goto the Operator Panel i. From the front choose more j. Select Setup k. Select Library l. Select Partions m. Select option you desire For an IBM 3582 Library a: Goto the Operator Panel b. Select the Setup option c. Goto config slots d. cycle through until 'Part' is displayed e. Select 1 to turn partioning off f. power cycle library g. load new library ucode h: Goto the Operator Panel i. Select the Setup option j. Goto config slots k. cycle through until 'Part' is displayed l. Select 2 to turn partioning on If you have an IBM 3582 library, upgrade the microcode on the library to microcode level 215B.GY001, or higher. If you have an IBM 3583 library, upgrade the microcode on the library to microcode level 5.14.0001, or higher. After the microcode is upgraded, set up the logical partitioning of your library. Option 2 -- IBM recommends that you choose option 1, but if you do not wish to upgrade your library microcode in the IBM 3582 or IBM 3583 library, you cannot attach more than one logical library in a physical library to a host server. 6) Tivoli Storage Manager customers (and others, perhaps, depending on their application) using the IBM 3582 Library, need to set the barcode scanning mode to Extended to have the barcodes seen correctly by their application. To do so, from the operator panel, go to Setup -> Scanner -> set Enable to ON. Then set the Mode to Extended. 7) Restriction for various SAN components when certain QLogic HBAs are also in your SAN fabric. If you have the IBM TotalStorage SAN Switch or the Brocade SAN switch or McData SAN products or InRange SAN products and certain QLogic HBAs in your SAN, IBM recommends that you quiesce any jobs running through the QLogic HBAs before creating or modifying zones in your SAN. This is because when a zone is created or modified, an RSCN is sent to all HBA ports in the fabric registered for RSCN notification. If there is active I/O on certain Qlogic HBAs, I/O will fail when the HBA receives the RSCN. Devices are not loss. This has been observed on the following OSes and HBAs: - Windows 2000/NT/2003 -- only with the Qlogic QLA2200 8) Check this readme file for the latest information, which supercedes information in the Installation and User's Guides. 5.0 HBA Restrictions: 1) Use of Adaptec 39160 Host Bus Adapters with IBM Ultrium Generation I Tape drives. The Adaptec 39160 HBA is a dual-ported SCSI host bus adapter. The maximum number of IBM tape devices that are supported for this HBA are two IBM tape devices daisy-chained to one port of the HBA and one IBM tape device attached to the other port of the HBA. 2) Use of Adaptec 29160/39160 Host Bus Adapters with IBM Ultrium Generation 2 Tape Drives If you are using microcode level 34X0 or later on your IBM Ultrium Gen II tape drive, you are not affected by this problem, and you do not need to read any further into this notice. If you are running earlier microcode than level 34X0 on your IBM Ultrium Gen II tape drive, please update to microcode level 34X0 or later to avoid this problem. If you are running a level of microcode less than 34X0 on your IBM Ultrium Gen II tape drive and cannot upgrade to level 34X0 or greater, you may be affected by a problem. Due to problems encountered with Adaptec 29160 and 39160 SCSI LVD Host Bus Adapters, the IBM Ultrium Generation 2 tape drives (with microcode level less than 34X0) are only supported when the transfer rate for the Ultra 160 Adaptec adapters is reduced from the standard 160 MB/sec. to 80 MB/sec. Use the following procedure to update your system BIOS SCSI Device Configuration to limit the transfer rate to 80 MB/sec: (Note: these instructions are for BIOS update and are independent of the specific operating system(s), Windows and/or Linux, running on your system.) 1. Terminate all User applications and reboot the host system. 2. Monitor the system console as the system boots and press 'Control A' on the keyboard when messages appear for the Adaptec card(s). This will enter you into the BIOS configuration mode. 3. Choose the Adaptec HBA that you want to reconfigure. 4. Choose "Configure/View SCSI Controller Setting" 5. Under "Additional Options", choose "SCSI Device Configuration" 6. Change "Sync Transfer Rate (MB/sec)" from 160 to 80 under the SCSI ID for your attached tape device. 7. Press the 'escape key', save the changes and reboot your system again. ------------------------------- Information and assistance is available through the IBM Web site and by phone. 6.1 Web sites IBM Support Web Site: http://www.ibm.com/pc/support/ IBM eServer Web site: http://www.ibm.com/eserver/xseries/ IBM IntelliStation Web site: http://www.ibm.com/pc/intellistation/ 6.2 Software service and support -------------------------------- Through IBM Support Line, you can get telephone assistance, for a fee, with usage, configuration, and software problems with xSeries servers, IntelliStation workstations, and appliances. For information about which products are supported by Support Line in your country or region, go to http://www.ibm.com/services/sl/products/. For more information about Support Line and other IBM services, go to http://www.ibm.com/services/, or go to http://www.ibm.com/planetwide/ for support telephone numbers. In the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378). 6.3 Hardware service and support -------------------------------- You can receive hardware service through IBM Services or through your IBM reseller, if your reseller is authorized by IBM to provide warranty service. Go to http://www.ibm.com/planetwide/ for support telephone numbers, or in the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378). In the U.S. and Canada, hardware service and support is available 24 hours a day, 7 days a week. In the U.K., these services are available Monday through Friday, from 9 a.m. to 6 p.m. 7.0 NOTICES AND TRADEMARKS INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. IBM, the e-business logo, eServer, IntelliStation, xxx, and xxx are trademarks of the IBM Corporation in the United States, other countries, or both. ****************************************************************** The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: e-business logo eServer IBM IntelliStation xxx xxx ****************************************************************** Intel, MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Adaptec and HostRAID are trademarks of Adaptec, Inc., in the United States, other countries, or both. Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others. 8.0 Disclaimer (Required) ---------------------------- 8.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. 8.2 Note to Government Users Include the following note after the disclaimer paragraph. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.