
               
               Emulex Corporation


           Light Pulse Family Host Adapter
              BootBIOS Release Notes

                    1.61A2

                August 20, 2002





The current BIOS provides x86 boot capability through the use of INT13 system 
BIOS calls. This Emulex BootBIOS currently supports:

*  Multi-topology: Fabric Point to Point, FC-AL Private Loop, FC-AL Public Loop 
*  Multi-initiators: Up to 8 adapters in a system
*  Multi-LUNs: Up to 256 LUNs 
*  Multi-boot: Complies with the BIOS Boot Specification (BBS).
*  EDD (Enhanced Disk Drive Services): it supports both EDD 3.0 and EDD 2.1 
     depending on a selection in the Emulex BIOS Utility. 
*  Boot fail over feature: supported by BIOS version 1.20 or later. There 
     are eight boot entries that can be configured. If the first boot entry fails 
     for whatever reason, it will attempt to boot the other entries in order.


This README applies to the following boot products:

   SB161A2.PRG        Lp7000 BIOS version 1.61A2
   DB161A2.PRG        Lp8000 BIOS version 1.61A2
   CB161A2.PRG        Lp9000 BIOS version 1.61A2
   HB161A2.PRG        Lp9802 BIOS version 1.61A2
   QB161A2.PRG        Lp850 BIOS version 1.61A2
   RB161A2.PRG        Lp950 BIOS version 1.61A2
   LB161A2.PRG        Lp982 BIOS version 1.61A2


Although a specific BIOS file for the LP6000 does not exist, all current 
versions of BIOS will scan and process any LP6000 adapters in the system.



            *****  Important Notes  ******

(1) BIOS downloading

This version of BIOS image has increased in size from 42K to 44K. On some HBAs,
it might fail during the downloading of the .prg file only if there is not enough
space. One way to correct the problem on those controllers is to first download
an .AWC image which does not contain boot code (for example: dd380a0.awc). This
will clear enough space to allow the boot .PRG file to be downloaded.

(2) BIOS was not activated (enabled)

If the adapter BIOS is not activated (enabled) by LP6DUTIL or other Emulex driver
utility, the adapter will not be configured.  Also, a "No BIOS support" message
will be displayed next to this adapter in the Emulex BootBIOS Utility.  The user
must use LP6DUTIL or other Emulex driver utility to activate (enable) the BootBIOS
in order to make this card bootable.


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

1. History:


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

                           1.61A2
Problems Fixed, Features added or Other Updates Since 1.61A1:

*  There should be a update for the data valuable after each INT13 call, because INT13
   call has reset function.  161a1 did not add the update data valuable on the last 
   INT13 call and cause boot fail on DL760 with MSA1000.  The next 1.61a2 release will
   takes care this boot failure problem.


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

                           1.61A1
Problems Fixed, Features added or Other Updates Since 1.61A0:

* Corrected the image header ID for LP850.

* Added the ALPA parameter update to NVRAM.

* Added the new spinup banner display when spinup delay is enabled.

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

                           1.61A0
Problems Fixed, Features added or Other Updates Since 1.60A7:

* System will not pass post if either Lp9802 or Lp982 installed with Lp7000, this
  version of BIOS fixed this not pass post problem.

* System will display second banner when the Pegasus Lp982 was installed, because 
  there isn't any device tables in the code.  This new release was fixed.

* Add the auto detect feature to automatically detect the format of boot sector
  (32 sector or 63 sector format) when there is MSA1000 array controller present.
  Also, add the option to either disable or enable this auto sector detect feature,
  the default is auto enable.
 
* Update the copyright date in all boot bios banner to 2002.

* Changed the boot order option to new behave which load the HBA from latest
  LP9802 down to oldest LP6000.

* Changed the new Spin-up delay behave which check for the device presence first
  if the device was ready, boot immediately, otherwise wait for spin-up delay.

***********************************************************************************  
    
                           1.60A7

Problems Fixed, Features added or Other Updates Since 1.60A6:

