   All NetWare Products

     Installation Notes for PRO/100 VE,VM & 82562AH Network 
Connectors and Desktop Adapters with Novell NetWare* Operating Systems 


 CONTENTS
 A. File Locations on the CD
 B. Making an installation diskette (MakeDisk)
 C. NETWARE SERVER DRIVER INSTALLATION 
     General Instructions
     Instructions using Novell Utilities
     Instructions for manually loading drivers
     Sample Load Commands
     Tips
 D. NETWARE CLIENT DRIVER INSTALLATION 
     I. NETWARE CLIENT 32 FOR DOS/WINDOWS 3.1X INSTALLATION 
         General Instructions
         Tips
         Sample Files
    II. NETWARE CLIENT 32 FOR WINDOWS* 9x and NT 4.0
   III. NETWARE OS/2* ODI CLIENT DRIVER INSTALLATION 
        Requirements
        Installation Instructions
        Tips
        Sample Files
    IV. NETWARE DOS ODI CLIENT DRIVER INSTALLATION 
      NetX General Installation
      VLM General Installation
      Tips
      Sample Files
 E. COMMAND LINE KEYWORDS and PARAMETERS
======================================================================

A. File Locations on the CD
===========================

\ - e100bODI.com and the NDIS drivers
\Makedisk - ReadMeNW.1st and utility to make diskette install
\Info\netware - Installation notes and Advanced Networking Services 
                files (nwteam.txt, iANS.txt)
\DOS  - e100b.DOS, e100BODI.COM, LSL, IPXODI, NETX, and net.cfg
\NWServer  -  CE100B.LAN (CHSM 1.11 driver - base driver),   
      ETHERTSM, MSM, MSM31x, NBI & NBI31x NLMs (support nlms)
      iANS.lan (for advanced services if a PRO/100 server card is added)
\OS2 - OS2 files


B. Making an Installation Diskette (MakeDisk)
==================================================
A diskette for installation on systems without a CD may be created 
from a system with both a CD and a floppy drive using the MakeDisk 
utility found in the \MAKEDISK directory of the CD and run from the
makedisk directory. Syntax is:

makedisk NW <destination diskette> 
 Example: d:\makedisk> makedisk NW A:


C. NETWARE SERVER DRIVER INSTALLATION (version 3.2, 4.2 and above):
=======================================    

General Instructions:   
---------------------

