
NDIS Bindings
---------------
	The NDIS (Network Driver Interface Specification) method binds
	multiple protocols to a particular installed network card.  A
	protocol manager is used to read a protocol.ini file to determine
	which protocols are to be associated with which network card (if
	more than one is installed) and to what network type (ie: 10base2,
	10baseT, TokenRing, etc).  The protocol manager is then responsible
	for arbitrating the network traffic using the installed network cards.
	Adding the IPX procotol is as easy as obtaining the MS IPX NDIS driver
	binding it to the network card on your machine.  (The MSIPX dirvers
	take up about 17Kb of memory.)


	o PC-NFS v4.x & v5.x Sample
	  (using a 3Com EtherLink II [3c503] network card)
	------------------------------------------------------
	  Obtain the MS IPX NDIS drivers (msipx.sys and msipx.com) from
	  ftp.microsoft.com, the Microsoft BBS (206)936-6735, or the
	  Windows for Workgroups DISK#8, and place them in your c:\lanman
	  directory.  Make the following changes to your config.sys,
	  autoexec.bat, and protocol.ini files.

	NOTE: PC-NFS uses NDIS v1.x, so the protocol manager is protman.sys
	      and it makes use of the netbind.exe file.  These should be
	      included with your PC-NFS distribution diskettes.


	CONFIG.SYS
		device=c:\lanman\protman.sys /i:c:\lanman
		device=c:\lanman\elnkii.dos
		device=c:\lanman\nfs-ndis.sys
		device=c:\lanman\msipx.sys

	AUTOEXEC.BAT
		c:\lanman\netbind.exe
		c:\lanman\msipx.com
		c:\nfs\prt.com -T10 *
		c:\nfs\net.exe init

	PROTOCOL.INI
		[Protocol Manager]
		  drivername = PROTMAN$

		[EtherLink]
		  drivername   = ELNKII$
		  ioaddress    = 0x300
		  interrupt    = 5
		  transceiver  = onboard

		[NFS-NDIS]
		  drivername = NFSLINK$
		  bindings   = EtherLink

		[IPX]
		  drivername = IPX$
		  bindings   = EtherLink