* On the first Int 13 call, if there was an link down event error happened,
  The BIOS will mark the adapter not ready. As a result, it would fail to
  boot. This version of BIOS fixed this problem.

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

                           1.60A6

Problems Fixed, Features added or Other Updates Since 1.60A5:

* If user hit <Alt E> to enter BIOS Utility, it would issue Flogi  first before go 
  into the BIOS Utility. In other words, it will issue Flogi right after the Link
  is up. This is a clean way to implement Flogi in BIOS Utility.

* Cleaned up Link Attention discovery in BIOS Utility under Fabric environment.

* With Spinup Enabled. If a user select more than one configured boot device, it would
  not continue scan the rest of boot entries if the first boot entry (primary boot 
  entry) failed. This version of BIOS will continue scan with the rest of boot entries
  until it successfully scan the configured device.

* Fixed runtime Int13 call auto topology flags. As a result, it could always successful 
  bring the link up during the first Int13 call with auto topology protocol.


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

                           1.60A5

Problems Fixed, Features added or Other Updates Since 1.60A4:

* Make CT timeout to be 2 * Ratov instead of 1 sec before. Also, the resolution interval is 
  100msec. In other words, every 100 msec, it will check CT payload, timeout after 2 * Ratov.

* Remove third Test Unit Ready during the disk scan.

* If sector number is 0 for any Int 13 read, write, or verify, it should return ah = 04, 
  (Invalid sector) with carry set.

* if a LBA with input 0xffffffffffffffff for ext int 13 read, write, or verify, it should
  return ah = 04 (Invalid sector) with carry set.

* Increase Start Unit Command timeout to 45 sec from 15 sec before.

* If there were an Logout from a Raid box with multiple ports attached to a HBA and they were 
  configured as boot devices, DID variable got corrupted. As a result, Plogi would login to 
  a wrong DID. This version of BIOS fixed the problem.

* Reduced Io_sequence timeout value if ABTS happened. In this way, it would reduce Boot time 
  if a Raid Box issued a logout during SCSI commands.


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

                         1.60A4

Problems Fixed, Features added or Other Updates Since 1.60A3:

* Finished debugging Start Unit Option in BIOS Utility. This option is used to issue a SCSI
  start unit command to a device.

* Fixed a bug in Environment Variable.

* During BIOS Utility device scanning, if a device gives a check condition to the first 
  report lun, it will retry again. 

* A bug in Int 13 function 15: read disk type. This version will give the correct number
  of 512-byte sectors.

* If a head number to Regular Int 13 call is greater than 255, it will return error code
  sector not found (0x04).

* Retry 2 more times if Flogi sequence failed. This happen when there are too many ports 
  traffic on Brocade switch.



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

                         1.60A3

Problems Fixed, Features added or Other Updates Since 1.60A2:

* If the adapter BIOS is not activated (enabled) by LP6dutil or other O.S. utility, 
  this adapter would not be configured. Also, there is "No BIOS support" message next 
  to this adapter in BIOS Utility. User must use LP6dutil or other O.S. Utility to 
  activate (enable) the BIOS.

* Fixed an endian issue in handling the Environment Variable. 

* For EDD get parameter, this version of BIOS fixed geometry formula to return the correct 
  disk size, which was derived from SCSI read capacity.

* Add one more option in Auto Topology:
  (a) Auto Topology (Default): Loop first, if it fails, it will try Fabric point to point.
  (b) Auto Topology: Fabric point to point first, if it fails, it will try Loop.
  (c) FC-AL (Loop) only
  (d) Fabric point to point only

* When we have two adapters with either LP850 or LP950 in the system. If we configure both
  of the adapters to have a boot disk, the link on the first adapter will not come up with
  the first int13 call. This version of BIOS fixes this problem.  

* When a user configured a boot device via D_ID, it could not be saved in the flash (this
  bug only existed in 1.60 BIOS). This version of BIOS fixes this problem.



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

                         1.60A2

