Novell NetWare.........IPX workstations

  NETWARE IPX INSTALLATION NOTES:
  FOR THE INTEL EtherExpress(tm) 16 FAMILY OF NETWORK ADAPTERS
  ============================================================

  This document applies to the EtherExpress(tm) 16, 16TP, 16C, MCA, 
  and MCA/TP.  It contains notes for installing the IPX driver and
  troubleshooting tips.  It does not explain how to configure an
  EtherExpress board.

  This document is also available on FaxBACK.  Document #6308.


  IPX IS ON THE DISK:
  -------------------
  Intel provides a pre-generated IPX.COM and NETX.COM on the
  EtherExpress disk.  The IPX is "auto-sensing."  It downloads the
  configuration from the EtherExpress card so it will work with
  any EtherExpress configuration.

  Copy IPX and NETX to the root directory of your boot disk, and add
  them to your Autoexec.bat or login batch file.

  IPX troubleshooting tips are located at the end of this document.


  IF YOU NEED TO CREATE A DIFFERENT IPX:
  --------------------------------------
  You will need to create a different IPX.COM if you want to turn off
  the auto-sensing feature or you have a newer revision of IPX than we
  provide.

  Novell provides a utility (WSGEN) with NetWare 2.2 and 3.1X that
  generates the workstation's IPX.  The rest of this document is an
  overview of the steps required to run WSGEN.  NetWare 2.1X uses a
  program called SHGEN instead of WSGEN.  The steps are similar, but
  there is not a one to one relationship.  See your Novell
  documentation for information on running SHGEN.

  WSGEN can either be run from a floppy disk, a local hard drive, or a
  network drive.  This document assumes you are running WSGEN from a
  local hard drive.


  1. If you have not installed WSGEN, create a NetWare subdirectory
     (C:\NETWARE).  Copy WSGEN.EXE and WSGEN.HLP from Novell's WSGEN
     disk to this directory.

  2. Change to the NETWARE directory and create a subdirectory called
     WSGEN.  (C:\NETWARE\WSGEN) Copy the all the files from the WSGEN
     diskette to this directory.

  3. Change to the NETWARE directory and type: WSGEN <enter>

  4. The introductory screen will appear.  Press enter and a list of
     drivers will appear.

  5. To add the driver for the EtherExpress adapter, press the INSERT
     KEY.  When prompted to insert a disk labeled LAN_DRV_xxx insert
     the original Intel EtherExpress diskette into any drive.  Press
     ENTER to continue.

     NOTE: If you use a backup copy of EtherExpress diskette, the 
           the volume label must be LAN_DRV_453.

  6. The driver for the EtherExpress adapter will be displayed on the
     screen.  Press ENTER to continue.  The EtherExpress will now be
     displayed in the list of drivers.  Hightlight this driver and
     press ENTER to continue.

  7. A list of available configurations will appear.  Select an option
     from this list.

     0: EtherExpress(tm) 16 Automatic Configuration
     1: I/O Base = 300H
     2: I/O Base = 310H
     3: I/O Base = 320H
     4: I/O Base = 220H
     5: Driver configurable by Jumpers Utility    

     Option zero creates an auto-sensing IPX.  This means the IPX checks
     the board's setting and downloads them to the driver.  Select this
     option most of the time.  You only need to choose another option if
     you have a hardware conflict caused by the IPX reading the board's
     configuration each time IPX loads.

     The Jumpers utility (option 5) would be used if the I/O address you
     choose in Softset does not match one of the options listed (2, 3 or
     4) and you do not want to use the automatic configuration option (0). 
     The Jumpers utility is software provided by Novell to modify the I/O
     setting in the IPX file that you created with WSGEN.  It is in the
     WSGEN directory you created earlier.  Do not confuse the Jumpers
     utility with physical jumpers on some network adapters.

  8. Details of the configuration option will now be displayed.

     Network Board Driver:
        Intel EtherExpress(tm) 16 v2.04EC (920410)
     Configuration Option 0:
        EtherExpress(tm) 16 Automatic Configuration

     Select: Yes, generate the workstation software.

     WSGEN will now link the driver.  When this is complete, exit WSGEN.

  9. NETX.COM and the newly created IPX.COM are in the
     C:\NETWARE\WSGEN directory.  Copy these to the root directory, and
     you're ready to login.

     NOTE: If you copy NETx and IPX into a subdirectory, see Novell's
           documentation for subdirectory requirements.  For example, 
           the SHELL.CFG must be in the same directory as IPX and you
           must execute IPX from that directory.

     Refer to your NetWare installation manual for additional information
     about WSGEN or SHGEN.


  TO ADD THE ETHEREXPRESS DRIVER TO WSGEN DRIVER LIST:
  ----------------------------------------------------
  Change to the NETWARE directory and create a subdirectory called
  LAN_DRV_.453.  (C:\NETWARE\LAN_DRV_.453)

  Copy EXP16SH.LAN and EXP16SH.OBJ from the root directory of the
  EtherExpress disk to this directory.

  The next time you run WSGEN, the EtherExpress will automatically be
  displayed with the other drivers.


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

     - The Lan Option should say Intel EtherExpress
     - The Hardware configuration should say AUTOMATIC or it should 
       match the I/O you selected.  

  2. Thin ethernet requires a T-connector on EVERY workstation and
     terminators on the end of each trunk segment.  One of the two 
     terminators must be grounded.  You cannot directly connect 2
     workstations.  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:
        Make sure the volume SYS: is mounted.
        Make sure you BIND the ethernet driver.

     - 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 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 will usually default to F as the
     first drive.

  5. If you copy the EtherExpress drivers to another floppy disk, make
     sure you label the disk LAN_DRV_453 with the DOS volume LABEL
     command.

  6. If you are using memory manager, make sure you EXCLUDE any memory
     ranges the EtherExpress is using.
