ACCTON TECHNOLOGY CORPORATION ETHERNET FAMILY LAN ADAPTER BOARD DRIVERS FOR USE WITH MICROSOFT OS/2 LAN MANAGER The drivers contained in this diskette are for the following ACCTON Ethernet adapters: EtherCoax-8 (EN1809)ÄÄÄÄÄÄ¿ EtherPair-8 (EN1801) ³ EtherCoax-16N (EN1603) ÃÄ AT-bus EtherPair-16N (EN1602)ÄÄÄÄÄÄÙ EtherCoax-NE2 (EN1623)ÄÄÄÄÄÄ¿ EtherPair-NE2 (EN1622) ÃÄ Micro EtherCoax-MC (EN1606) ³ Channel- EtherPair-MC (EN1605)ÄÄÄÄÄÄÙ bus They are used with 3Com 3+Open, Microsoft OS/2 LAN Manager OEM distribution, Release 1.x or 2.0, and other compatible OEM versions of LAN Manager. The drivers named ETHNE conform to the Network Driver Interface Specification (NDIS) defined by Microsoft/3Com. Included in this directory are the following files: READ.ME This File ETHNE.OS2 The OS/2 NDIS MAC driver ETHNE.DOS The DOS NDIS MAC driver PROTOCOL.INI A sample PROTOCOL.INI file ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ INITIAL INSTALLATION ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1) Install the adapter. Proper installation can be verified by running the diagnostic program under DOS. Note that the diagnostic program will not run properly from the OS/2 compatibility box. 2) Decide what protocol stack will be used by selecting one from the three stacks supported by the drivers. The supplied drivers support the DLC/NETBEUI, NBP, and the XNS protocol stack from Microsoft, 3Com, and most LAN Manager vendors. 3) When setting up LAN Manager, your system will ask you to select a MAC driver to use. Choose any driver from the list shown on your screen. As you proceed with the installation process, the driver selected in this step will later be replaced by an ACCTON driver. For illustration purpose, the examples used in this document assume that the 3Com EtherLink II has been selected with 3+Open. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ INSTALLING ON OS/2 ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1) Copy the OS/2 driver from this diskette to the same directory used by LAN Manager to store its drivers. For example, when installing a 3+Open server using the normal directory structure type: COPY A:\LANMAN\ETHNE.OS2 C:\3OPEN\SERVER\LANMAN\DRIVERS When installing a 3+Open OS/2 workstation type: COPY A:\LANMAN\ETHNE.OS2 C:\3OPEN\OS2WKSTA\LANMAN\DRIVERS 2) Modify the CONFIG.SYS or CONFIG.OS2 file to refer to the adapter installed in Step 1 of the INITIAL INSTALLATION, rather than the adapter selected during LAN Manager installation in Step 3 of the same section. For example, if the 3Com EtherLink II was selected during a server installation, use a text editor to change the line: DEVICE=\3OPEN\SERVER\LANMAN\DRIVERS\ELNNKII.OS2 to the line: DEVICE=\3OPEN\SERVER\LANMAN\DRIVERS\ETHNE.OS2 If the 3Com EtherLink II was selected during a workstation installation, use a text editor to change the line: DEVICE=\3OPEN\OS2WKSTA\LANMAN\DRIVERS\ELNNKII.OS2 to the line: DEVICE=\3OPEN\OS2WKSTA\LANMAN\DRIVERS\ETHNE.OS2 ****** Note 1: Other varieties of LAN Manager keep their drivers in different directories. The CONFIG.SYS file should be modified to contain a command line that refers to the ACCTON driver instead of the driver selected during the INITIAL INSTALLATION process (Step 3 of INITIAL INSTALLATION). Note 2: The LAN Manager installation will add several drivers to the CONFIG.SYS file also. Only the MAC driver referring to a particular board should be replaced. Other drivers like the PROTMAN.OS2 should not be modified. ****** 3) Modify the PROTOCOL.INI file to include an entry for the ACCTON driver. The PROTOCOL.INI file defines the parameters for all the protocol drivers used by LAN Manager. Use a text editor to add the following lines to the file: [ETHERPAIRNE] drivername = ETHNE$ irq = 3 iobase = 0x300 The line containing "[ETHERPAIRNE]" defines the name of the driver, and will be used in the Bindings command described below. The drivername "ETHNE$" is used by the protocol manager. The lines: irq = iobase = define the parameters for the driver, and should be modified appropriately depending on the adapter and the PC configuration. The values shown correspond to the current factory default settings for the adapter supported. Additional explanation about these parameters are given at the end of this document. ***** Note : If no parameter follows the parameter name, then the protocol manager will use the default value. ***** 4) Modify the PROTOCOL.INI file to change the Bindings of the protocol stack to refer to the ACCTON driver instead of the driver selected during INITIAL INSTALLATION. Use a text editor to modify the "Bindings =" command line to refer to the "ETHERPAIRNE" name defined in Step 3 of this section. For example: If the DLC/NETBEUI protocol stack was selected to be used with 3+Open, the same lines must be changed in the PROTOCOL.INI file section labeled "[DLC]". BINDINGS = ETHERLINKII must be changed to: BINDINGS = ETHERPAIRNE 5) The installation is now complete. Reboot your system and run LAN Manager using the instructions supplied by the LAN Manager application vendor. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ INSTALLING ON DOS WITH THE DLC/NETBEUI PROTOCOL STACK ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ The procedure for installing on DOS with the DLC/NETBEUI protocol stack is very similar to the procedure used for OS/2. Only the directory names and file extensions will be changed. 1) Copy the DOS ETHNE.DOS driver from this diskette to the same directory used by LAN Manager to store its driver. For example, when installing a 3+Open DOS workstation using the normal directory structure type: COPY A:\LANMAN\ETHNE.DOS C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS 2) Modify the CONFIG.SYS or CONFIG.DOS file to refer to this adapter rather than the adapter selected during LAN Manager installation (INITIAL INSTALLATION). For example, if the 3Com EtherLink II was selected during a workstation installation, use a text editor to change the command line: DEVICE=\3OPEN\DOSWKSTA\LANMAN\DRIVERS\ELNNKII.DOS to the command line: DEVICE=\3OPEN\DOSWKSTA\LANMAN\DRIVERS\ETHNE.DOS ****** Note 1: Other varieties of LAN Manager keep their drivers in different directories. The CONFIG.SYS file should be modified to contain a command line that refers to the ACCTON driver instead of the driver selected during the INITIAL INSTALLATION process (Step 3 of INITIAL INSTALLATION). Note 2: The LAN Manager installation will add several drivers to the CONFIG.SYS file also. Only the MAC driver referring to a particular board should be replaced. Other drivers like the PROTMAN.DOS should not be modified. ****** 3) Modify the PROTOCOL.INI file to include an entry for this driver. The PROTOCOL.INI file defines the parameters for all the protocol drivers used by LAN Manager. Use a text editor to add the following command lines to the file: [ETHERPAIRNE] drivername = ETHNE$ irq = 3 iobase = 0x300 The line containing "[ETHERPAIRNE]" defines the name of the driver, and will be used in the Bindings command described below. The drivername "ETHNE$" is used by the protocol manager. The lines: irq = iobase = define other parameters for the driver, and should be modified appropriately depending on how the adapter and the PC are configured. The values shown correspond to the current factory default settings for the supported adapters. Additional information about these parameters are given at the end of this document. 4) Modify the PROTOCOL.INI file to change the Bindings of the protocol stack to refer to the ACCTON driver instead of the driver selected during INITIAL INSTALLATION. Use a text editor to modify the "Bindings =" command line to refer to the "ETHERPAIRNE" name defined in Step 3 of this section. For example: Under 3+Open using the DLC/NETBEUI protocol stack, and selecting 3Com EtherLink II during the INITIAL INSTALLATION, the "BINDINGS=" command line located at the section labeled "[DLC]" of the PROTOCOL.INI file must be changed from: BINDINGS = ETHERLINKII to: BINDINGS = ETHERPAIRNE 5) The installation is now complete. Reboot your PC and run LAN Manager using the instructions supplied by your vendor. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ SAMPLE PROTOCOL.INI FILE AND PARAMETERS ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ; This is the default protocol.ini file for the ACCTON AccEth Adapter [protocol manager] drivername = PROTMAN$ [netbeui] drivername = MNETB$ bindings = DLC0 DLC.MAXIN = 1 DLC.MAXOUT = 4 [dlc0] drivername = MDLC$ bindings = ETHERPAIRNE [ETHERPAIRNE] drivername = ETHNE$ irq = 3 iobase = 0x300 ; End of this sample file Several parameters are included in the ETHERPAIRNE section of the PROTOCOL.INI file. However, the only parameter that must be specified is the "drivername". The other parameters use the default values supplied by the driver. No values may be specified in the PROTOCOL.INI file if default adapter configuration values are used. irq Specifies the interrupt channel used by the adapter. The default value is 3. The interrupt is selected with a jumper on the adapter. Consult the installation guide for information on how to determine or modify the interrupt. Acceptable values for this parameter range from 2 to 7. However, some of the mentioned ACCTON adapters do not support all the acceptable values. iobase Specifies the iobase address used by the adapter. The default is 0x300. The iobase address is selected using jumpers. Consult the installation guide for information on how to determine or modify the iobase address. This parameter is given in hexadecimal values that range from 0x300 to 0x3e0. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ADDITIONAL PARAMETERS IN THE PROTOCOL.INI FILE FOR THE ACCTON ETHERPAIRNE NDIC DRIVER CONFIGURATION ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Keyword Parameter 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 GeneralRequests. This configures the size of the GeneralRequest Queue. MaxTransmits 6 .. 64 Default 12 Maximum number of outstanding TransmitChain commands. This configures the size of the TransmitChain Request Queue. MaxReceives 6 .. 96 Default 12 Maximum number of outstanding ReceiveChain commands. This configures the size of the ReceiveChain Request Queue. ReceiveBuffers 6 .. 96 Default 12 Configures the number of the Receive buffers in the Receive Buffer Pool. TransmitBufSize 128 .. 1514 Default 1514 Configures the size (in bytes) of buffers in the Transmit Buffer Pool. ReceiveBufSize 128 .. 1536 Default 256 Configures the size (in bytes) of buffers in the Receive Buffer Pool. ***** Note 1: Values for the preceding parameters are seldom changed by the user. Most of the time, the default values are used. Note 2: For users of the LAN Manager Beta Site Test Version V1.00 R00. When the LAN's traffic is heavy, the connection of server and workstation will be disconnected. This problem has been solved in the Version 1.00 R01 of the driver. Note 3: LAN Manager driver version V1.00 R02 fix a bug of previous version V1.00 R01 in running some application. ****** Trademarks: Microsoft OS/2 LAN Manager is a trademark of Microsoft Corporation. 3Com, 3+, 3+Open and EtherLink II are registered trademarks of 3Com Corporation.Download Driver Pack
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.