Problems Fixed, Features added or Other Updates Since 1.60A1:

* Change auto-topology: it will try loop first, if it fails, it will try 
  Fabric point to point. The default is auto-topology in the Topology Selection.

* Cleaned up selection menu if Start Unit Command was enabled. 



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

                         1.60A1                    

Problems Fixed, Features added or Other Updates Since 1.60A0:

* Add an option in the BIOS Utility to Enable or Disable the Environment Variable. 
  The default is disabled. 


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

                         1.60A0

Problems Fixed, Features added or Other Updates Since 1.53A1:

* Support Volume set addressing mode

* When some arrays are connected to a switch, they can issue a logout to the host
  causing new commands sent to the array to fail. This version of BIOS added the 
  capability to log back in to the array and continue the boot process.

* Implemented auto-topology: it tries Point to point first, if it fails, it will try 
  FC-AL.

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



2. BIOS Load Procedure

The Light Pulse BIOS is distributed as a .PRG file.  This file may be downloaded 
to the Adapter using the firmware upgrade procedure with the DOS based 
utility LP6DUTIL.EXE, or the appropriate Emulex driver utility, such as:

     *  LPNTUTIL Mini-port Driver Utility
     *  Emulex Configuration Tool for Port Driver

Please refer to the user manual for details on using these utilities.


2.1 BIOS Upgrade Procedure with LP6DUTIL Version 8 (LP6000 to LP9402DC HBAs)

(1) Install the adapter to be upgraded into a PCI system capable of running
    DOS (see Hardware Compatibility for a recommended configuration).

(2) Boot the DOS PCI system.

(3) Run LP6DUTIL (found in the firmware distribution on the released diskette,
    CD-ROM, or from www.emulex.com).  Ensure that LP6DUTIL is at least revision
    8.6a4 or greater before proceeding.  Some HBAs may require later versions.

(4) From the Main Menu, Select Option 5 (Maintenance)
 
(5) From the Maintenance Menu, Select Option 1 (Update Firmware)
    The program will prompt for the file name to download.  Specify the drive and 
    path where xBxxxx.PRG (the appropriate boot file for your HBA model)
    can be found. 

     This image file is downloaded into the HBA's FLASH memory.  This operation
     should take less than 2 minutes to complete.

     NOTE:  The update operation must not be interrupted or the FLASH may become 
     corrupted.  This can lead to a permanent self-test failure, which usually
     results in the LEDs not lighting after power up.  If this occurs, the adapter
     must be returned to Emulex for FLASH reprogramming.

(6) The Adapter must be re-initialized to start using the upgraded BIOS.  
    Perform a Hard Reset to the system or cycle the power.

     NOTE:  Each newly installed Host Adapter must have BIOS activated using the 
     DOS utility (LP6DUTIL). Until BootBIOS is enabled in this manner, you will
     not see the Boot BIOS message during boot. Once BootBIOS is activated,
     a message will appear during the boot sequence asking you press the <Alt-E>
     key to enter the Emulex BIOS utility or the <s> key to skip BootBIOS.


2.1.1  To Activate Emulex BootBios from LP6DUTIL Version 8:  

     Note: BootBIOS is automatically activated when it is downloaded through
     LP6DUTIL.

     From the LP6DUTIL Main menu,

       1. Type <5> and press <Enter> to open the Maintenance menu. 
       2. Type <3> and press <Enter> to open the Enable/Disable BootBIOS menu.
            If "Enable BootBIOS for Host Adapter" is displayed,
            type <1> and press <Enter>.
            If "Disable BootBIOS for Host Adapter" is displayed,
            type <0> and press <Enter>.
       3. Type <0> and press <Enter> to return to the previous menu. 
       4. Type <7> and press <Enter> to exit the LP6DUTIL program. 


2.2  BIOS Upgrade Procedure with LP6DUTIL Version 9 (LP6000 to LP9802 HBAs)

(1) Install the adapter to be upgraded into a PCI system capable of running
    DOS (see Hardware Compatibility for a recommended configuration).

