NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  ODI33F.EXE: ODI 3.31/1.11 Update.
README FOR:  ODI33F.EXE

NOVELL PRODUCTS and VERSIONS:
NetWare 3.12
NetWare 4.1
NetWare 4.11
intraNetWare Client 2.20 for DOS/WIN - IWCD897
intraNetWare Client 2.20 for WIN 95 - IWCD897
intraNetWare Client 4.11 for Windows NT - IWCD897

ABSTRACT:

This file contains the latest LAN ODI 3.31/1.11 support modules (NBI, MSM,
TSMs, etc.) for both Novell NetWare file servers and clients. LAN drivers
written by Novell are also included. (There are no third party LAN drivers
included.) This new ODI spec adds support for Hot Plug PCI, and for removing a
single instance of a driver. Do not use ODI33F with NetWare Connect 2.0 (or
lower), MPR 3.0 (or lower), or NetWare for SAA. If NIAS v4.0 or MPR v3.1 is
installed ODIWANx.EXE is also required.


 -----------------------------------------------------------------
 DISCLAIMER
 THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
 NOVELL.  NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS
 INFORMATION.  HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT
 IS FOR YOUR INFORMATION ONLY.  NOVELL MAKES NO EXPLICIT OR IMPLIED
 CLAIMS TO THE VALIDITY OF THIS INFORMATION.
 -----------------------------------------------------------------


ISSUE: 

This ODI update is for English only.

 Do not install the ODI 3.31/1.11 support files update kit on file servers that
have NetWare Connect 2.0 (or lower), MPR 3.0 (or lower), or NetWare for SAA.
The WAN drivers in these products will not load with the ODI 3.31/1.11 support
files. The install checks for these specific products, and the install will not
allow the ODI 3.31/1.11 support files update kit to be installed if they exist.
If NIAS V4.0 or MPR V3.1 is installed, ODIWANx.EXE must also be install after
ODI33E to update the WAN drivers for these products. The shipping versions of
these products contain WAN drivers that will not load with the ODI 3.31/1.11
support files.

 ODI33F contains updated ODI 3.31/1.11 LAN drivers written by Novell, and
updated ODI 3.31/1.11 support modules (NBI, MSM, TSMs, etc.) for both Novell
file servers and Novell clients. This file does not contain any third party LAN
drivers. This new ODI spec adds support for Hot Plug PCI, and for removing a
single instance of a LAN driver.

 For details on the new ODI spec and possible issues with third party HSM
(Hardware Specific Module) LAN drivers, see the "HSM Specification Description
and Issues Section" below.

 For syntax on removing a single instance of a LAN driver, see the "ODI
Selective Unload User Interface Instructions" below.

 Details on changes to specific files are given in the "ODI Files Updates and
Changes Section" below.

 ****************************************************************
  HSM Specification Description and Issues Section.
 ****************************************************************

  There are three HSM (Hardware Specific Module) specifications that LAN
drivers can be written to. They are (1) the 16-bit Client HSM spec, currently
at v4.00, (2) the 32-bit Assembly HSM spec, currently at v3.31, and (3) the
32-bit "C" HSM spec, currently at v1.11. If LAN drivers have been certified by
Novell Labs, the Novell Labs test bulletin will list the HSM spec version that
the driver was written to.

  The 16-bit Client HSM spec v4.00 has not changed since Feb. 1996.  Drivers
written to this spec can be used on Novell Clients running on DOS/WIN or
Windows95. These drivers are *.com files.  If a driver written to this spec is
being used on an adapter that is automatically detected by Windows95, a *.inf
file will also be necessary in order to install the driver on Windows95. The
*.inf  Windows95 installation file should be supplied by the driver
manufacturer.

  The current ODI 3.31/1.11 support modules (NBI, MSM, TSMs, etc.) in ODI33F
that allow 32-bit LAN drivers to load on Novell file servers or Novell clients
will support 32-bit LAN drivers written to the Assembly spec v3.31, Assembly
spec v3.30, and "C" spec v1.11. Most 32-bit LAN drivers that are written to the
Assembly 3.20 spec should run on the current ODI 3.31/1.11 support modules. 
However, some Assembly 3.20 spec drivers may have problems. The ODI support
modules that were written to support the Assembly 3.20 spec LAN drivers have
been included for customers who currently have Assembly 3.20 spec LAN drivers
that will not work with the current ODI 3.31/1.11 support modules.

  The HSM "C" spec v1.10 was the first HSM "C" spec supported. The HSM "C" spec
v1.10 was first available at the same time the Assembly HSM v3.30 spec was
available. 32-bit LAN drivers written to the "C" spec v1.10 will not work with
the current ODI 3.31/1.11 support modules. There has been only one third party
driver (CMDGODI.LAN 06/07/96 124292) certified to the "C" spec v1.10.  If this
driver is being used, do not update to the current ODI 3.31/1.11 support
modules until an updated driver from Madge written to the "C" spec v1.11 is
available to be used.  All of Novell's "C" spec v1.10 LAN drivers have been
updated to the "C" spec v1.11, and are included.

  The ODI 3.20 support modules and Assembly spec v3.20 LAN drivers have not
been tested on and are not supported on NetWare file servers starting with
v4.11. They can be tried, but the results are unknown.

  The latest ODI support modules and LAN drivers that can be run on NetWare
v3.11 are the ODI 3.20 support modules and Assembly spec v3.20 LAN drivers. The
ODI 3.20 support modules and Assembly spec v3.20 LAN drivers written by Novell
are included for NetWare v3.11.

 ****************************************************************
  ODI Selective Unload User Interface Instructions.
 ****************************************************************

  New Command Line Verbs and /or Entry Points

  The following five commands have been added to the server's command set, for
