1. en2218.zip Driver
2. README.TXT File Contents

README.TXT Driver File Contents (en2218.zip)

		      Accton Technology Corporation
		  Netware Driver Installation Overview
		   For EN2218 Mut-function PCMCIA Adapters

    Copyright (C) 1995, 1996 by Accton Technology Corporation.
    All rights reserved.


This README file is an explanation of the files contained in the
\NETWARE subdirectory of this diskette.  For more information, please
refer to the "NOVELL NetWare ODI Shell for DOS" manual.


LSL.COM:

       This file implements the Link Support Layer  for  DOS/ODI
       workstations  and is  the program that is generally loaded first
       after booting.  The Link Support Layer file enables the
       workstation to communicate over several protocols.

IPXODI.COM:

       This is Novell's protocol stack for DOS/ODI workstations.
       It performs the same functions what IPX.COM does for DOS
       workstations.  It is loaded after the LAN driver.  Other protocols
       can be loaded in  place	of it or along with it.  This is one of
       the key features of the ODI environment.

NETx.COM:
       NetWare Network program.

       If you use		  You Need
       ------------------------------------------
       Conventional memory	  NETx.COM

       Expanded memory		  EMSNETx.EXE
       (LIM 4.0 EMS Compatible)

       Extended memory		  XMSNETx.EXE
       (XMS 2.0 compatible)


NETBIOS.EXE
       Netbios emulation program (INT 5CH interface) allows you to
       run  Netbios  application  programs  based  on  the NETBIOS.EXE
       interface.  The running sequence is:


       1. DOS/ODI driver
		    LSL.COM
		    PCMMLID.COM   --> Accton DOS/ODI driver
		    IPXODI.COM
		    NETBIOS.EXE  --> netbios emulation interface
		    ...


Note:This version PCMMLID.COM do NOT support Windows' Modem Application.
ex: Comit for windows.


If the DOS/ODI driver PCMMLID executed successfully, it would display
the adapter mode and configuration information.  Otherwise you
would see an error message and the cause of the failure.

Here is the list of error messages the driver may display and the correction
method:

  *    "The board cannot be found."

       The adapter does not exist or the driver does not recognize the adapter.

       Correction: Insert an Accton PCMCIA adapter into the slot.

  *    "Board RAM failed the memory test."

       The RAM buffer on the adapter failed.

       Correction: Insert a new adapter and run the driver again.

  *    "The board did not respond to the initialization command."

       The driver recognized the adapter but the adapter failed to respond.

       Correction: Insert a new adapter and run the driver again.

  *    "There is no cable connecting to the adapter."

       There is no cable connecting to the adapter or the transceiver within
       the adapter failed.

       Correction: Connect the cable to the adapter and run the driver again.

       Normally,  you do not need a NET.CFG file because the  established
       defaults are adequate for your network.	One exception is when your
       workstation  has more than one network adapters.  In this case,
       for  each adapter, there  must  exist a MLID section
       in the NET.CFG file.

       Note: ODI driver always parses your NET.CFG file first. The
	     configuration in NET.CFG takes precedence over the
	     parameter settings stored in the internal memory of the adapter.

       Below is a sample NET.CFG file:

	      LINK DRIVER PCMMLID
		  INT	5
		  PORT	300
		     :
		     :

       You can consult "NetWare 386 Installation, Appendix E" for  more
       information about NET.CFG.

       Novell has already changed the Ethernet default frame type to 802.2
       starting with the release of NetWare v4.0. The move has to be made to
       enable it to better support future protocol  and networking features.
       Some of these features are IPX with checksum,  security enhancements,
       and  protocol independence.  Following this change,  the default frame
       type of	DOS/ODI  driver is Ethernet 802.2 when there  is no protocol
       binding in NET.CFG file.  In this case,	if  your server  is not
       NetWare v4.0, please make sure the Ethernet 802.2 frame type has been
       bound before logging in.