BusLogic MultiMaster SCSI Host Adapter Driver For IBM OS/2 2.1x/Warp Version 1.48 Introduction ============ BusLogic's MultiMaster SCSI Adapter Driver BTSCSI.ADD Ver 1.48 runs under IBM OS/2 2.1, 2.11 and 3.0 (Warp). This README file contains instructions on installing this driver on these OS/2 platforms and describes the various command line switches available to tailor the device driver to your needs. The installation procedures covered in this README file are as follows: I. Installation II. Upgrade III. Installation with IDE as Primary IV. Command Line Switches V. Miscellaneous Notes I. Installation =============== The BusLogic BTSCSI.ADD driver is embedded in the OS/2 2.1x and Warp releases. To upgrade to the new BTSCSI.ADD driver, follow the upgrade procedure described in section II. The embedded driver, however, may have incompatibility on certain PCI motherboards and may prevent the initial installation of OS/2. The following procedure instructs you on how to replace the embedded driver with the latest driver to do your installation. ( OS/2 2.1x Notes: Because OS/2 2.1x does not have built-in ) ( PCI support in OS2LDR, make sure the ISA-compatible port is ) ( set for Primary or Alternate. ) 1. Make a copy of the OS/2 Warp Disk 1. 2. Replace the BTSCSI.ADD on the new diskette with the BusLogic file \OS2\WARP\BTSCSI.ADD from the BusLogic driver diskette. (The driver can be used on both OS/2 2.1x and Warp.) 3. When all the packages from the CD-ROM or floppies have been extracted, you will be prompted to reboot from the hard disk. At this point, boot the system using the OS/2 Warp Installation diskette, and insert Diskette 1 when prompted. 4. Press or to go to the command prompt, insert the BusLogic SW-191 Software Driver diskette, and copy \OS2\WARP\BTSCSI.ADD from the diskette to C:\. 5. Remove the diskette and reboot the system. II. Upgrade ============ 1. Insert the BusLogic SW-191 Software Drivers diskette in the floppy drive. 2. Double-click, in order, the OS/2 System, System Setup, and Device Driver Install icons. 3. Press the Change button in the Source directory. 4. Select, in order, the OS2 and Warp directories. On OS/2 2.1x, select the OS2 and 2.1x directories. 5. Click on the Install button. 6. Select the BusLogic MultiMaster driver and press OK. OS/2 automatically updates the CONFIG.SYS file for the new driver. 7. Eject the driver diskette and reboot the system. III. Installation with IDE as Primary ===================================== Installation of OS/2 driver can be performed in one of two ways, depending on whether OS/2 is being installed from diskettes or CD-ROM. Floppy Installation ------------------- Install OS/2 using the embedded INT 13 driver. After installation, follow the Upgrade procedure in Section II. CD-ROM Installation ------------------- Follow the CD-ROM Installation instruction described in Section I. When OS/2 Installation presents the System Configuration window, perform device driver installation as described in the Upgrade instruction in Section II above. Reboot the system using without closing the System Configuration window. Upon boot up, you will be prompted with the same window with the BusLogic MultiMaster driver in the SCSI Adapter Support list box. Proceed with the installation. IV. Command Line Switches ========================= BusLogic's MultiMaster OS/2 Adapter Device Driver supports the following command line switches: ( Note that the /WD option is no longer necessary for wide ) ( adapters and the /AT option has been renamed to /TO. ) I. Global Switches ------------------ /V Verbose switch. This switch enables driver verbosity at initialization time. /QU Warning-error suppression switch. When invoked, the driver will not complain about references to non-existent targets/ luns specified on the BusLogic ADD driver command line. /O Early Opti chipset work-around switch. This switch provides a work-around for an early version of the Opti PCI chipset which can generate spurious interrupts. Do not use this option unless your system hangs at boot-time and you are using an Opti chipset. II. Per-Host Adapter Switches ----------------------------- /A:x Adapter identification switch. x is between 0 and 5 and identifies the adapter being referenced. This switch is followed by one or more of the switches below. /DM:xx DASD Manager Support switch. As defined by IBM, this switch enables/disables support for this unit by the IBM-supplied DASD Manager (OS2DASD.DMD). /SM:xx SCSI Manager Support switch. As defined by IBM, this switch enables/disables support for this unit by the IBM-supplied SCSI Manager (OS2SCSI.DMD). /BON:xx & /BOFF:xx Bus On / Bus Off switches. x is between 2 and 15 and specifies the desired bus on/bus off time in microseconds. /TQ Enable tagged queuing support on ALL targets on the specified host adapter (specified by the receding /A: switch) that supports tagged queuing. If this switch is Tagged queuing is an advanced SCSI-II feature that allows overlapped commands to a SCSI device, this results in enhanced performance. While BusLogic provides support for this important SCSI-II feature, not all SCSI devices support tagged queuing. The SCSI device must support tagged queuing to take advantage of this feature. BusLogic's OS/2 SCSI Adapter Driver defaults to tagged queuing DISABLED on all devices. For devices that support tagged queuing, the following command line switches are provided to manage tagged queuing support on a finer device-specific level. /TQ:x,y,z,... Enable tagged queuing support on a specified list of SCSI targets. x,y,and z is a list of embedded SCSI targets separated by commas. The Logical Unit Number (LUN) is presumed to be 0. /TQ:(a,b), (c,d), ... Enable tagged queuing support on a specified list of pairs of SCSI targets/LUNs in parenthesies. Each parenthesied pair is separated by commas. Examples: 1) BASEDEV=BTSCSI.ADD /A:0 /TQ This example enables tagged queuing on host adapter 0 on all targets that support it. Targets attached to host adapter 0 that do not support tagged queuing are not affected. 2) BASEDEV=BTSCSI.ADD /A:0 /TQ /A:1 /TQ This example enables tagged queuing on all targets on host adapters 0 and 1 that support it. Targets attached to host adapters 0 and 1 that do not support tagged queuing are not affected. 3) BASEDEV=BTSCSI.ADD /A:0 /TQ:0,2,3 /A:2 /TQ:0,1 This example enables tagged queuing on targets 0, 2, and 3 on host adapter 0 and on targets 0 and 1 on host adapter 2. If any of the specified targets are not attached or do not support tagged queuing, specification of those particular devices is ignored. 4) BASEDEV=BTSCSI.ADD /A:0 /TQ:(0,0),(2,1) This example enables tagged queuing on target 0 LUN 0 and target 2 LUN 1 on host adapter 0. If any of the specified target/LUN combinations are not attached or do not support tagged queuing, specification of those particular devices is ignored. /LUNS:xx This switch specifies the maximum number of Logical Units (LUNs) the host adapter will support (try to detect). If the switch is not specified, the default is 8. Valid range is from 1 to 64. If the host adapter only has embedded SCSI targets attached (that is, all attached devices are at LUN 0), it is recommended to set this option value to 1 to turn off LUN support for LUNS other than 0. Examples: 1) BASEDEV=BTSCSI.ADD /A:0 /LUNS:1 This example effectively disables lun support on host adapter #0. 2) BASEDEV=BTSCSI.ADD /A:0 /LUNS:4 This example scans up to 4 LUNS on host adapter #0. /TO:xx Command Timeout switch. This per-host adapter switch specifies a timeout on each I/O request in seconds. It takes a decimal digit input between 1 and 99. The driver default is 15 seconds in this absence of this switch. Setting the timeout value to 0 turns off the timeout mechanism. Note: This switch has no effect on tape requests. Example: BASEDEV=BTSCSI.ADD /A:0 /TO:10 This example causes the driver to wait 10 seconds before timing out on an outstanding request. /MR:xx Maximum Request switch. This per-host adapter switch specifies the maximum number of requests that can be pending on the host adapter. Valid range is 1 - 64. Default is 32. /MA:xx Maximum Active switch. This per-host adapter switch specifies the maximum number of active requests that can be outstanding on each device on the host adapter. Valid range is 1 - . Default is 8. This value can be adjusted to increase performance. V. Miscellaneous Notes ====================== 1. To use a third-party ASPI driver (such as Corel SCSI) on a particular SCSI ID, you must disable the OS/2 DASD and SCSI managers as follows in the BASEDEV line in CONFIG.SYS: BASEDEV=BTSCSI.ADD /!DM:3 /!SM:3 The example disables the DASD and SCSI managers on SCSI ID 3. 2. On Intel and certain motherboards that scan PCI cards from high to low PCI bus and device number, you must disable the "Use Bus and Device # for PCI Scanning Seq." option in the AutoSCSI Advanced Option if you are using multiple BusLogic 948, 958, or 958D Host Adapters. To get to the Advanced Option, Select the View/Modify Adapter Configuration menu option and press . --- Version: $Id: readme.txt 1.5 1996/02/29 04:02:42 awin Exp $