use with the server's existing command capability. These commands are available
only after installing the 3.31/1.11 ODI support modules.

 1) REMOVE NETWORK INTERFACE <logical board #> | <logical board name>

  This function will remove an instance of a logical board. This function is
only supported on HSMs written to the C spec v1.11 and Assembly spec v3.31.

  The boards' logical # corresponds to the order in which it shows up when
config is typed at the server console prompt or when load  <driver name> is
performed at the server prompt.

 2) REMOVE NETWORK ADAPTER <filename>,<BoardInstance number>

  When using this function do not use the filename extensions, just use the
first part of the filename, i.e. CNEAMD. This function will remove all logical
boards associated with the specified adapter.

  The combination of Filename and BoardInstance number uniquely identifies the
adapter (and all of its associated logical boards) to be removed. But the
BoardInstance number is not currently available to the user. In the future the
Monitor.nlm utility will be able to display the BoardInstance number.

 3) SHUTDOWN NETWORK INTERFACE <logical board #> | <logical board name>

  This function will do a partial shutdown of the specified logical board. This
function is only  supported on HSMs written to the C spec v1.11 and assembly
spec v3.31.

  For an explanation about the logical board # see REMOVE NETWORK INTERFACE.

 4) RESET NETWORK ADAPTER <filename>,<BoardInstance number>

  When using this function do not use the filename extensions, just use the
first part of the filename, i.e. CNEAMD. This command is simply a way to get to
the already existing DriverRest capability from the command line.

 5) RESET NETWORK INTERFACE <logical board #> | <logical board name>

  For an explanation about the logical board # see REMOVE NETWORK INTERFACE.
This function calls HSM DriverReset to reset a single logical board. This
function is only supported on HSMs written to the C spec v1.11 and Assembly
spec v3.31.

  This may or may not be meaningful for a particular adapter/driver, if it is
not meaningful it would be a no-op.  Further, if it is meaningful, the exact
function may vary form driver to driver. WAN drivers are the most likely to
benefit from this command line function.

 ****************************************************************
  ODISETUP.EXE Usage..
 ****************************************************************

 ODISETUP.EXE is a command line utility used for installing/updating ODI
