INSTRUCTIONS TO INSTALL ON NETWARE V3.11:

A) Rename the old .lan file, monitor.nlm, patchman.nlm.
B) Copy the .lan and all .nlm files into your system directory.
   (Except for PM311IO.NLM, LSLENH3.NLM, and IOSHIM.NLM these files
    are for SFT III v3.11 only.)
C) Load lslenh.nlm first.  this will auto load patchman.nlm.
D) Load <filename>.lan, this will auto load msm/msm31x and xxxxxTSM.NLM.

* * * * * * * * * * * * * *  PLEASE NOTE * * * * * * * * * * * * * * * * * *
NOTE 1:  USE the included MONITOR.NLM with these new drivers.  If you use
      the shipping v3.11 MONITOR.NLM your server could abend when viewing
      LAN statistics in MONITOR.NLM with these newer drivers.  This
      MONITOR.NLM included is tested and fixed.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
NOTE 2:  Loading MSM.NLM will generate warnings that cause MSM31X.NLM
      to be auto-loaded.  This is normal.  The warning messages generated
      will be as follows:
      "Loader cannot find public symbol:" followed by the public symbol
      name.
      On NetWare v3.1x you can remove MSM.NLM and rename MSM31X.NLM to
      MSM.NLM which will eliminate the warning messages.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
NOTE 3:  Do not use PM311IO.NLM, LSLENH3.NLM, and IOSHIM.NLM on NetWare v3.11
      these files are for SFT III v3.11 only.




INSTRUCTIONS TO INSTALL ON SFT III V3.11:

A) Rename the old *.lan, *tsm.nlm, and msm*.nlm files.
B) Copy the new *.lan *tsm.nlm, and msm*.nlm files into the dos directory
   of each server where files loaded from IOSTART.NCF are loaded.  These
   files should also be put into the SYSTEM directory of VOL SYS in case
   the drivers are unloaded and reloaded while the servers are still up
   and running.
C) Copy PM311IO.NLM and LSLENH3.NLM into the dos directory of each server
   where files loaded from IOSTART.NCF are loaded.
D) Add "load lslenh3" to the IOSTART.NCF of each server prior to the load
   statement for the lan drivers, this will auto load PM311IO.NLM.
E) Load <filename>.lan in the IOSTART.NCF of each server after the load
   statement for lslenh3.nlm, this will auto load msm/msm31x and
   xxxxxTSM.NLM.

* * * * * * * * * * * * * *  PLEASE NOTE * * * * * * * * * * * * * * * * * *
NOTE 1:  Do not use the included MONITOR.NLM with SFT III V3.11.  Use
      the shipping MONITOR.NLM with SFT III V3.11.  LAN statistics
      are not part of MONITOR.NLM in SFT III V3.11.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
NOTE 2:  Loading MSM.NLM will generate warnings that cause MSM31X.NLM
      to be auto-loaded.  This is normal.  The warning messages generated
      will be as follows:
      "Loader cannot find public symbol:" followed by the public symbol
      name.
      On SFT III V3.11 you can remove MSM.NLM and rename MSM31X.NLM to
      MSM.NLM which will eliminate the warning messages.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
NOTE 3:  Do not use LSLENH.NLM, PATCHMAN.NLM, MONITOR.NLM, XLOAD.EXE, or
      LDR001.PTF with SFT III V3.11, these files are for NetWare V3.11
      only.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
NOTE 4:  If you are using NE2000.LAN copy IOSHIM.NLM and make sure it is
      loaded prior to LSLENH3.NLM.


LANDR2.EXE contains the following Novell server drivers.  The following files
are the latest certified OS drivers available.