The base driver (ce100b.lan) is an ODI C (CHSM) Specification v1.11 driver 
which works for NetWare 3.20, 4.20, 5.0, and 5.1. It is located in the 
\nwserver directory of the disk. Also in the \nwserver directory is the 
advanced networking services driver (iANS.lan) which is only to be used in 
addition to the base driver if an additional NIC (PRO/100 server) is added. 
To load the iANS.lan driver, you must follow the instructions in the 
additional text files named nwteam.txt and examples.txt found on the disk 
at \info\netware\.

   NOTE: Some NetWare CDs ship with drivers for Intel Adapters but
      Those drivers do not give full functionality. You must use the 
      drivers provided by Intel with the PRO/100 adapter (This is also 
      true for any additional PRO/100 adapters that you load and wish 
      to add the Advanced Network Services (Teaming and VLAN.)

Intel recommends you use the latest Novell Service Packs. The latest server 
NLMs and support files for NetWare can be found on Novell's automated 
services under the heading of "Minimum Patch List". Specifically you must 
be using the three networking support NLMs dated as listed below or later. 
These are also included in the \nwserver directory on the disk for your 
convenience. 

Required support NLMs with oldest acceptable version and date:
NBI.NLM    v2.25 10/20/98 
MSM.NLM    v3.95 5/12/99 


ETHERTSM.NLM  v3.8 3/1/99      
   Note: These must be loaded in the order listed (NBI first). 


Instructions - using the Novell Utilities INSTALL or NWCONFIG
-------------------------------------------------------
1  Load Novell's Install.nlm (3.x & 4.x) or nwconfig.nlm (5.x).

2  From the Installation Options screen, choose "Driver options" and 
   press Enter.

3  Choose "Configure network drivers" and press Enter. If any drivers 
   are already loaded, a list of them appears.

4  Choose "Select an additional driver" and press Enter. A list of 
   drivers appears but you will be installing an Unlisted Driver.

5  Insert the disk and press the Insert key. If the path is not
   a:\nwserver, press F3 and type in the full path. Press Enter.

6 CE100b.LAN will be displayed. Highlight it and press Enter. Select 
   Yes to Start loading the driver. It is up to you if you wish to 
   save the old driver or not.

7  Next the install utillity will give you a choice of Modifying 
   or Saving parameters. If you choose modify, you may move around
   with the arrow keys. You should specify slot and usually speed 
   and duplex before arrowing down to save. To avoid parameters (not
   recommended) you may press the escape key multiple times and back
   out of the install screens. For more information on parameters,
   see Section E: Command Line Keywords and their Parameters.

8  The utility will load the driver and assign network numbers for 
   IPX with all four frame types. You may overide these numbers by 
   entering your own number at each prompt. (If you wish to limit
   the number of frame types loaded, edit autoexec.ncf.)

9  When returned to the Drivers screen, press the Esc key 3 times 
   to exit the utility and return to the prompt.


Instructions for manually loading drivers
-----------------------------------------
1 Copy the driver (\NWSERVER\CE100B.LAN) and any  
updated NLMs to the NetWare server's hard drive.

   If you can't log in to the server (before starting the server) 
   copy the CE100B.LAN driver from the \NWSERVER directory on the 
   Configuration and Drivers disk to the root directory of the 
   server's hard drive.

   If you can log into the server, copy the driver to the SYSTEM
   subdirectory. If you do this, you won't need to specify a path on    
   the load line. If you copy it to another directory, make sure the 
   LOAD statement includes the correct path.

2  Start the server. At the server console, load NBI, MSM and 
   ETHERTSM in this order. Next, load and bind CE100B.LAN.

2 Add the load and bind statements to the server's AUTOEXEC.NCF file 
   so the adapter driver loads automatically when the server 
   starts.
 
SAMPLE LOAD COMMANDS (server):
-------------------------------
   
   LOAD CE100B SLOT=n SPEED=100 FORCEDUPLEX=2 FRAME=ETHERNET_802.2
   BIND IPX TO CE100B NET=yy

   **IMPORTANT**  When using command line options with the .LAN 
   driver, make sure the equal sign is followed by a value. 
   Otherwise, unpredictable results may occur.  

See Section E. COMMAND LINE KEYWORDS AND PARAMETERS for additional 
commands and their parameters.

Tips (Server):
--------------
1  If the error message "Loader cannot find public symbol: <symbol 
   name>" is encountered:

   Upgrade the ETHERTSM.NLM and MSM.NLM.

2  Installing multiple adapters:

   If you have multiple adapters in a single server, each adapter 
   must have a different NET number and SLOT number. Also, you may 
   want to name each adapter. For example:
      
      LOAD C:\CE100B SLOT=3 NAME=LAN_A
      BIND IPX TO LAN_A NET=222
      LOAD C:\CE100B SLOT=4 NAME=LAN_B
      BIND IPX TO LAN_B NET=333

3  If you have problems loading the driver on multiple adapters and  
   the initialization fails due to "Insufficient RCBs," increase the 
   number of buffers allocated to the server. Add the following to
   STARTUP.NCF:
      
      SET MINIMUM PACKET RECEIVE BUFFERS = 100 (or larger)

   The MINIMUM value you specify should be at least 100 times the 
   number of Intel adapters in the computer.

   The MAXIMUM you can specify depends on the amount of memory in 
   the server, but it must be greater than the MINIMUM. 

      SET MAXIMUM PACKET RECEIVE BUFFERS = 2000 (or larger)

4  If you're installing one adapter with multiple frame types:

   When binding multiple frame types to one adapter, enter a LOAD and
   BIND statement for each frame type. Each LOAD statement uses the 
   Same SLOT number, but each BIND statement needs a unique network 
   number. You must also include a name on each load line to avoid  
   being prompted for the adapter to bind IPX to.
      
      Example:

      LOAD C:\CE100B SLOT=3 FRAME=ETHERNET_802.2 NAME=LAN8022
      BIND IPX TO LAN8022 NET=88888
      LOAD C:\CE100B SLOT=3 FRAME=ETHERNET_802.3 NAME=LAN8023
      BIND IPX TO LAN8023 NET=77777


5  Optional LOAD line parameters: see Section E.

See Teaming and VLAN information at info\nwserver\nwteam.txt IF you 
have added an Intel PRO/100 Server Adapter.


D. NETWARE CLIENT DRIVER INSTALLATION 
=====================================

I. NETWARE CLIENT 32 FOR DOS/WINDOWS 3.1X INSTALLATION  
-----------------------------------------------------------
   
   General Instructions  
   --------------------
1  From the Novell NetWare Client 32 software, run INSTALL.EXE.

2  Select the NetWare Client 32 products you want to install on
   your workstation from the list:
      
      [X] NetWare Client 32 for DOS
      [X] NetWare Client 32 for Windows
      [ ] NetWare TCP/IP protocol stack
           [ ] NetWare IP (TCP/IP Required)
      [ ]Desktop SNMP
           [ ] HOSTMIB for SNMP (SNMP Required)
      [ ] NetWare TSA for SMS
     
      Note: "NetWare Client 32 for DOS" and "NetWare Client 32 for
            Windows" are usually selected by default.

3  From the Customize Support for Windows menu, specify if you want 
   to use multiple country codes or if you want to set the shared 
   Windows path. The default for both of these is NO.

4  From the Select LAN Driver Type menu, select "32-bit LAN drivers".

5  From the 32-Bit Network Board Drivers menu, select:

        "USER SPECIFIED 32 BIT DRIVER"

   Insert the driver diskette and type <drive>:\NWSERVER, select:

        "Intel(R) PRO/100 LAN Adapter"

6  <OPTIONAL> Specify the following settings for the PRO/100 adapter:

          Parameter                       Default
          -------------                   -------
          Speed (100B only)               0 (auto detect)
          IOMAPMODE                       Memory Mapped
          Forceduplex                     0 (auto negotiate)
          Frame Type                      Ethernet_802.2
                                          Ethernet_802.3
      
      Note: The default settings will work for most installations. 
      If you use multiple frame types, please see the Tips section 
      below.

7  From the Installation Configuration Summary, verify the default
   settings for Client 32 are correct, or modify as necessary.
      
      Modify AUTOEXEC.BAT and CONFIG.SYS      [YES]
      
      Client Directory:       C:\NOVELL\CLIENT32
      Windows Directory:      C:\WINDOWS
      LAN driver type:        32-bit LAN drivers
      LAN driver:             Intel(R) PCI Adapters

8  Novell NetWare will now copy the files to your workstations and
   modify the configuration files to match your selected 
   configuration.

   TIPS (Client32 for DOS/Win3.x):
   --------------------------------------------
1  To avoid the following message when you load the driver:
      
      "Do you want to load another frame type for a previously 
      loaded board?  Y/N "

   Add the slot number to the LOAD line in STARTNET.BAT (by default 
   it is located in the \NOVELL\CLIENT32 directory). The only way to     
   determine the slot number Novell is expecting is to put an 
   invalid value on the load line. For example (but the load line 
   should be all on one line):
      
           LOAD C:\NOVELL\CLIENT32\CE100B.LAN SPEED=0 IOMAPMODE=0
           FORCEDUPLEX=0 FRAME=ETHERNET_802.2 SLOT=e

   When you next reboot, you will be prompted with the correct value.
   Modify the STARTNET.BAT again, and use that value. If the slot is 
   not specified correctly, only the first frame type will load. The
   parameters for Speed, Forceduplex and Iomapmode are optional given
   they have a default value if not listed.    
     
2  CONFIG.SYS must contain the LASTDRIVE=Z statement.

3  NET.CFG must contain FIRST NETWORK DRIVE = F indented under the 
   NetWare DOS Requester section

4  Verify that the adapter passes the diagnostics test by
   running SETUP.EXE found on the root of the CD. If the adapter 
   fails diagnostics it will not function correctly running 
   Client 32.

5  Using the 16-bit ODI driver with Client 32 requires CLIENT32.NLM 
   dated 10/09/96 or later. The driver won't load with older versions.

6  If you encounter the error message "An attempt to load ce100b.LAN
   failed because the module references an undefined external:
   MSMHardwareFailure", you need to update the NetWare client files. 
   Download ODI33x.EXE (where x=latest revision number) from Novell's 
   electronic services and run the update utility.

   Sample Files:
   =============

   CONFIG.SYS
   ----------
   DEVICE=C:\WINDOWS\HIMEM.SYS
   BUFFERS=30,0
   FILES=60
   LASTDRIVE=Z
   
   AUTOEXEC.BAT
   ------------
   prompt $P$G
   path=C:\WINDOWS;c:\dos;C:\NOVELL\CLIENT32\
   SET TEMP=C:\TEMP
   @CALL C:\NOVELL\CLIENT32\STARTNET
   
   STARTNET.BAT
   ------------
   SET NWLANGUAGE=ENGLISH
   C:\NOVELL\CLIENT32\NIOS.EXE
   LOAD C:\NOVELL\CLIENT32\LSLC32.NLM
   LOAD C:\NOVELL\CLIENT32\CMSM.NLM
   LOAD C:\NOVELL\CLIENT32\ETHERTSM.NLM
   LOAD C:\NOVELL\CLIENT32\CE100B.LAN SPEED=0 IOMAPMODE=0 FORCEDUPLEX=0
        FRAME=ETHERNET_802.2 SLOT=2
   LOAD C:\NOVELL\CLIENT32\CE100B.LAN SPEED=0 IOMAPMODE=0 FORCEDUPLEX=0
        FRAME=ETHERNET_802.3 SLOT=2
   LOAD C:\NOVELL\CLIENT32\TRANNTA.NLM
   LOAD C:\NOVELL\CLIENT32\IPX.NLM
   LOAD C:\NOVELL\CLIENT32\CLIENT32.NLM
      
      NOTE: If you are loading multiple frame types, you will need to
            specify the slot number of the adapter on the load lines.
            See NOTES section above for detailed information.
   
   NET.CFG
   -------
   NetWare DOS Requester
      FIRST NETWORK DRIVE F
      NETWARE PROTOCOL NDS BIND
   
   Protocol IPX
      IPX SOCKETS 40

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


II. NETWARE CLIENT 32 FOR WINDOWS* 9x, Windows 2000 and Windows NT
==================================================================
The current version of client 32 does not support the .LAN drivers.
Install the appropriate NDIS driver prior to installing Client32. 
The NDIS drivers are located in the root of the Intel adapter CD. 
Refer to Info\ms\ms.txt for instructions on installation.
**    **     **     **     **     **     **    **    **   **

III. NETWARE OS/2* ODI CLIENT DRIVER INSTALLATION 
===================================================

 Requirements:
 -------------

 a. The latest version of the Novell NetWare Requester for OS/2 
    (including Install). If running IBM* OS/2 2.0, 2.1, or Warp - you
    need OS/2 Requester ver 2.01 (or later). 
 b. The PRO/100 adapter OS/2 ODI driver from the Intel adapter disk
    at \OS2\E100BODI.SYS
    See "B. Making an installation disk (MAKEDISK)" earlier in this
    file for more information.


 Installation Instructions:
 -------------------------

1  Run the INSTALL that ships with Novell's OS/2 requester. If asked 
   for the name of the network interface driver, enter E100BODI.SYS.

2  Choose the session support you need for your configuration. 
   See the "NetWare Requester for OS/2" manual if you need help.

3  Save the configuration.

4  When asked for the path and filename for the driver, insert the 
   Intel adapter disk into the drive and press Enter.

5  After completing installation, choose CONFIGURATION from the main 
   menu. Then choose THIS WORKSTATION. This allows you to modify the 
   NET.CFG file, which must reside in the root directory.
   
 Note: The default frame type for E100BODI.SYS is 802.2. If you're
 using the 802.3 frame type, you have to include a FRAME statement 
 in the NET.CFG file and list the 802.3 FRAME type first.

 Tips (OS/2 ODI)
 ---------------

1  To verify the driver loaded properly In the CONFIG.SYS file, add 
   a "fake" device=xxx statement after theE100BODI.SYS line. This
   will cause a screen scrolling pause so you can check for error
   messages.

2  The Error message "not getting a connection ID" appears when
   there is a frame type mismatch or cable disconnect.

 Sample Files  
 ============

  CONFIG.SYS
  -----------
   DEVICE=C:\NETWARE\E100BODI.SYS


  NET.CFG
  --------
   LINK DRIVER E100BODI
     FRAME ETHERNET_802.3 (802.2 is default if not listed)
     SLOT=n
     SPEED 100
     THRESHOLD 16
     NODE ADDRESS 02xxxxxxxxxx
   PROTOCOL IPX E0 ETHERNET_802.2

      PROTOCOL Values: e0=Ethernet_802.2
                        0=Ethernet_802.3
               8137=Ethernet_II
               8137=Ethernet_SNAP
  
    Note: When using the 802.3 frame type, you MUST include a 
    FRAME statement LISTED FIRST in the NET.CFG file. 

For other command line keywords and parameters see Section E

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

IV. NETWARE DOS ODI CLIENT DRIVER INSTALLATION
===================================================
  Location of Driver:  \DOS\E100BODI.COM

  NOTE: Novell no longer supports NETX.EXE or the VLM client software.
  However, as a convenience to Intel customers, a copy of NETX.EXE is
  provided on the Intel Configuration and Drivers CD. Intel recommends
  that you use the latest Novell Client32 software.

 NETX General Installation 
 -------------------------

1  From the \DOS  directory of the adapter installation disk load 
   (as needed) LSL.COM, E100BODI.COM, IPXODI.COM, NETX.EXE and NET.CFG 
   to the hard drive (\NWServer). 

2  Configure AUTOEXEC.BAT and NET.CFG based on the sample files below.
   NET.CFG should be in the same directory as the driver.

3  Reboot and the client should connect to the server.

 VLM General Installation
 ------------------------

This version of E100BODI.COM requires VLM client version 1.21.

1  Run install.exe on the workstation you are configuring.

   Install.exe can be found:

   For IntranetWare 4.11: from the IntranetWare CD at:
       \PRODUCTS\VLM\IBM_6\INSTALL.EXE
       \PRODUCTS\VLMIP\IBM_6\INSTALL.EXE  (the TCP/IP client)

   or (server):\PUBLIC\CLIENT\DOSWIN (except with NetWare 3.12).

   For 4.1/3.12 clients: from the workstation from the 
       NetWare Workstation for DOS disk. It must be version 1.22 
       or greater (supplied with IntranetWare 4.11.)

2  Follow the screen prompts including the following options:
     - Directory on the hard drive for the client software. Default 
     directory is C:\NWCLIENT. You can specify another directory.
     - Automatically update CONFIG.SYS and AUTOEXEC.BAT files Y/N
     - Specify the directory to load Windows (if applicable) and 
     option to customize for Windows.
     - Configure workstation for back-up by a NetWare server.

3  Select a network driver and set configuration options. Do NOT 
   select a Driver from the list Novell provides, rather choose 
   OTHER DRIVER and insert Intel adapter disk.  Select the Intel 
   PRO/100 LAN Adapter. Then optionally set:
     Frame Type: match the server.
     Adapter Node Address:
     Force Duplex Mode: 
     Line Speed: 
   (See Section E Keywords and Parameters for possible values.)

4  Then Install will copy the appropriate files to your hard drive 
   and set NET.CFG. This is the final step.    

  TIPS (DOS ODI)
  ---------------

1  In CONFIG.SYS add LASTDRIVE=Z and in NET.CFG add under the NetWare 
   DOS REQUESTER section (indented) FIRST NETWORK DRIVE F.

2  Promiscuous mode support is not supported since ASM does not 
   include a receive monitor stack. If needed, load RXMONSTK.COM 
   (from the VLM client kit) after LSL.COM and before E100BODI.COM. 

3  This version of E100BODI.COM requires VLM client version 1.21 or
   higher. Attempting to use an older version of the VLM client may
   cause connection problems, slow response or computer system lock
   -ups. 

4  If running EMM386, make sure you are using v4.49 or later (ships 
   with DOS 6.22).

  Sample Files  
  ==========================

   AUTOEXEC.BAT:
   -------------
   CD\NWCLIENT
   LSL
   E100BODI
   IPXODI
   NETX     (or VLM  optional for NetWare 3.12 or higher)

   NET.CFG :
   ---------
   LINK DRIVER E100BODI
     FRAME ETHERNET_802.2  (generally NetWare 3.12 and later servers)
     ;FRAME ETHERNET_802.3  (generally NetWare 3.11 and earlier)      
     SPEED=100
     PROTOCOL IPX EO Ethernet_802.2

   NETWARE DOS REQUESTER
     FIRST NETWORK DRIVE = F  (Used only with the VLM.EXE). 
     PB BUFFERS = 10

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

SECTION E: COMMAND LINE KEYWORDS and PARAMETERS
======================================================
Used with the LOAD <driver> command (in net.cfg or startnet.bat)

    NOTE:  For servers, use this format: command=parameter 

           For clients, use this format: command parameter
                                         (no equal sign) 
        Examples: 
        (SERVER)  Load ce100b Speed=100 ForceDuplex=2 Name=eo83
        (CLIENT)  Load ce100b Speed 100 ForceDuplex 2 Name eo83

SPEED: Syntax:
-----
         For Servers:  SPEED=n  (where n = 10 or 100)
         For Clients:  SPEED n  (where n = 10 or 100)

   Default: 10, the adapter automatically senses speed
   If unable to autosense (including no network cable), default=10
      
   NOTE: Match the speed/duplex of your switch (if set). 
   If you don't have an auto-negotiating switch and are forcing the 
   duplex mode, you must specify the speed.

   NOTE: You must set the SPEED parameter to either 10 or 100 if
   you're setting the FORCEDUPLEX parameter to either half or full.


FORCEDUPLEX:  Syntax:
-----------
         For Servers:  FORCEDUPLEX=n
         For Clients:  FORCEDUPLEX n

         Where n = 0 auto-negotiate (PRO/100+ TX adapter only)
                      1 half duplex
                      2 full duplex

   Duplex Support and Default listed by Card Type: 
     All PRO/100+, PRO/100B TX: Full and Half, 10&100 Default:auto
     PRO/100B T4:  100 half, both at 10 (no autonegotiation, no nway)
     PRO/10+ PCI:  full on the TPE connector only (no autonegotiation)
     Default: half duplex. 
      
   Auto-negotiate:  The adapter negotiates with the switch whether to
   use full or half duplex. If unsuccessful, the adapter defaults to 
   half duplex. You must have an auto-negotiating switch (an Nway* 
   switch) to get full duplex support using autonegotiation.

   Full duplex:  The adapter sends and receives packets at the same 
   time. This improves the performance of your adapter. 

   Half duplex:  The adapter communicates in one direction at a time. 
   It either sends or receives.

      Note: If you use the FORCEDUPLEX command, you must also set the 
      SPEED parameter to either 10 or 100. (see SPEED above).

SLOT:  Syntax:  SLOT=n
----   (required only when multiple adapters are installed)
            where n = 1,2,3,4,...)

      For PCI adapters, SLOT is derived from bus number and device
      location as defined by the PCI specification and NBI. One way to 
      determine the slot number is to load the driver from the command
      line. You'll be prompted with valid device number(s) for the 
      adapter(s). Select one of them.