modules on Windows 95.

 usage: odisetup [-r | -u | -x] [-p <path to inf files>] [-c] [-n]

      The -p option allows inf files from the specified directory path to
      be copied the the windows inf directory.  A path is required with the
      option.  The fat table reordering will take place with the inf files
      just copied being first in the list.

      The -r, -u, and -x are mutually exclusive.

      The -r option does a replacement, meaning that is searches all inf
      files for a match to the currently installed driver rather than simply
      using the current driver's inf.  This is useful in such cases as a
      driver's name changed or the driver's inf file name changed.

      The -u option just does an update on the current driver.  Inf files
      are not searched, the installed driver's inf file is used.  This is
      useful in cases where the name of the driver and inf file remained
      the same but there the driver is updated and/or there is new info
      in the driver's inf file.  The -u is the default if a -r or -x is not
      present

      The -x indicates that no driver replacement be performed.  The
      absence of the -x indicates that the default replacement take place
      unless a -r or -u is present.

      The -n option does not try to replace NDIS drivers with ODI drivers.

      The -c options runs the registry cleanup procedure.

      If no argument is given, then only the default driver replacement is
      run.

 ****************************************************************
  ODI Files Updates and Changes Section.
 ****************************************************************

 **LAN DRIVER FILES**

   NOVELL 32 BIT ASSEMBLY LAN DRIVER FILES

 NE3200.LAN and NE3200P.LAN
      Fixed a problem where the driver sometimes failed to filter out
      unwanted multicast receive frames when in promiscous mode.

      Fixed a problem where frames were received when the board was shutdown.

 NTR2000.LAN and NE2_32.LAN
      Fixed a problem that caused occasional load failures.

 NE2000.LAN
      Fixed a problem that prevented the driver from loading on some of the
      older NE2000 adapters.

   NOVELL 32 BIT "C" HSM LAN DRIVER FILES

 CNE2.LAN, CNE2_32.LAN, CNE2000.LAN, CNEAMD.LAN and CNE3200.LAN
      Fixed problems with shutting down and/or resetting an instance
      of the driver.

 CNEAMD.LAN
      Increased performance and reliability by increasing the number of
      receive buffers.

      Fixed a problem with receiving and passing up error packets when
      in promiscuous mode.

 CNTR2000.LAN
      Fixed a problem where the driver caused a prompt for the memory
      parameter even though it was already on the command line.

 **NOVELL SERVER FILES**

 MSM.NLM and MSM31X.NLM have been updated to improve performance and
      reliability. Support has been added for LAN drivers that perform
      IP ckecksumming.

      The LAN Driver TSM modules have been updated to improve performance
      and reliability.

 **NOVELL ODI CLIENT32 FILES**

 LSLC32.NLM has been updated to improve performance and reliability.
      Fixed a problem that could prevent protocol stacks from loading.

 CMSM.NLM has been updated to improve performance and reliability.
      Support has been added for adapters that perform checksumming.

      Fixed a potential problem where adapter interrupts were being
      disabled for an extended amount of time.

      Fixed a problem where configuration table values were being over-
      written by outdated information.

      Fixed parser problems to eliminate driver load issues and
      unnecessary parameter prompting.

      Fixed problems with driver instance loads and unloads.

      Now prints the correct message if the keyword value is missing.

 The Client32 LAN Driver TSM modules have been updated to improve
      performance and reliability. Support has been added for adapters
      that perform checksumming

 TOKENTSM.NLM, FDDITSM.NLM

      Fixed problems in priority packet support.

 ODILOAD.VXD has been updated to increase performance and reliability.
      Added instance unload of a logical LAN board. Enabled Odiload
      to work on Win98.

 ODINSUP.SYS has been updated to increase performance and reliability.
      It is now an NDIS Miniport driver.

      Fixed the potential of two odinsups binding to the same adapter.

      Fixed a problem where if a packet arrived longer than the maximum
      allowed by the media, odinsup would allow the entire packet to be
      written to its buffer. This caused corruption of the internal
      structures.

      Fixed a problem, ensuring all multicast addresses are added to the list.

      Provided a time out to wait for adapters to become ready. Token-Ring
      adapters with a cable disconnected would appear to hang the machine.

 ODIPAGE.DLL has been updated to increase performance and reliability.
      Added three new tabs: LSL, ODI Info, and Statistics.The LSL tab
      allows LSL parameters to be set.  The ODI Info tab displays
      configuration table information for the MLID, LSL, CMSM, and CTSMs.
      The Statistics tab displays the statistic tables for the MLID and LSL.
      The statistics tables are updated once a second.

      Fixed a potential page fault when used in conjunction with ATM drivers.

      Fixed a problem with installing a device and the wrong resources
      were getting assigned.

      Fixed parsing of quoted strings to handle intermixed white space.

      Fixed potential page faults due to memory relocation.

      Preserved the driver's hardware profile state.  The previous version
      would always enable the driver for all profiles even if the user had
      marked it as disabled.

 **NOVELL ODI NT Files**

 LSL.SYS has been updated to increase performance and reliability
      Cleaned up buffer management.

      Added the ability for the LSL to read from the registry minimum and
      maximum ECB counts for various ECB buffer pools.

 ODILOAD.SYS has been updated to increase performance and reliability
      Added missing specification APIs.  Some drivers would fail to load
      without these APIs. Priority packets are now supported.

      Fixed register preservation for assembly language drivers which would
      cause load failures or exceptions in some drivers.

      Added checks for invalid parameters.  This protects against possible
      exceptions.

      Cleaned up the return codes for those calling MLIDShutdown.

      Updated parsing the driver's command line parameters to better handle
      the various types of parameter options.

      Updated the shutdown, reset, and removal to set the correct state,
      manage resources, and notify others of the state change.

      Enhanced limitations of retrieving resources from docking stations
      in order for LAN drivers to successfully load in these environments.

      Fixed the problem of removing individual logical boards.

      Corrected problems where drivers wanted physical RCBs

      Protected against interrupt enable and disable counts from getting
      out of sync.  This problem would prevent drivers from sending and
      receiving packets.

      Corrected problem were Token-Ring drivers would not get the
      information they needed to finish initializing or reseting due
      to odiload disabling their interrupts.

      Corrected a problem where information for one of the driver's
      configuration tables got copied to one or more of the driver's
      other configuration tables.  This increases driver performance.

      Corrected a problem where drivers using physical addresses to packet
      information needed to get logical address of the information.

      Provided extra information in the registry for odinsup. Odinsup uses
      this information to prevent it from binding to the same adapter more
      than once.

 ODINSUP.SYS
      Odinsup.sys in now a NDIS Miniport driver.

      Fixed the potential of two odinsups binding to the same adapter.

      Fixed a problem where if a packet arrived longer than the maximum
      allowed by the media, odinsup would allow the entire packet to be
      written to its buffer. This caused corruption of the internal
      structures.

      Increased performance by using timers rather than process scheduling.

      Provided a time out to wait for adapters to become ready.Token-Ring
      adapters with a cable disconnected would appear to hang the machine.

 OEMNADOA.INF
      Added "Microdyne EtherMAX ISA Adapter" to the list of adapters.

 OEMNADOD.INF
      Added "Microdyne NE10/100 PCI FAST Ethernet Adapter",
      "Olicom Ethernet PCI/II 10/100 Adapter", "Olicom Ethernet
      PCI/II 10/100 Adapter", and "Olicom Ethernet PCI/II 10
      Adapter" to the list of adapters.

 ODINTMSG.DLL
      Replaced the message "The expected board name for the NAME parameter
      was missing or invalid." with "Missing the value for keyword '%2'."

 ****************************************************************
  Source Routing and RPL Information.
 ****************************************************************

       The source routing files have been included and are copied during the
installation process. For information on configuring the source routing files,
see the documents in the SROUTE.DOC directory. The RPL files that are needed
for 16-bit Clients have also been included. For information on configuring RPL
see the RPL documents in the RPL\RPLDOC directory.

Self-Extracting File Name: odi33f.exe

Files Included     Size     Date      Time

..\
      ODI33F.TXT     (This file)
      ODIKIT.IPS           14509        12-17-97     12:31:18 pm
     PI_ICMD.NLM           20085         2-19-97      1:00:48 pm
    PI_IOCON.NLM            1868         7-29-96     10:32:30 am
    PI_IOMKD.NLM            1250         6-28-96      9:04:58 am
..\CLIENT\
    MPRDINST.NLM            6535          1-3-96     11:00:36 am
    PINSTALL.HLP            5585        11-15-95     11:54:18 am
    PINSTALL.NLM          161904          1-3-96      5:15:08 pm
     PSCRIPT.DAT            7761        12-17-97     12:33:44 pm
      RSPAWN.NLM           23087          1-3-96      5:15:32 pm
