                                  File Name: MPTOS2.TXT

LSI Logic Fusion-MPT (TM) Driver: LSIMPT.ADD V1.01.00

CONTENTS
---------

   1.0   Overview
   2.0   Change history
   3.0   Installation and setup instructions
   4.0   Configuration information
   5.0   Unattended mode
   6.0   Web sites and support phone number
   7.0   Trademarks and notices
   8.0   Disclaimer


1.0   Overview:  This file describes the features and use of the LSI Logic Fusion-MPT SCSI 
                 device driver for the OS/2 Warp Server for eBusiness operating system 
                 environment.


   1.1   Overview about this code:

         None.

   1.2   Limitations:

         None.

   1.3   Enhancements:
	
         None.

   1.4   Level of recommendations and prerequisites for the Update:

         None.

   1.5   Dependencies:

         None.


2.0   Change history
      --------------------

      1.01.00   New release.                                  
                  

3.0   Installation and Setup Instructions
      -----------------------------------------

             	                                             
      3.1  Introduction for OS/2 Warp Server for eBusiness  

                The OS/2 Warp Server for eBusiness operating system version 4.52 or later 
                provides a network operating system with the functions and features you need
                for an advanced application server platform. It is designed for small and 
                medium-sized businesses, departmental workgroups, or large coporations and 
                institutions. It supports Journaled File System (JFS), Tivoli's Lightweight 
                Client Framework (LCF) Endpoint Agent,  Netfinity Manager and Client 
                Services, Network File System (NFS),  Year 2000 and Euro currency ready, 
                Logical Volume Manager (LVM), Windows NT Server management, Dynamic Domain 
                Name Server (DDNS) for Windows 95, and NT Clients and Dynamic Host 
                Configuration Protocol (DHCP).

                The LSI Logic Fusion-MPT (TM) driver is LSIMPT.ADD. It provides support for 
                the devices mentioned below. LSI Logic recommends reviewing the OS/2 Warp 
                Server for eBusiness manual prior to proceeding. 

      3.1.1  Features 

                The LSIMPT.ADD device driver for OS/2 Warp Server for eBusiness supports 
                these features:

                o  Supports 320 Mbytes/s parallel SCSI transfers
                o  Supports PCI and PCI-X bus protocols
                o  Supports LSI Logic Fusion-MPT common software interface
                o  Supports multiple host adapters
                o  Supports multiple Logical Unit Numbers (LUNs)
                o  Disconnect/Reselect
                o  Supports Scatter-Gather
                o  Tagged command queuing
                o  Target-initiated negotiation
                o  Allow up to 8 host adapters
                o  Command line options and configuraton through Bios Configuration utility
                o  Higher performance by requiring only one interrupt per multiple I/O's
                o  Auto request sense

      3.1.2  LSI Logic devices supported 

                The LSIMPT.ADD driver supports the following devices and their associated
                LSI Logic host adapters:

                  o  LSI53C1020
                  o  LSI53C1030

      3.1.3  Description

                Although the LSI Logic SCSI controller BIOS can access the SCSI hard disk 
                drives attached to the computer independently, the SCSI device driver 
                LSIMPT.ADD provides an enhanced interface between the computer system and the
                SCSI firmware. Using the device driver increases the abilities of the SCSI 
                controller firmware and fully utilizes the improvements of Pentium-based and 
                higher microprocessors.

                The device driver is also necessary to support the use of SCSI tape drives 
                and CD-ROM drives with an OS/2 system. The LSIMPT.ADD device driver supports
                the IBM OS/2 Adapter Device Driver (ADD) specification, and the device driver
                operates with third party applications that comply with the same
                specification.

                LSIMPT.ADD driver supports up to eight host adapters in a system. The system
                accesses the first four host adapters in the order that you specify in the 
                SCSI BIOS Configuration Utility. The system accesses the remaining host 
                adapters in the order of their physical position in the system. Refer to your
                system documentation for further information.

      3.2  Installing the Fusion-MPT (TM) OS/2 Drivers 

                This section provides instructions on:

                  o    Installing LSIMPT.ADD During New System Installations
                  o    Updating LSIMPT.ADD For Existing System Installations

                Note: If you previously installed LSIMPT.ADD in a directory other than 
                      \OS2\BOOT, move LSIMPT.ADD to \OS2\BOOT, where the new version of the 
                      driver can replace the old version. The system will continue to boot 
                      using the previous driver until these steps are taken.

      3.2.1  Installing LSIMPT.ADD During New System Installations

                The system configuration determines which installation instructions are
                appropriate.

                If neither the boot drive nor SCSI CD-ROM connects to an LSI Logic Fusion-MPT
                device, install OS/2 and then add the driver.  Refer to the OS/2 Installation
                Guide for operating system installation instructions. After installing the 
                operating system, follow the steps in "Updating LSIMPT.ADD For Existing 
                System Installations" to add the Fusion-MPT driver.

                -or-

                If your boot drive or SCSI CD-ROM attaches to an LSI Logic Fusion-MPT device,
                follow these steps:

                1. Make copies of the diskettes used for installation that are included
                   with the CD-ROM version of OS/2 Warp Server for eBusiness. There are
                   three diskettes.

                2. Copy the LSIMPT.ADD driver from the LSI Logic Fusion-MPT OS/2 driver 
                   diskette to the copy of Diskette 1 made under step 1.

                   In order to do so, you must delete files on Diskette 1 to provide space.
                   Consult the README.1ST file on the Device Driver Pak. It contains a list
                   of files that may not be deleted. Follow the instructions provided in the
                   README.1ST file. Once space is made available on Diskette 1, copy the
                   device driver onto this diskette.

                   When ADD drivers are deleted from Diskette 1, make certain to delete or
                   remark out the corresponding BASEDEV= statement in the CONFIG.SYS file.
                   Otherwise, error messages will show up during installation.

                3. Edit the CONFIG.SYS file on the copy of Diskette 1 by adding the following
                   line at the end of the file:

                   BASEDEV=LSIMPT.ADD /V

                4. Follow the directions in the README.1ST file for adding the following line
                   to the CONFIG.SYS file:

                   SET COPYFROMFLOPPY=1

                   This allows the driver to be copied from the installation diskette to the
                   system's boot drive.

                6. Place the copy of Installation Diskette 0 in the A: drive and reboot the
                   computer.

                7. Proceed with the OS/2 installation process as documented in the OS/2
                   Installation Guide.


      3.2.3  Updating LSIMPT.ADD For Existing System Installations

                This section provides instructions for existing system installations. Apply
                these instructions when:

                o Adding drivers for newly installed LSI Logic Fusion-MPT devices, or
                o Updating drivers for existing LSI Logic Fusion-MPT devices.

                To add or update LSI Logic Fusion-MPT OS/2 drivers, follow these steps:

                1. Open the System Setup folder located within the OS/2 System folder on the
                   OS/2 Desktop.

                2. Open the Install/Remove folder and then double click on the Device Driver
                   Install icon.

                3. Insert the diskette containing the LSI Logic Fusion-MPT device driver in
                   the source drive.

                   The system finds the DDP file on the floppy diskette and automatically
                   install the driver.

                4. Verify that the installation was successful by following these steps:

                   A. Open the Utilities folder located within the Programs folder on the 
                      OS/2 Desktop.

                   B. Double click on the OS/2 System Editor to start the editor.

                   C. Open the CONFIG.SYS file in the root directory and find the line:

                      BASEDEV=LSIMPT.ADD /V

                   D. Check that the driver is in the \OS2\BOOT directory on the boot drive.


      3.2.4  Driver Order in the CONFIG.SYS File

                Because of the way OS/2 assigns drive letters, the order in which drivers
                appear in the CONFIG.SYS file is important. The drivers must appear in the
                order in which the drive letters are to be assigned. In particular:

                o   OS/2 will install the BASEDEV= line at the beginning of the target
                    system's CONFIG.SYS file regardless of where the line is located in that
                    file on Diskette 1. You may need to rearrange the order in which drivers
                    appear in the CONFIG.SYS file for the target system.

                o   The driver for the host adapter to which the boot device is attached must
                    appear before all other BASEDEV= drivers in the CONFIG.SYS file.

                Refer to the OS/2 documentation to fully understand this requirement.

      3.3  Troubleshooting 

                This section describes some potential problems and provides solution 
                suggestions.

                Problem: You cannot access the SCSI device(s).

                    Solution:

                    a. Verify that the SCSI device driver is installed properly.

                    b. Verify that each device has power.

                    c. Verify that the line BASEDEV=LSIMPT.ADD /V is in the CONFIG.SYS file.

                    d. Check the ordering of BASEDEV= entries in the CONFIG.SYS file to 
                       verify that the boot device loads first.

                    e. Verify that the correct driver is in the appropriate directory
                       (\OS2\BOOT).

                    f. Check the cable connections and the host adapter installation.

                    g. Verify that the adapter is not turned off in the SCSI BIOS 
                       Configuration Utility and that the adapter is not excluded using the 
                       /EXCLUDE command line option.

                Problem: The computer locks up when booting and does not see the
                         attached SCSI devices.

                    Solution:

                    a. Verify that all the SCSI devices have different ID numbers. If booting
                       the system from a device on the SCSI bus, the boot drive must have the
                       lowest ID or the highest ID, depending on the scan order.

                    b. Verify that both the ends of the SCSI bus are terminated and that the 
                       SCSI bus is terminated only at its ends.

                    c. Make sure the device driver is listed in the CONFIG.SYS file and loads
                       when the system boots.

                Problem: The device driver does not see one of the SCSI devices.

                    Solution:

                    a. Make sure the SCSI devices have different ID numbers.

                    b. Verify that both the ends of the SCSI bus are terminated and that the 
                       SCSI bus is terminated only at its ends.

                    c. Check the cable and power connections.

                    d. Check the ordering of BASEDEV= entries in the CONFIG.SYS file to be 
                       sure that the boot device loads first.

                    e. Verify that the adapter is not turned off in the SCSI BIOS 
                       Configuration Utility and that the adapter is not excluded using the 
                       /EXCLUDE command line option.

                    f. Reboot the computer.

                Problem: OS/2 attempts to install to or boot from an IDE drive instead of
                         the SCSI drive.

                    Solution:

                     The system BIOS finds the IDE drive before it finds the SCSI drive, and
                     therefore uses the IDE drive as the boot device.

                    a.  Check that the line BASEDEV=LSIMPT.ADD /V appears first in the
                        CONFIG.SYS file.

                    b.  Disable the IDE drive in the CMOS setup.

                    c.  On some hardware platforms, the IDE drive must be physically 
                        disconnected before installing to a SCSI drive.

                Problem: The following message appears at bootup:

                           "OS/2 is unable to operate your hard disk or diskette drive.
                            The system is stopped. Correct the preceding error and restart
                            the system."

                    Solution:

                    a. This problem occurs when the system is booting from a hard drive 
                       attached to an IDE bus, a SCSI disk is attached to the LSI Logic host
                       adapter, and the BASEDEV=LSIMPT.ADD /V appears in the CONFIG.SYS file
                       before the IDE device driver statement.

                       -or-

                       This problem occurs when the system is booting from a hard drive 
                       attached to the LSI Logic adapter, an IDE drive is in the system, and 
                       the IDE BASEDEV= line appears in the CONFIG.SYS file before the
                       BASEDEV=LSIMPT.ADD /V line.	

                      b. Boot the system using the floppy drive and installation diskettes to
                         the F3=Command Prompt screen. Use the TEDIT.EXE editor to edit the
                         CONFIG.SYS file. Move the BASEDEV= statements to be in the 
                         appropriate order for the system's configuration.

                      c. Restart your system.


