a:\ndis2\readme.txt 13-JUL-1995
This README file is for the NDIS2 DOS and NDIS2 OS/2 device
drivers for Digital's DEPCA and EtherWORKS 2 adapters.
Supported adapters: DEPCA,DE100,DE101,DE200,DE201,DE202,DE210,DE212,DE422
Device drivers: DEPCA.DOS and DEPCA.OS2
For simplicity, all of the above supported adapters will be
referred to as "EtherWORKS 2 adapters" throughout this document.
These device drivers comply with the NDIS 2.0.1 specification.
The EtherWORKS 2 adapters and the NDIS2 drivers meet the networking
needs of any Network Operation System (NOS) which adheres to the
NDIS 2.0.1 specification.
This file contains information on the following topics:
1. PROTOCOL.INI parameters
2. Installing multiple adapters
3. PATHWORKS V4.1 installation
4. PATHWORKS V5.0 installation
5. IBM OS/2 2.1 + LAN Server 3.X installation
6. 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.
***************************
* PROTOCOL.INI PARAMETERS *
***************************
The only parameter that must be specified is the "DriverName".
Note that many of these parameters have default values (which
are specified below). A parameter need not be specified in the
PROTOCOL.INI file if its default value is satisfactory.
DriverName
units:[n/a]
range:[DEPCA$]
default:[DEPCA$]
This parameter's value must be DEPCA$, it identifies the
network device driver.
The following entries are optional under the [DEPCA] section.
MaxMulticast
units:[integer]
range:[1-256]
default:[8]
Example: 8
This specifies the maximum number of multicast addresses that
can be in effect simultaneously. (NOTE that there's no 's' on
the end of this keyword.)
MaxTransmits
units:[integer]
range:[0-256]
default:[16]
Example: 16
This specifies the number of "TransmitChain"s that the MAC
driver guarantees to accept without giving an "OUT_OF_RESOURCE"
response.
The following parameters ONLY need to be set if your DEC EtherWORKS
2 adapter does not contain a diagnostic or remote boot ROM chip.
AdapterName
units:[n/a]
range:[DE100,DE101,DE200,DE201,DE202,DE210,DE212,DE422]
default:[n/a]
Example: DE100
This specifies the name of the ethernet adapter.
values adapter
------------ -------------------
DE100 DEC EtherWORKS LC
DE101 DEC EtherWORKS LC/TP
DE200 DEC EtherWORKS Turbo
DE201 DEC EtherWORKS Turbo/TP
DE202 DEC EtherWORKS Turbo/TP/BNC
DE210 DEC EtherWORKS MC
DE212 DEC EtherWORKS MC/TP
DE422 DEC EtherWORKS EISA/TP/BNC
RamAddress
units:[hex]
range:[C000,C800,D000,D800,E000,E800]
range for Micro Channel cards with 16KB mode option:
[C000, C100, C200, C300, C400, C500
C600, C700, C800, C900, CA00, CB00
CC00, D000, D100, D200, D300, D400
D500, D600, D700, D800, D900, DA00
DB00, DC00, E000, E100, E200, E300
E400, E500, E600, E700, E800, E900
EA00, EB00, EC00]
default:[n/a]
Example: 0xD000
This specifies the physical base address in the PC memory
address space of the "window" through which the adapter's RAM
will be referenced. This parameter's value must agree with
the jumpered configuration of the adapter. Not required for
DEC EtherWORKS 2 MC Adapter and DEC EtherWORKS 2 EISA Adapter.
Interrupt
units:[integer]
range:[2-15]
default:[n/a]
Example: 5
This specifies the IRQ level that will be used by the adapter-
to-PC interrupt. Its value must agree with the jumpered
configuration of the adapter. Not required for DEC EtherWORKS
2 MC Adapter and DEC EtherWORKS 2 EISA Adapter.
values adapter
------------ -------------------
2,3,4,5,7 DEC EtherWORKS 2 LC
5,9,10,11,15 DEC EtherWORKS 2 Turbo
5,9,10,11 DEC EtherWORKS 2 MC
5,9,10,11 DEC EtherWORKS 2 EISA
Netaddress
units:[integer/character]
range:[0h-0Fh] quotes are required
default:[n/a]
Example: "08002B12AF34"
This specifies the station address that will be used by the
adapter if the upper layers do not provide a way to set the
station address. If the upper layers set the station address,
then this switch will be ignored.
Following is an example PROTOCOL.INI fragment for a DEC EtherWORKS
2 Turbo adapter with no diagnostic or remote boot ROM chip:
[DEPCA_NIF]
DriverName = DEPCA$
MaxMulticast = 12
MaxTransmits = 32
AdapterName = DE200
RamAddress = 0xD000
Interrupt = 5
********************************
* INSTALLING MULTIPLE ADAPTERS *
********************************
For multiple adapter installation, check the DECPCI Forum on
CompuServe, or the BBS, or call your authorized Digital reseller.
See the README in the root directory of this distribution for
contact information.
******************************
* PATHWORKS 4.1 INSTALLATION *
******************************
Manual Installation:
If PATHWORKS is already installed and configured and you do
not wish to use the PATHWORKS installation program, perform
the following steps manually to install the NDIS2 driver:
1. Copy the DEPCA.DOS file from the driver installation
diskette (A:\NDIS2\DOS\DEPCA.DOS) to the C:\DECNET
directory.
2. Add the following line to CONFIG.SYS to load the driver:
DEVICE = C:\DECNET\DEPCA.DOS
3. ADD the PROTOCOL.INI stub from the driver installation
disk to the end of the existing PROTOCOL.INI file located
in the DECNET directory. The stub appears as follows:
[DEPCA]
DRIVERNAME=DEPCA$
4. Modify the [DATALINK] and [IPX4MAC] sections in the
PROTOCOL.INI file to change the value of the keyword
BINDINGS = driverlabel to BINDINGS = DEPCA.DOS
Automatic Installation Using the PATHWORKS Client Setup Diskettes:
Insert the PATHWORKS Client Setup diskette 1 of 2 in the
floppy disk drive.
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\DEPCA.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\DEPCA.DOS
FILES=30
Buffers=40
STACKS=9,256
SHELL = C:\COMMAND.com /P /E:1024
lastdrive=z
----- PROTOCOL.INI -----
[protocol manager]
DRIVERNAME = PROTMAN$
BINDINGS = DEPCA_NIF
[DEPCA_NIF]
DriverName = DEPCA$
[DATALINK]
DRIVERNAME = DLL$MAC
LG_BUFFERS = 16
SM_BUFFERS = 6
OUTSTANDING = 32
HEURISTICS = 0
BINDINGS = DEPCA_NIF
*******************************
* PATHWORKS V5.1 INSTALLATION *
*******************************
Automatic Installation Using the PATHWORKS Client Setup:
Insert the PATHWORKS 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 DEPCA]
NDIS Driver Path: [a:\ndis2\dos]
NDIS Driver File: [DEPCA.dos]
NDIS Driver Name: [DEPCA]
Other File: [ ]
Enter ALT_O
3. Please insert the disk which contains file:
A:\NDIS2\DOS\DEPCA.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_FULL_DUPLEX, etc.
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 *
**********************************************
Installation using 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. Use arrow keys or mouse to select <Install> from the
main menu.
3. Insert the Driver Distribution Diskette in the drive.
Enter <drive:\NDIS2\OS2> for the source directory.
4. LAPS will copy the network drivers onto 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. Select DEC DEPCA Adapter and add the driver to the
current configuration.
8. Select the protocols used on your network. See your
network administrator if you do not know what protocols
are used.
9. 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 LAN Manager installation program,
you must perform the following steps manually:
1. Create DEPCA driver directory
<DRIVE>:\LANMAN.DOS\DRIVERS\ETHERNET\DEPCA
2. Copy the files
\MSLANMAN.DOS\DRIVERS\ETHERNET\DEPCA\DEPCA.DOS and
\MSLANMAN.DOS\DRIVERS\ETHERNET\DEPCA\PROTOCOL.INI
to the new directory.
3. Copy the file \MSLANMAN.DOS\DRIVERS\NIF\DEPCA.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\DEPCA\DEPCA.DOS
5. Modify PROTOCOL.INI by appending the following
information:
[DEPCA_NIF]
DRIVERNAME=DEPCA$
6. Modify TCPIP_XIF and NETBEUI_XIF modules in PROTOCOL.INI
by changing the value of the bindings keyword.
from BINDINGS = driverlabel
to BINDINGS = DEPCA_NIF
Manual installation for OS/2 LAN Manager
----------------------------------------
If LAN Manager is already installed and configured and you
do not wish to use the LAN Manager installation program,
you must perform the following steps manually:
1. Create DEPCA driver directory
<DRIVE>:\LANMAN.OS2\DRIVERS\ETHERNET\DEPCA
2. Copy the files
\MSLANMAN.OS2\DRIVERS\ETHERNET\DEPCA\DEPCA.OS2 and
\MSLANMAN.OS2\DRIVERS\ETHERNET\DEPCA\PROTOCOL.INI
to the new directory.
3. Copy the file \MSLANMAN.OS2\DRIVERS\NIF\DEPCA.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\DEPCA\DEPCA.OS2
5. Modify PROTOCOL.INI by appending the following:
[DEPCA_NIF]
DRIVERNAME=DEPCA$
6. Modify TCPIP_XIF and NETBEUI_XIF modules in PROTOCOL.INI
by changing the value of the bindings keyword.
from BINDINGS = driverlabel
to BINDINGS = DEPCA_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.