..\CLIENT\16BIT\
      LANSUP.COM           23398          4-1-96      1:39:40 pm
      LANSUP.INS             961          1-4-96      4:56:26 pm
         LSL.COM           18356          4-1-96     10:55:08 am
      NE1000.COM           21826          4-1-96     11:33:18 am
      NE1000.INS             655          1-4-96      4:56:26 pm
     NE1500T.COM           31240          4-1-96      1:23:20 pm
     NE1500T.INS             726          1-4-96      4:56:26 pm
         NE2.COM           22328          4-1-96      1:20:24 pm
         NE2.INS             467          1-5-96      1:53:08 pm
      NE2000.COM           23509          4-1-96      1:21:20 pm
      NE2000.INS            1177         8-26-96      9:11:50 am
      NE2100.COM           31238          4-1-96      1:23:08 pm
      NE2100.INS             716          1-4-96      4:56:26 pm
      NE2_32.COM           22016          4-1-96      1:22:50 pm
      NE2_32.INS             449          1-4-96      4:48:00 pm
      NE3200.COM           28582         9-19-96      9:03:14 am
      NE3200.INS             678          1-4-96      4:56:26 pm
        NESL.COM            9696          4-1-96     11:16:54 am
     NTR2000.COM           27143         3-13-97      1:50:10 pm
     NTR2000.INS             797         3-30-96     10:51:22 am
     ODINSUP.COM           34380         1-10-96      1:47:38 pm
       ROUTE.COM            4936         1-10-96     12:28:52 pm
      TRXNET.COM           21031         2-19-97      9:29:48 am
      TRXNET.INS             686          1-4-96      4:48:00 pm
..\CLIENT\16BIT\NLS\
         LSL.MSG            3596         1-10-96     12:14:24 pm
        NESL.MSG            1134         1-10-96      1:50:58 pm
..\CLIENT\32BIT\
        CNE2.LAN           10426         8-25-97      4:23:24 pm
     CNE2000.LAN           14250        11-25-97      2:08:30 pm
     CNE2_32.LAN           10434         7-17-97      2:51:20 pm
     CNE3200.LAN           20292        11-11-97     10:44:38 am
      CNEAMD.LAN           20533        11-13-97      5:50:12 pm
    CNTR2000.LAN           18628         12-2-97     10:48:30 am
      NE1000.LAN            4664         2-13-97      1:30:52 pm
..\CLIENT\32BIT\CLIENT32\
        CMSM.NLM           71987        12-10-97     10:21:52 am
    ETHERTSM.NLM           16013        11-14-97      7:05:40 pm
     FDDITSM.NLM           16061        11-14-97      6:56:04 pm
      LSLC32.NLM           20032        11-17-97     11:25:18 am
      N16ODI.COM            9053        11-20-97      7:44:28 pm
    PC32MLID.LAN           33265        11-26-97      4:52:08 pm
      SROUTE.NLM            9658         3-12-97     10:53:44 am
    TOKENTSM.NLM           17879        11-14-97      6:59:00 pm
..\CLIENT\32BIT\CLIENT32\DOSWIN\
        CNE2.LDI            3508         12-8-97      4:18:34 pm
     CNE2000.LDI           23123         12-8-97      4:16:00 pm
     CNE2_32.LDI            3683         12-8-97      4:20:58 pm
     CNE3200.LDI            5200         12-8-97      4:23:40 pm
      CNEAMD.LDI           14596         12-9-97     10:13:28 am
    CNTR2000.LDI           14034         12-8-97      4:14:52 pm
      NE1000.LDI            6678         2-12-97      4:19:54 am
     ODINSUP.386           33778          5-8-97      7:55:30 am
     PDOSETH.COM           23122         2-18-97      3:31:08 pm
    PDOSFDDI.COM           23071         2-18-97      3:31:36 pm
    PDOSMLID.NLM           12110         2-28-97      9:23:54 am
     PDOSTOK.COM           23876         2-18-97      3:31:22 pm
      UPDATE.BAT             429         4-14-97     11:25:40 am
     VLANINT.386            9377         6-23-95      1:18:50 pm
..\CLIENT\32BIT\CLIENT32\WIN95\
      ATMLEC.DLL           13648          6-4-97     10:56:56 am
      ATMLEC.INF            8782         1-24-97      4:54:40 pm
      LANSUP.INF            6676          8-8-96      3:31:36 pm
      NE1000.INF            9105        11-18-97     11:51:26 am
         NE2.INF            7874        11-18-97     12:06:48 pm
      NE2000.INF           17436        11-18-97     11:29:10 am
      NE2_32.INF            7318        11-18-97     12:04:50 pm
      NE3200.INF            8355        11-18-97     11:30:32 am
       NEAMD.INF           14865        11-18-97     12:01:10 pm
     NTR2000.INF            8820        11-18-97     12:03:04 pm
     ODILOAD.VXD           19818         11-4-97     11:26:54 am
     ODINSUP.INF            4102         4-23-97      9:40:22 am
     ODINSUP.SYS           17248        11-26-97      5:22:34 pm
     ODIPAGE.DLL           74688         12-8-97      2:49:22 pm
    ODISETUP.EXE           40688         10-2-97      5:47:44 pm
      TRXNET.INF            9851          8-8-96      3:30:28 pm
      UPDATE.BAT             883        12-17-97     11:25:38 am
