Before installing the BusLogic OS/2 2.0 SCSI Adapter Driver, you must fully
install OS/2 2.0. You are able to do this out of the box because IBM ships
a generic "Int 13" driver that will get you through the installation.
Once OS/2 is installed and you have rebooted OS/2 from the hard disk following
the installation, you can install the 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 OS220 directory 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 \OS220\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:

	BASEDEV = BTSCSI.ADD

The system will find the 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.


**** New Command Line Switches ****

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 2.0 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:

/A:x - 	Adapter identification switch. x is between 0 and 5 and identifies
	the adapter being referenced. This switch is followed by
	one of the switches below describing the enabling/disabling of
	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.