AICU160.ADD

Device driver for Adaptec AIC-7892 Single Channel PCI-to-Ultra160 SCSI ASIC and AIC-7899 Dual Channel PCI-to-Ultra160 SCSI ASIC

Supported Devices

• AHA-3960D/39160 Dual Channel 64-bit PCI-to-Ultra160 SCSI Host Adapter
• 29160 Single Channel 64-bit PCI-to-Ultra160 SCSI Host Adapter
• 29160N Single Channel 32-bit PCI-to-Ultra160 SCSI Host Adapter (OEM)
• 29160LP Single Channel 64-bit Low Profile PCI-to-Ultra160 SCSI Host Adapter
• 39160 64-bit PCI controller Ultra160 SCSI (SCSI Card 39160)
• 39160D 64-bit PCI controller Ultra160 SCSI

BASEDEV=AICU160.ADD [Universal Parameter][Adapter ID][Unit Parameter]{[SCSI Target ID]}

Parameters

• [Universal Parameter] - An option that applies to all adapters controlled by the driver.
• [Adapter ID] - /A:n, where n is the number (zero relative) of the adapter installed in the system. The adapter ID is determined when the driver is loaded based on the order that adapters are found in the system. (Refer to the Configuration Examples in the "General Unit Parameters" section below for information on how to use this option.)
• [Unit Parameter] - Modifies the behavior of the selected host adapter.
• [SCSI Target ID] - 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).

Universal Parameters

• /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 if the driver loads successfully. Information on all targets found in the system will also be displayed.

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).
• /TAG - Specifies the maximum number of tagged commands for all target devices on the host adapter (1-16). A value of 1 disables tagged queuing. The maximum number allowed is 16. (The default is 8.)
• /UR - Enables reporting of under runs (DEFAULT).
• /!UR - Disables reporting of under runs.

NOTE= Intel Errata #8511 lists known data integrity issues with the processor cache on the Saturn-1 chipset (82424TX). For this reason, Adaptec recommends that processor cache be disabled via the CMOS setup to avoid data corruption. For more information, see Intel Errata #8511. You may get this from Intel's FaxBack system at or .

There are installation problems when installing on the maximum hard disk drive partition size supported by OS/2 v3.0. On OS/2 v3.0 it is a known problem. Refer to IBM for further info. IBM's APARs PJ15988 and PJ 6151 deal with this issue.

There are known installation problems installing OS/2 Warp v4.0 on a Micron (LSI chipset) 64 bit PCI system.

There are known installation problems installing OS/2 Warp with 8MB of RAM unless all the third-party basedev statements are removed from config.sys.

There are known installation problems installing OS/2 using two SCSI host adapters on a "Marl" motherboard. Whenever you have a LVD HDD on one Ultra160 host adapter and a HDD, CD-ROM, and removable Syjet on another UltraSCSI host adapter, Syjet conflicts with the CD-ROM and the system is unable to access the CD-ROM.

This version of the Ultra160 Family Manager Set driver supports the AIC-7892/99 Family of Host Adapters. Adapter numbers are first assigned to boards with their BIOS enabled. The numbers are assigned from lowest BIOS address to highest address. Any remaining boards are assigned numbers by scanning slots. Each slot is a combination of a bus number and a device number pair starting from lowest to highest numbers, and the adapters are assigned a number in the order they are found.

Example:

Bus 0, device 0 assigned as adapter 0; Bus 1, device 1 assigned as adapter 1, etc.

There are no switches for controlling OS2ASPI.DMD directly. IBM did not define them in their specification and Adaptec cannot be sure that other host adapters will have the same switches. OS2SCSI.DMD will only allocate devices when a device driver requests it, but this will prevent OS2ASPI from accessing it. There is nothing in the ASPI specification regarding device allocation so OS2ASPI must rely on other managers to fairly share targets. This should only be a problem if you have two drivers that use different managers and you want them both to access the same target at the same time.

Do NOT disable DASD manager access to target 0 if you are booting from your SCSI host adapter. This will prevent the system from booting!

Fault Tolerance is supported in the driver. However, ABORT and SCSI BUS RESET will only work for targets that are properly behaved.

IBM does not support installing the operating system onto magneto optical devices. Additionally, OPTICAL.SYS (OS/2 3.0) or OPTICAL.DMD (OS/2 4.0) allows magneto optical devices to be supported as though they were large floppy devices.

LOCKDRV.FLT allows removable media such as MO's to be supported as though they were fixed hard drives. It is not possible to install OS/2 3.0 on drives with capacity greater than 8 GB, nor in a partition greater than 4 GB.

OS/2 will allocate the SCSI devices as the order in CONFIG.SYS if two drivers (such as the AIC7870.ADD and AICU160.ADD) are loaded. OS/2 will assign drive letters for SCSI devices first then IDE devices.

Configuration Examples

Example 1

Suppose that you had a removable hard drive as target 3 and you wanted to control the hard drive with an ASPI application and driver. Normally OS2DASD will allocate this device, treat it as a large floppy and prevent you from sending any SCSI commands via ASPI. The following command line will prevent OS2DASD.DMD from accessing the target and still allow OS2SCSI.DMD and OS2ASPI.DMD to share access to it.

BASEDEV=AICU160.ADD /A:0 /!DM:3

Example 2

Suppose that you had a multi-disk CD-ROM as target 4 on host adapter 0 and two DASD devices as targets 1 and 5 on host adapter 1. The following command line will prevent OS2SCSI.DMD from accessing the CD-ROM and prevent OS2DASD.DMD from controlling the DASD devices. The driver will also search for multiple LUNs on all host adapters.

BASEDEV=AICU160.ADD /ET /A:0 /!SM:4 /A:1 /!DM:1,5