..\CLIENT\32BIT\NLS\
        CMSM.MSG            3770         10-9-97      2:07:52 pm
        CNE2.MSG             980         8-25-97      4:23:20 pm
     CNE2000.MSG            1092         8-25-97      4:21:02 pm
     CNE2_32.MSG             777         7-17-97      2:51:20 pm
     CNE3200.MSG            1088        11-11-97     10:44:04 am
      CNEAMD.MSG             867        11-13-97     12:31:24 pm
    CNTR2000.MSG            1708          6-9-97      4:29:34 pm
    ETHERTSM.MSG             968        11-14-97      7:05:02 pm
     FDDITSM.MSG             980        11-14-97      6:55:32 pm
      LSLC32.MSG            1941        11-17-97     11:21:32 am
      N16ODI.MSG            2548        11-20-97      6:45:48 pm
    PC32MLID.MSG            6217         3-13-97      1:56:54 pm
    PDOSMLID.MSG            1694         2-27-96      8:05:08 pm
      SROUTE.MSG            2739         1-27-97     11:37:14 am
    TOKENTSM.MSG            1044        11-14-97      6:58:26 pm
..\CLIENT\32BIT\NT\
    ETHERTSM.NLM           15852        11-14-97      7:07:04 pm
     FDDITSM.NLM           15900        11-14-97      6:57:30 pm
         LSL.SYS           26080         10-9-97      1:56:56 pm
         NBI.SYS            9312          9-4-97     10:32:40 am
     ODILOAD.SYS           64032         12-9-97      5:08:20 pm
     ODINSUP.SYS           16832        11-26-97      5:02:48 pm
    ODINTMSG.DLL            9728         8-19-97      4:17:54 pm
    OEMNADOA.INF           40989         3-21-97      9:48:26 am
    OEMNADOB.INF           36845         3-21-97      9:48:34 am
    OEMNADOC.INF           36437         3-21-97      9:48:40 am
    OEMNADOD.INF           39268         3-21-97      9:48:46 am
      REGAMD.EXE           35840          4-7-97      1:14:36 pm
      SROUTE.SYS           14176        11-10-97      2:17:00 pm
    TOKENTSM.NLM           17686        11-14-97      7:00:24 pm
      UPDATE.BAT            1526         5-22-97      1:43:06 pm
..\CLIENT\NLS4\
    MPRDINST.MSG             863          1-3-96     11:00:36 am
      RSPAWN.MSG            1658          1-3-96      5:15:32 pm
..\RPL\
      3CBOOT.NLM            8604         11-2-92      9:22:58 am
       A8022.LAN             152         5-12-93      3:24:12 pm
       A8022.OBJ            3620         4-14-93     11:19:04 am
       B8022.OBJ            3620         4-14-93     11:19:12 am
     BOOTNCP.COM            5136         10-8-91      3:48:20 pm
       C8022.OBJ            3620         4-14-93     11:19:20 am
       D8022.OBJ            3620         4-14-93     11:19:28 am
     DCONFIG.EXE           22701          7-1-92      1:31:48 pm
      DOSGEN.EXE           11008          8-5-93     12:26:22 pm
       ETHER.RPL           16264         10-3-94      8:48:20 am
       F1ETH.RPL           12133         10-3-94      9:27:54 am
    NEARSERV.EXE            9214        11-22-93     11:44:48 am
       PCN2L.RPL           10991         10-3-94      9:31:26 am
       RBOOT.RPL            8074         4-30-96     10:46:34 am
    RPCONFIG.COM            2744         7-14-92      9:05:00 am
         RPL.COM            8318         4-29-93     11:33:30 am
         RPL.NLM            6389         5-23-96      3:24:54 pm
         RPL.TXT            3235          4-7-97      9:48:02 am
         RPL.VP1            1897         10-5-93      8:55:46 am
      RPLFIX.COM            1838         6-30-93     10:56:12 pm
      RPLODI.COM            1652         3-21-91      2:24:30 pm
       TOKEN.RPL           18676         7-17-96      8:42:42 am
..\RPL\RPLDOC\
      DOSGEN.DOC            2501          2-2-96      2:35:40 pm
    NEARSERV.DOC             332         2-13-96      3:30:56 pm
      RPLCOM.DOC           32353        10-14-93      5:38:06 pm
      RPLFIX.DOC            4214        10-15-93     10:16:00 am
      RPLNLM.DOC           23229         2-28-96      9:08:06 am
      RPLODI.DOC            2464        10-15-93     10:00:46 am
      RPLVP1.DOC           11310          2-2-96      2:45:10 pm
..\SERVER\
    MPRDINST.NLM            6535          1-3-96     11:00:36 am
    PINSTALL.HLP            5585        11-15-95     11:54:18 am
    PINSTALL.NLM          161904          1-3-96      5:15:08 pm
     PSCRIPT.DAT            3035        12-17-97     12:32:42 pm
      RSPAWN.NLM           23087          1-3-96      5:15:32 pm