4.0   Configuration Information 
      -------------------------------

   4.1  Command Line Options

                Using the /VERBOSE Option
                Using the /!DM Option
                Using the /!SM Option
                Using the /EXCLUDE Option
                Using the /SYNCH_RATE Option
                Using the /SYNCH_OFFSET Option
                Using the /TIMEOUT Option
                Using the /DISCONNECT Option
                Using the /QTAG Option
                Using the /WIDTH Option

            Your host adapter has a default configuration that consists of optimal values
            for operation. You can alter these default values if there is a conflict between
            device settings or if you need to optimize system performance. You can change
            some values using the Fusion MPT SCSI BIOS Configuration Utility. In addition, 
            LSI Logic Fusion-MPT OS/2 device driver have several embedded functions that you
            can access by using switches on the command line in the CONFIG.SYS file.

            Note: Values are applied in the following order:

                  o Manufacturer's settings
                  o Fusion-MPT SCSI BIOS Configuration Utility changes
                  o Command line options

                  When applying new values using the command line options, changes
                  in synchronous and wide negotiations can only decrease speed or
                  reduce width. Any changes that attempt to increase speed or width
                  are ignored.

            The options available using command line switches are described below.

            The following conventions are used:

            The term "hba" represents the logical number of a host board adapter as the 
            Verbose option displays in the HBA column. This is not the SCSI ID of the host 
            adapter. Use an hba value with no id following it to indicate all devices on an 
            adapter. The term "id" represents a SCSI target ID on the indicated adapter.

            [ ] indicates optional information

             *  indicates the pattern enclosed in the [ ] may be repeated


      4.1.1  Using the /VERBOSE (or /V) Option

             This option appears on the command line by default. It enables the display of a
             banner, version number, and SCSI bus information during startup of the system.

             Usage: /VERBOSE

             For example, to see more detailed information when booting, edit the line in the
             CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /VERBOSE

                    or

                    BASEDEV=LSIMPT.ADD /V

             To disable this feature, remove this switch from the command line.

      4.1.2  Using the /!DM Option

             This option disables use of the IBM-supplied DASD manager (OS2DASD.DMD) for the
             devices listed. The DASD manager supports direct access devices such as hard
             drives.

             Usage: /!DM<hba[:id]>[,<hba[:id]>]*

             For example, to disable OS2DASD.DMD for devices on host adapter 0 at target
             IDs 3 and 5, edit the line in the CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /!DM<0:3>,<0:5>

      4.1.3  Using the /!SM Option

             This option disables use of the IBM-supplied SCSI manager (OS2SCSI.DMD) for the
             devices listed. The SCSI manager supports SCSI tape drives.

             Usage: /!SM<hba[:id]>[,<hba[:id]>]*

             For example, to disable OS2SCSI.DMD for devices on host adapter 0 at target IDs
             3 and 5, edit the line in the CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /!SM<0:3>,<0:5>

      4.1.4  Using the /EXCLUDE (or /X) Option

             This option disables a host adapter so that the LSIMPT.ADD device driver does
             not see the adapter. This allows the system to ignore a host adapter without 
             physically removing the board, which is helpful if the adapter is causing a 
             resource conflict.

             Note: If you exclude the adapter to which the boot device is attached, you
                   cannot boot the system.

             Usage: /EXCLUDE<chip:bus:dev/func>[,<chip:bus:dev/func>]*

             Where:
                    chip is a unique identifier that indicates the LSI Logic board type. The
                    Verbose option displays a table with this value appearing in the "CHIP"
                    column.

                    bus represents the PCI bus number into which the adapter is plugged. The
                    Verbose option displays a table with this value appearing in the "BUS"
                    column.

                    dev/func is the number derived by combining the PCI device and function
                    numbers and serves as a unique board identifier. The Verbose option
                    displays a table with this hexadecimal value appearing in the "DEV/FUNC"
                    column. It may contain an A, B, C, D, E, or F as part of its value.

             For example, to exclude a host adapter with chip type F, PCI bus number 0,
             and dev/func number A0, edit the line in the CONFIG.SYS file that loads 
             LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /EXCLUDE<F:0:A0>

                    or

                    BASEDEV=LSIMPT.ADD /X<F:0:A0>


      4.1.5  Using the /SYNCH_RATE (or /SR) Option

             This option sets the maximum synchronous transfer rate (in Megatransfers per
             second) to negotiate with a particular device. The allowable values for this
             setting are 0, 5, 10, 20, 40, 80, and 160 Megatransfers per second. To turn
             off synchronous transfers, specify 0 (zero). The value set by this option
             defines the maximum transfer rate negotiated. The domain validation process
             can limit the actual synchronous speed negotiated with a device, depending on
             the device capabilities and the SCSI bus configuration. The default value is
             the fastest supported transfer rate.

             Note: The maximum synchronous transfer rates effectively double when the
                   adapter and device permit wide transfers (See the /WIDTH option).
                   For example, a synchronous transfer rate setting of 40 Megatransfers
                   per second produces a transfer rate of 80 Mbytes per second
                   if the adapter and device both allow and are set to perform wide
                   transfers.

             Usage: /SYNCH_RATE=n<hba[:id]>[,n<hba[:id]>]*

             Where: n = 0, 5, 10, 20, 40, 80, or 160.

             Two examples illustrate how to use this option:

             1. To turn off synchronous transfers to ID 3 on host adapter 0, edit the
                line in the CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /SYNCH_RATE=0<0:3>

             2. To set synchronous transfers to 80 Mbyte transfers per second on all devices
                on host adapter 1, eidt the line in the CONFIG.SYS file that loads LSIMPT.ADD
                to:

                    BASEDEV=LSIMPT.ADD /SR=80<1>

      4.1.6  Using the /SYNCH_OFFSET (or /SO) Option

             This option sets the maximum synchronous offset to negotiate with a particular
             device. The allowable values for this setting are 0 to the maximum synchronous
             offset supported by the specified adapter. The LSI Logic controller chips
             support offsets up to between 0 and 127. Refer to your host adapter user's guide
             for information on the maximum offset supported by your host adapter. Specifying
             0 for the synchronous offset value, disables synchronous transfers. The value 
             set by this option defines the maximum offset that is negotiated. The domain 
             validation process can limit this setting depending on the device capabilities 
             and the SCSI bus configuration. The default value is the maximum supported 
             offset.

             Usage: /SYNCH_OFFSET=n<hba[:id]>[,n<hba[:id]>]*

             Where: n = 0 up to maximum synchronous offset for the adapter.

             For example, to change the synchronous offset to 63 for ID 3 on host adapter 0,
             edit the line in the CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /SYNCH_OFFSET=63<0:3>

                    or

                    BASEDEV=LSIMPT.ADD /SO=63<0:3>


      4.1.7  Using the /TIMEOUT (or /T) Option

             LSI Logic Fusion-MPT OS/2 device drivers use a timeout mechanism to detect
             certain errors. When the driver issues a command to a SCSI device, a timer
             starts. If the timer expires before the command completes, the driver
             assumes that something is wrong with the device, and takes steps to recover.
             The default value for the timer is 10 seconds. If you set the value to less than
             the system has allocated for a particular device, the system ignores your
             setting. To turn off the timeout mechanism for a particular device, set the
             timer value to 0 (zero).

             Usage: /TIMEOUT=n<hba[:id]>[,n<hba[:id]>]*

             Where: n = timeout value in seconds for device (0-65535).

             For example, if you have a particularly slow device at ID 3 on host adapter 0
             and you want to extend the timeout on this device to 60 seconds, edit the line
             in the CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /TIMEOUT=60<0:3>

                    or

                    BASEDEV=LSIMPT.ADD /T=60<0:3>


      4.1.8  Using the /DISCONNECT (or /DC) Option

             SCSI devices can disconnect from the bus during an I/O transfer. This option
             controls the ability of a device to disconnect during an I/O transfer.

             Usage: /DISCONNECT=n<hba[:id]>[,n<hba[:id]>]*

             Where: n = ON allows disconnects and is the default value for all devices.
                        OFF does not allow disconnects.
             
             For example, to disable disconnects on the device at ID 2 on host adapter 0,
             edit the line in the CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /DISCONNECT=OFF<0:2>

                    or

                    BASEDEV=LSIMPT.ADD /DC=OFF<0:2>


      4.1.9  Using the /QTAG (or /QT) Option

             Queue tagging allows more than one outstanding command per SCSI device. Some
             non-compliant SCSI devices do not support queue tags. To use one of these
             devices you must disable queue tagging. The value given in the command line is
             the depth of the queue for queue tags for the indicated device(s). To disable
             queue tags, set this value to 0 or 1.

             Usage: /QTAG=n<hba[:id]>[,n<hba[:id]>]*

             Where: n = the number of queue tags allowed for a device, and is between 0 and 
             255.

             Two examples illustrate how to use this option:

             1. To turn off queue tagging for ID 3 on host adapter 0, edit the line in the
                CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /QTAG=0<0:3>

             2. To set the queue depth to 5 for all devices on host adapter 2, edit the line
                in the CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /QT=5<2>

      4.1.10 Using the /WIDTH (or /W) Option

             SCSI devices are narrow or wide devices. Narrow devices transfer data one byte
             (8 bits) at a time. Wide devices transfer data two bytes (16 bits) at a time.
             The value given in the command line option determines the maximum size of data
             transfers.  The domain validation process can limit this setting depending on the
             device capabilities and the SCSI bus configuration.

             Usage: /WIDTH=n<hba[:id]>[,n<hba[:id]>]*

             Where: n = 8 or 16.

             Two examples illustrate how to use this option:

             1. To treat the device at ID 3 on host adapter 0 as a narrow device,
                edit the line in the CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /WIDTH=8<0:3>

             2. To treat all devices on host adapter 2 treated as devices, edit the
                line in the CONFIG.SYS file that loads LSIMPT.ADD to:

                    BASEDEV=LSIMPT.ADD /W=8<2>

