   Workstation for DOS IPX client

  This document applies to the EtherExpress(tm) 16, 16TP, 16C, FLASH,
  FLASH TP, FLASHC, MCA, and MCA/TP adapters. 

  IPX.COM IS ON THE DISK
  ----------------------
  Intel(R) provides a pre-generated IPX.COM and NETX.EXE on the
  EtherExpress 16 adapter disk in the \NWCLIENT directory. This IPX.COM 
  will auto-detect the I/O address and interrupt being used by the 
  EtherExpress 16 adapter, so it will work with any EtherExpress16 
  configuration.


  BEFORE YOU START
  ----------------
  You must configure and test the EtherExpress 16 adapter with SOFTSET.EXE 
  Boot the workstation with DOS, and then insert the EtherExpress 16 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 to use.
  
  2. Select "RUN DIAGNOSTICS" from the main menu to test the configuration 
     you have selected. 


  GENERAL INSTALLATION
  --------------------
  1.  Copy IPX.COM and NETX.EXE from the \NWCLIENT directory of 
      EtherExpress 16 disk to the root directory of your boot disk. 
      
  2.  Edit your AUTOEXEC.BAT batch file to include these commands in this 
      order:
  
 	IPX.COM
	NETX.EXE
    

  TROUBLESHOOTING TIPS
  --------------------
  1. Type "IPX i" in the directory where your IPX.COM file is located.

     - The Lan Option should say Intel EtherExpress(TM)16 v3.05EC. 
     - The Hardware configuration should say AUTOMATIC or it should 
       match the I/O you selected.  

  2. Thin Ethernet (RG58A/U COAX) requires a T-connector on EVERY workstation 
     and 50-ohm terminators on the end of each trunk segment.  One of 
     the two terminators must be grounded.  You cannot directly connect 2
     workstations without using T-connectors.  Refer to your Novell* 
     Supplements manual for specifications on thin & thick Ethernet networks.

  3. If workstations cannot login to the file server:
  
     - On the file server:

       Verify the NetWare* file server has the frame type Ethernet_802.3
       loaded and that IPX is bound to it. 

     Here is a list of the default frame types for NetWare servers:
 
     	NetWare 2.x 	802.3
	NetWare 3.11	802.3
	NetWare 3.12	802.2
	NetWare 4.x	802.2

     You can verify what frame types you your NetWare file server is using by 
     typing the command "CONFIG" at your NetWare server console screen. 
 

     - On the workstation:

       Reboot the workstation without loading IPX/NETX and run the 
       EtherExpress SOFTSET/MCADIAGS on-board and on-network
       diagnostics.  If you have more than one EtherExpress card
       installed on the network, reboot the other workstation without
       loading IPX/NETX, run SOFTSET/MCADIAGS diagnostics and set this
       workstation up as a responder.  Rerun the on-network diagnostics
       on the first workstation and see if the two machines see each
       other.  This process can be reversed to fully check
       communication between the EtherExpress cards.  If on-network
       diagnostics fail, there is likely a cable, connector, hub or
       concentrator problem.

       If On-Board diagnostics fail, try setting the EtherExpress16 
       adapter to a different I/O address, a different interrupt, or change 
       Force 8 bit to "YES".

       If On-Network diagnostics fail, there is likely a cable, connector, 
       or hub problem. Verify that the cabling you are using is connected 
       properly and that the cable is not defective. For more information
       on cable specifications, view the 10BaseT or COAX ethernet cabling 
       readme files on the EtherExpress LAN adapter and Options disk. 

       If the on-network diagnostics pass, the boards tested can
       communicate.  This indicates there could be a problem with the
       drivers.  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 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.

  4. Check for a LASTDRIVE statement in the config.sys. LASTDRIVE is not 
     required, but if your last drive is S, you will only have drives T-Z 
     available for NetWare.  If you want drives F-Z available for 
     NetWare, your LASTDRIVE should be E.  Without a LASTDRIVE statement, 
     NetWare defaults to F as the first drive.

  5. If you are using a memory manager, make sure you EXCLUDE any memory
     ranges the EtherExpress FLASH chip is using.

  6. Below are sample files for reference:

	C:\CONFIG.SYS
      --------------
	files=25
	buffers=25
	lastdrive=E

	C:\AUTOEXEC.BAT
       ---------------
	path=c:\dos
	prompt $P$G
	ipx.com
	netx.exe
	f:
	login



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