

QLogic QLA2X00 HAM Driver for NetWare 5.x, 6.x 
==============================================

Contents 
--------

1     OS Support
2     Adapter Support
3     Supported Features
4     Release History
5     Creating the Driver Diskette
6     Installing the Driver
6.1   Installing driver during OS installation
6.2   Installing the driver on an existing NetWare server
6.3   Forcing HDETECT to install the driver
6.4   Manually installing the driver
7     Removing the Driver
8     Driver/Adapter Parameters
8.1   System Parameters
8.2   Nvram Parameters
9     Limitations
10    Additional Notes
10.1  Novell NetWare support of QLogic HAM driver
10.2  PCI Hot Plug
10.3  256 Lun Support
10.5  Multipath support
10.6  Server Memory Recommendations
10.7  DOS Partition Recommendations
11    CD/Diskette Content
12    Contacting QLogic

======================================================================

1  OS Support 
-------------

This driver has been tested with NetWare 6.x and 5.x, 
and complies with Novell's NWPA specification.

======================================================================

2  Adapter Support 
------------------

This driver supports ISP24xx, ISP23xx and ISP63xx based adapters.

======================================================================

3  Supported Features
---------------------

* NetWare Multi-Processor Support
* NetWare PCI Adapter Hot Plug Support
* NetWare Driver Hot Replace Support
* Driver 256 Lun Support
* Driver Fabric Name Server Support
* Driver Adapter Path Lun Failover
* Driver Storage Port Lun Failover
* Driver DMI and QMS Support

======================================================================

4  Release History 
------------------

Please refer to the following: 

a.  Release notes (Release.txt) 
b.  Change history (History.txt)

======================================================================

5  Creating the Driver Diskette
-------------------------------

The NetWare driver files are located on the SANsurfer CD and on the 
QLogic website. Please check the QLogic website for the most current 
version of the driver. This section describes how to download the 
driver from the QLogic web page or the SANsurfer CD to a floppy disk.

Note:
    During NetWare OS installation, the driver must be on a
    floppy disk.  The NetWare installer does not allow
    swapping of CDs during installation.

Follow these steps to copy the driver to a floppy disk:

1.  Locate the driver on the QLogic support website
    (support.qlogic.com) or on the SANsurfer CD and click
    the Download link.

2.  Insert a blank floppy disk into the A: drive.

3.  If prompted to Open the file or Save to your computer,
    select Save and specify a temporary folder for the
    self-extracting file.

4.  From this temporary folder, execute the self-extracting
    file and specify the folder A:\NWUPDATE\DRIVERS for the
    files to be extracted.

5.  Verify that the folder A:\NWUPDATE\DRIVERS contains the
    files QL2X00.HAM and QL2X00.DDI.

6.  Insert this floppy disk into your NetWare server.

======================================================================

6  Installing the Driver
------------------------

This section describes the following installation options:

1. Installing the driver during NetWare OS installation.
2. Installing the driver on an existing NetWare server.
3. Updating the existing driver on a NetWare server.

======================================================================

6.1  Installing the driver during NetWare OS installation
---------------------------------------------------------

Perform the following steps to install the driver during the
installation of the NetWare OS:

0.  Install the QLogic adapter board in the server hardware.

1.  Insert the floppy disk and the NetWare OS install CD into
    the NetWare server, and power on the server.

2.  Follow the standard NetWare install instructions
    (provided by Novell).

3.  If the server is booting from a device attached
    by the QLogic adapter, then you must enable the
    BIOS and specify the boot device, as follows:

    a.  Start Fast!UTIL (see section 7.1).
    b.  Enable the BIOS (see section 7.2.1).
    c.  Specify the boot device (see section 7.2.2).
    d.  Exit Fast!UTIL.

    If the server is booting from a device attached
    by some adapter other than the QLogic adapter,
    then you must disable the BIOS, as follows:

    a.  Start Fast!UTIL (see section 7.1).
    b.  Disable the BIOS (see section 7.2.1).
    c.  Exit Fast!UTIL.

4.  When finished installing NetWare, restart the server.

======================================================================

6.2  Installing the driver on an existing NetWare server
--------------------------------------------------------

Perform the following steps to install the driver on an
already installed NetWare server:

0.  Install the QLogic adapter board in the server hardware.

1.  Insert the floppy disk, and power on the server and
    (if not done automatically) start the NetWare server.

