EtherWORKS 3 TURBO V2.51 README 14-Aug-1996
===============================
Thank You for purchasing a Digital EtherWORKS 3 TURBO Network Interface
Card. Digital's Network Products Group is committed to providing you
with updated EtherWORKS 3 TURBO device drivers to ensure that these cards will
install easily, perform exceptionally well, and operate in all the latest
network operating systems (NOS).
This file contains important information that was not available when the
EtherWORKS 3 TURBO User Information manual was printed. A RELEASE.NOT file,
also included in the root directory of this diskette, contains detailed
technical information regarding known anomalies in the use of the EtherWORKS 3
TURBO cards.
Section 1:....................................... Notes on EZWORKS utility
Section 2:....................................... Accessing the latest drivers
Section 3:....................................... Diagnostic error messages
Section 4:....................................... V2.51 Kit description
Section 1
=========
Note: EZWORKS now allows changing EtherWORKS 3 settings via command line
switches. See the file \EZWORKS.TXT for a full description on how
to use the switches. Please note that whenever executing any command
line switches be sure to include /CMD as one of the switches.
For most network operating environments, the EtherWORKS 3 TURBO Ethernet
controller card must be configured with the EZWORKS utility
before the network can be used. EZWORKS is not required when the
EtherWORKS 3 TURBO card is used in a Microsoft Windows NT environment.
The EZWORKS utility allows you to configure EtherWORKS 3 TURBO Ethernet
controller cards, and serves as a diagnostic tool for the cards. EZWORKS
works in unison with the RAMDIAG.COM file. Make sure that the RAMDIAG.COM file
is in the same directory as EZWORKS to run diagnostics.
To execute the EZWORKS utility, change your disk drive to the top-level
directory of this distribution diskette (for example, a:\), then enter
SETUP at the DOS prompt. The utility is completely menu driven and
contains help for each option shown at the bottom of the screen. The
bottom line of the screen will always contain the valid keys needed to
execute the options.
The EZWORKS utility will allow up to four controller cards to be
configured at a time. For simplicity sake, you may wish to install and
configure one card at a time.
During execution of the EZWORKS utility, you will have the option of
changing and storing the EtherWORKS 3 TURBO card settings. If any of the
following settings are changed, you MUST edit (using any standard text editor
such as EDIT or BRIEF) the corresponding configuration file for the driver that
you will be using (PROTOCOL.INI for NDIS, NET.CFG for ODI Client).
1. Base I/O Address
2. Memory Base Address
3. Memory Mode
4. IRQ Value
Refer to the README.TXT files contained within the \NOVELL\DOSODI and
\NDIS2\DOS subdirectories of this distribution diskette for more details
on editing the ConFiGuration/INItialization files that affect your operation.
The EtherWORKS 3 TURBO Controller card default settings are as
follows:
Base I/O Address = 300h
Memory Mode = 2K
Memory Base Address = D000h
IRQ = 5
RESOLVING A BUS CONFLICT
------------------------
If you realize, before installing the EtherWORKS 3 TURBO controller card,
that any of these default settings will pose a system conflict, or if you
install the card and the system will not boot due to a system conflict,
you have the option to hardstrap the card. To hardstrap the card, insert
one or both of the jumpers found at the locations marked W1 and W2 on the
EtherWORKS 3 TURBO card. Hardstrapping the EtherWORKS 3 TURBO card requires
only that an I/O range is available. When hardstrapped, the EtherWORKS 3 TURBO
card does not take up any memory area or IRQ lines, thereby reducing the
chance of a bus conflict.
The following table details how the board will be set with one or both of
these jumpers installed:
I/O Range W2 W1
---------------- -- --
200h - 21Fh ON ON
280h - 29Fh OFF ON
EISA mode ON OFF
Normal operation OFF OFF
After using the W1 and/or W2 jumpers to hardstrap the EtherWORKS 3 TURBO
card, the next step is to run EZWORKS to reconfigure the EtherWORKS 3 card
to reside where no bus conflict will occur. Use the EZWORKS Setup menu
and follow the guiding directions. After EZWORKS is complete, power down
the PC, remove the W1 and/or W2 jumpers, then power up the PC.
If a bus conflict persists, determine what the bus conflict is, set the
jumpers again, then run EZWORKS to resolve the conflict (following the
previous steps).
NOTE: W1 and/or W2 cannot be installed for normal operation!
Remember that if you change the EtherWORKS 3 TURBO default settings using
EZWORKS, you will have to update the appropriate network files
(PROTOCOL.INI for NDIS, NET.CFG for ODI, CONFIG.SYS, and EISA Setup).
USER NOTES
----------
When running EZWORKS diagnostics with the DE203 or DE205 cards connected
to a ThinWire network, it is necessary for the BNC (network) connector to
be terminated with a T-connector and two 50-ohm terminators. If this is
not done, EZWORKS will display a Loopback Error message. Also, full
diagnostics, including Loopback, cannot be properly run on a live network.
Running diagnostics with a DE203 or DE205 card installed on a live network
may also give Loopback Error messages.
EZWORKS will not allow diagnostics to be run when it detects that the
EtherWORKS 3 TURBO card is active. The EtherWORKS 3 TURBO card is
considered active if a network device driver has been loaded. It may be
necessary to remove the statement that loads the device driver in CONFIG.SYS
or other file and power cycle (cold boot) the PC to deactivate the
EtherWORKS 3 TURBO card.
Section 2
=========
***********************************************************************
* NOTE: When unZIPping the kit: *
* *
* 1) Please use the -d switch so that subdirectories are *
* properly created. *
* 2) Make sure the kit is unZIPped to the ROOT directory of a *
* diskette so that the original directory structure is *
* maintained. *
***********************************************************************
To obtain the latest EtherWORKS 3 TURBO software from the Internet:
1. Perform an ftp connect to ftp.digital.com. Your login name is anonymous.
2. Enter your password. (Use your Internet address as your password.)
3a. To obtain the currently RELEASED (shipping) EtherWORKS 3 kit
(matching upper/lowercase lettering) change your directory as follows:
cd /pub/DEC/adapters/ethernet/ewrk3/release
3b. To obtain the latest drivers prior to a major release of an EtherWORKS 3
kit. We maintain an interim kit. This kit is the currently released
(shipping) kit plus any drivers that were released/completed thereafter.
(Matching upper/lowercase lettering) change your directory as follows:
cd /pub/DEC/adapters/ethernet/ewrk3/interim
4. List all the files in the directory to determine the kit number. Released
and Interim kits will have the following syntax e3kitn. Where "n" is a
version number. For example for a released kit "n" could be 22(meaning
V2.2). For an Interim kit "n" could be 226(meaning V2.26).
ftp> ls
5. Select ftp image mode:
ftp> i
6. Perform a get command on the e3kitn.zip file. (where "n" is the kit
number determined in step 4.)
ftp> get e3kitn.zip
7. Type quit to exit ftp:
ftp> quit
To obtain the latest EtherWORKS 3 TURBO software from CompuServe:
1. Type GO DECPCI to select the depci forum and enter the LAN Controllers
library.
2. Select the Browse option to scroll through the library titles.
3. Click on the EtherWORKS title, then press Return to display the
description of the EtherWORKS 3 TURBO card.
4. Select the Retrieve option to copy the file to your system.
For information on obtaining a CompuServe account in the U.S.,
call (800)848-8990.
To obtain the latest EtherWORKS 3 TURBO software from the Network Product
Business BBS:
1. Using a modem connect to one of the following numbers:
USA: Network Product Business BBS 1-(508)-486-5777 (open 24hrs)
Europe: (33)92-96-03-12, select network products / area 23.
2. Follow the screen's menu-driven instructions to download the driver
files.
Section 3
=========
For information on ERROR messages, consult the ERROR.TXT file, located
in the root directory of this distribution diskette.
Section 4
=========
[Changes from V2.5 to V2.51]
o New EtherWORKS 3 MDI driver(V1.0.2) for SCO OpenServer 5. See \sco\readme.txt
for further details.
o Newly certified EtherWORKS 3 NetWare DOS ODI Client and Server drivers.
Copyright (c) Digital Equipment Corporation, 1996.
All Rights Reserved. Unpublished rights reserved
under the copyright laws of the United States.
RESTRICTED RIGHTS LEGEND Use, duplication, or
disclosure by the U.S. Government is subject to
restrictions as set forth in Subparagraph (c)(1)(ii)
of DFARS 252.227-7013, or in FAR 52.227-19, as
applicable.
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.