FRAME: Syntax:  FRAME=n
-----      where n = Ethernet_802.2
                     Ethernet_802.3
                     Ethernet_II
                     Ethernet_SNAP
           Default: Ethernet_802.2

   Configures the adapter to process the valid NetWare frame types.

TXTHRESHOLD: Syntax: TXTHRESHOLD(=)n (n = number of 8 bytes).
------------         Default: dynamically set
        
   Represents the threshold for transmits from extender SRAM
   FIFO (output buffer).
   If n=16 then the bytes are set at 128 (16x8). In this case, the LAN 
   controller transmits after copying 128 bytes from the host memory. 
   The maximum number that you can specify is 200 (200x8=1600 bytes) 
   which ensures there will not be any underruns.


EARLYRECV (client ONLY): Syntax: EARLYRECV n
---------     Where n = 0 disables early receives
                        1 enables early receives
              Default: early receives enabled

   This determines whether the driver enables early receives.
   Early receives allows a frame to start being processed before it is
   completely received into host memory. 


IRQMODE (VLM clients ONLY): Syntax: IRQMODE n
------- Where n = 0 automatically selects interrupt sharing mode
                  1 interrupt sharing is disabled
                  2 interrupt sharing is enabled

        Default: 0 automatically selects

   This parameter enables or disables interrupt sharing mode of the
   driver. It has the capability to automatically select the
   enabled or disabled state depending on system configuration. If
   the IRQ assigned to the driver is not being shared with another
   device, then interrupt sharing is disabled.  If the IRQ assigned
   to the driver is being shared, then the interrupt sharing is
   enabled.

NODE ADDRESS: Syntax: NODE=xNxxxxxxxxxx
------------  where N must = 2, 6, A, or E; x = hexadecimal number

       Default: The adapter's assigned address (UAA Universal Address)

   Specifies a locally administered address (LAA) unique to each 
   adapter. The node address is a 12-digit hexadecimal number; the 
   second digit must be one of the following digits: 2, 6, A, or E.
   
   02AA => LAA, 02 is set by the driver if not specified.
   00A0 => Typical Intel address (default)


PROTOCOL (VLM clients ONLY): Syntax: Protocol IPX E0 Ethernet_802.2
--------          Values: E0=Ethernet_802.2
                           0=Ethernet_802.3
                        8137=Ethernet_II
                        8137=Ethernet_SNAP    

   Indicates the standard protocol in use.


      
*  Third-party trademarks are the property of their respective owners.