(2) Boot the DOS PCI system.  Make sure that there are no other programs loaded
    (such as smartdrive) which occupy DOS memory and may not allow enough room
    for the LP6DUTIL program to initialize.

(3) Run LP6DUTIL (found in the firmware distribution on the released diskette,
    CD-ROM, or from www.emulex.com).  Ensure that LP6DUTIL is at least version
    9.0A9 or greater before proceeding.  Some HBAs may require later versions.

(4) From the main menu, press and hold down the ALT key and press L.
    The "Flash" drop-down menu should appear.

(5) Press "D" for the Download menu.  The "Download Image" box should appear.

(6) Choose the adapter and the BootBIOS file you wish to download, then
    select "OK".  The BootBIOS file should download.

    There are other ways to download files to one or more HBAs using LP6DUTIL
    version 9.  Please consult the LP6DUTIL.DOC file for further information.


3. BIOS Limitations and Default Configuration


3.1 Limitations and Features

Below is a list of the current preliminary Light Pulse BIOS limitations and 
features.

*  In order to work properly, this version of BIOS has to work with Firmware 
   2.22 or above for LP6000 and LP7000, firmware 1.01 for LP850 and firmware 
   2.81 or above for LP8000.

*  For multi adapter support, you must use the Windows NT Port Driver version
   1.24A2 or above.
  
*  If there are any hardware changes such as replacing drives or re-configuring
   a Fabric switch environment, make sure to also re-configure the BIOS using
   the Emulex BIOS Utility.

*  If the message "Retry this adapter!!" was displayed during boot-up, 
   please check the hardware configuration or re-configure BootBIOS using the
   Emulex BIOS Utility.

*  The "Configure Legacy Private Loop" option has been removed.  We suggest that
   you re-configure any boot device that was configured using the "Legacy
   Private Loop" options on previous versions of Boot BIOS.

*  BootBIOS will allow any number of Light Pulse adapters in a system.  It can
   support any combination of LP7000, 8000, 9000, 850 and 950 adapters. However,
   only the first eight adapters can be configured as the boot adapters; any
   adapter after the first eight will not be visible during the boot process.

*  Multi-initiators on different systems in a loop must be connected through 
   hub(s).

*  You must press <Alt-E> during system boot-up to enter the Emulex BIOS Utility.

*  If a system does not have Multi-boot (BBS), the Boot disk (drive C:) 
   is determined by the first configured boot entry (Primary boot entry).
   It can be on the first adapter or the second adapter. If you want to 
   configure it on the second adapter, do not configure any boot entry on 
   the first adapter.

      Example 1:

      Adapter 1: boot_entry0, boot_entry1.
      Adapter 2: boot_entry2, boot_entry3.
   
      Drive C: boot_entry0

      Example 2:

      Adapter 1: 
      Adapter 2: boot_entry2, boot_entry3.
   
      Drive C: boot_entry2


*  If a system supports Multi-boot (BBS), the Boot disk (drive C:) will be
   the first entry in Multi-boot on system BIOS setup Menu. The list of 
   entry, that are export to Multi-boot menu, are determine by the list
   of configured boot entry in the BIOS utility. For example:

      Adapter 1: boot_entry0, boot_entry1.
      Adapter 2: boot_entry2, boot_entry3.

   The order of boot entries that are exported to the Multi-Boot (BBS) are:
   boot_entry0, boot_entry1, boot_entry2 and boot_entry3. However, Multi-
   boot can overwrite this order with: boot_entry2, boot_entry0, boot_entry1
   and boot_entry3. In this case, Drive C: is boot_entry2.


*  A maximum of 256 LUNs are supported (LUN 0 through 255) per target ID 
   (DID or ALPA). These 256 LUNs can be scanned in different stages using the
   BIOS Utility. However, only 8 entries can be seen during BIOS initialization.