5.0   Unattended Mode
      -------------------------------
             
   5.1   Steps for unattended mode:

             None.
                  

6.0   WEB Sites and Support Phone Number
      ----------------

   6.1   IBM Support Web Site:
             http://www.ibm.com/pc/support

   6.2   IBM Support Telephone Numbers: 
             http://www.ibm.com/planetwide/


7.0   Trademarks and Notices
      ----------------------------

   7.1   The following terms are trademarks of the IBM Corporation
         in the United States or other countries or both:

                IBM

   7.2   Intel trademarks or registered trademarks are trademarks
         of Intel Corporation.

         Microsoft and Windows 2000 are trademarks of Microsoft Corporation in the 
         United States, other countries, or both.

   7.3   Other company, product, and service names may be
         trademarks or service marks of others.



8.0   Disclaimer
      ----------------------------

   8.1   THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF
         ANY KIND.   IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS
         OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED
         WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND
         MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
         DOCUMENT.   BY FURNISHING THIS DOCUMENT, IBM GRANTS NO
         LICENSES TO ANY PATENTS OR COPYRIGHTS.


   8.2   Note to Government Users

         Note to U.S. Government Users -- Documentation related to
         restricted rights -- Use, duplication or disclosure is
         subject to restrictions set forth in GSA ADP Schedule
         Contract with IBM Corporation.