2.  HDETECT automatically detects the presence of
    the adapter installed and locates and loads the driver;
    you may have to specify the path of the floppy.

    Note:
        If HDETECT fails to locate the driver automatically,
        you can do either of the following:
        
        a.  force HDETECT to install the driver (see section 6.3);
        
        b.  manually install the driver (see section 6.4).

======================================================================

6.3  Forcing HDETECT to install the driver
------------------------------------------

If HDETECT fails to detect the adapter, perform the following steps:

0.  At the server prompt, down the server and power off.

1.  Remove the QLogic adapter that you're trying to install.

2.  Power on and start the NetWare server.

3.  At the server prompt, down the server and power off.

4.  Insert the QLogic adapter removed at step 1. above.

5.  Power on and start the NetWare server.

6.  HDETECT will now automatically detect the adapter 
    and will now locate and load the driver.

======================================================================

6.4  Manually installing the driver
-----------------------------------

If HDETECT or NWCONFIG do not prompt you for storage adapter
driver installation, perform the following steps to
manually install the driver:

1.  To manually copy the driver files (QL2X00.HAM and
    QL2X00.DDI) to the following directories:

        C:\NWSERVER\DRIVERS  for NW6.x
        C:\NWSERVER          for NW5.x

    The two ways to copy the files from the floppy disk
    to one of the above directories, are as follows:

    a.  Using the NetWare Remote Manager:
        Start the NetWare Remote Manager from the NetWare GUI
        (execute STARTX to start the NetWare GUI) and  copy the
        files (drag-and-drop) from the floppy disk to one of the
        directories on the C: driver as specified above.

    b.  Using the DOS copy command:
        Open the DOS prompt (if your server does not stop at
        the DOS prompt, press the F8 key just at the same time
        that the "DOS starting..." string is printed during a
        hardware boot, and respond to all the questions by
        pressing "Y", except for the last question "SERVER ?"
        to this respond press "N"); copy the files from the
        floppy disk to one of the directories specified above.

2.  Start the server and manually load the driver for as many
    instances of QLogic adapter as are installed in the
    server hardware; for each manual load take note of the
    slot number for each instance.

3.  Start NWCONFIG and select "NCF Files Options" and select
    "Edit STARTUP.NCF File" to edit the file STARTUP.NCF;
    at the end of this file append the following load line
    once for each instance using the slot number n as noted
    in the previous paragraph:

        LOAD QL2X00.HAM SLOT=n /LUNS

    For example, if you have two QLA200 adapter boards in
    slots 2 and 3, you would append the following lines:

        LOAD QL2X00.HAM SLOT=2 /LUNS
        LOAD QL2X00.HAM SLOT=3 /LUNS

 4. Exit from the editor (saving the changes you made),
    exit from NWCONFIG, and restart the NetWare server.

======================================================================

7  Removing the driver from an existing NetWare server
------------------------------------------------------

To remove the QLogic adapter board from the server hardware,
perform the following steps to remove the driver:

0.  Remove the QLogic adapter board from the server hardware.

1.  Power on the server and (if not done automatically)
    start the NetWare server.

2.  HDETECT should automatically detect the absence of
    QLogic adapter board and should remove the driver
    load instance; if HDETECT does not remove the driver, 
    continue by performing the following procedure.
    
If you are leaving the QLogic adapter board in the server 
hardware and want to disable the driver, perform the 
following steps:

