   4.x server          

  NETWARE* 4.x SERVER INSTALLATION NOTES
  FOR THE INTEL EtherExpress(tm) 16 FAMILY OF NETWORK ADAPTERS
  ============================================================
  This document applies to the EtherExpress(tm) 16, 16TP, 16C, FLASH,
  FLASH TP, FLASHC, MCA, and MCA/TP adapters. 


  BEFORE YOU START
  ================
  You must configure and test the EtherExpress 16 adapter with SOFTSET.EXE 
  Boot the workstation with DOS, and then insert the EtherExpress16 LAN 
  Adapter Configuration and Driver disk into drive A. From DOS, type:

	A:SOFTSET

  1. Select "AUTOMATIC SETUP" to let SOFTSET configure the EtherExpress 
     adapter to work in your computer, or select "MANUAL SETUP" if you want 
     to designate which interrupt and I/O address you want the EtherExpress
     16 adapter to use.
  
  2. Select "RUN DIAGNOSTICS" from the main menu to test the configuration you 
     have selected. 


  GENERAL INSTALLATION
  ===================== 
  1. Install NetWare 4.1x according to the NetWare 4.1x installation
     manual.

  2. When prompted to select the server network driver, select <INS> to 
     install an unlisted driver. 

  3. When prompted for a path for the driver, insert the EtherExpress driver 
     disk into drive A:, then select <F3> to specify the path as:

	 A:\NWSERVER 

  4.  Select the "Intel EtherExpress ISA Family" if you are using an 
      EtherExpress 16 or other ISA adapter. 
	  
      If you have a EtherExpress MicroChannel adapter, select 
      "Intel EtherExpress MCA Family" from the list of adapters.

  5.  Configure the LAN driver by entering the Port Value (I/O Address)
      that you noted when you ran SOFTSET or the IBM SC utility. Press 
      F10 to exit the and load the driver.

  6.  Continue with the NetWare 4.1x installation.



  NOTE: 4.01 or 4.02 Servers
  ==========================
  This version of EXP16.LAN auto-loads two Novell* NLMs (ETHERTSM and MSM)
  when you load the EXP16.LAN driver. You may need to update the versions of 
  these two NLMS currently installed on your NetWare 4.01 or 4.02 file server 
  to these versions:

		MSM.NLM       (06-28-94 v2.31)
		ETHERTSM.NLM  (06-28-94 v2.31)
		
  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>" 

  These updated NLMs are located on the EtherExpress16 driver disk in 
  the directory \NWSERVER\NLM in a self-extracting file called NLMS.EXE. 
  Copy the file NLMS.EXE onto the C: drive of your file server and then run it 
  to extract the files.

  If you can log in to the server, copy these updated NLMs into the SYSTEM 
  subdirectory.  If you do this, you won't need to specify a path on the load 
  line. If you copy it to another directory, make sure the LOAD statement 
  includes the correct path.


  For NetWare 4.01 and 4.02, add these lines to the AUTOEXEC.NCF before 
  loading EXP16.LAN:

		LOAD C:<PATH>\MSM
		LOAD C:<PATH>\ETHERTSM
		LOAD C:<PATH>\EXP16 PORT=xxx INT=y  

	
  WHERE: xxx is the I/O address of the EtherExpress card and y is the 
		 interrupt (IRQ) in Hex.  


 TROUBLESHOOTING TIPS
 ====================

  TROUBLE LOADING THE DRIVER
  --------------------------
  If you have problems loading a driver, remove the driver statements
  from the AUTOEXEC.NCF file and enter them manually with no
  parameters.  From the Colon prompt, type:

	 LOAD C:<PATH>EXP16

  NetWare will prompt you for the interrupt and port address.  Add
  parameters back one at a time.  If you receive any error messages,
  check the NetWare System Messages manual for an explanation.

  Do the same for the BIND statement.  Type:

	 BIND IPX TO EXP16 


  INSTALLING MULTIPLE ETHEREXPRESS CARDS
  --------------------------------------
  If you have multiple network cards in a single server, each card must
  have a different NETwork number, a different PORT address, and a
  different INTerrupt.  You must name each board using the "NAME=" 
  parameter.  For example:

	 LOAD C:\EXP16 PORT=300 INT=3 NAME=LANA
	 BIND IPX TO LANA NET=10
	 LOAD C:\EXP16 PORT=350 INT=5 NAME=LANB
	 BIND IPX TO LANB 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.


  INSTALLING ONE ETHEREXPRESS CARD WITH MULTIPLE FRAME TYPES
  ----------------------------------------------------------
  When binding multiple frame types to one card, enter a LOAD statement
  for each frame type.  Each LOAD statement will use the same PORT
  address and INTerrupt, but a different NETwork number. You must name 
  each board using the "NAME=" parameter. For example:

	 LOAD C:\EXP16 PORT=300 INT=3 FRAME=ETHERNET_802.2 NAME=LAN8022
	 BIND IPX TO LAN8022 NET=10
	 LOAD C:\EXP16 PORT=300 INT=3 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 to TCPIP.  For example:

	 LOAD C:\EXP16 PORT=300 INT=3 FRAME=ETHERNET_802.2 NAME=LAN_IPX
	 BIND IPX TO LAN_IPX NET=1
	 LOAD C:\EXP16 PORT=300 INT=3 FRAME=ETHERNET_II NAME=LAN_IP
	 LOAD TCPIP
	 BIND IP TO LAN_IP ADDR=xxx.xxx.xxx.xxx 

	WHERE: xxx.xxx.xxx.xxx is your internet address.

  You may also have MASK and GATE parameters on the BIND IP line.  See
  NetWare's documentation for more information.


  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 MSM31X.NLM. Verify that you are loading 
  version 2.31 or later of these NLMs.  


  IF WORKSTATIONS CANNOT ATTACH TO THE FILESERVER
  -----------------------------------------------  
  On the server:

  - Make sure the volume sys: is mounted.
  - Make sure you BIND IPX to the EtherExpress driver.
  - Make sure the FRAME type is the same on server and workstation. The 
    default frame type is 802.2

  If both of these have been checked and workstations still cannot
  attach to the file server then verify that the EtherExpress in the
  server and workstation(s) are working and that they are communicating
  with each other:

  a.  Down the file server and reboot with DOS.  Run the
      SOFTSET/MCADIAGS on-board and on-network diagnotics.  If these
      pass, set the file server up as a responder in SOFTSET/MCADIAGS
      diagnostics.  

  b.  Reboot the workstation(s) without loading ipx/netx and run the
      SOFTSET/MCADIAGS on-board and on-network diagnostics.  During the
      on-network diagnostics, the server (set up as a responder) should
      count and echo the packets sent by the workstation.

  c.  Rerun the workstation and set it up as a responder and try the
      on-network diagnostics from the server machine.

  d.  If on-network diagnostics fail, there is likely a cable,
      connector, hub, or concentrator problem.

      If the on-network diagnostics pass, the boards tested can
      communicate.  This indicates there could be a problem with the
      drivers.  Bring the server machine back up as a server.  Reload
      the drivers in the workstation.  If the workstation still cannot
      connect to the server, there is likely a problem with the
      configuration of the drivers.  Verify that the server and
      workstation drivers load properly.  You can do this by loading
      them one at a time, rather than in a batch file, and watch for
      error messages.


	  Note: "Responder not found" is NOT an error.  This message will
		be displayed IF YOU ARE NOT RUNNING THE SOFTSET/MCADIAGS
		RESPONDER ON ANOTHER MACHINE with an EtherExpress card or
		if the card cannot actually communicate with the responder
		card.  If you do not have a responder running or if the
		two cards cannot communicate, the diags will try to send
		packets back to itself.



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