*  For FC-AL, the adapter's ALPA, PCI bus number and PCI device number can be 
   viewed on the welcome screen or in the BIOS Utility menu. In this way, 
   the user can know exactly which adapter is in which PCI slot in the system.

*  For Fabric Point to Point or Public Loop, the S_ID (source id), PCI bus
   number and PCI device number will be printed on the screen. 

*  In the Fabric environment, the maximum number of devices (DID) is 90 when 
   configuring the boot device in the Emulex BIOS Utility.

*  In a Private Loop environment, the maximum number of devices (ALPA) is 99
   when configuring the boot device in the Emulex BIOS Utility.



3.2  Default Configuration

*  To reset the selected adapter to its defaults, press <d> in the Parameter 
   menu of the Emulex BIOS Utility. 

*  Boot BIOS is disabled by default. In order to use Emulex Boot BIOS, you
   must first make sure it is enabled through the LP6DUTIL or other Emulex
   utility (see above), and then you must enter the Emulex BIOS Utility to
   fully enable the Emulex BootBIOS.

*  In "Configure Boot Devices" option, Loop is the default mode. BIOS will 
   look for a Public Loop first,. If a Public Loop is not detected, it will
   look for a Private Loop.

*  For "Configure Boot Devices" option, the eight boot entries will be zero 
   when they are reset to default by the <d> key.

*  For FC-AL, each host adapter has a default ALPA of 01 (Hex).

*  If more than one adapter is in the system with the same PCI bus number, and 
   each has a Boot drive attached, the first PCI-scan adapter will be the BOOT 
   adapter.  The first adapter is usually the lowest PCI slot in the system.  
   This information can be viewed from the BIOS Utility.

*  The default PLOGI Retry Timer setting is 0 (no retry).  It can be changed
   to 50, 100, or 200 milliseconds.

*  Spinup delay is disabled by default.

*  Auto Scan is disabled by default.

*  All the above default settings can be changed in the BIOS Utility. All 
   adapters or BOOT drives can be configured to different ALPAs other than 
   their default values.


*  EDD 3.0 was disabled in default. This is because current Win2K does not 
   support EDD 3.0 and it could hang during the Win2K installation on regular 
   Pentium series systems.


*  Environmental variables are disabled by default.

*  The Start Unit command is disabled by default.


4. BIOS Utility


You press <Alt E> during system boot to enter the Emulex BIOS Utility.
Each menu is described below.

4.1 Main Menu

This menu lists all the adapters in the system and the BIOS version number.  
User can enter the number to select the particular adapter.

4.2 Adapter Menu

*  The adapter is displayed by ALPA for FC-AL, PCI bus number and device number.

*  The screen also displays the I/O base address, HBA firmware version, 
   port name and node name of each adapter.

*  <d> is used to reset the selected adapter to default value while in 
   the BIOS Utility.

*  <x> is the only way to exit the BIOS Utility and reboot the system.


4.2.1 Configure Boot Devices

Fail-over booting has been available since BIOS version 1.20. There are 
eight boot entries that can be configured. If first boot entry fails for 
whatever hardware reason, the system will be able to boot from the second
or subsequent boot entries.

Currently, this menu supports FC-AL: Private Loop and Public Loop, and Fabric 
Point to point. If the board is configured as FC-AL, it will attempt Public
Loop first.  If Public Loop fails, it will attempt Private Loop operation.

Configure Boot Devices will accept Fabric, Public Loop and Private 
Loop devices. On Private Loop, it can boot by either WWPN or an ALPA.
On Fabric, it can boot by WWPN or DID.

The first entry is the primary boot entry.  This entry must be filled in
before filling in any of the other entries.

There are 8 boot entries with the first one as the primary boot entry. 

*  If you select any entry, another menu will be displayed:

      00. Clear selected boot entry!!
   This is used to clear the selected boot entry.
 
      01. DID or ALPA, WWPN and disk information.
   The LUN will stop on the first LUN found in this particular target device.

      02. same as 01 with different target device.

*  If user selects any two-digit number such as 01, then a Pop up menu will be
   shown. Enter the first two digits of the LUN to be scanned.