..\SERVER\32SPEC\
      32SPEC.DOC            6734        10-16-96      1:38:54 pm
    ETHERTSM.NLM            9425         4-18-95     11:04:26 am
     FDDITSM.NLM            8914         3-14-95      2:39:12 pm
    FIRMLOAD.COM            1628          1-4-91      8:57:38 am
     HISTORY.DOC           15771         8-28-96     10:32:58 am
      NE1000.LAN            4472         3-28-94      8:28:04 am
     NE1500T.LAN            7500        11-23-94      3:59:52 pm
         NE2.LAN            5034        11-23-94      3:53:52 pm
      NE2000.LAN            7382        11-23-94      3:56:28 pm
      NE2100.LAN            7498        11-23-94      4:00:00 pm
      NE2_32.LAN            5090         3-28-94      8:48:10 am
      NE3200.LAN           14237         6-30-94      8:04:40 am
     NE32HUB.LAN           12266         1-27-93      9:11:10 am
     NTR2000.LAN           11399        11-23-94      1:49:44 pm
       PCN2L.LAN            4726         1-29-93      8:45:04 pm
    PCN2LTSM.NLM            5691         1-30-93     11:32:22 am
       ROUTE.NLM            5077          6-4-96      8:14:44 am
    RXNETTSM.NLM            6321         9-26-94     10:46:54 am
       STATS.DOC           63446         10-6-93      3:55:10 pm
    TOKENDMA.DOC            6203         4-11-96     11:20:34 am
    TOKENDMA.LAN           10861         5-26-93      3:16:54 pm
    TOKENTSM.NLM            9457         3-14-95      2:39:44 pm
      TRXNET.LAN            3075          1-7-93      1:23:28 pm
..\SERVER\32SPEC\31X\
      MSM31X.NLM           21308        11-23-94     11:41:38 am
..\SERVER\32SPEC\31X\311\
      LSLENH.NLM           11645        12-21-94     12:17:28 pm
    PATCHMAN.NLM           15591         1-22-96     11:22:52 am
..\SERVER\32SPEC\410\
         MSM.NLM           20252        11-23-94     11:41:26 am
..\SERVER\32SPEC\CONFIG\
    !NVL0701.CFG            2745          9-2-92      1:25:30 pm
    !NVL0901.CFG            8293         10-4-90     10:42:34 am
    !NVL1201.CFG            7378         3-26-92      9:08:46 am
    !NVL1301.CFG            1169         3-12-92      2:28:50 pm
    !NVL1401.CFG             986         6-10-92      4:02:08 pm
    !NVL1501.CFG           11994         1-11-93      3:24:22 pm
       @7151.ADF            2346         7-26-89      5:08:06 pm
       @7154.ADF            2657         4-27-92      1:54:54 pm
..\SERVER\33SPEC\
        CNE2.LAN           10426         8-25-97      4:23:24 pm
        CNE2.LDI            3508         12-8-97      4:18:34 pm
     CNE2000.LAN           14250        11-25-97      2:08:30 pm
     CNE2000.LDI           23123         12-8-97      4:16:00 pm
     CNE2_32.LAN           10434         7-17-97      2:51:20 pm
     CNE2_32.LDI            3683         12-8-97      4:20:58 pm
     CNE3200.LAN           20292        11-11-97     10:44:38 am
     CNE3200.LDI            5200         12-8-97      4:23:40 pm
      CNEAMD.LAN           20533        11-13-97      5:50:12 pm
      CNEAMD.LDI           14596         12-9-97     10:13:28 am
    CNTR2000.LAN           18628         12-2-97     10:48:30 am
    CNTR2000.LDI           14034         12-8-97      4:14:52 pm
    ETHERTSM.NLM           13054         12-8-97      3:20:38 pm
     FDDITSM.NLM           12500        11-19-97      4:43:02 pm
      NE1000.LDI            6729         12-8-97      4:38:28 pm
     NE1500T.LAN            7758         5-22-97      9:29:24 am
     NE1500T.LDI            4122         2-12-97      4:57:48 am
         NE2.LAN            5307         7-10-97     12:06:02 pm
         NE2.LDI            3811         12-8-97      4:43:56 pm
      NE2000.LAN            8091         7-10-97     11:58:40 am
      NE2000.LDI           14420         12-8-97      4:41:46 pm
      NE2100.LAN            7756         5-22-97      9:29:08 am
      NE2100.LDI            4056         2-12-97      4:59:22 am
      NE2_32.LAN            5354         2-13-97      1:49:56 pm
      NE2_32.LDI            3880         2-12-97      4:56:32 am
      NE3200.LAN           16043        11-14-97      3:54:54 pm
      NE3200.LDI            5764         12-8-97      4:47:16 pm
     NE3200P.LAN           16551        11-14-97      3:55:22 pm
     NE3200P.LDI            5778         12-8-97      4:48:02 pm
     NTR2000.LAN           11646        12-17-97      9:26:56 am
     NTR2000.LDI           13696         12-8-97      4:50:38 pm
       ROUTE.NLM            5077          6-4-96      8:14:44 am
    TOKENTSM.NLM           13194         12-5-97      5:00:14 pm
..\SERVER\33SPEC\312\
      MSM31X.NLM           69024         12-2-97      4:05:42 pm
      NBI31X.NLM           37802         8-29-97      2:09:30 pm
..\SERVER\33SPEC\41X\
         MSM.NLM           76997         12-2-97      4:05:26 pm
         NBI.NLM           20338         8-29-97      2:08:36 pm
         NEB.NLM           19952         4-30-97      4:39:56 pm
      ODINEB.NLM           12821        11-14-97      7:26:00 pm
..\SERVER\NLS4\
    MPRDINST.MSG             863          1-3-96     11:00:36 am
      RSPAWN.MSG            1658          1-3-96      5:15:32 pm
..\SROUTE.DOC\
     HISTORY.DOC            3517         3-10-97      3:25:26 pm
       ROUTE.VP0            3896        11-30-93      3:28:44 pm
    SRCONFIG.COM            5462         12-2-93     10:07:12 am
      SROUTE.DOC           11466         11-8-96      8:17:58 am


Installation Instructions:


 ****************************************************************
  Note: This ODI update is for English only.
 ****************************************************************

  Before installing, make sure the following items have been completed.

 410PTx.EXE (Where "x" is 6 or higher) must be installed on NetWare v4.10 file