0.  Start NWCONFIG and select "NCF Files Options" and select 
    "Edit STARTUP.NCF File" to edit the file STARTUP.NCF;
    at the start of each line that loads QL2X00.HAM, insert 
    a pound character (#) to comment out that line; spaces 
    are allowed after the pound character; be sure to do this 
    on all lines that load the QLogic driver.
    
    For example, the load lines for two driver instances
    commented out with the pound (#) character are shown below:
    
        # LOAD QL2X00.HAM SLOT=2 /LUNS
        # LOAD QL2X00.HAM SLOT=3 /LUNS

1.  Exit from the editor (saving the changes you made),
    exit from NWCONFIG, and restart the NetWare server.

2.  At any time that you want to reload the QLogic driver 
    again, use NWCONFIG (as in step 0) to edit STARTUP.NCF 
    and remove the pound (#) characters that you inserted 
    in step 1; exit the editor (saving any changes you made), 
    exit NWCONFIG, and restart the server.

======================================================================

8  Driver/Adapter Parameters
----------------------------

The HAM driver has two types of optional parameters:

1.  Driver parameters (specified at driver load time)
2.  Adapter parameters (stored in the adapter nvram)

These are described in the following subsections.

======================================================================

8.1  Driver Parameters
----------------------

Driver parameters are specified on the driver load line. 

There are two categories of driver optional parameters:

Global   - the parameter acts on all driver instances;
           the value specified on the first instance 
           is used globally for all instances.

Instance - the parameter acts only on the individual 
           driver instance in which it is specified.


SLOT=n
   (Instance)
   Specifies to NetWare the PCI slot number n of the 
   adapter for which to load this driver instance.  

      LOAD QL2X00.HAM SLOT=3

/LUNS
   (Instance)
   Specifies to NetWare to scan for all luns during the 
   load of this driver instance (otherwise NetWare  
   only scans for lun zero devices); the scanned lun 
   number range is 0 to (n - 1) where n is specified 
   by the /MAXLUNS=n option.

      LOAD QL2X00.HAM SLOT=3 /LUNS
       
/ALLPATHS
   (Global)
   Disables adapter failover and reports to NetWare all 
   devices on all adapter paths; this allows upper layer 
   modules to do failover across a NetWare server's 
   multiple adapters. 
 
      LOAD QL2X00.HAM SLOT=3 /LUNS /ALLPATHS\
      
/ALLPORTS   
   (Global)
   Same as function as /PORTNAMES (see next option).
   
      LOAD QL2X00.HAM SLOT=3 /LUNS /ALLPORTS
   
/PORTNAMES
   (Global)
   Disables device port failover on each adapter and 
   reports all ports as individual devices to Netware;
   this allows upper layer modules to do failover across 
   a storage subsystem's multiple ports; internally 
   manages devices by portname rather than nodename; 
   this is required when storage luns do not have 
   a 1:1 correspondence across portnames. 
   
      LOAD QL2X00.HAM SLOT=3 /LUNS /PORTNAMES

/GANXT
   (Instance)
   Use GANXT sequence rather than single GNNFT to query 
   the fabric name server; used for compatibility with 
   name servers that do not support the GNNFT command.
   
      LOAD QL2X00.HAM SLOT=3 /LUNS /GANXT

/LOGINRETRY=n
   (Global)
   Sets the fabric port login retry count to n;
   when a fabric port login fails, it is retried 
   up to n times; each retry is delayed one second.

      LOAD QL2X00.HAM SLOT=3 /LUNS /LOGINRETRY=n

/LINKDOWN=n
   (Global)
   Sets the link down timeout period to n seconds;
   this is the timeout period for adapter link down; 
   the expiration of this timeout triggers adapter 
   path failover if multiple paths are available.

      LOAD QL2X00.HAM SLOT=3 /LUNS /LINKDOWN=n

/PORTDOWN=n
   (Global)
   Sets the port down timeout period to n seconds;
   this is the timeout period for storage port down; 
   the expiration of this timeout triggers storage 
   port failover if multiple ports are available.

      LOAD QL2X00.HAM SLOT=3 /LUNS /PORTDOWN=n

/FAILBACK=n
   (Global)
   Sets the failback delay time period to n seconds;
   this is the time period that elapses when some 
   port update has event occurred before any attempt 
   is made to failback paths/ports.

      LOAD QL2X00.HAM SLOT=3 /LUNS /FAILBACK=n

/BACKOFF
   (Global)
   Disables failback of I/O after a broken link or a 
   broken port has been restored and made operational.
   
      LOAD QL2X00.HAM SLOT=3 /LUNS /BACKOFF
      
/IGNCFG
   (Global)
   Avoids reading the configuration file QL2x00.CFG, 
   and allows all devices to be reported to NetWare. 
   This file is located in the default DOS directory 
   (C:\NWSERVER), and is written by QLogic SANsurfer 
   software  or the CFG.NLM test tool.
      
      LOAD QL2X00.HAM SLOT=3 /LUNS /IGNCFG

/REQCFG
   (Global)
   Requires reading the configuration file QL2x00.CFG, 
   and ignores all devices not specified therein, or 
   ignores all devices if this file does not exist.
   This file is located in the default DOS directory 
   (C:\NWSERVER), and is written by QLogic SANsurfer 
   software or the CFG.NLM test tool.
      
      LOAD QL2X00.HAM SLOT=3 /LUNS /REQCFG

/FDMI
   (Instance)
   Registers this adapter's FC-4 symbolic nodename 
   with the fabric name server for FDMI.

      LOAD QL2X00.HAM SLOT=3 /LUNS /FDMI
     
/HPLEDS
   (Instance)
   Enables HP LED control mode.  With this option, 
   the LEDs will blink according to HP specification.
   
      LOAD QL2X00.HAM SLOT=3 /LUNS /HPLEDS

/CONSOLE
   (Global)
   Sends system alerts to the server console when  
   failover and failback events occur.

      LOAD QL2X00.HAM SLOT=3 /LUNS /CONSOLE

/FIRSTLID=n
    (Instance)
    Sets the loop id of the first logged in device to 
    the value n (hexadecimal); used for debugging.
    
      LOAD QL2X00.HAM SLOT=3 /LUNS /FIRSTLID=B7
      
/ELEVATOR=n
    (Instance)
    Sets the elevator threshold to n; Netware uses this 
    value to determine when to do scatter/gather list 
    sorting.
      
/MAXLUNS=n
   (Global)
   Sets the maximum number of luns allowed during the 
   lun scan; the range of luns searched is 0 to (n-1).
   
      LOAD QL2X00.HAM SLOT=3 /LUNS /MAXLUNS=256

/SKIPREPORT
   (Instance)
   Avoids executing the SCSI Report Luns command during 
   lun scanning; otherwise if this option is not used, 
   the information returned by the Report Luns is used 
   to optimize the lun scan by doing SCSI Inquiries to 
   the luns listed in the Report Luns information only.
   
      LOAD QL2X00.HAM SLOT=3 /LUNS /SKIPREPORT
      
/INQUIRY
   (Instance)
   Force SCSI Inquiry commands to be used during the 
   lun scan regardless of the luns listed by the SCSI 
   Report Luns command; the existence of a particular 
   lun is determined solely by the results of the 
   Inquiry to that lun.

   
      LOAD QL2X00.HAM SLOT=3 /LUNS /INQUIRY

/COMPLEXTAG
   (Instance)
   Enables SCSI complex tag queuing; the hacb preserve 
   order control flag maps to ordered queue, and the hacb 
   priority control flag maps to head of queue; otherwise 
   if the absence of these hacb control flags maps to 
   simple queue tag.

      LOAD QL2X00.HAM SLOT=3 /LUNS /COMPLEXTAG

/STARTUNIT
   (Instance)
   Sends the SCSI Start Unit command to each lun during 
   the lun scan; on some multiple port RAID subsystems, 
   this may cause lun ownership to transfer across ports.
   
     LOAD QL2X00.HAM SLOT=3 /LUNS /STARTUNIT

/XRETRY=n
   (Instance)
   Extends the retry count to n for any IO command that 
   experiences failure with SCSI sense info SK/ASC/ASCQ 
   code in this list: 2/04/01, 6/8B/02.
      
      LOAD QL2X00.HAM SLOT=3 /LUNS /XRETRY=10

/XTIMEOUT=n
   (Instance)
   Extends the timeout value to n seconds for any IO 
   command that experiences a timeout (ie. held by the 
   storage device for a long period of time).

      LOAD QL2X00.HAM SLOT=3 /LUNS /XTIMEOUT=120
     
/QUALIFIED
   (Instance)
   Extends the Inquiry data lun present test to allow 
   RAID subsystem luns to be filtered as follows:
      Luns returning 20 XX are reported,
      Luns returning 20 00 are ignored.

      LOAD QL2X00.HAM SLOT=3 /LUNS /QUALIFIED
      
/LUNZERO
   (Instance)
   Reports to NetWare lun 0 regardless of its actual 
   existence as determined by the response to the SCSI 
   Inquiry command, as long as the port was logged in.
   This is used for RAID subsystems that do not report 
   any luns on a port until the subsystem is configured 
   for the first time.
 
      LOAD QL2X00.HAM SLOT=3 /ALLPATHS /LUNZERO
 
======================================================================

8.2  Adapter Parameters
-----------------------

The adapter parameters are stored in the adapter's nvram;
these are also referred to as adapter nvram parameters.

The adapter nvram parameters are modified by entering Fast!UTIL 
during server hardware boot (press ALT-Q when prompted by the adapter).

In Fast!UTIL, first select the host adapter, and then select 
"Configuration Settings".

The following headings with corresponding parameters are displayed:

    Host Adapter Settings
    ---------------------
    +  Frame Size
    :  Loop Reset Delay
    +  Adapter Hard Loop Id
    +  Hard Loop Id
    
    Advanced Adapter Settings
    -------------------------
    +  Execution Throttle
    +  Fast Command Posting
    :  >4GB Addressing
    +  Luns Per Target
    +  Enable LIP Reset
    +  Enable LIP Full Login
    +  Enable Target Reset
    +  Login Retry Count
    +  Port Down Retry Count
    +  Link Down Timeout
    +  Drivers Load Risc Code
    =  Enable Database Updates
    :  Disable Database Load
    :  IOCB Allocation
    :  Extended Error Logging
        
    Extended Firmware Settings
    --------------------------
    =  Extended Control Block
    @  RIO Operation Mode
    +  Connection Options
    @  Class 2 Service
    @  ACK0
    +  Fibre Channel Tape Support
    +  Fibre Channel Confirm
    @  Command Reference Number
    @  Read Transfer Ready
    @  Response Timer
    @  Interrupt Delay Timer
    +  Data Rate
    

    Key:
    +   Used by HAM driver (change effects behavior)
    @   Default value expected by HAM driver (do NOT change)
    =   Overridden by HAM driver (change has no effect)
    :   Not used by HAM driver (change has no effect)


NOTES
-----

0.  The QLA200 does not use any of these nvram parameters.

1.  Enable both of the following to support FC-Tape 
    (see "Extended Firmware Settings" above):

        Fibre Channel Tape Support
        Fibre Channel Confirm
        
2.  The timeout for port down is set [in seconds] by
    (see "Advanced Adapter Settings" above):

        Port Down Retry Count
        
    The timeout for link down is set [in seconds] by
    (see "Advanced Adapter Settings" above):

        Link Down Timeout
        
    For best results, set these parameters to 15 or 20 (seconds).
 
======================================================================

9  Limitations
--------------

Refer to the following subsections below:

a.  10.3  256 Lun Support
b.  10.6  Server Memory Recommendations

======================================================================

10  Additional Notes
--------------------

10.1  Novell NetWare support of QLogic HAM driver
-------------------------------------------------

The following drivers are provided with Novell NetWare for supporting 
various Fibre Channel devices through the Fibre Channel HAM driver:

  SCSIHD.CDM    SCSI hard disk device driver
  SCSICD.CDM    SCSI CD-ROM device device driver
  SCSIMO.CDM    SCSI magneto-optical device driver
  NWTAPE.CDM    SCSI tape device driver (replaces SCSI2TP.CDM)

  After the HAM driver is loaded, the CDM drivers are loaded
  automatically by NetWare as needed.

NOTE: Contact Novell for any missing CDM drivers that you need.

======================================================================

10.2  PCI Hot Plug
------------------

NOTE: 
    This procedure addresses only the driver-related portion of the
    PCI Hot Swap operation. The server must have PCI slots that are 
    capable of being powered up and down independently. Depending 
    on the server platform, this entire operation may be controlled 
    by a platform specific software module supplied by the platform 
    vendor. In such a case, these commands are issued directly to 
    the driver and do not require the user to enter them. 

PCI Hot Plug works by unloading a specific instance of the driver 
associated with a specific host adapter. It allows a failed adapter 
to be removed and replaced by an adapter of the same type without 
disrupting the operation of other adapters of the same type. The 
steps necessary to perform a hot swap operation are listed below. 

1. Type "List Devices" or "List Storage Adapters" at the server 
   console.  A list similar to the example below is displayed:

       [V591-A0-D0:0] SCSI HARD DISK
       [V591-A0-D1:0] SCSI HARD DISK
       [V591-A1-D3:0] SCSI HARD DISK
       [V591-A1-D4:0] SCSI HARD DISK

2. To remove host adapter instance 0 controlling the first two
   hard drives, enter the following command:

       REMOVE STORAGE ADAPTER A0

3. After the host adapter has been replaced, the new adapter is made  
   operational by loading another instance of the driver using the
   normal load command syntax. For example:

       LOAD QL2X00.HAM SLOT=3

======================================================================

10.3  256 Lun Support
---------------------

To find all luns, load the driver with the /LUNS option. 

For example:

    LOAD QL2X00.HAM SLOT=3 /LUNS

If the driver is already loaded, use the command SCAN ALL LUNS at 
the server console prompt to find all luns (new and existing luns).

To specify the maximum lun number, use the /MAXLUNS=n driver load option, 
or set the "Luns Per Target" parameter in Fast!Util to the required 
number of luns per target ID (see ** below); if not using multiple luns 
per target, set this parameter to 0 (the driver treats this as 1 lun per 
target).

** To set the "Luns Per Target" parameter:

1.  Reboot the hardware, and press ALT-Q when the QLogic banner appears.
2.  Select the desired adapter.
3.  Select Configuration Settings.
4.  Select Advanced Adapter Settings.
5.  Select Luns Per Target and change the luns range.
6.  Press ESC twice and select Save.
7.  Press ESC again and select Reboot. 


NOTE:
    The largest number of luns per device that NetWare supports is 256;
    therefore the largest value of n specifiable by /MAXLUNS=n is 256; 
    this is purely a limitation of NetWare.

======================================================================

10.5  Multipath support
-----------------------
The driver by default presents only one path to NetWare if multiple
adapters and/or multiple ports are connected to the same storage device. 
This prevents volumes from being multiple mapped and causing mount 
segment corruption.

To disable HAM multipath mode and allow NetWare to see all paths, load
the driver with the /ALLPATHS and /ALLPORTS options, as shown here:

    LOAD QL2X00.HAM SLOT=3 /LUNS /ALLPATHS /ALLPORTS

The /ALLPATHS and /ALLPORTS options are required if an upper layer 
module is going to handle failover (it expects to see all paths).

If you want to use NetWare Multi-Path IO (MPIO), you need to ensure 
that STARTUP.NCF contains the following line before loading any 
drivers:

    SET MULTI-PATH SUPPORT = ON

(it is recommended that you have this line regardless of whether 
you want NetWare MPIO failover or QLogic HAM failover);

You must also ensure that the latest support packs are installed.

When deciding whether to use NetWare MPIO failover or HAM failover, 
use the following table to consider the available possibilities:


   /ALLPATHS  /ALLPORTS           HAM              MPIO
    present     present         Failover         Failover
    
       No         No         adapter & port        none
                                 (1x1)             [1]
       
       No         Yes         adapter only       port only
                                 (1xN)             [N]
       
       Yes        No           port only        adapter only
                                 (Mx1)             [M]
       
       Yes        Yes            none          adapter & port  
                                 (MxN)            [MxN]
       

   Assuming there are M adapters and N storage ports:
       
      a number shown in parentheses () is the number of 
      instances that the HAM reports each device to NetWare; 
          
      a numbers shown brackets [] is the number of paths 
      per device that NetWare displays in response to the 
      command LIST FAILOVER DEVICES.
       
   In other words: 

      /ALLPATHS disables HAM adapter "path" failover 
      (and reports all adapter paths for each device;
      all adapters report the same devices).
   
      /ALLPORTS disables HAM storage "port" failover 
      (and reports all storage ports for each device 
      on the reporting adapter(s)).
      
   Note: 
   
      /ALLPORTS and /PORTNAMES are different names for the same option.      

======================================================================

10.6  Server Memory Recommendations
-----------------------------------

In general, at least 512MB of memory is recommended.

For large numbers of volumes, at least 1024MB is recommended.
 
======================================================================

10.7  DOS Partition Recommendations
-----------------------------------

In general it is recommended that you load DOSFAT.NSS in STARTUP.NCF 
to allow NetWare to access the DOS partition using the attaching HAM 
driver rather than the DOS INT 13 interface.

This allows the attaching HAM driver to apply its features to 
any I/Os to the DOS partition (e.g. the QL2X00.HAM driver provides 
a failover mechanism which the HBA BIOS does not provide).

The HAM driver and the corresponding CDM driver must be loaded prior 
to loading DOSFAT.NSS; for example, STARTUP.NCF would contain:

   LOAD SCSIHD.CDM
   LOAD QL2X00.HAM /LUNS
   LOAD DOSFAT.NSS
   
You can also do this when the DOS partition is IDE attached.

======================================================================

11  CD/Diskette Content
-----------------------

The CD/diskette contains the following files:

QL2X00.DDI     NetWare driver installation description file
QL2X00.HAM     NetWare host adapter module (HAM) driver
RELEASE.TXT    Release notes for this version
README.TXT     This file

The CD/diskette may additionally contain the following files:

QL2X00D.HAM    NetWare debug driver (prints on screen)
QL2X00D.DDI    NetWare debug driver installation description file
HISTORY.TXT    NetWare driver change history

The CD/diskette may also contain the following files:

CFG.NLM        Failover configuration tool
CFG1.TXT       CFG.NLM command line options
CFG2.TXT       CFG.NLM failover configuration guide
CFG3.TXT       CFG.NLM failover configuration dictionary

======================================================================

12  Contacting QLogic
---------------------

Please visit QLogic's website http://www.qlogic.com where you will 
find product information, our latest Novell certified drivers, and 
links to technical assistance.

We thank you for using QLogic products.

======================================================================

Copyright (c) 2000 - 2005 QLogic Corporation.  All rights reserved. 

======================================================================