*  A list of 16 LUNs can be entered, starting with LUN that was
   entered in the above paragraph.

      In front of each entry, B#D or B#W specifies the Boot entry number with
      boot via DID or WWPN. For example, B1D means Boot entry number one will
      boot via  DID. B2W means Boot entry number two will boot via WWPN.

      Enter the two digit LUN.

      If any two-digit number is entered, another Pop up menu will be shown. 

        1. Boot this device via WWPN
        2. Boot this device via DID

      If you select <1>, the WWPN of the earlier selected entry will be
      saved in the Flash. However, during initial BIOS scan, it will issue a
      Name Server Inquiry GID_PN (Get Port Identifier); then, based on this
      DID, do the rest of the scanning.

      If you select <2>, the DID of the earlier selected entry will be saved 
      in the Flash.


4.2.2 Configure This Adapter's Parameters

This option is used to configure parameters for this adapter.


4.2.2.1 Enable or disable BIOS on this adapter

This option is used to Enable or Disable Boot BIOS on an individual adapter 
basis. The default is disabled.


4.2.2.2 Change default ALPA of this adapter

This applies only to FC-AL. This option can be used to change the ALPA of the 
adapter. The default value of the ALPA for the adapter BIOS is 01 in Hex. If 
a user changes the Host ALPA to a different value, it will not show on the
NVRAM ALPA until the system has been reset.


4.2.2.3 Change PLOGI Retry Timer

This option is used to set the interval time for the PLOGI Retry Timer. This 
option is especially useful for Tachyon-based RAID arrays.  Under very rare 
occasion, a Tachyon-based RAID array will reset itself and the port will be 
temporarily off line in the loop.  When the port comes to life, the PLOGI 
retry interval helps to discover this device. 

The resolutions are 0 (no retry), 50, 100 and 200 msec.   The time it takes 
for one PLOGI to scan the whole loop (if 126 ALPA are on the loop) is shown 
below:

          50 msec will take 5 to 6 seconds.
          100 msec will take 12 seconds.
          200 msec will take 22 seconds.


4.2.2.4 Topology Selection

This menu is used to choose the Topology:

  (1) Auto Topology (Default):
        Try Loop first, then try Fabric Point to Point.
  (2) Auto Topology:
	Try Fabric Point to Point first, then try Loop.
  (3) FC-AL (Loop) only
  (4) Fabric Point to Point only
 

4.2.2.5  Enable or Disable Spinup delay 

The default for this setting is "disabled".

There are two different behaviors, depending on whether or not a boot device 
has been defined. If at least one boot device has been defined, the BIOS will 
wait for 2 minutes before trying to find a boot device. After the two minute 
delay, the BIOS will try to find, for up to three additional minutes, only the 
boot device defined in the first entry of the eight-entry multi-boot list. If 
the BIOS finds this device within the three minute time period, it will boot 
from the device without waiting for other devices to become available. If the
BIOS doesn't fine the device within three minutes, then it will continue 
booting scanning algorithm, and hopefully another multi-boot device is 
available.

If no boot devices have been defined, and the Auto Scan flag option is enabled
(defaults to disabled), then the BIOS will delay for 5 minutes before scanning 
for devices. In the private loop case, we will attempt to boot from the lowest 
target AL_PA we find. In the fabric-attached case, we will attempt to boot from 
the first target found in the NameServer data.


4.2.2.6  Enable or Disable Auto Scan

If there is a configured boot entry, the autoscan setting will be ignored.
It has to be set to default first by <d>, then autoscan can be set.

The default is "disabled". The other options are

2. Any first device
3. First LUN 0 device
4. First NOT LUN 0 device

The above options are valid only if none of all the eight boot entries is 
configured. In other words, the configured boot entry will override any above 
option was selected.


4.2.2.6.1 Any first device

The first adapter will:

*  Issue a Name Server Inquiry.  
*  The first D_ID from Name Server Inquiry will become the boot device.

