NDIS.TXT Driver File Contents (en1203-nec.zip)

                Accton Technology Corporation
             NDIS Driver Installation Overview
             =================================

Copyright (c) 1994, 1995 by Accton Technology Corporation.
All rights reserved.

The driver you need are in the directories MSLANMAN.DOS,
NDIS. The NDIS drivers contained in these subdirectories
are used with 3Com 3+Open, Microsoft OS/2 LAN Manager OEM
distribution, Release 1.x or 2.x,  and other compatible
OEM versions of LAN Manager.

The drivers named ETHPCI conform to the Network Driver
Interface Specification (NDIS) defined by Microsoft/3Com.

Included in MSLANMAN.DOS,  and NDIS subdirectories
are the following files:

\MSLANMAN.DOS\DRIVERS\ACCTON\ETHPCI\

    ETHPCI.DOS          The DOS NDIS MAC driver
    PROTOCOL.INI        A sample section of PROTOCOL.INI file

\MSLANMAN.DOS\DRIVERS\NIF\

    ETHPCI.NIF           Network Information File

\NDIS

    NDIS.TXT            This readme file

    WFW.TXT             The Installation guide for
                        Windows for Workgroups v3.11

    LANMAN.TXT          The Installation guide for
                        LAN Manager

    LANSVR.TXT          The Installation guide for Lan Server

    BANYAN.TXT          The Installation guide for Banyan VINES

    PATHWAY.TXT         The Installation guide for Wollongong Pathway
                        Access.

    PATHWORK.TXT        The Installation guide for DEC PATHWORKS

    PCNFS.TXT           The Installation guide for Sun PC-NFS


\NDIS\DOS

    EN1203D.NIF         Network Information File for LAN Server (DOS)
    ETHPCI.DOS          The DOS NDIS MAC driver
    OEMSETUP.INF        Network Information File for Windows
                        for Workgroups v3.11
    PROTOCOL.INI        A sample section of PROTOCOL.INI file

\NDIS\OS2

    EN1203O.NIF         Network Information File for LAN Server (OS2)
    ETHPCI.OS2          The OS2 NDIS MAC driver
    PROTOCOL.INI        A sample section of PROTOCOL.INI file


Sample PROTOCOL.INI Files and Parameters
----------------------------------------

[ETHPCI_NIF]

;  Default section of protocol.ini file for the Accton Adapter
    drivername = ETHPCI$
    ;SIA_MODE = AUTOSENSE [AUTOSENSE, TP, AUI, TP_FULL_DUPLEX]
; End of this sample file

There are several parameters included in the ETHPCI_NIF
section of the PROTOCOL.INI file. However, the only parameter
that you should specify is the "drivername."

If you change other parameter settings, such as the SIA_MODE
, make sure that it matches the hardware setting.
Otherwise, the adapter may fail.

If you don't specify these settings, Accton's NDIS driver
will automatically detect them.

SIA_MODE    Specifies the medium type used by the adapter.
            Acceptable values for this parameter are AUTOSENSE, TP, AUI
            and TP_FULL_DUPLEX. If you didn't specify this settings it
            would be AUTOSENSE. It means it can auto-detect what medium
            used.


List of Additional Parameters in the PROTOCOL.INI file
for the NDIS Driver Configuration
------------------------------------------------------
Note that values for the following parameters are seldom
changed by the user. Most of the time the default
values are used.

Keyword         Parameter

MAXTRANSMITS    1 .. 20  Default 4
                Maximum number of TransmitChain Buffers.
                This configures the number of the transmit buffers.

MAXRECEIVES     1 .. 20  Default 4
                Maximum number of ReceiveChain buffers.
                This configures the number of the Receive buffers.

MaxMultiCast    1 .. 1000  Default 10
                Maximum number of MultiCast Addresses.
                This configures the size of the MultiCast
                Address Table.

MaxRequests     6 .. 64  Default 8
                Maximum number of outstanding General Requests.
                This configures the size of the General Request
                Queue.



Troubleshooting and Error Messages
----------------------------------

To check for problems, please run the Test Adapter option
from ACCTEST.EXE in driver diskette DIAG subdirectory.

Error Message:
        MAC0000E: Inialization failure.
  Possible Causes:
        1. It is not PCI machine.
  Solution:
        Check is it PCI computer ?

Error Message:
        MAC0006E: Network Interface Hardware Not Responsing.
        MAC0007E: Unable to detect PCI ethernet card.
  Possible Causes:
        1. The adapter is not installed correctly in its slot.
        2. PCI adapter didn't setup correctly in BIOS setup.
  Solution:
        .Run the ACCTEST program to determine reason for the error.
        .Restart computer and setup the PCI adapter from BIOS again.

Error Message:
        MAC0009E: Invalid Drivername specified in protocol.ini files.
  Possible Causes:
        1. wrong drivername in protocol.ini.
        2. Binding to wrong drivername.
  Solution:
        . Make sure that bindings to correct protocol.ini file and drivername.
        . And Make sure that the key word of DriverName is ETHPCI and it must
          be upper cast.
---
All trademarks or brand names mentioned are properties
of their respective companies.

-- THE END --
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web4, load: 1.57