File: a:\NDIS2\README.TXT 12-MAY-1995
This readme is for the NDIS2 DOS and NDIS2 OS/2 device drivers for
Digital Equipment Corporation's EtherWORKS 3 adapters.
Supported adapters: DE203, DE204, DE205
Device drivers: EWRK3.DOS and EWRK3.OS2
These device drivers comply with the NDIS 2.0.1 specification. The
EtherWORKS 3 adapters and the NDIS2 drivers meet the networking needs of
any Network Operating System (NOS) which adheres to the NDIS 2.0.1
specification.
This file contains information on the following topics:
1. Basic Operation
2. PROTOCOL.INI parameters
3. Multiple Adapter Support
4. Error Messages
5. PATHWORKS V4.1 installation
6. PATHWORKS V5.0 installation
7. IBM OS/2 2.1 + LAN Server 3.x Installation
8. Microsoft LAN Manager 2.X installation (DOS and OS/2)
For information on installing the NDIS2 DOS driver with Windows for
Workgroups, see the readme.txt in the WFW directory of this diskette.
*******************
* Basic Operation *
*******************
Upon loading a sign-on banner similar to the following is displayed:
EtherWORKS 3 NDIS MAC Driver V3.02
(C) Copyright 1994 Digital Equipment Corporation.
EISA SLOT: 02 IRQ: 0B BASE: D8000 SIZE: 2K ADAPTER: DE205-AB
The EISA SLOT: field indicates the EISA slot number in which the adapter is
located. In the event that ISA mode is used, this field appears labeled
'IO:' followed by the four digit ISA IO Base address in hex. This field
gives a quick indication of the mode that the adapter is running in. If it's
in EISA mode, you'll see the EISA slot number. If it's in ISA mode, you get
the IO base address.
IRQ: is the interrupt request level in hex. This may be 05, 0A, 0B, or 0F.
BASE: is the shared RAM base address. This is a 20-bit physical 80x86 address
in hexadecimal, and may be in the range of physical addresses allowed by the
NICSETUP utility provided with the EtherWORKS 3 adapter.
SIZE: indicates the size of memory for which the adapter is configured. All
memory modes are allowed (2K, 32K, 64K). I/O mode is not allowed.
ADAPTER: identifies the model and rev of the adapter being used.
The banner may be followed by a number of warning messages. These messages
are detailed in the section titled 'Error Messages' below.
Up to four instances of the driver may be loaded at once. An attempt to load
a fifth instance produces an error. For more information on multiple adapter
support, see the section titled 'multiple adapter support' below.
***************************
* PROTOCOL.INI Parameters *
***************************
DRIVERNAME required
This parameter is required of all NDIS drivers. This driver uses the
name EWRK3n$ where n is a number from 0-3 based on the number of drivers
installed. For more information on multiple adapter support, see the section
titled 'multiple adapter support' below.
For single adapter setups, this parameter should look like:
DRIVERNAME=EWRK3$
IOADDRESS optional legal values 0x100 to 0x3E0,
in increments of 0x20
This parameter is used to specify the base I/O address of the adapter
when running in ISA mode. It is not necessary to specify this parameter
when running in a single adapter system. The driver locates the adapter
automatically whether it is in ISA or EISA mode. If you choose to specify
this parameter it is validated. If an EtherWORKS 3 adapter cannot be
located at the specified address, an error message is printed, and the driver
load fails. If this address is not specified and the PC exhibits unexpected
behavior, it should be specified.
Example: IOADDRESS=0x220
EISASLOT optional legal values 1 to 15, in increments of 1
This parameter is used to specify the EISA slot number of the adapter
when running in EISA mode. It is not necessary to specify this parameter
when running in a single adapter system. The driver locates the adapter
automatically whether it is in ISA or EISA mode. If you choose to specify
this parameter it is validated. If an EtherWORKS 3 adapter cannot be
located in the specified slot, an error message is printed, and the driver
load fails. If this address is not specified and the PC exhibits unexpected
behavior, it should be specified.
Example: EISASLOT=4
INTERRUPT optional legal values 5, 10, 11, 15
This parameter is used to verify the interrupt request level stored in
the adapter NV RAM. If it does not match the interrupt level stored in NV
RAM, an error message is printed. This is not considered a fatal error and
the driver will continue to load.
Example: INTERRUPT=11
RAMADDRESS optional legal values specified by NICSETUP,
depending on value of memory mode
This parameter is used to verify the ram address stored in the adapter
NV RAM. If it does not match the ram address stored in NV RAM, an error
message is printed. This is not considered a fatal error and the driver
will continue to load.
Example: RAMADDRESS = 0xD000
MEMORYMODE optional legal values 2, 32, or 64
This parameter is used to verify the memory mode stored in the adapter
NV RAM. If it does not match the memory mode stored in NV RAM, an error
message is printed. This is not considered a fatal error and the driver
will continue to load.
For this driver, 2K mode is always the best choice. Other drivers may
have architectural constraints which require the choice of 32K or 64K modes.
2K mode has 63 network buffers.
32K mode has 15 network buffers.
64K mode has 31 network buffers.
After binding, the driver will change the adapter to 2K mode, regardless
of which memory mode is stored in NV RAM. The adapter will still "claim" the
memory space stored in NVRAM (2, 32, or 64Kbytes), but will use only 2Kbytes.
This is to give the driver full use of all 63 network buffers. The original
memory mode will be restored to the adapter on a cold boot or ctl-alt-del.
Example: MEMORYMODE = 2
NETADDRESS optional String of twelve ASCII encoded HEX digits.
This parameter is used to override the MAC address of the adapter.
The address must be specified as a string of twelve ASCII encoded HEX digits.
Examples: NETADDRESS="AA0004001234" Correct
NETADDRESS="08002B123456" Correct
NETADDRESS="08-00-2B-12-34-56" Correct
NETADDRESS=08002B123456 WRONG. PROTMAN.SYS will parse this
as a number, and NOT a string.
Must use quotes.
FLAGS optional legal values 0 or 1
This parameter is used to modify operation of the driver for particular
stack or application implementations. Each bit within this value may have
a meaning. Currently only bit 0 is defined.
Bit 0 1 = NETADDRESS parameter changes the current and permanent
station addresses in the service-specific table.
(this does not follow the NDIS2 specification)
FLAGS = 1
0 = NETADDRESS parameter changes the current station address
only in the service-specific table. (default)
(this adheres to the NDIS2 specification)
FLAGS = 0
Example: FLAGS=1
****************************
* Multiple Adapter Support *
****************************
When using multiple EtherWORKS 3 adapters in a single system, it is necessary
to identify them uniquely in terms of both the driver name, and the location
of the card in EISA or ISA space. In some Network OS installations, the
second installation does not specify the PROTOCOL.INI parameters as the
EtherWORKS 3 NDIS2 driver requires. The resulting PROTOCOL.INI should be
reviewed and modified as in the example below:
[NETBEUI]
DRIVERNAME=EWRK3$
EISASLOT=2
[DECNET]
DRIVERNAME=EWRK31$
EISASLOT=3
[TCPIP]
DRIVERNAME=EWRK32$
IOADDRESS=0x220
This PROTOCOL.INI stub is for a system with three EtherWORKS 3 adapters. The
adapter that is logically called 'NETBEUI' is bound to the adapter in EISA
slot #2, and has the DRIVERNAME EWRK3$. The adapter that is logically called
'DECNET' is in EISA slot #3, and has the DRIVERNAME EWRK31$. The adapter
that is logically called 'TCPIP' is in ISA space, at IO address 220 hex. It
is called EWRK32$.
Up to four adapters are supported.
******************
* Error Messages *
******************
During Initialization, any one of the following error messages may appear.
EEPROM Checksum Error.
The EEPROM which holds the adapter configuration set by NICSETUP has
failed a checksum test. The information contained in it is invalid.
Run the NICSETUP utility to reset the adapter configuration. Driver
load fails.
Could not locate adapter.
The driver, in attempting to probe for the adapter automatically, could
not locate one. Driver load fails.
Invalid IOADDRESS in PROTOCOL.INI.
User supplied an invalid IOADDRESS in PROTOCOL.INI. Correct PROTOCOL.INI
by specifying correct IO Base address if in ISA mode, remove statement
if in EISA mode. Driver load fails.
Invalid EISASLOT in PROTOCOL.INI.
User supplied an invalid EISASLOT in PROTOCOL.INI. Correct PROTOCOL.INI
by specifying correct EISA slot number if in EISA mode, remove statement
if in ISA mode. Driver load fails.
Adapter must not be configured for I/O mode.
Use NICSETUP to configure the adapter for 2K, 32K, or 64K memory mode.
Driver load fails.
Ignoring RAMADDRESS in PROTOCOL.INI - does not match hardware setting.
Use NICSETUP to change setting.
Either remove the protocol.ini entry, change it to match the hardware,
or change the hardware to match the entry. Driver load continues,
using the value from NV RAM.
Ignoring MEMORYMODE in PROTOCOL.INI - does not match hardware setting.
Use NICSETUP to change setting.
Either remove the protocol.ini entry, change it to match the hardware,
or change the hardware to match the entry. Driver load continues,
using the value from NV RAM.
Ignoring INTERRUPT in PROTOCOL.INI - does not match hardware setting.
Use NICSETUP to change setting.
Either remove the protocol.ini entry, change it to match the hardware,
or change the hardware to match the entry. Driver load continues,
using the value from NV RAM.
Invalid interrupt number.
The interrupt number in adapter NV RAM is corrupt. Use NICSETUP
to change the interrupt number. Driver load fails.
Driver Instance Limit Exceeded.
Attempted to load 5 or more instances of the EWRK3 driver. Edit
CONFIG.SYS to reduce the number of driver instances to a maximum of 4.
Driver load fails. This failure does not effect the load status of
other copies of the driver already loaded.
Could not open Protocol Manager.
Driver was unable to open PROTMAN$. Ensure that your networking software
is correctly installed, and that the DEVICE statement used to load
PROTMAN in CONFIG.SYS comes BEFORE the device statement to load the
EWRK3 driver. Driver load fails.
Could not register driver with Protocol Manager.
Driver was unable to register with PROTMAN$. No corrective action.
Driver load fails.
Could not close Protocol Manager.
Driver could not close the PROTMAN$ driver after successfully registering
itself. No corrective action. Driver load fails.
Invalid keyword in PROTOCOL.INI.
Warning message. User has specified an invalid keyword in PROTOCOL.INI
for this driver. Remove the invalid entry. Driver load continues.
PROTOCOL.INI keyword has too many parameters.
Warning message. User has specified too many parameters for a valid
PROTOCOL.INI keyword. Correct the parameters. Driver load continues.
PROTOCOL.INI parameter too low, ignored.
PROTOCOL.INI parameter too high, ignored.
Warning message. User has specified a value that is out of range for a
valid PROTOCOL.INI keyword. Correct the offending parameter. Driver load
continues.
PROTOCOL.INI string parameter too long, ignored.
Warning message. User has specified a value that is too long for a valid
string field in PROTOCOL.INI. Correct the offending string. Driver load
continues if the offending parameter is not DRIVERNAME. If DRIVERNAME is
in error, the driver load fails.
******************************
* PATHWORKS 4.1 INSTALLATION *
******************************
Manual Installation:
If PATHWORKS is already installed and configured and you do not wish
to use the installation program, perform the following steps manually
to install the NDIS 2 MAC Driver:
1. Copy the EWRK3.DOS file from the driver installation
diskette (A:\NDIS2\DOS\EWRK3.DOS) to the C:\DECNET directory.
2. Add the following line to your CONFIG.SYS to load the driver:
DEVICE = C:\DECNET\EWRK3.DOS
3. ADD the PROTOCOL.INI stub from the driver installation disk
to the end of the old PROTOCOL.INI file located in the DECNET
directory. The stub appears as follows:
[EWRK3]
DRIVERNAME=EWRK3$
4. Modify the [DATALINK] and [IPX4MAC] sections in the
PROTOCOL.INI file to change the value of the keyword
BINDINGS = driverlabel to BINDINGS = EWRK3.DOS
Automatic Installation Using the PATHWORKS Client Setup Diskettes:
Insert the PWRKS Client Setup diskette 1 of 2 in your floppy disk.
Run NETSETUP from that drive and follow the instructions until you
reach the window labeled:
Select the network adapter type:
o Select "Ethernet" and press ENTER key.
Select the Ethernet adapter:
o Select "Other NDIS" and press ENTER key.
Enter full DRIVE:\PATH\FILENAME for NDIS driver:
o Type A:\NDIS2\DOS\EWRK3.DOS and press ENTER.
Enter full DRIVE:\PATH\ for the PROTOCOL.INI stub:
o Type A:\NDIS2\DOS\ and press ENTER.
After you have performed these steps, PATHWORKS will copy the
corresponding files from the installation diskette to the directory.
Example of CONFIG.SYS and PROTOCOL.INI for PATHWORKS 4.1
----------------------------------------------------------
----- CONFIG.SYS -----
DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\WINDOWS\EMM386.EXE 3072 RAM FRAME=E000
DOS=HIGH,UMB
DEVICE=C:\DECNET\laddrv.sys /D:4
DEVICE=C:\DECNET\PROTMAN.SYS /I:C:\DECNET
DEVICE=C:\DECNET\EWRK3.DOS
FILES=30
Buffers=40
STACKS=9,256
SHELL = C:\COMMAND.com /P /E:1024
lastdrive=z
----- PROTOCOL.INI -----
[protocol manager]
DRIVERNAME = PROTMAN$
BINDINGS = EWRK3_NIF
[EWRK3_NIF]
DriverName = EWRK3$
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 16
SM_BUFFERS = 6
OUTSTANDING = 32
HEURISTICS = 0
BINDINGS = EWRK3_NIF
*******************************
* PATHWORKS V5.1 INSTALLATION *
*******************************
Automatic Installation Using the PATHWORKS Client Setup:
Insert the PWRKS Client Setup diskette 17 in your floppy drive.
Run SETUP from that drive and follow the instructions
1. From "Select Drive" screen
Select Alt_N for Network
Select Decnet_Transport
2. Select "Other Adapter"
Example: "Other Adapter" Screen
Adapter Name: [Digital EtherWORKS 3]
NDIS Driver Path: [a:\ndis2\dos]
NDIS Driver File: [EWRK3.DOS]
NDIS Driver Name: [EWRK3]
Other File: [ ]
Enter ALT_O
3. Please insert the disk which contains file:
A:\NDIS2\DOS\EWRK3.DOS
Insert Diskette <enter>
Re-insert SETUP diskette when prompted <enter>
4. Is the adapter a token ring adapter? [NO]
5. "Verify Network Information" Screen
Example:
Your Node Name:[LAB004] Your Node Address: [4.711]
Lan Manager Username:[ADMIN]
Lan Manager Username:[********] (enter twice for verification)
Server Name:[LAB001] Server Node Address: [4.700]
Service:[PWV51]
Enter password for service: [ ] (<enter> if none)
6. "Edit Protocol.ini" Screen
Enter the correct Medium as displayed. TP, TP_FULLDUPLEX
ALT_S to save.
7. The SETUP utility will auto connect you to your desired
PATHWORKS client setup service.
Continue with the instructions to complete the installation.
**********************************************
* IBM OS/2 2.1 + LAN SERVER 3.X INSTALLATION *
**********************************************
Automatic installation using the IBM LAN Adapter and Protocol Support (LAPS)
----------------------------------------------------------------------------
1. In OS/2 open the OS/2 System window, the System Setup window and
the LAPS window. If you are installing Lan Server for the first
time, LAPS is automatically started.
2. Select <Install> from the main menu.
3. Insert the Digital EtherWORKS 3 Installation Disk in the
drive. Enter <drive:\NDIS2\OS2> for the source directory.
4. LAPS will copy the EWRK3 drivers on the system drive and display
a message saying <Installation Complete>. Click on <OK>
5. Select <Configure> from the LAPS main window.
6. Select <Configure LAN transports> and <Continue>.
7. Add the DEC EWRK3 Adapter driver to the current configuration.
Select the protocols used on your network. See your network
administrator if you do not know what protocols are used.
8. Select <OK> when completed. Select Exit at the main LAPS window
and <Continue> at the Update Drives window. Exit LAPS, shut down
OS/2 and reboot the machine.
Refer to the LAN Server installation guide for additional directions
on using LAPS.
*********************************************************
* MICROSOFT LAN MANAGER 2.X INSTALLATION (DOS AND OS/2) *
*********************************************************
Automatic installation using the LAN Manager setup program (DOS and OS/2)
-------------------------------------------------------------------------
1. In the \LANMAN directory, start the SETUP program.
2. Select <Configuration> from the main menu.
3. Select <Network Driver> from the configuration menu.
4. Remove any old adapter using <Remove Configuration>.
5. Select <Add Configuration>.
6. Select <Other Drivers> and follow the directions.
Manual installation for DOS LAN Manager
---------------------------------------
If LAN Manager is already installed and configured and you do not
wish to use the installation program, you have to perform the
following steps manually:
1. Create EWRK3 driver directory
<DRIVE>:\LANMAN.DOS\DRIVERS\ETHERNET\EWRK3
2. Copy the files \NDIS2\DOS\EWRK3.DOS and \NDIS2\DOS\PROTOCOL.INI
to the new directory.
3. Copy the file \NDIS2\DOS\EWRK3.NIF to the directory
<DRIVE>:\LANMAN.DOS\DRIVERS\NIF
4. Add the following to CONFIG.SYS to load the driver:
DEVICE=<DRIVE>:\LANMAN.DOS\DRIVERS\ETHERNET\EWRK3\EWRK3.DOS
5. Modify PROTOCOL.INI by appending the following information:
[EWRK3_NIF]
DRIVERNAME=EWRK3$
6. Modify TCPIP_XIF and NETBEUI_XIF modules in PROTOCOL.INI by
changing the value of the bindings keyword.
from BINDINGS = driverlabel
to BINDINGS = EWRK3_NIF
Manual installation for OS/2 LAN Manager
----------------------------------------
If LAN Manager is already installed and configured and you do not
wish to use the installation program, you have to perform the
following steps manually:
1. Create EWRK3 driver directory
<DRIVE>:\LANMAN.OS2\DRIVERS\ETHERNET\EWRK3
2. Copy the files \NDIS2\OS2\EWRK3.OS2 and \NDIS2\OS2\PROTOCOL.INI
to the new directory.
3. Copy the file \NDIS2\OS2\EWRK3.NIF to the directory
<DRIVE>:\LANMAN.OS2\DRIVERS\NIF
4. Add the following to CONFIG.SYS to load the driver:
DEVICE=<DRIVE>:\LANMAN.OS2\DRIVERS\ETHERNET\EWRK3\EWRK3.OS2
5. Modify PROTOCOL.INI by appending the following information:
[EWRK3_NIF]
DRIVERNAME=EWRK3$
6. Modify TCPIP_XIF and NETBEUI_XIF modules in PROTOCOL.INI by
changing the value of the bindings keyword.
from BINDINGS = driverlabel
to BINDINGS = EWRK3_NIF
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.