Adaptec Ultra160 Family Manager Set
README for IBM OS/2

The following information is available in this README file

Supported Hardware

Changes From Prior Release

Installation Instructions

- Installing a New Driver or Updating an Existing Driver for OS/2 Warp 3.x, 4.x and Server for e-business
- First-Time Installation of OS/2 Warp 3.x and 4.x From Floppy Diskette
- First-Time Installation of OS/2 Warp 3.x, 4.x and Server for e-business From CD-ROM

Known Issues

Additional Notes

Command Line Options

Diskette Contents

Contacting Adaptec
 

Supported Hardware

The following Adaptec SCSI Host Adapters are supported by the Adaptec Ultra160 Family Manager Set.
 

AIC-7892	Single Channel PCI-to-Ultra160 SCSI ASIC
AIC-7899	Dual Channel PCI-to-Ultra160 SCSI ASIC
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

Changes From Prior Release

• This is the initial Ultra160 release for OS/2.

Installation Instructions

The AICU160.ADD Ultra160 SCSI driver only supports OS/2 Warp 3.x, 4.x, and Server for e-business.

Installing a New Driver or Updating an Existing Driver for OS/2 Warp 3.x, 4.x and Server for e-business

(NOTE: When installing a new host adapter, make sure it is inserted in the system before installing the driver.)

1. Open the OS/2 System Folder, then open the System Setup folder.
2. If running OS/2 Warp 4.x or Server for e-business, open the Install/Remove Folder.
3. Double-click on Device Driver Install.
4. Insert the Family Manager Set floppy in the appropriate drive.
5. Change to the directory where the driver is located (..\AICU160\).
6. When you find the driver (AICU160.ADD), select INSTALL.
7. After the installation finishes, be sure to check the C:\ directory and delete any previous versions of the AICU160.ADD drivers before rebooting the system. If you do not remove those drivers, OS/2 will load them instead of the new drivers that you have just installed.
8. Select EXIT and reboot the computer.

 You may also install the driver manually.

1. Copy AICU160.ADD to C:\OS2\BOOT.
2. Add a line to your CONFIG.SYS that says BASEDEV=AICU160.ADD /V. 

 First-Time Installation of OS/2 Warp 3.x and 4.x From Floppy Diskette

(NOTE: To install the driver, it is necessary to copy the driver from the Family Manager Set diskette for OS/2 on to the OS/2 Diskette 1. However, before you can copy the driver, you must first remove various files from the OS/2 Diskette 1, as explained in step 2 below.)

1. Make backup copies of the Installation Diskette and Diskette 1.
2. Delete some of the existing files on the backup copy of the OS/2 Diskette 1 so that approximately 160 KB of disk space is available on the diskette. Use the following information to help you decide which files to delete:
   1. If the Ultra160 host adapter is the only Adaptec host adapter installed in your system, delete all other Adaptec drivers (aha152x.add, aha154x.add, aha164x.add, aha174x.add, aic7770.add, aic7870.add, aic78u2.add and fd16-700.add).
   2. For each driver removed from the OS/2 Diskette 1, remove its corresponding line in the config.sys file (also on OS/2 Diskette 1). For example, if you deleted all Adaptec drivers, as explained in step 2a above, remove the following lines from the config.sys:

      rem basedev=aha152x.add

      rem basedev=aha154x.add

      rem basedev=aha164x.add

      rem basedev=aha174x.add

      rem basedev=aic7770.add

      rem basedev=aic7870.add

      rem basedev=aic78u2.add

      rem basedev=fd16-700.add

   3. If you have deleted the suggested Adaptec drivers above, and you still do not have approximately 160 KB of disk space available on the diskette, delete the file: CDINST.EXE.

      ***************************************************************

      Note: The following files MUST NOT BE DELETED from Diskette 1:

      CLOCK01.SYS, CLOCK02.SYS, IBM1S506.ADD, IBM1FLPY.ADD, IBM2FLPY.ADD, IBM2ADSK.ADD, IBM2SCSI.ADD, IBMINT13.I13, IBMKBD.SYS, KBDBASE.SYS, OS2LOGO, OS2DASD.DMD, PNP.SYS, RESERVE.SYS, RESOURCE.SYS, SCREEN01.SYS, SCREEN02.SYS, XDFLOPPY.FLT, and all *.SNP files.

      ***************************************************************

3. Copy the driver from the Family Manager Set diskette for OS/2 onto the OS/2 Diskette 1 (\AICU160\AICU160.ADD).
4. Add the following lines to the top of the config.sys file on OS/2 Diskette 1:
   1. BASEDEV=AICU160.ADD /V
   2. Set CopyFromFloppy=1  
5. Install OS/2 using the backup diskettes and the remainder of the standard OS/2 diskettes. When installation has completed, reboot the system.

First-Time Installation of OS/2 Warp 3.x, 4.x and Server for e-business From CD-ROM

(NOTE: To install the driver, it is necessary to copy the driver from the Family Manager Set diskette for OS/2 on to the OS/2 Diskette 1. However, before you can copy the driver, you must first remove various files from the OS/2 Diskette 1, as explained in step 2 below.)

