----------------------------------------------------------------------------
  Installing the NetWare SFT III 4.X MSL Driver on NetWare SFT III Servers
----------------------------------------------------------------------------

The \NOVELL\SFT3.4X subdirectory contains the following files:

README.TXT   - This file.
DECMSL4X.MSL - NetWare SFT III 4.1X Mirrored-Server Link Driver
	       for both the DEC FDDIcontroller/EISA and the 
	       DEC FDDIcontroller/PCI adapters. 

Product Requirements:

Oper. Sys. - Novell NetWare SFT III 4.10 or 4.11



			 ***TRADEMARKS***

DEC, Digital, and DECpc are trademarks of Digital Equipment 
Corporation. 

Novell, NetWare, and LAN WorkPlace are registered trademarks and NetWare
Loadable Module, NLM, and NetWare SFT are trademarks of Novell, Incorporated.



Section 1  INSTALLING THE NETWARE SFT III 4.X DRIVER ON NETWARE SFT III
-----------------------------------------------------------------------
The DECMSL4X.MSL driver will run only on Novell NetWare SFT III 4.10 and 4.11
server and takes advantage of the multiple MSL adapters feature of 
NetWare SFT III 4.10 and 4.11.  The DECMSL3X.MSL driver will run on Novell 
NetWare SFT III 3.11, 4.10, and 4.11 but only supports a single MSL 
adapter in an IOENGINE.

To install the NetWare SFT III 4.1x MSL driver on a NetWare 4.1x file 
server, perform the following steps (Note: DEC FDDIcontroller refers
to either the EISA or PCI variants):

I.   Verify that the FDDI network interface card (NIC) is properly
     configured and installed.  Refer to "DEC FDDIcontroller/EISA
     Installation" or "DEC FDDIcontroller/PCI User Information"
     for instructions.

II.  Perform substeps IIA. and IIB. to configure the NetWare 4.10 file
     server to use the DEC FDDIcontroller NetWare SFT III 4.1x MSL 
     server driver.

     A. Copy the driver files to the server hard disk in the same directory
	from which MSERVER.EXE is started.

	For example, if MSERVER.EXE was located in C:\NETWARE, you would
	enter the following command to copy the driver:

	      COPY A:\NOVELL\SFT3.4X\DECMSL4X.MSL C:\NETWARE

     B. Edit the IOSTART.NCF file to automatically load the new MSL driver
	every time the server is brought up:

	      LOAD C:DECMSL4X.MSL SLOT=48

				     NOTE
	   The "slot" value given above is an example.  For the DEC 
	   FDDIcontroller/EISA the slot number will in the range 1-15 and 
	   is the EISA slot where the DEC FDDIcontroller/EISA is installed. 
	   For the DEC FDDIcontroller/PCI the number will be a value greater
	   than 16 and represents a unique identifier for the DEC 
	   FDDIcontroller/PCI adapter found.
	   
	   Replace "C:" with another directory path if the MSL driver was 
	   not copied to the same directory as MSERVER.EXE.

III. Start the server with the DEC FDDIcontroller MSL server driver.

     Enter the following command at the DOS prompt:

	MSERVER

     The changes made to IOSTART.NCF in step II above take effect.



Section 2  ADDITIONAL MODES OF OPERATION
----------------------------------------

NETWORK COEXISTENCE MODE
------------------------

In a "Normal Mode" of operation, the MSL link will be a point to point
connection between the two MSL cards.  The DEC FDDIcontroller also
allows the link to coexist on an FDDI network as long as there are 
NO ROUTERS in the path between the two linked servers.  In this mode of 
operation IT IS MANDATORY THAT YOU SPECIFY THE PARTNER'S IOENGINE NAME.
To do this, keep both MSL adapters connected to the network and load 
the MSL driver on both IOENGINEs.  From the example in Section II:

	LOAD C:DECMSL4X.MSL SLOT=48 PARTNER=IO_RIGHT

Where IO_RIGHT is the name of the other server's IOENGINE.
Repeat this on the other IOENGINE using this IOENGINE's name.
The IOENGINEs should find each other, reporting that the link is 
available and will synchronize once the server is activated.


INCREASING MESSAGE RETRY COUNT
------------------------------

Running the driver on a busy network increases the possibility for a packet 
to become lost between the two MSL cards.  If your network is fairly loaded, 
it may become necessary to increase the retry count.  To adjust the retry 
count, add the following switch to the command line when loading the 
MSL driver.

	LOAD C:DECMSL4X.MSL SLOT=48 PARTNER=IO_RIGHT RETRY=2


FULL DUPLEX OPERATION
---------------------

The driver can be configured to run in a Digital proprietary mode of 
operation known as Full Duplex (FDX).  The MSL adapters must be connected 
in a point to point configuration.  In this mode, the normal FDDI token 
rotation is eliminated, allowing the adapters to send and receive at the 
same time.  This increases the bandwidth of the connection above the 
100 Megabits/second limitation of standard FDDI.  To activate this mode of 
operation, add the following switch to the command line when loading the 
MSL driver.

	LOAD C:DECMSL4X.MSL SLOT=48 FULLDUPLEX=ON