File Name: os2.txt IBM Ultra320 SCSI Controller 2 p/n 13N2249, FRU p/n 13N2250 IBM OS/2 Warp Server for e-Business IBM eServer xSeries CONTENTS --------- 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Command Line Options 5.0 Additional Information 6.0 Web Sites and Support Phone Number 7.0 Trademarks and Notices 8.0 Disclaimer 1.0 Overview ------------ This package contains the Adaptec Ultra320 Family Manager Set v1.1 for IBM OS/2 Warp Server for e-Business v4.52 Convenience Pack 2 1.1 Supported Adaptec Host Adapters Ultra320 Adapters Description ---------------------------------------------------------------- AIC-7901 H2A Single Channel PCI-to-Ultra320 SCSI ASIC AIC-7901 H1B Single Channel PCI-to-Ultra320 SCSI ASIC AIC-7902 H2B Dual Channel PCI-to-Ultra320 SCSI ASIC ASC29320LP H1A Single Channel 64-bit Low Profile PCI-to-Ultra320 SCSI Host Adapter ASC29320ALP H1B Single Channel 64-bit Low Profile PCI-to-Ultra320 SCSI Host Adapter ASC39320A H2B Dual Channel 64-bit Low Profile PCI-to-Ultra320 SCSI Host Adapter 1.2 Supported Servers x225, 8647 x226, 8648 x235, 8671 2.0 Change History ------------------ v1.0 This is the first Ultra320 driver release for OS/2 Warp Server for e-Business. v1.1 Modified timing in the driver to make it processor independent. 3.0 Installation and Setup Instructions --------------------------------------- The AICU320.ADD Ultra320 SCSI driver only supports OS/2 Warp Server for e-business. 3.1 Installing a New Driver or Updating an Existing Driver 3.1.1 Using "OS/2 Device Driver Install" Program NOTE: When installing a new host adapter, make sure it is inserted in the system before installing the driver. 1. Insert the Adaptec’s OS/2 Ultra320 Device Driver Installation Floppy in the appropriate floppy drive. 2. Select the "System Setup" Icon in the tools bar at the bottom of the OS/2 desktop, select "Install/Remove" and then select "Device Driver Install". 3. Alternatively, you can also accomplish the same by opening on the OS/2 desktop, the "OS/2 System" folder, the "System Setup" folder, the "Install/Remove" folder and then double-click on the Device Driver Install icon. 4. In the OS/2 Warp 4 Device Driver Installation dialog box, if the Installation Floppy is not located in A:, change the default Source directory to point to the appropriate drive. The Device Driver Install program makes use of the destination directory information contained in the Device Driver profile file (AICU320.DDP) on the floppy and installs the AICU320.ADD driver into the \OS2\BOOT directory. You can, however, also change that by specifying a new Destination directory. 5. Select "Install..." to start the installation process. 6. *** IMPORTANT *** After the installation has been completed, be sure to check the C:\ directory and delete any previous versions of the AICU320.ADD drivers before rebooting the system. If you do not remove those drivers, OS/2 will load them instead of the new drivers that you have just installed. You can easily check for the existence of multiple copies of the driver by typing at the C:\ prompt, dir aicu320.add /s. 7. Select EXIT and reboot the computer. 3.1.2 Installing Manually You may also install the driver manually by using the following steps. 1. Copy AICU320.ADD to C:\OS2\BOOT. 2. Add the following line to your CONFIG.SYS file: BASEDEV=AICU320.ADD /V. 3.2 First-Time Installation from CD-ROM NOTE: To install the driver, it is necessary to copy the driver from the Adaptec’s OS/2 Ultra320 Device Driver Installation Floppy on to the OS/2 Diskette 1. However, before you can copy the driver, you must first remove various files from the OS/2 Diskette 1, as explained in step 2 below. 1. Type CDINST from CD-ROM drive and follow the instructions to create the boot diskettes from the OS/2 Installation CD. 2. Delete some of the existing files on the OS/2 Diskette 1 so that approximately 200 KB of disk space is available on the diskette. Use the following information to help you decide which files to delete: - If the Ultra320 host adapter is the only Adaptec host adapter installed in your system, delete all other Adaptec drivers (aha152x.add, aha154x.add, aha164x.add, aha174x.add, aic7770.add, aic7870.add, aic78u2.add and fd16-700.add). - For each driver removed from the OS/2 Diskette 1, remove its corresponding line in the config.sys file (also on OS/2 Diskette 1). For example, if you deleted all Adaptec drivers as explained in the above, remove the following lines from the config.sys file: rem basedev=aha152x.add rem basedev=aha154x.add rem basedev=aha164x.add rem basedev=aha174x.add rem basedev=aic7770.add rem basedev=aic7870.add rem basedev=aic78u2.add rem basedev=fd16-700.add - If you have deleted the suggested Adaptec drivers and you still do not have approximately 200 KB of disk space available on the diskette, delete the file: CDINST.EXE. *************************************************************** Note: The following files MUST NOT BE DELETED from Diskette 1: CLOCK01.SYS, CLOCK02.SYS, IBM1S506.ADD, IBM1FLPY.ADD, IBM2FLPY.ADD, IBM2ADSK.ADD, IBM2SCSI.ADD, IBMINT13.I13, IBMKBD.SYS, KBDBASE.SYS, OS2LOGO, OS2DASD.DMD, PNP.SYS, RESERVE.SYS, RESOURCE.SYS, SCREEN01.SYS, SCREEN02.SYS, XDFLOPPY.FLT, and all *.SNP files. *************************************************************** 3. Copy the driver from the Adaptec’s OS/2 Ultra320 Device Driver Installation Floppy onto the OS/2 Diskette 1 (\AICU320\AICU320.ADD). 4. In the config.sys file on OS/2 Diskette 1, add the line set copyfromfloppy=1 5. This line should be added so that the install process copies the AICU320.ADD driver from the OS/2 Diskette 1, rather than the driver included on the OS/2 CD-ROM. 6. Add the following line to the top line of config.sys on OS/2 Diskette 1. BASEDEV=AICU320.ADD /V 7. Run the OS/2 installation program; follow the instructions in your OS/2 documentation, until you reach the System Configuration window. 8. In the System Configuration window, click the SCSI Adapter Support icon. 9. Deselect any highlighted adapters (including the Adaptec 294x, 394x, AIC7870 PCI SCSI), and click OK. NOTE: If these adapters are not deselected, the driver included on the CD-ROM will be copied over the driver being installed. 10. Follow the instructions in your OS/2 documentation to complete the installation. 4.0 Command Line Options ------------------------ OS/2 adapter device drivers (.ADD files) are normally installed automatically and require no further information from the user. However, in certain situations the user may wish to modify the behavior of the driver to meet their specific needs. IMPORTANT: Please proceed cautiously with the following information. The standard format for command line switches is: BASEDEV=AICU320.ADD [GlobalParam][AdapterID][UnitParam]{[ScsiTargetID]} GlobalParam Global Parameters. These options apply to all adapters controlled by the driver. ET Allow embedded targets. This parameter indicates that the ADD should assume that all targets have more than one logical unit (LUN) defined. /!ET Do not allow embedded targets (DEFAULT). This parameter indicates that the ADD should assume that all targets have only one logical unit (LUN) defined. /V Load driver verbosely. This parameter will display the driver name as well as the version number and Adaptec copyright information. Information on all targets found in the system will also be displayed. AdapterID The adapter ID # is assigned during the device driver initialization and is based on the order that the adapters are discovered in the system. Each channel on a host adapter is considered as an independent adapter, hence, a 2 channels host adapter is assigned with 2 consecutive adapter IDs. /A:n where, n is the ID number (zero relative) of the host adapter installed in the system. UnitParam Unit Parameters. General: /I Ignore the specified adapter. This allows another driver to share the adapters that the ADD would normally use. /DM: Enable DASD manager support (DEFAULT). This parameter allows OS2DASD.DMD to control the specified target(s) if they are identified as DASD (hard disk) devices. /!DM: Disable DASD manager support. This parameter prevents OS2DASD.DMD from controlling the specified target(s). /SM: Enable SCSI manager support (DEFAULT). This parameter allows OS2SCSI.DMD to control the specified target(s) if they are identified as NON-DASD SCSI devices. All SCSI hard drives will be controlled by OS2DASD.DMD. /!SM: Disable SCSI manager support. This parameter prevents OS2SCSI.DMD from controlling the specified target(s). /UR Enables reporting of under runs (DEFAULT). /!UR Disables reporting of under runs. Special: /TAG:n Specifies the maximum number (n) of tagged commands for all target devices on the host adapter. A value of 1 disables tagged queuing. The maximum number allowed is 16. The default is 8. U320 devices are required to support tag commands and the disconnect features. The driver will negotiate with the U320 devices and adjust its settings accordingly. The driver also maintains a maximum of 2 non-tagged commands per target internally and sends only one non-tagged command at a time per target to the host adapter. ScsiTargetID SCSI Target IDs. The targets to which the Unit Parameter will be applied. This parameter may be a single ID (d) or list of IDs (d,d,d). 5.0 Additional Information -------------------------- Additional information for the OS/2 drivers can be found in the file Reados2.htm which is in the directory readme of the OS/2 device driver package, 6.0 WEB Sites and Support Phone Number -------------------------------------- 6.1 IBM Support Web Site: http://www.ibm.com/pc/support 6.2 IBM Marketing Netfinity Web Site: http://www.pc.ibm.com/netfinity 6.3 If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: 1-800-772-2227 http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html. 7.0 Trademarks and Notices -------------------------- 7.1 IBM, OS/2, and the e(logo) are registered trademarks of International Business Machines Corporation in the United States, other countries, or both. 7.2 This software contains the valuable trade secrets of Adaptec or its licensors. The software is protected under international copyright laws and treaties. This software may only be used in accordance with the terms of its accompanying license agreement. 8.0 Disclaimer -------------- 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 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.