BusLogic's Netware 3.11 driver - BT311.DSK,version 2.20, includes support for SCSI-II Tagged Queuing. Two new command line switches are available to support this feature, detailed below in the Addendum. BusLogic's Netware v3.11 device driver supports BusLogics' ISA, EISA, and Microchannel SCSI host adapters. BTASPI.DSK is BusLogics' ASPI Support Manager. In Addition to standard Netware disk support, the driver provides the following features: 1) Removable device support (including fixed disk, MO, and CDROM). 2) ASPI support. 3) Netware Ready support. 4) Scatter/Gather support. 5) ISA Host Adapter support in a greater-than-16Meg-memory environment. ASPI support ------------ To use the BusLogic driver without ASPI support, simply load the BusLogic driver BT311.DSK: load BT311 To enable BusLogic ASPI support , load BT311.DSK followed by a load of of the BusLogic ASPI Support Manager - BTASPI.DSK: load BT311 load btaspi BTASPI.DSK may only be loaded once regardless of how many times you load BT311. "Over16Meg" Switch ------------------------- If you wish to run one or more ISA (BT-542B) BusLogic host adapter in a system with more than 16 meg of memory you must use the following switch on the FIRST load of the BusLogic driver. load BT311 Over16Meg The presence or absence of this command line switch on subsequent loads of the driver will be ignored. When the "Over16Meg" switch is invoked, the following line should be added to your startup.ncf file to enlarge the pool of available buffers below 16 meg: set Reserved Buffers Below 16 Meg=200 "Exclude_IDs" Switch ------------------------- If you wish to exclude one or more Disk or CDROM SCSI devices from being reported to Netware when they are found by the BusLogic driver, you may use this option to do so. These devices can then be reserved for ASPI Netware applications such as: - disk array software which needs to present several SCSI devices as a single logical device to the operating system - 3rd party software controlling CDROM devices through an ASPI interface. To specify which devices to hide on this host adapter, enter one or more SCSI target IDS separated by commas. For example: load BT311 Exclude_IDs = 1,2 This would hide SCSI target 1 and target 2 from the operating system. New SBackup required -------------------- NOTE: To run Novells' SBackup, you must download their new version from CompuServe. The version shipped with Netware v3.11 looks specifically for Adaptec's Aspitran module and will not work with any other ASPI manager such as BTASPI.DSK from BusLogic. To download the new version, type "go novlib" in CompuServe. Then browse on keyword "Sbackup" in file library 1 to find the appropriate file. Addendum -------- This is a special version of the BusLogic Netware 3.11 driver which includes support for SCSI-II Tagged Queuing. Two new command line switches are available: "Enable_TQ" Switch ---------------- Tagged Queuing is an advanced SCSI-II feature which allows overlapped commands to a SCSI device, thus enhancing performance. The BusLogic SCSI Host Adapters provide support for this feature. However, many SCSI devices do not, and both the host adapter and the SCSI device must support Tagged Queuing in order to take advantage of this feature. The BusLogic SCSI Disk Driver defaults to Tagged Queueing DISABLED for all devices on all BusLogic Host Adapters. Use the ENABLE_TQ switch to enable Tagged Queueing on a given BusLogic Host Adapter: load BT311 Enable_TQ This will only affect those SCSI devices connected to this Host Adapter which also support Tagged Queueing. The maximum number of Tagged requests outstanding is specified by MaxActive switch described below. "MaxActive" Switch --------------- This switch allows you to modify the maximum number of outstanding requests per device allowed at any one time: load BT311 MaxActive=2 Modification of this parameter will allow you to tune the driver for maximum performance based on your specific configuration. Valid values are 1 through 8. If this switch is not specified, the default is value is 1. If you specify the MaxActive switch in conjunction with the Enable_TQ switch, the MaxActive switch will actually control the maximum number of Tagged Queue requests outstanding: load BT311 Enable_TQ MaxActive=4 If you specify the MaxActive switch without specifying the Enable_TQ switch, the MaxActive switch will actually control the maximum number of non-tagged requests outstanding (queued at the Host Adapter, rather than at the device, level). In this case, best performance may be achieved by using the default value. NOTE!!! The value assigned to MaxActive multiplied by the actual number of devices attached to the Host Adapter (each Target/Lun is considered one device) should NOT exceed 32 to avoid potential starvation of a device. Example 1 - The following 4 devices are attached: Target 0 (Lun 0) Target 2 (Lun 0) Target 4 (Lun 0) Target 5 (Lun 0) You may set MaxActive as high as 8 since (4 devices x 8) = 32. Example 2 - The following 8 devices are attached: Target 0 (Lun 0) Target 2 (Lun 0) Target 4 (Lun 0) Target 5 (Lun 0) Target 3 (Lun 0) Target 3 (Lun 1) Target 3 (Lun 2) Target 3 (Lun 3) Target 3 (Lun 4) You may set MaxActive NO HIGHER than 4 since (8 devices x 4) = 32. "LongTimeout" Switch --------------- This switch allows you to increase the amount of time the driver's watchdog timer routine will wait before attempting to abort a CCB which has not finished. The default (if this switch is not invoked) is 10 seconds. If the switch is invoked, the timeout value is increased to 60 seconds. Only special hardware applications which anticipate long periods of time during which a device may remain busy will find this switch useful. In general, it should be ignored. load BT311 LongTimeout