MSM      NLM    15380  3-11-93 12:38p - 4.0 Media Support Module (MSM)
MSM31X   NLM    16189  3-11-93 12:38p - 3.11 Media Support Module (MSM)
ETHERTSM NLM     7929  5-24-93  4:18p - Ethernet Topology Support Module (TSM)
TOKENTSM NLM     7668  5-12-93  4:03p - Token Topology Support Module
RXNETTSM NLM     6202  1-06-93 10:04a - Arcnet Topology Support Module
PCN2LTSM NLM     5691  1-30-93 11:32a - PCN2L Topology Support Module
FDDITSM  NLM     7211  5-12-93  4:06p - FDDI Topology Support Module
NE1000   LAN     4468  1-20-93  3:18p
NE2000   LAN     7353  3-03-93  1:27p
NE2      LAN     4974  1-20-93  3:19p
NE2_32   LAN     5066  5-12-93  4:03p
NE3200   LAN    13767  5-12-93  4:10p
NE1500T  LAN     9903  6-01-93 11:01a
NE32HUB  LAN    12266  1-27-93  9:11a
TOKENDMA LAN    10861  5-26-93  3:16p
TOKEN    LAN    10125  6-07-93  1:29p
NTR2000  LAN    10133  5-17-93 12:04p - Novell NTR2000 TOKEN RING Driver
TRXNET   LAN     3075  1-07-93  1:23p
PCN2L    LAN     4726  1-29-93  8:45p
LSLENH   NLM    11641 11-16-92  8:29a - LSL ENHANCED NLM.
PATCHMAN NLM     9051  4-16-92 11:21a
MONITOR  NLM   117775 10-26-92  9:21a - REQUIRED with new drivers on v3.11
!NVL1201 CFG     7378  3-26-92  9:08a - NE32HUB CFG file
@7151    ADF     2346  7-26-89  5:08p - NE2_32 ADF file
!NVL0701 CFG     2745  9-02-92  1:25p - NE3200 CFG file
!NVL1301 CFG     1169  3-12-92  2:28p - NE32HUB TPE CFG file
!NVL1401 CFG      986  6-10-92  4:02p - NE32HUB PME CFG file
!NVL1501 CFG    11994  1-11-93  3:24p - NE2000 plus CFG file
!NVL0901 CFG     8293 10-04-90 10:42a - NE2100/NE1500T CFG file
@7154    ADF     2657  4-27-92  1:54p - NE2 ADF file
FIRMLOAD COM     1628  1-04-91  8:57a - Use with TOKENDMA to load firmware.
XLOAD    EXE    13872  8-06-91  4:47p
XLOAD    DOC     3472  7-06-92 11:00a
LDR001   PTF    52920 11-06-91  4:55p
LDR001   DOC     3200 07-06-92 11:00a
LANDR2   TXT     (this file)
PM311IO  NLM     8384 04-13-93 11:28a - Use with SFT III v3.11 (Patchman)
LSLENH3  NLM    10500 06-02-93 11:34a - Use with SFT III v3.11
IOSHIM   NLM     1649 06-09-93  9:50a - Needed when running SFT III v3.11
                         with LSLENH3.NLM and the NE2000.LAN
                         driver.
---------------------------------------------------

Overview:  Server ODI drivers are now composed of 3 different NLMs. For
example when loading the NE2000.LAN both ETHERTSM.NLM and MSM31X.NLM will
autoload.  When loading TOKEN.LAN both TOKENTSM.NLM and MSM31X.NLM will
autoload etc.  The MSM31X.NLM will always load and the TSM is specific to
topology.

LANDR2.EXE has the following limitation:

       1)   LSLENH.NLM and LSLENH3.NLM may have problems with third party
         drivers that don't use the ECB driver workspace properly.
         Developers must use this work space according to the spec.
         Recently certified drivers do so.



LANDR2.EXE replaces the following in NE386.ZIP.

NE2      LAN    15548 11-11-91 11:19a
!NVL0701 CFG     2585 12-17-91  8:38a
NE3200   LAN    19198  1-15-92 11:24a
NE1000   LAN    11857  7-25-91 12:02p
NE2000   LAN    12389  7-26-91  9:36a
NE2-32   LAN    12185  7-25-91 11:52a
@7151    ADF     2346  7-26-89  5:08p
@7154    ADF     2657 10-03-88  9:42a
NE2100   LAN    16405 10-09-91  4:36p
NE1500T  LAN    16406 10-09-91  4:35p
NE386    DOC     3294  5-29-92 12:28p

The server drivers originally provided in NE386.ZIP fixed the following:

     1)   These versions have been rewritten to now use the MSM (Media
       Support Module).  The MSM is the new tool (module) available to LAN
       driver developers from Novell to develop better LAN drivers.

     2)   In some environments these new drivers could help solve
       communication problems.

     3)   The file server has the potential of locking up under a heavy load
       if the file server is a 486 machine and you are using either an
       NE2000 or an NE/2.  A race condition exists where the last remote
       DMA write cycle of the National Semiconductor DP8390 (on the NIC
       card) can be prematurely terminated by writing to the Command
       Register with bit "RD2" set before the remote DMA write cycle has
       completed (refer to a future IMSP technical bulletin for more
       detailed information).  These later versions of the drivers address
       the issue.

     4)   On certain networks with high traffic the adapter would stop
       receiving.