servers prior to installing ODI33F.EXE.  Without this patch the following
message may be displayed when NBI.NLM loads.

 "Warning: This version of NetWare does not support protected mode BIOS
accesses. Without a loader patch some PCI drivers may fail."

 312PTx.EXE (Where "x" is 8 or higher) must be installed on NetWare v3.12 file
servers prior to installing ODI33F.EXE.  Without this patch the following
message may be displayed when NBI.NLM loads.

 "Warning: This version of NetWare does not support protected mode BIOS
accesses. Without a loader patch some PCI drivers may fail."

 Note: If NIAS V4.0 or MPR V3.1 is installed, ODIWANx.EXE must also be install
after ODI33F to update the WAN drivers for these products. The shipping
versions of these products contain WAN drivers that will not load with the ODI
3.31/1.11 support files.

  Note: Do not install the ODI 3.31/1.11 support files update kit on file
servers that have NetWare Connect 2.0 (or lower), MPR 3.0 (or lower), or
NetWare for SAA. The WAN drivers in these products will not load with the ODI
3.31/1.11 support files. The install checks for these specific products, and
the install will not allow the ODI 3.31/1.11 support files update kit to be
installed if they exist.

 Note: 32-bit LAN drivers written to the "C" spec v1.10 will not work with the
current ODI 3.31/1.11 support modules.  There has been only one third party
driver (CMDGODI.LAN 06/07/96 124292) certified to the "C" spec v1.10.  If this
driver is being used, do not update to the current ODI 3.31/1.11 support
modules until an updated driver from Madge written to the "C" spec v1.11 is
available to be used.  All of Novell's "C" spec v1.10 LAN drivers have been
updated to the "C" spec v1.11, and are included.

 Note: CNE2100.LAN and CNE1500T.LAN will be replaced with CNEAMD.LAN. If you
were using CNE2100.LAN or CNE1500T.LAN, the configuration file that loaded this
driver will need to be changed to match the new name CNEAMD.LAN. On file
servers this will be AUTOEXEC.NCF or INETCFG.NLM. On Client32 for DOS/WIN this
will be STARTNET.BAT. On Client32 for Windows95 ODISETUP.EXE has been provided
to update the registry. On NT Clients REGAMD.EXE has been provided to update
the registry. Details are given in each of the installation instructions for
each platform.

 Make a backup of LAN drivers and support modules (NBI, MSM, and TSMs). This is
important in case third party LAN drivers have problems with the new ODI
support modules. The 4.1x install puts the existing NBI, MSM, and TSMs in
sys:system\oldlan.  However, it was not possible to do this with the install
script for 3.1x.

 =======================================================
 ODIKIT Installation Instructions on 4.1X versions of NetWare using
INSTALL.NLM.
 =======================================================

  Novell has provided an installation script to be used with INSTALL.NLM
"Product Options".

  This script file can be run in several ways:
  1- From a local A: drive at the file server <Enter> or <F3>.
  2- From a local drive at the client using Rconsole <F4>.
  3- From a local volume at the file server <F3>, by specifying the path
including volume name..ie SYS:\FODI33F.
  4- From a different file server on the network <F3> by specifying full path
including server name..ie Server_Name\SYS:\FODI33F.

  NOTE: The fastest installation in order of performance is: option 3, option
4, option 2, option 1.
 ________________________________________________________________
     
 Installation Instructions on 4.1X versions of NetWare:

    1) Extract FODI33F to a Network drive or a local hard drive according to
the install option desired. All of the files in FODI33F will not fit onto a
diskette. If you need to use a diskette to install; copy *.nlm and *.ips from
the root of FODI33F, the "Server" directory structure and files from FODI33F,
and the "RPL" directory structure and files from FODI33F onto a diskette.

    2) Load Install at the file server.

    3) Select "Product options".

    4) Select "Install a product not listed".

    5) Choose the install option (<F3>, <F4>, or <Enter>).

    6) Enter the path to the location where FODI33F was extracted. If <Enter>
was used in the previous step, the root of A: at the file server is used.

    7) At this point two file groups will be displayed.  Mark the file group
that is to be installed. Only one file group may be selected. The v3.2 Spec
file group may not be installed on NetWare v4.11.

    8) Press <F10> to continue.

 Note:  The files copied to the dos partition on each IOEngine on SFT III File
Servers will have the date of the machine when they were copied.

 =======================================================
 ODIKIT Installation Instructions on 3.1X versions of NetWare
 using INSTALL.NLM.
 =======================================================

 Note: This install procedure will install the ODI 3.31/1.11 spec support
modules and LAN drivers on 3.12 file servers and the ODI 3.20 spec support
modules and LAN drivers on 3.11 file servers.  If you want the ODI 3.20 spec
support modules and LAN drivers on a 3.12 file server you will need to copy
them manually.  See 32SPEC.DOC in the server\32spec directory.
 ________________________________________________________________

      Novell has provided PINSTALL.NLM to be used with INSTALL.NLM  "Product
Options" to install .

 PINSTALL.NLM can be run in either of the following ways:
  1- From a local A: Drive at the file server.
  2- From a local volume at the file server, by specifying the path including
volume name..ie SYS:\BOID33F\SERVER.
 ________________________________________________________________
     
 Installation Instructions on 3.1X versions of NetWare:

    1) Extract BOID33F to a Network drive on the file server.  If you are using