1. Type CDINST from CD-ROM drive to create the boot diskettes from OS/2 CD.
2. Delete some of the existing files on the OS/2 Diskette 1 so that approximately 160 KB of disk space is available on the diskette. Use the following information to help you decide which files to delete:
   1. If the Ultra160 host adapter is the only Adaptec host adapter installed in your system, delete all other Adaptec drivers (aha152x.add, aha154x.add, aha164x.add, aha174x.add, aic7770.add, aic7870.add, aic78u2.add and fd16-700.add).
   2. For each driver removed from the OS/2 Diskette 1, remove its corresponding line in the config.sys file (also on OS/2 Diskette 1). For example, if you deleted all Adaptec drivers, as explained in step 2a above, remove the following lines from the config.sys:

      rem basedev=aha152x.add

      rem basedev=aha154x.add

      rem basedev=aha164x.add

      rem basedev=aha174x.add

      rem basedev=aic7770.add

      rem basedev=aic7870.add

      rem basedev=aic78u2.add

      rem basedev=fd16-700.add

   3. If you have deleted the suggested Adaptec drivers above, and you still do not have approximately 160 KB of disk space available on the diskette, delete the file: CDINST.EXE.

      ********************************************************

      Note: The following files MUST NOT BE DELETED from Diskette 1:

      CLOCK01.SYS, CLOCK02.SYS, IBM1S506.ADD, IBM1FLPY.ADD, IBM2FLPY.ADD, IBM2ADSK.ADD, IBM2SCSI.ADD, IBMINT13.I13, IBMKBD.SYS, KBDBASE.SYS, OS2LOGO, OS2DASD.DMD, PNP.SYS, RESERVE.SYS, RESOURCE.SYS, SCREEN01.SYS, SCREEN02.SYS, XDFLOPPY.FLT, and all *.SNP files.

      ************************************************************

3. Copy the driver from the Family Manager Set diskette for OS/2 onto the OS/2 Diskette 1 (\AICU160\AICU160.ADD).
4. Add the following lines to the top of the config.sys file on OS/2 Diskette 1: (Note: The line "set copyfromfloppy=1" should be added so that the install process copies the AICU160.ADD driver from the OS/2 Diskette 1, rather than the driver included on the OS/2 CD-ROM.)
   1. BASEDEV=AICU160.ADD /V
   2. Set CopyFromFloppy=1  
5. Run the OS/2 installation program; follow the instructions in your OS/2 documentation, until you reach the System Configuration window.
6. In the System Configuration window, click the SCSI Adapter Support icon.
7. Deselect any highlighted adapters (including the Adaptec 294x, 394x, AIC7870 PCI SCSI), and click OK.

   (NOTE: If these adapters are not deselected, the driver included on the CD-ROM will be copied over the driver being installed.) 

8. Follow the instructions in your OS/2 documentation to complete the installation. 

Known Issues

• 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 800.628.2283 or 916.356.3105.
• 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.

Additional Notes

• 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. The following is the suggestion from IBM on this problem:

Problems with large partitions and installation or booting: There is a BIOS restriction that installable (startable) or bootable partitions must be contained within the first 1024 physical cylinders of the disk. FDISK does not enforce this limitation. If you have installation or boot failures this could be the reason. Use FDISK to reduce the size of your startable or bootable partition by sufficient MBs. One way to calculate the correct size partitions is to do the following:

1. Edit your CONFIG.SYS and add the following parameter to the BASEDEV=IBM1S506.ADD line as below:

   BASEDEV=IBM1S506.ADD /V

2. Save this change.
3. Reboot your system.
4. At initialization, record the far left hand column of number of the Geometry information under the ACT heading.

Example: ACT Cyl 1027 Head 63 Sec 128 (head x sec) /2 = bootable partition must be contained within this boundary in MBytes (round down)

This is the maximum size of a bootable partition in MBytes. Any bootable partition must also be contained from the beginning of the drive to this number of MBytes. A bootable partition may be smaller than the maximum size but still must be contained within this boundary. In this example the bootable partition must be contained in the first 4032 MBbytes of the disk and cannot exceed a single partition size of 4032 MBytes within this area. No bootable partition may extend beyond the first 4032 MBytes. Use this information when configuring your bootable partition with FDISK.

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

Command Line Options

OS/2 adapter device drivers (.ADD files) are normally installed automatically and require no further information from the user. However, in certain situations the user may wish to modify the behavior of the driver to meet their specific needs.

(IMPORTANT: Please proceed cautiously with the following information.)

The standard format for command line switches is:

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

• [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.

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

Special :

• /TAG: -- Sets the number (1-16) of tagged commands for all target devices on the host adapter. A value of one disables tagged queuing. Sixteen is the maximum number allowed and 8 is the default value.
• /TAG:1 -- Disables tagged queuing for all target devices on a given host adapter. The driver maintains a maximum of 2 non-tagged commands per target internally. The driver treats all target devices as non-tagged devices, and sends only one command at a time per target to the host adapter.

Example:

BASEDEV=AICU160.ADD /A:0 /TAG:8

This will set the number of tagged commands for all target devices on the first host adapter to 8.

Diskette Contents

The following files are included in this diskette:
 

\AICU160\AICU160.ADD	Ultra160 SCSI driver for OS/2 Warp 3.x, 4.x and Server for e-business
\AICU160\AICU160.DDP	AICU160 device driver profile.
\AICU160\U160PRES.EXE	Adaptec Ultra160 Family Devices Detection Module.
\README\READOS2.HTM	This file.

Contacting Adaptec

Technical information, including product literature, answers to commonly asked questions, information on software upgrades, and other topics is available electronically through the following:

• Search the Adaptec World Wide Web site at http://www.adaptec.com
• Connect to the File Transfer Protocol (FTP) server at ftp://ftp.adaptec.com/pub/BBS/
• Search the Adaptec Support Knowledgebase (A.S.K.) at http://ask.adaptec.com for articles, troubleshooting tips, and frequently asked questions for your product.
• For Internet support, send technical questions to Adaptec's Technical Support Specialists via WebMail at http://www.adaptec.com/support/webmail.html .
  To speak with a Technical Support Specialist, call 408-934-7274, Monday-Friday, 6:00 A.M. to 5:00 P.M., Pacific Time.