**
**                                   
**  VIA Rhine Family Fast Ethernet Adapter
** 
**  ODI Driver (CHSM, Specification v1.11) for 5.0, 5.1, 6.0, 6.5 Servers
** 
**  v5.25    Nov, 2003
**
**

Introduction:
=============

  The Fast  Ethernet 10M/100M  ODI Driver  for NetWare Servers confirms to 
  the  Novell Open Data-Link Interface (ODI) specification. This document 
  shows you how to setup the driver and how to use the enhanced functions 
  by setting the custom keywords.


Contents of the Subdirectory:
=============================

    FETNWSC.LAN         The ODI driver for NetWare 5.0, 5.1,6.0 and 6.5 Servers.
    FETNWSC.LDI         The installation information file.
    NW56.TXT            This file.

Installation:
=============

  Before starting with the installation process, make sure that the adapter
  is properly installed and configured. You can use the diagnostic program
  (A:\SETUP.EXE) in DOS mode to make sure your connection with the network is
  correct.

  Use Server Install utility:
  -----------------------------
    For Netware 5.0, 5.1, 6.0, execute the NWconfig program:
    1) On the server console:
        NWConfig <Enter>

    2) Choose "Driver Option/Configure network drivers/Load an additional driver".

    3) Press the <Ins> key to install the driver which is not on the list.

    4) Press <F3> to specify a different path and press <Enter>.

    5) The FETNWSC.LAN should appear on the selection list. Press <Enter> to
       choose it.

    6) You can choose "Select/Modify driver parameters and protocols", and then choose
       "Save parameters and load driver" to finish driver loading.

    For Netware 6.5, execute the hdetect program:
    1) On the server console:
        hdetect <Enter>
        
    2) In "Options" menu, choose "Continue" item.
    
    3) Choose "Network boards" in "Device types" box and press <Enter>.
    
    4) Choose "Modify" in "Additional Driver Options" box and press <Enter>.
    
    5) Press the <Ins> key twice to add an unlisted driver.
    
    6) Press <F3> to specify a different path and press <Enter>.

    7) The FETNWSC.LAN should appear on the selection list. Press <Enter> to
       choose it.

    8) You can choose "Modify driver properties", and to change the driver properties.
    
    9) Go back to the top "Options" menu, choose "Load" to load the driver.       
    
  Loading Driver Manually:
  ------------------------
    1) On the server console, load the driver directly, for example:

          LOAD A:\NETWARE\NWSERVER56\FETNWSC FRAME=Ethernet_802.2

    2) Bind with IPX:

          BIND IPX FETNWSC

    3) You can login the server from a workstation, and then copy FETNWSC.LAN to
       the directory SYS:\SYSTEM on server. Add the LOAD and BIND command lines
       to AUTOEXEC.NCF file so that the lan driver will be loaded automatically
       while the server starting up next time.


  NOTE:
  -----
    1) Multiple Lan Adapters in a system:
        If you want to install mutiple lan adapters in a server, you have to use
        the keyword, SLOT, to let driver locate the right adapter.
        For example:

            LOAD FETNWSC SLOT=1 FRAME=Ethernet_802.2 NAME=Lan_1
            BIND IPX TO Lan_1 NET=2001
            LOAD FETNWSC SLOT=2 FRAME=Ethernet_802.2 NAME=Lan_2
            BIND IPX TO Lan_2 NET=2002

    2) Tagging ability :
        If keyword "TAG" is supported, the transmited packets
        will be tagged packets. It's only supportted by management adapter.
        
    3) Hardware checksum offload :
        If "HCHECHSUM" keyword is supported. The ability will be activated. 
        It's only supported by management adapter.
        
    4) VLAN support :
        For now, we only support one VID value setting. It's only supportted by 
        management adapter.
        
    5) The original keywords "FULLDUPLEX", "HALFDUPLEX", "SPEED" and "AUTO" are still
       supported.

    6) In Netware 6.5, suggest use the update hdetect utility within the driver binary 
       folder (please overwrite the built-in hdetect utility in Netware 6.5 with the new
       one) because the hdetect utility will have problem parsing the LDI file and the 
       driver keyword display will be wrong.

Configuration Parameters:
=========================

    Custom Keywords:
    ----------------
  
        FULLDUPLEX                      This keyword is used to force full
                                        duplex mode.
                                        (suggest use CONNECTIONTYPE instead of this keyword)

        HALFDUPLEX                      This keyword is used to force half
                                        duplex mode.
                                        (suggest use CONNECTIONTYPE instead of this keyword)

        SPEED                           This keyword is used to force Line
                                        Speed at 10 or 100 Mbps.
                                        (suggest use CONNECTIONTYPE instead of this keyword)
        
        AUTO                            This keyword is used to force the
                                        chip at Auto-Negotiation mode.
                                        (suggest use CONNECTIONTYPE instead of this keyword)

        CONNECTIONTYPE                  This keyword is used to specify media type.
        
            CONNECTIONTYPE=AutoSense
            CONNECTIONTYPE=10BASET
            CONNECTIONTYPE=10BASETFD
            CONNECTIONTYPE=100BASETX
            CONNECTIONTYPE=100BASETXFD
            
        FLOW_CONTROL                    This keyword is used to specify flow control
                                        ability.
            FLOW_CONTROL=DISABLE
            FLOW_CONTROL=ENABLE
            FLOW_CONTROL=HARDWARE_DEFAULT   (default)
            
        HCHECKSUM                       This keyword is used to force hardware checksum.
                                        Only be supported by management adapter.
            HCHECKSUM=DISABLE
            HCHECKSUM=ENABLE            (default)
            
        TAG                             This keyword is used to enable TX tagging.
                                        It's combined with VID keyword for transmitting
                                        tagged packet. Only be supported by management 
                                        adapter.
            TAG=ENABLE
            TAG=DISABLE                 (default)
            
        VID                             This keyword is used to support VLAN's VID.
                                        It's only worked when TAG keyword is enabled.
                                        Only be supported by management adapter.
            VID=1~4094                  