LANDR2.EXE drivers additionally include the following enhancements:

     5)   The default frame type for ethernet drivers is now ethernet_802.2
       rather than ethernet_802.3.  However the ETHERTSM.NLM will detect
       if the driver is being loaded on Netware 3.11 and default to
       Ethernet_802.3.  If the OS isn't Netware 3.11 then the default
       frame type will be Ethernet_802.2.

     6)   Drivers updated to the latest Novell 4.0 specification.

     7)   NE2000.LAN has been enhanced to use shared ram for the NE2000+.

     8)   NE2100.LAN has been enhanced to take advantage of the new PCNET
       ISA chip set from AMD (performance enhancement).  This will allow
       the new clones that have this chipset to run faster.

     9)   NE3200.LAN has had some performance enhancements.  This newer
       driver in combination with the newer .CFG file is more stable.
       When using the NE3200.LAN, Novell support recommends selecting EDGE
       TRIGGERED Interrupts when running the EISA configuration and using
       the latest !NVL0701.CFG (DMA timing modified) file supplied in
       LANDR1.ZIP.

     10)  TOKEN.LAN has been enhanced to use the FAST or QUICK path
       available on the IBM NASSAU II FRU #74F9415.  This should increase
       performance over early TOKEN.LAN drivers if using these boards
       in the file server.  If this driver doesn't load with the IBM
       token ring card you have, you may have one of the newer cards
       from IBM that requires the IBM supplied driver (for example
       TOKENBM.LAN).

     11)  TOKENDMA.LAN - This driver is more reliable and better written
       than previous drivers provided and distributed.  Also note that
       because the card is busmastering and not 32 bit the driver has
       to double buffer when writing above 16 meg of RAM.  The issue
       doesn't apply to servers that have 16 meg or less of ram.
       To install this version of TOKENDMA.LAN:

       a. Copy TOKENDMA.LAN, MSM.NLM, and TOKENTSM.NLM and MONITOR.NLM to
          the SYSTEM directory.
       b. When you load TOKENDMA.LAN it will autoload MSM.NLM and
          TOKENTSM.NLM. The lan driver is now more modular and is in 3
          separate NLMS instead of being combined as the 3.11 drivers you
          have been used to in the past.
       c. When loading this driver with 16meg or more on the server, use
          the following syntax:  "load tokendma below16"
       d. When loading the driver more than once for multiple boards in
          the server and the server has 16meg of memory or more, increase
          the Reserved Buffers Below 16 Meg in STARTUP.NCF:
          "Set Reserved Buffers Below 16 Meg = 50".
          If the error
          "TokenDMA-NW-073: Unable to allocate memory. Attempt to
          reinitialize re-entrant module FAILED 12/30/92 1:20pm: 1.1.39
          Cache memory allocator out of available memory."
          comes up on the screen when loading the driver, more Reserved
          Buffers Below 16 Meg need to be allocated.

       * * * * * * * * PLEASE NOTE: * * * * * * * * * * * * * * * * * * *
       The loader portion of the Server.exe will need to be modified in
       order to properly load the new tokendma.lan driver.  To make this
       change in Server.exe you will need to use XLOAD.EXE and LDR001.PTF.
       For more information about xload and ldr001, read XLOAD.DOC and
       LDR001.DOC.  XLOAD should always be applied when using interrupts
       2 and 9 on microchannel buss machines.
       * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

     12)  TRXNET.LAN - This driver is tested only with the Novell RX-NET
       RX-NET/2 boards.  It may or may not work with other cards or
       brands.  From a support standpoint third party vendors should
       provide their own drivers for their cards.



*****************************************************************
              DISCLAIMER

Novell, Inc. makes no representations or warranties with respect to
any NetWare software, and specifically disclaims any express or
implied warranties of merchantability, title, or fitness for a
particular purpose.

Distribution of any NetWare software is forbidden without the
express written consent of Novell, Inc.  Further, Novell reserves
the right to discontinue distribution of any NetWare software.

Novell is not responsible for lost profits or revenue, loss of use
of the software, loss of data, costs of re-creating lost data, the 
cost of any substitute equipment or program, or claims by any party 
other than you.  Novell strongly recommends a backup be made before 
any software is installed.   Technical support for this software 
may be provided at the discretion of Novell. 
*****************************************************************
