*********************************************************
*							*
*							*
*   BusLogic SCSI Host Adapter Driver Ver. 1.43		*
*							*
*   for IBM OS/2 2.x & OS/2 WARP 			*
*							*
*				                        *
*********************************************************


Introduction
============

BusLogic's SCSI Adapter Driver BTSCSI.ADD Ver 1.43 runs under IBM
OS/2 2.0/2.10/2.1/2.11 and 3.0 (Warp).  The README file contains
instructions on installing this driver on OS/2 2.x, OS/2 Warp,
and various command line switches available to taylor the device
driver to your needs.


Installation on OS/2 2.x
========================

Before installing the BusLogic OS/2 SCSI Adapter Driver, you must
fully install OS/2. Once OS/2 is installed and you have rebooted
OS/2 from the hard disk following the installation, you can install
the new BusLogic driver using one of the two following methods:

    Method A - Automatic Method
    ---------------------------

    1)  Insert the BusLogic diskette in Drive A:.  Either:

	a)  Choose the System Setup icon from the OS/2 Desktop, then
	    choose the Device Driver Install icon from the System
	    Setup icon view screen

		or ..

	b)  Type DDINSTAL at the system prompt
	    (This will invoke the same icon as above).
 
    2)  Click on the Change button of the Source directory.

    3)  Select the directory with our driver and click on the Set button.

    4)  Click on the Install button, select the BusLogic driver, and
	then click on OK.  The installation and modification to
	CONFIG.SYS will be performed automatically.


    Method B - Manual Method
    ------------------------

    1)  Copy the BusLogic file BTSCSI.ADD over to the \OS2
	directory on the C: boot drive.

    2)  Edit C:\CONFIG.SYS you can invoke E - the IBM OS/2 editor
	that is automatically installed and after invoking the IBM
	OS/2 editor, add the following line (if it is not already
	present):

		BASEDEV = BTSCSI.ADD

	The system will find the new driver in the \OS2 directory.
	If you plan on using CDROM.SYS or OPTICAL.SYS from IBM,
	you must also add the following line to C:\CONFIG.SYS:

		BASEDEV = OS2SCSI.DMD

Once you have completed either method of driver installation, you
must reboot for changes to take effect.


Installation on OS/2 Warp
=========================

The BusLogic BTSCSI.ADD driver is embedded in the OS/2 Warp release.
To upgrade to the new BTSCSI.ADD driver, follow the "Method A"
described above in the Installation on OS/2 2.x section.

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 you can replace the
embedded driver with the latest driver to do your installation.

    1)  Make a copy of the OS/2 Warp Disk 1.

    2)  Replace the BTSCSI.ADD on the new diskette with the
	BusLogic file BTSCSI.ADD from the BusLogic
	driver diskette.

    3)  When all the packages from the CD-ROM 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 the Diskette 1 when prompted.

    4)  Press <F3> to go to the command prompt, insert the
	BusLogic driver diskette, and copy BTSCSI.ADD
	from the diskette to C:\.

    5)  Reboot the system.


Command Line Switches
=====================

BusLogic's OS/2  Adapter Device Driver supports the following 
command line switches:

    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.

    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.

    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. Both
    the host adapter and 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:

    /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
	    specified and the specified host adapter supports tagged
	    queuing (revision 3.30 firmware and above), then tagged
	    queuing is enabled.

    /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.

    /WD	    When this switch is specified, the  driver will scan for
	    up to 15 targets on the specified host adapter. The driver
	    defaults to support for 8 targets in the absence of this
	    switch.

	    Example:

		BASEDEV = BTSCSI.ADD /A:0 /WD    

    /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.  
	
	    NOTE:  If the /WD switch described above is not specified
	    on the command line, it is invalid to specify a value
	    greater than 8 for the /LUNS switch.

	    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 /WD /LUNS:64 

		    This examply scan for up to 64 LUNS (and 16 Targets)
		    on host adapter #0.

    /AT:xx
	    Abort Timeout switch. This per-host adapter switch
	    specifies a timeout on driver abort attempts in seconds.
	    It takes a decimal digit input between 1 and 99. The driver
	    default is 3 seconds in this absence of this switch.

	    Example: 
	    
		BASEDEV = BTSCSI.ADD /A:0 /AT:10   

	        This example causes the driver to wait 10 seconds
		before timing out on an outstanding attempt to abort
		a request.


To reach us & the latest drivers and information:

Tech Support:   (408) 654-0760
FAX:            (408) 492-1542
BBS:            (408) 492-1984
Email:          techsup@buslogic.com
FTP Site:       ftp.buslogic.com (204.160.180.11)
WWW Page:       http://www.buslogic.com