| From: NETCAD::NETCAD::DENAULT "Adrienne DTN 226-6025 17-Mar-1997 1700 -0500" 17-MAR-1997 18:29:46.32
To: @NETWORKS.DIS
CC: DENAULT
Subj: New DE500 DOS-format driver diskette available (V2.70)
From: NETCAD::FERGUSON "Janice Ferguson 508-486-6915 Network Adapters 13-Mar-1997 2212 -0500" 13-MAR-1997 22:14:50.90
To: @PCDRIVERS:[MISC.DIS_LIST]DE500_MANUF_KIT_RELEASE.DIS
CC:
Subj: FYI: new DE500 DOS-format driver diskette available (v2.70)
New software available for DE500, March 1997.
DOS-format Fast EtherWORKS PCI 10/100 driver diskette V2.7
kali::pcdrivers:[ethernet.de500.release]50kit270.zip (unzip with -d)
This driver diskette is a manufacturing release. This version of the
diskette is required for the DE500-BA, and will be phased into the DE500-AA
and DE500-XA adapters when the existing stock of the V2.6 release is depleted.
See below for detail of the changes to this diskette since the previous
manufacturing release, V2.6. This diskette supports the DE500-BA, DE500-AA,
and DE500-XA. The previous V2.6 release supported only the DE500-AA and
DE500-XA adapters.
This DOS-format diskette contains the following drivers: NDIS2 (DOS and OS/2),
Novell NetWare, Pathworks Native DLL, SCO MDI and LLI, WFW 3.11 enhanced mode,
Windows 95, Windows NT 3.51 and 4.0, and Packet Driver.
The Network Management diskette shipping with the DE500 product has not
changed. The Network Management diskette supports only Intel platforms.
DOS-format EtherWORKS PCI Network Management diskette V1.0
kali::pcdrivers:[ethernet.de500.release]ebmgt100.zip (unzip with -d)
Also available is Network Management software supporting both the Alpha
and Intel platforms. This software will not fit on a diskette, and is
available only electronically.
DOS-format EtherWORKS PCI Network Management Software V1.0
kali::pcdrivers:[ethernet.de500.interim]efmgt100.zip (unzip with -d)
These diskette files will be available on ftp, www, and bbs in a few days.
ftp.digital.com/pub/DEC/adapters/ethernet/de500
www.networks.digital.com/dr/nics/drivers
**************************************************
* DRIVER DISKETTE CHANGES SINCE PREVIOUS RELEASE *
**************************************************
V2.70 changes since V2.60
-------------------------
RELEASE.NOT
Added section detailing minimum driver revisions required for
DE500-AA and DE500-BA support.
EZWORKS and Diagnostics
Updated to support new DE500-BA hardware.
NDIS2
Updated to support new DE500-BA hardware.
Corrected protocol.ini file in mslanman.dos subdirectory.
Disable memory access to adapter (driver has always only used
I/O space). No longer check if memory space is configured; we
don't need it.
NetWare ODI DOS Client
Updated to support new DE500-BA hardware.
NetWare ODI OS/2 Client
Removed from this diskette, to make room for other more widely
used drivers. This driver is no longer supported for DE500.
NetWare ODI Server
Updated to support new DE500-BA hardware.
Updated to use Early Transmit Interrupt for DE500-AA and DE500-BA
(DE500-XA hardware does not support early tx interrupt).
NLMs updated.
\novell\srvodi\odide500.txt updated to enhance installation
instructions for Client32 for Windows 95.
Packet Driver
Added packet driver supporting DE500-BA, DE500-AA, and DE500-XA.
Pathworks Native DLL
Updated to support DE500-BA hardware.
SCO MDI
Changed prefix from dcx to dcxf. Removed support for 10 Mb
adapters (DE425, DE434, DE435, DE450) from the driver. This new
dcxf driver supports DE500-BA, DE500-AA, and DE500-XA. Systems
relying on the dcx driver to support both 10 and 10/100 cards
must use new 10 Mb drivers (dcxe) and new 10/100 Mb drivers
(dcxf). The 10 Mb driver can be obtained from the 10 Mb
electronic release sites (see readme.txt).
The 10/100 Mb dcxf driver supports DE500-BA, DE500-AA, and
DE500-XA.
SCO LLI
DE500 software kit V2.6 contained LLI driver V2.2.7
2.2.8 fixed a DE450 BNC connector problem
2.4.0 added DE500-BA support
2.4.2 keyword changes
2.4.3a fixed a DE435 cable disconnect problem
2.4.4 fixed DE500-BA receive overflow errata,
DE435 cable disconnect fix not in this version
2.4.5 added DE435 cable disconnect fix
NDIS3 (WFW)
Updated to support DE500-BA hardware.
NDIS3 (WinNT and Win95)
Updated to support DE500-BA hardware.
Fixed bug that would cause a crash during initialization if an
interrupt occurred.
The installation file for Windows NT (oemsetnt.inf), was updated
to correct a bug during unattended installations (those relying
on using the file unattend.txt).
Updated Windows 95 installation file, some keywords have changed.
Uninstall old driver, then install according to win95\readme.txt
instructions. See win95\readme.txt for more info about keyword
definitions.
Updated Windows NT installation file, some keywords have changed.
Uninstall old driver, then install according to winnt\readme.txt
instructions. Removed support for Windows NT 3.50. Windows NT
3.51 and 4.0 are supported. See winnt\readme.txt for more info
about keyword definitions.
|
| You need to pull down the V2.7 kit (as mentioned in the previous note)
and following the directions in the Win95 directory to install the
driver. In summary, you need to do the following:
1. In the network control panel, remove the DE500 adapter.
2. Exit the network control panel but do not reboot yet!!!
3. Insert the V2.7 kit in the floppy and run A:setup
4. From the O/S menu select Windows 95 and hit install.
5. When complete, exit ezworks and reboot the computer.
On the next boot, the DE500 adapter should be detected and the
DE500.SYS driver should be automatically installed.
-Brent
|
| re: .4 by GIDDAY::ANDREASEND
>> WIN95 still waits indefinitely after NT domain login screen if
>> twisted-pair cable is pulled out of card...
Hi Shayne,
You're clearly working on some other issue, but is the above normal
operating procedure for you or your customer?
I'm baffled,
/Bill
|
| Shayne,
I recreated your problem today and it looks to be a Windows 95
problem more than a DE500.SYS problem. When set to autosense mode, the
DE500.SYS driver monitors the cable status. If the system attempts to
send a packet while the cable is not present, the driver returns a no
cable status. It appears that Windows 95 is just continually retrying
rather that eventually failing. For a workaround, try forcing the card
through the network control panel to 10 Mb/ Half Duplex. When the
adapter is forced to a speed, the driver will try to send the packet
regardless of whether or not a cable is connected. A different status
will be returned rather than the no cable status and hopefully Win. 95
will deal with this better.
Hope this helps.
Brent Hiller
NDIS Driver Developer
Network Adapter Group
|
| Re .6 - Brent, thanks for the workaround, forcing the speed
to 10Mb / Half Duplex on the DE500 was successful. It caters for the worst-case
scenario, that being if the PC at the other end of the direct-connect
twisted pair cable is switched off. However this customer is very fussy
and wants cards that plug in and go - hence making a single configuration
change is too much for them... So I am recommending the customer go with the
DE450 which does that. Is the DE450 going to be available for couple
of years?
Re .5 Bill, yes it is an unusual configuration. The company is preparing
to roll out pairs of direct-connected computers to many parts of the state of
New South Wales. This contrasts with a "normal" configuration where the PC
would connect to a repeater so the PC would be able to load WIN95 OK if the
domain controller had gone away.
This is my first encounter with two PCs directly connected with a crossed,
twisted pair cable. To answer your question, pulling the cable out of the
network card seems to be the same as if the other machine were switched off.
The customer simply wanted the client machine to be able to enter WIN95 and/or
reboot if the server machine were switched off.
Many thanks, Shayne
|