The adapter will attempt to log in to a Public Loop first. If it fails, it will 
log in to a Private Loop. The first successful scan device will be the boot device 
and only this one device will be exported to the Multi-Boot Menu. 


4.2.2.6.2 First LUN 0 device

Same as 3.2.2.6.1 except auto scan the first LUN 0 as the boot device.


4.2.2.6.3 First NOT LUN 0 device

Same as 3.2.2.6.1 except auto scan the first NOT LUN 0 as the boot device.


Therefore, it is strongly recommended that you use  the "Configure Boot Devices" 
option to configure at least one boot entry for Fabric, Public loop or Private 
loop configuration.


4.2.2.7 Enable or Disable EDD 3.0

EDD 3.0 was disabled by default. This is because current Win2K does not 
support EDD 3.0 and would hang the system during the Win2K installation.


4.2.2.8 Enable or Disable Start Unit Command

This option was disabled by default. It is used to issue SCSI Start Unit
command. When it is enabled, the user has to know the specific LUN for
the SCSI Start Unit Command. This is because when the user configures the
boot device, "Enter two digits of starting LUN (hex):" has to be the known 
specific LUN. It will not display like the regular LUN scanning.


4.2.2.9 Enable or Disable Environment Variable

This option is disabled by default. It is used to set the boot controller 
order if the system supports the Environment Variable.


5. Procedure to Build the Boot Disk from the Light Pulse Adapter

(1) Set the boot disk to be the lowest AL_PA in the loop or use BIOS Utility 
    to configure the ALPA.
(2) Prepare a floppy disk that contains both DOS FDISK and FORMAT programs.
(3) Boot from floppy and use FDISK to create DOS primary partition.
(4) Format the C: drive from the floppy.
(5) Install DOS version 6.00 or above.
(6) Install Windows NT.


6. Procedure to Install Windows on the Fibre Channel Disk

Make sure to always use the latest version of Windows NT Port driver or 
Mini-Port driver. 

*  Your computer's system BIOS may require that another controller take
precedence over the Emulex adapter during boot.  If this occurs, you must
disconnect or disable the other adapter.  This will allow you to configure 
and build your operating system on the drive connected to the Emulex adapter.


6.1 Install Windows NT 4.0

(1) Boot with Windows NT 4.0 Setup Media (See Microsoft Documentation For 
    Details)
(2) When the "Specify additional storage driver" message is displayed, insert 
    the Emulex driver diskette.
(3) Follow the instruction to complete the installation.

  
6.2 Install Windows 2000

(1) Boot with  Windows 2000 Setup Media (See Microsoft Documentation For 
    Details)
(2) Monitor the white bar on the bottom of the screen. 
(3) Press [F6] within 5 seconds when the "Press F6 if you need to install a 
    third party SCSI or RAID driver" message is displayed. 
(4) When the "Setup could not determine the type of one or more mass storage 
    devices installed in your system, or you have chosen to manually specify an 
    adapter." message is displayed, insert the Emulex driver diskette.
(5) Follow the remaining instructions to complete the Windows 2000 installation


7. Advanced BIOS Features

7.1 Multi-Boot BIOS (BBS)

Multi-boot BIOS is in compliance with BIOS Boot Specification (BBS). The 
system must have multi-boot system BIOS in order to take advantage of this 
feature. Multi-boot BIOS allows a user to select any boot disk in the system 
BIOS setup menu. The boot disk can be a Fibre Channel drive, a SCSI drive, an 
IDE drive or a floppy drive.  Emulex BIOS will supply the first 16 drives to 
the system BIOS menu. The multi-boot BIOS can override the Fibre Channel 
drive that is selected in the BIOS Utility.  

For example, the system has only eight Fibre Channel disks. The boot disk has 
ALPA 02. However, the user can select ALPA 23 in the system BIOS setup menu. 
The boot device will be Fibre Channel disk with ALPA 23 instead of ALPA 02 
that is set in BIOS Utility.

