TCP/IP.................Configuration notes and examples

  TCP/IP NOTES:
  FOR THE INTEL EtherExpress(tm) 16 FAMILY OF NETWORK ADAPTERS
  ============================================================

  This document applies to the EtherExpress(tm) 16, 16/TP, 16C, FLASHC,
  MCA, and MCA/TP.  It contains general information notes about the
  EtherExpress drivers and TCP/IP applications.  It does not explain
  how to configure an EtherExpress board.  For instructions about
  configuring the board, see either the Expert's Guide or the Complete
  Guide for your board.


  ARE THE ETHEREXPRESS CARDS TCP/IP COMPATIBLE?  FaxBACK #6260
  ------------------------------------------------------------
  Intel does not sell TCP/IP software, however, TCP/IP software may be
  purchased from several different vendors.  Intel provides NDIS and ODI
  drivers that work with most TCP/IP software.  First, determine if the
  TCP/IP software is a NDIS or ODI compliant and then find the section
  below that applies.


  NDIS GENERAL:
  -------------
  Intel's EtherExpress 16 NDIS drivers are certified to meet
  Microsoft's NDIS Specification version 2.0.1.  If the TCP/IP software
  is NDIS compliant, it "should" work with the EtherExpress NDIS
  drivers.  Applications and protocol stacks that use NDIS driver are
  not certified my Microsoft so there is room for possible compatibility
  issues.  The NDIS drivers are on the EtherExpress diskette in the
  following subdirectory:

    NDIS\EXP16.DOS   (for DOS)
    NDIS\EXP16.OS2   (for OS/2)

  In addition to the driver, a Protocol.ini file may be needed.
  For a sample Protocol.ini, please refer to the PROTOCOL.INI
  file included in the same subdirectory as the driver.

  The Protocol.ini should look like the following:

  [EXP16]
     IOADDRESS = 0x300
     DRIVERNAME = EXP16$

  NOTE:  The IOADDRESS must be modified to match the I/O Address
         of the card.  The EXP16$ must be in capital letters.


  NDIS AND BANYAN VINES:
  ----------------------
  The version of TCP/IP supplied with Banyan Vines 4.X does not support
  NDIS drivers.  To use TCP/IP with an NDIS driver, you will need to
  purchase a version of TCP/IP that supports NDIS.  We recommend you
  call your Banyan support representative for more information.


  ODI GENERAL:
  ------------
  The ODI driver is certified to meet Novell's ODI Specification.  If
  the TCP/IP software is NDIS compliant, it "should" work with the
  EtherExpress NDIS drivers.  Applications and protocol stacks that use
  NDIS driver are not certified my Microsoft so there is room for
  possible compatibility issues.  These drivers are on the diskette in
  the following subdirectory.

    NETWARE.ODI\EXP16ODI.COM  (for DOS) 
    NETWARE.ODI\EXP16ODI.SYS  (for OS/2)

  ODI Drivers use a Net.cfg file that works similar to the Protocol.ini
  file.  This sample is for 1 INTEL EE16 in one workstation, running 
  TCP/IP and IPX concurrently:

  Link Support
	Buffers 8 1568
	MemPool 4096

  ; This provides the INTEL card specific setup
  Link Driver EXP16ODI
	PORT #1 300
	INT #1 11
	Frame Ethernet_802.3      ; <---You must have Novell frame
	Frame Ethernet_II         ; <---As well as TCP/IP frame    
	Protocol IPX 0 Ethernet_802.3 ; <-and IPX uses 802.3 by default

  ; This section sets up the TCPIP parameters
  Protocol TCPIP
	BIND EXP16ODI     
	ip_address 134.242.1.36  ; address of this workstation
	ip_router 134.242.1.254  ; address of the network router
	ip_netmask 255.255.255.0
	etc....

  ; This section may actually be ommitted if there is only one card
  ; in the machine and only one Link Driver section, IPXODI will take as 
  ; default the only driver given.
  Protocol IPX
	Bind EXP16ODI    

  ;END NET.CFG