1. Intel-100-Pro.zip Driver
2. NW4X.TXT File Contents

NW4X.TXT Driver File Contents (Intel-100-Pro.zip)

   NetWare 4.x Server 


   Novell NetWare* 4.x INSTALLATION NOTES FOR THE INTEL EtherExpress 
   PRO/100 ISA ADAPTER
   ==================================================================
  
   DRIVER LOCATION
   ---------------
   Location of Driver: \NETWARE\E100ISA.LAN


   REQUIRED NLMS FOR NETWARE 4.x
   ------------------------------
   This version of E100ISA.LAN auto-loads three Novell NLMs (ETHERTSM, 
   MSM, and NBI) when you load the E100ISA.LAN driver. You may need to 
   update the versions of these three NLMS currently installed on your 
   NetWare 4.x file server to:

		MSM.NLM       (07-01-96 v3.17 or later)
		ETHERTSM.NLM  (07-03-96 v3.11 or later)
		NBI.NLM	      (05-10-96 v1.44 or later)
		
   Make sure you use these (or later) versions. Earlier versions may not work 
   properly or generate this error message:

   	"Loader cannot find public symbol: <symbol name>" 

   If you need these updated Novell NetWare NLMs, you can download a file 
   called 100ILAN.EXE available on any of the Intel automated services (BBS, 
   FTP, WWW). Please refer to the readme titled " Using Intel's 
   automated customer support" for information on how to download the file.  
 
   GENERAL INSTALLATION
   --------------------

   1   From the DOS prompt on the server, copy the EtherExpress PRO/100 ISA 
       adapter driver (\NETWARE\E100ISA.LAN) to the Novell directory on the 
       DOS partition of the server's hard drive (drive C:).

   2   If necessary, copy the updated Novell NLMs to the Novell directory on 
       the DOS partition of the server's hard drive (drive C:).

   3   Start NetWare by typing SERVER or the name of your startup batch file.

   4   Load the updated Novell NLMs. 

		LOAD C:<PATH>\MSM
		LOAD C:<PATH>\ETHERTSM
	
   5   Load the EtherExpress PRO/100 ISA driver.  At the server's colon (:) 
       prompt, type:

	  LOAD C:<PATH>\E100ISA 

   6   Bind the driver.  At the server's colon (:) prompt, type:

	  BIND IPX TO E100ISA NET=xx

	  WHERE: xx is the external network number.

	  At this point you should be able to log into the server from a
	  workstation.

   TO MAKE THIS PERMANENT
   ----------------------
   Using Novell's INSTALL program, edit the AUTOEXEC.NCF file to add the
   LOAD and BIND statements for the EtherExpress adapter.

   USING E100ISA.LAN KEYWORD OPTIONS
   ---------------------------------
   There are several driver keywords that are supported when loading the
   EtherExpress PRO/100 ISA driver. Please see the README file titled 
   PRO/100 ISA DRIVER KEYWORDS for detailed information. For example:

   LOAD C:\E100ISA MEDIATYPE=HALF100 RXEARLY=OFF USE32BITIO=NO


   INSTALLING MULTIPLE ETHEREXPRESS PRO/100 ISA ADAPTERS
   -----------------------------------------------------
   If you have multiple network adapters in a single server, each 
   adapter must have a different NETwork number, a different SERIAL 
   Also, You must name each adapter using the "NAME=" parameter.  
   For example:

       	 LOAD C:\E100ISA SERIAL=044721 NAME=LANA
	 BIND IPX TO LANA NET=10
	 LOAD C:\E100ISA SERIAL=044735 NAME=LANB
	 BIND IPX TO LANB NET=20	 

    NOTE: The serial number is the last six digits of the EtherExpress
	  PRO/100 ISA MAC address. The MAC address lable is on the back
          of the EtherExpress PRO/100 ISA LAN adapter.


   INSTALLING ONE ETHEREXPRESS CARD WITH MULTIPLE FRAME TYPES
   ----------------------------------------------------------
   When binding multiple frame types to one card, enter a LOAD statement
   for each frame type. You must name each board using the "NAME=" 
   parameter. For example:

	 LOAD C:\E100ISA FRAME=ETHERNET_802.2 NAME=LAN8022
	 BIND IPX TO LAN8022 NET=10
	 LOAD C:\E100ISA FRAME=ETHERNET_II NAME=LANII
	 BIND IPX TO LANII NET=20

   Do not confuse the NETwork number with the internal IPX number. They 
   need to be different. See the NetWare Installation manual for more 
   information.


   TCP/IP
   ------
   If you are using NetWare's TCP/IP NLM, you must load an Ethernet type
   II frame and bind the EtherExpress adapter to TCPIP.  For example:

	 LOAD C:\E100ISA FRAME=ETHERNET_802.2 NAME=LAN_IPX
	 BIND IPX TO LAN_IPX NET=10
	 LOAD C:\E100ISA FRAME=ETHERNET_II NAME=LAN_IP
	 LOAD TCPIP FORWARD=YES
	 BIND IP TO LAN_IP ADDR=xxx.xxx.xxx.xxx 

	 where xxx.xxx.xxx.xxx is your internet address.


   ERROR MESSAGE: "Loader cannot find public symbol: <symbol name>"
                  "Load file referenced undefined public variable"
   ----------------------------------------------------------------
   This error message occurs when the server is loading older versions of
   ETHERTSM.NLM or MSM.NLM. 


  CUSTOM STATISTICS
  -----------------
  The PRO/100 ISA server driver maintains the following custom statistics, 
  which can be viewed by loading the NetWare MONITOR program:

     Current Line Speed (Mbps):                 10 or 100
     Duplex Mode (0 = Half, 1 = Full):          0 or 1
     Link State (0=Down, 1=Up, 2=Unknown):      0, 1, or 2
     Receive Symbol Errors (100 Mbps only):     count
     Get RCB Attempts Reject Count:             count
     Early Receive Interrupts Count:            count
     Back-to-back Send Count:                   count
     No Transmit Resources Count:               count

   If the driver's MEDIATYPE setting for the PRO/100 ISA adapter is
   AUTO (or was not been specified) the Current Line Speed, Duplex Mode, 
   and Link State are updated any time that the driver detects changes 
   in the PRO/100 ISA adapter and its physical network connection.

   Receive Symbol Errors apply to 100 Mbps operation only. They are 
   also counted in the General Statistics Checksum Errors counter.

   If the Get RCB Attempts Reject Count is counting upward quickly, it 
   probably means that some client station(s) on the network is not using 
   the correct FRAME type to communicate to the server or that the server 
   does not have the correct FRAME types bound to the IPX protocol stack.

   The Early Receive Interrupts Count gives an indication of how much early
   receive packet processing is happening.  This count will remain at 0 if 
   RXEARLY=OFF has been used or if both RXBURSTCOUNT and RXBURSTTIMEOUT have 
   been specified.

   The Back-to-back Send Count is the number of packets that were queued to 
   the driver for transmission while the driver was busy.

   The No Transmit Resources Count is the number of transmit attempts that 
   failed because the driver had run out of transmit descriptors.

   * Third-party trademarks are the property of their respective owners.