diskettes to install BOID33F, you will need to format two diskettes.  Label one
diskette "SERVER" and the other "RPL" using the dos label command.  Copy all of
the files (including subdirectories and files) in the Server directory of
BOID33F to the diskette labeled "SERVER".  Copy all of the files (including
subdirectories and files) in the RPL directory of BOID33F to the diskette
labeled "RPL".

    2) Load Install at the file server.

    3) Select "Product Options".

    4) Press <Ins>.

    5) Enter the path to the location of the "SERVER" directory where BOID33F
was extracted..ie SYS:\BOID33F\SERVER.

    6) Select "Install Product".

    7) Press <Enter> and select "Yes" to start the installation.

 ****************************************************************
 On NetWare Clients, INSTALL.NLM needs to be used on a v3.12, v4.10, or v4.11
file server to set up install directories on the file server containing the ODI
files needed for each of the clients. This is described in each of the NetWare
Client's install instructions. However, setting up the install directories on
the file server containing the Client ODI files needs to be done only once. The
instructions for installing the files to the Client is different for each
Client.
 ****************************************************************

 =======================================================
 ODIKIT Installation Instructions for Windows95 Client ODI files.
 =======================================================

 Note: This ODI update is for English only.
     
 Installation Instructions for Windows95 Client:

    1) Extract BOID33F to a Network drive on the file server.

    2) Load Install at the file server.

    3) Select "Product Options".

    4) On 4.1x servers select "Install a product not listed" and press <F3>. 
On 3.12 servers Press <Ins>.

    5) Enter the path to the location of the "CLIENT" directory where BOID33F
was extracted..ie SYS:\BOID33F\CLIENT.

    6) Select "Install Product".

    7) Press <Enter> and select "Yes" to start the installation.

    8) Exit install.

    9) At this point the Windows95 ODI files are located on the file server in
SYS:ODIKIT\CLNT_ENU\WIN95.  Use this location or copy these files to another
location to continue the installation.

    10) Close all applications and open windows to avoid any possible sharing
violations while updating files.

    11) Change to the drive letter where these files are located.

    12) CD to the directory where these files are located.

    13) Run UPDATE.BAT from this same directory.  UPDATE.BAT assumes Novell's
client and Windows95 are installed in the default directories of drive C.

    14) A message "The disk labeled 'Novell NetWare Client-32 LAN driver disk'
is now required.  This disk is provided by your computer manufacturer.  Click
OK to continue." will be displayed.  Click OK to continue.

    15) A message listing a file that could not be found will be displayed. 
This message prompts for the location of the file that can not be found.  If
the file is a *.com file, enter "c:\Novell\NWClient" as the directory.  If the
file is a *.lan file, enter "c:\Novell\Client32" as the directory.  If the file
is a *.msg file, enter "c:\Novell\Client32\NLS\English" as the directory.

    16) Steps 14 and 15 may need to be done several times depending on the LAN
drivers installed on the workstation.

 =======================================================
 ODIKIT Installation Instructions for NT Client ODI files.
 =======================================================

 Note: This ODI update is for English only.
     
 Installation Instructions for NT Client:

    1) Extract BOID33F to a network drive on the file server.

    2) Load Install at the file server.

    3) Select "Product Options".

    4) On 4.1x servers select "Install a product not listed" and press <F3>. 
On 3.12 servers Press <Ins>.

    5) Enter the path to the location of the "CLIENT" directory where BOID33F
was extracted..ie SYS:\BOID33F\CLIENT.

    6) Select "Install Product".

    7) Press <Enter> and select "Yes" to start the installation.

    8) Exit install.

    9) At this point the NT ODI files are located in SYS:ODIKIT\CLNT_ENU\NT. 
Use this location or copy these files to another location to continue the
installation.

    10) Change to the drive letter where these files are located.

    11) CD to the directory where these files are located.

    12) Run UPDATE.BAT from this same directory.

 =======================================================
 ODIKIT Installation Instructions for DOS/WIN Client ODI files.
 =======================================================

 Note: This ODI update is for English only.
     
 Installation Instructions for DOS/WIN Client:

    1) Extract BOID33F to a network drive on the file server.

    2) Load Install at the file server.

    3) Select "Product Options".

    4) On 4.1x servers select "Install a product not listed" and press <F3>. 
On 3.12 servers Press <Ins>.

    5) Enter the path to the location of the "CLIENT" directory where ODI33F
was extracted..ie SYS:\BOID33F\CLIENT.

    6) Select "Install Product".

    7) Press <Enter> and select "Yes" to start the installation.

    8) Exit install.

    9) At this point the DOS/WIN ODI files are located on the file server in
SYS:ODIKIT\CLNT_ENU\DOSWIN.  Use this location or copy these files to another
location to continue the installation.

    10) Change to the drive letter where these files are located.

    11) CD to the directory where these files are located.

    12) Run UPDATE.BAT from this same directory.  UPDATE.BAT needs to be run
from DOS prior to loading Windows.

      Another way to update the ODI files would be to copy the files to a
location where a network client install for DOS/WIN exists.  The directory
structure under SYS:ODIKIT\CLNT_ENU\DOSWIN matches the directory structure of a
Network install for Client32 for DOS/WIN or Intranetware for DOS/WIN.  The new
ODI files can be copied into the Client Network install directory structure
using NCOPY with the "/s" parameter..ie "ncopy F:\ODIKIT\CLNT_ENU\DOSWIN\*.*
G:\PUBLIC\CLIENT\DOSWIN32\IBM_6\*.* /S". After the files are copied the client
install can be run to complete the update of the ODI files.



 -----------------------------------------------------------------
 Any trademarks referenced in this document are the property of their
respective owners.  Consult your product manuals for complete trademark
information.
 -----------------------------------------------------------------

