Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS721_LAN-V0400 Alpha V7.2-1 LAN ECO Summary
*OpenVMS] VMS721_LAN-V0400 Alpha V7.2-1 LAN ECO Summary
New Kit Date: 08-OCT-2002
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Compaq Computer Corporation 2001,2002. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: LAN - Local Area Network
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS721_LAN-V0400
DEC-AXPVMS-VMS721_LAN-V0400--4.PCSI
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 6064 Blocks
Kit Applies To: OpenVMS Alpha V7.2-1
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_1
1 - To be installed on all systems running
the listed version(s) of OpenVMS.
Kit Dependencies:
The following remedial kit(s), or later, must be installed BEFORE
installation of this kit:
VMS721_UPDATE-V0300
In order to receive all the corrections listed in this
kit, the following remedial kits, or later, should also be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for LAN on OpenVMS Alpha V7.2-1. This kit addresses the
following problems:
PROBLEMS ADDRESSED IN VMS721_LAN-V0400 KIT
o The system can crash when another instance in the Galaxy shuts
down and there is outstanding I/O. The driver fork routine now
verifies that the other instance has not shut down before
processing I/O on behalf of it.
Images Affected:[SYS$LDR]SYS$EBDRIVER.EXE
o The receiving side of a transmit request may crash because the
PFN count is incorrect. The transmit side now updates the PFN
count before updating the pointers given to the other instance
in the Galaxy (that is the target of the transmit request),
eliminating a race race condition in the driver.
Images Affected:[SYS$LDR]SYS$EBDRIVER.EXE
o If the cluster code (PEDRIVER) is using the device, it may
choose another slower LAN device rather than the shared memory
LAN device. This change sets the device line speed to 30000 so
that PEDRIVER chooses this interconnect over other slower
interconnects.
Images Affected:[SYS$LDR]SYS$EBDRIVER.EXE
o Occasionally, a transmit request to the device is not seen by
the device. This causes the transmit to be delayed until the
next transmit request is given to the device. Under heavy load
conditions, this is not noticeable. Under light load, this is
seen as a transmit that may take seconds to complete. Where
the device is used as a cluster interconnect, the result is
transmit retries and virtual circuit closures.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o If the link partner redoes auto-negotiation (switch powered
off, for example), the driver does not force a link transition
when appropriate, resulting in the link partner selecting
half-duplex mode when it should select full-duplex mode. Also,
the requested settings are not advertised correctly resulting
in difficulty auto-negotiating to the intended speed and duplex
mode.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o The driver is treating "twisted-pair" as "Full-Duplex,
Twisted-pair", where it should select half-duplex 10 mbit mode.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o The driver is not processing of the console environment
variable for the "FastFD" setting correctly. This can result
in a duplex mode mismatch problem. Most customers use the
auto-negotiation default and wil not see the problem.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o The device occasionally reads an invalid buffer descriptor from
the receive ring. When this happens a machine check occurs
with resulting system crash, often with an "invalid
scatter-gather map" error.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o Add support for the Intel 82559ER chip and the DE602-BB NIC.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o Add support for internal loopback mode. Some applications, for
example, the UETP system test package, use internal loopback
mode. This now runs correctly on these NICs.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o Add support for the 82559 Intel chip set. Also add support for
the 82558/82559 self-test after initialization. This test
ensures that the driver does not attempt to use the device
before it has passed some basic functional self-testing. If
self-test fails, the device is marked offline.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o Address performance problems with receive processing. This
change restructures receive processing to improve performance,
and reduce the number of receive overflows. Receive overflows
are visible in the LAN counters for the device and each
overflow represents a lost packet which causes application
pauses and retransmits.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o Fix a few problems with auto-negotiation to improve the ability
of the driver to auto-negotiate to the correct setting. This
includes adjusting the timing of various auto-negotiation
events, and restarting auto-negotiation when appropriate.
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o On rare occasions, it is possible for the driver to reset the
Tulip chip, but not wait long enough after reset before
touching the device resulting in a machine check system crash.
The solution is to increase the amount of time after a reset to
guarantee that the device has sufficient time to reset itself
after a reset.
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o The system can crash when configuring the DE425 on an
AlphaStation 150. The driver expects to have map registers but
they are not present on this system.
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o Adjust interrupt handling changes that were done for V7.2-1 to
address a problem with delayed interrupts. On occasion, the
interrupt for a receive packet is delayed until a subsequent
packet is received. Under heavy load conditions this is not
noticeable, under light load, it happens occasionally.
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o On the Alpha Professional Workstation (XP-1000) with the
embedded DE500-BA, auto-negotiation is not enabled correctly
after a user request to set the mode. This results in an
inability to negotiate to the desired speed and duplex mode.
(DE500-BA only).
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o A transmit may complete with false error status. The transmit
status is correctly recognized as 'success', but in the process
of setting the correct status, the driver clears the transmit
length, so transmit requests completed by the driver to the
user application have a length of zero bytes rather than the
requested length. This may affect an application which depends
on the valid length. (DE500-BA only).
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o Return SS$_DISCONNECT error status on transmit requests which
complete with a "loss of carrier" error. This error occurs if
the cable is disconnected using the 10Base5 MAU on the Alpha
Workstations. (DE500-BA only).
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o Although it is a rare occurance, it is possible for a system to
hang in a continuous interrupt loop. The DE500-BA generates an
unusual interrupt and the interrupt service routine does not
clear the interrupt condition, resulting in an apparent system
hang, as interrupts are continuously generated. (DE500-BA
only).
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o Add support for the Alpha Professional Workstation, XP-1000,
for the alternative MAU options, the 10/100 UTP, 10Base2, and
10Base5, which attach to the embedded DE500-BA. (DE500-BA
only).
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o Correct a receive overflow problem on the DE500-BA which causes
the receive process on the DE500-BA to hang, preventing
subsequent receives until the device is reset. Since there is
not a problem transmitting packets, the driver does not
recognize that the device needs to be reset. So, the system
must be rebooted or all applications using the device stopped
and restarted to clear the condition. This is a DE500-BA only
problem.
Images Affected:[SYS$LDR]SYS$ERDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER.EXE
[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o The DEGPA firmware cannot deal with a transmit buffer that is
within 12 bytes of a 4 gigabyte boundary. This could lead to
data corruption. This problem only affects the AlphaServer
4100, AlphaServer DS20, AlphaServer ES40, AlphaServer GS80 and
GS160, and system upgrades such as the DS25, ES45, and only
those systems with at least 4 gigabytes of memory. The fix is
to avoid the problem by copying the buffer to a special buffer
that is not near such a boundary. The number of times the
workaround is invoked is tallied in the internal driver
counters (MC LANCP SHOW DEVICE/INTERNAL_COUNTERS) called "4GB
workarounds", so you can see if the condition ever does occur.
Images Affected:[SYS$LDR]SYS$EW1000A.EXE
o Increase the amount of time given for device reset. The time
is increased from 80 to 640 milliseconds. On some systems,
insufficient reset time occasionally results in a machine check
system crash when the driver touches the device after a reset.
Images Affected:[SYS$LDR]SYS$EW1000A.EXE
o When a user (protocol) is stopped, the user context is not
reset correctly resulting in the inability to restart the user
without rebooting the system. For example, if DECnet is
stopped and restarted it may fail to restart.
Images Affected:[SYS$LDR]SYS$EW1000A.EXE
o The multicast addresses list is not given to the device again
after the driver resets the device to clear a transmit timeout
condition. This can happen if the cable is unplugged with
transmits outstanding to the device. The consequence is that
multicast traffic stops for all users (protocols) until another
user is started or an existing user is stopped and restarted.
Images Affected:[SYS$LDR]SYS$EW1000A.EXE
o "Add driver support for the DEGPA-SA and DEGPA-TA. In order to
use these devices DEGPA firmware will have to be upgraded to
Version 12.4.12. This is the only version of the firmware
supported by the driver.
Images Affected:[SYS$LDR]SYS$EW1000A.EXE
o Under rare circumstances, the TGEC driver, SYS$EZDRIVER, on DEC
4000 Model 410 systems, can bugcheck with a NETDLLERR crash
when the driver detects an inconsistency in its data
structures. This can occur when the last user (of the EZA or
EZB LAN device) stops and the number of outstanding transmits
is not zero. This fix corrects the problem.
Images Affected:[SYS$LDR]SYS$EZDRIVER.EXE
o On DEC 7000 systems which use mailbox hardware to read and
write registers, the error bits, which the driver should clear,
are not being cleared properly. This may result in a machine
check system crash because of stale error bits.
Images Affected:[SYS$LDR]SYS$FCDRIVER.EXE
[SYS$LDR]SYS$FADRIVER.EXE
[SYS$LDR]SYS$FRDRIVER.EXE
[SYS$LDR]SYS$FWDRIVER.EXE
o Increase the time after a reset before touching the device.
This as well as the above change may contribute to an
occasional machine check system crash after the driver resets
the device during system boot.
Images Affected:[SYS$LDR]SYS$FCDRIVER.EXE
[SYS$LDR]SYS$FADRIVER.EXE
[SYS$LDR]SYS$FRDRIVER.EXE
[SYS$LDR]SYS$FWDRIVER.EXE
o Change the restart policy after a device initialization error
from 'mark the device offline' to 'retry every 10 seconds
indefinitely'. This change allows the driver to recover from a
temporary initialization failure and to avoid the need for a
system reboot to clear the condition.
Images Affected:[SYS$LDR]SYS$FCDRIVER.EXE
[SYS$LDR]SYS$FADRIVER.EXE
[SYS$LDR]SYS$FRDRIVER.EXE
[SYS$LDR]SYS$FWDRIVER.EXE
o The number of outstanding control commands outstanding to the
device (for such things as user startup and shutdown) is not
cleared during initialization of the device. Under rare
circumstances, it is possible that this count is not zero at
the point that initialization is done. This can result in the
inability of an application to start a channel to the device.
Depending on the behavior of the application after the failure
to start the channel, the user may see an application failure
or a system crash.
Images Affected:[SYS$LDR]SYS$FXDRIVER.EXE
o In OpenVMS Version V7.2, the device line speed was added to the
LAN Device Characteristics block (LDC) that VCI applications
can look at to determine device characteristics. For the token
ring drivers, the speed field is incorrectly specified so it is
always zero. This fix correctly adds the line speed to the LDC
block.
Images Affected:[SYS$LDR]SYS$ICDRIVER.EXE
[SYS$LDR]SYS$IRDRIVER.EXE
[SYS$LDR]SYS$IWDRIVER.EXE
o Modify the VCI transmit path (used by PEDRIVER, DECnet-Plus,
TCP/IP, LAST, LAT and others) to verify the transmit request is
not too long, incrementing the "Transmit too long" error
counter and returning error status to the offending
application. This improves the ability to diagnose application
problems by identifying the failure to transmit in the device
counters and making it more visible.
Images Affected:[SYS$LDR]SYS$LAN.EXE
[SYS$LDR]SYS$LAN_CSMACD.EXE
[SYS$LDR]SYS$LAN_FDDI.EXE
[SYS$LDR]SYS$LAN_TR.EXE
[SYS$LDR]SYS$LAN_ATM.EXE
o Modify the VCI interface to allow a VCI user to enable
promiscuous mode.
Images Affected:[SYS$LDR]SYS$LAN.EXE
[SYS$LDR]SYS$LAN_CSMACD.EXE
[SYS$LDR]SYS$LAN_FDDI.EXE
[SYS$LDR]SYS$LAN_TR.EXE
[SYS$LDR]SYS$LAN_ATM.EXE
o Remove the limitation of 255 multicast addresses enabled for a
device.
Images Affected:[SYS$LDR]SYS$LAN.EXE
[SYS$LDR]SYS$LAN_CSMACD.EXE
[SYS$LDR]SYS$LAN_FDDI.EXE
[SYS$LDR]SYS$LAN_TR.EXE
[SYS$LDR]SYS$LAN_ATM.EXE
o Fix a system crash problem caused by a packet being received
for a user that had been stopped. The receive filtering code
had some stale last filtered user context that was used, so the
receive packet was delivered to a user who did not exist,
resulting in the system crash.
Images Affected:[SYS$LDR]SYS$LAN.EXE
[SYS$LDR]SYS$LAN_CSMACD.EXE
[SYS$LDR]SYS$LAN_FDDI.EXE
[SYS$LDR]SYS$LAN_TR.EXE
[SYS$LDR]SYS$LAN_ATM.EXE
o Modify the receive filtering code to allow reception of 802
frames with a DSAP equal to zero. Prior to this change, these
packets were considered illegal and could not be received by an
application.
Images Affected:[SYS$LDR]SYS$LAN.EXE
[SYS$LDR]SYS$LAN_CSMACD.EXE
[SYS$LDR]SYS$LAN_FDDI.EXE
[SYS$LDR]SYS$LAN_TR.EXE
[SYS$LDR]SYS$LAN_ATM.EXE
o Fix a problem with the LAN driver tracing code. If tracing was
stopped, resulting in the deallocation of the trace buffers, it
was still possible for a trace entry to be made during a driver
interrupt service routine. This happend because the trace mask
was cleared after the buffer was deallocated instead of before.
This would result in a system crash if driver tracing was
disabled in the midst of interrupt processing.
Images Affected:[SYS$LDR]SYS$LAN.EXE
[SYS$LDR]SYS$LAN_CSMACD.EXE
[SYS$LDR]SYS$LAN_FDDI.EXE
[SYS$LDR]SYS$LAN_TR.EXE
[SYS$LDR]SYS$LAN_ATM.EXE
o When a DECnet-Plus NCL command, "SHOW FDDI STATION * ALL"
request is processed by the LAN driver network management code,
if the requested device returns counters data asynchronously,
it is possible that R3 is destroyed during the LAN driver
processing. This results in an INVEXCPTN crash in NCL.EXE.
The problem is that R3 is not preserved cross the call to
obtain counters, when it should be. This affects any
DECnet-Plus network managed device that returns counters data
asynchronously to a counters request, which is all XMI and all
FDDI adapters.
Images Affected:[SYS$LDR]NET$CSMACD.EXE
[SYS$LDR]NET$FDDI.EXE
o Increase the buffer_limit quota when starting the LANACP
process to allow more LAN devices to be enabled for downline
load service. CLUSTER_CONFIG.COM configures all Ethernet and
FDDI LAN devices on the system for downline load service, and
if there are many LAN devices present, LANACP fails to start
because of insufficient quota.
Images Affected:[SYS$STARTUP]LAN$STARTUP.COM
o Improve the boot messages, so that more details are available
to diagnose boot failures.
Images Affected:[SYS$LDR]SYS$EWBTDRIVER.EXE
[SYS$LDR]SYS$ERBTDRIVER.EXE
[SYSEXE]APB.EXE
[SYSEXE]DEBUG_APB.EXE
o Add support for booting the Alpha Personal Workstation,
XP-1000, over the embedded 21143 chip.
Images Affected:[SYS$LDR]SYS$EWBTDRIVER.EXE
[SYS$LDR]SYS$ERBTDRIVER.EXE
[SYSEXE]APB.EXE
[SYSEXE]DEBUG_APB.EXE
o The boot driver is not restarting auto-negotiation after
resetting the device, which results in the link partner
(generally an auto-negotiating 10/100 switch) selecting
half-duplex mode and the boot driver selecting full-duplex
mode. The duplex mode mismatch slows satellite booting
considerably.
Images Affected:[SYS$LDR]SYS$EWBTDRIVER.EXE
[SYS$LDR]SYS$ERBTDRIVER.EXE
[SYSEXE]APB.EXE
[SYSEXE]DEBUG_APB.EXE
o The embedded chip in the Alpha Personal Workstation, is not
programmed correctly resulting in an inability to
auto-negotiate properly and an inability to work at all
console-specified modes (the console environment variable
settings).
Images Affected:[SYS$LDR]SYS$EWBTDRIVER.EXE
[SYS$LDR]SYS$ERBTDRIVER.EXE
[SYSEXE]APB.EXE
[SYSEXE]DEBUG_APB.EXE
o OpenVMS Version V7.3 LAN cluster support obsoletes the system
parameter, NISCS_LAN_OVRHD, which was typically set to 18
bytes. This parameter reduces the maximum packet size used by
the cluster code. When set to 0-5 bytes, the packet size
exceeds the size of the receive buffers in the FDDI boot
driver. This usually results in 1-6 bytes of zeros scattered
about the images loaded by the boot driver, which in turn,
results in a system crash when an affected image attempts to
execute the corrupted portion of the image.
The problem is significant only when the NISCA_LAN_OVRHD
parameter is set to 0-5 bytes on the system which is the FDDI
boot server, regardless of which OpenVMS release the server is
running on. For version V7.3 and later, the parameter is
obsolete and the LAN cluster driver (PEDRIVER) does not reduce
the maximum packet size at all.
The fix corrects the problem in the FDDI boot driver in the
satellite node by increasing the receive buffer size to
accomodate the maximum possible size FDDI packet.
Images Affected:[SYS$LDR]SYS$FCBTDRIVER.EXE
[SYS$LDR]SYS$FRBTDRIVER.EXE
[SYS$LDR]SYS$FWBTDRIVER.EXE
[SYSEXE]APB.EXE
[SYSEXE]DEBUG_APB.EXE
o Add support (device IDs) for the following new hardware:
o Emulex KGPSA Fibre Channel
o DEGPA-TA (Gigabit Ethernet)
o Adaptec AIC-7899
o PowerStorm 300/350
o 3DLabs P2V
o 3DLabs P3
o 8255x Fast Ethernet
o DE600-AA i82558 100BaseTX
o DE600-AA i82559 100BaseTX
o DE602-AA i82558 100BaseTX
o DE602-TA i82558 100BaseTX
o DE602-FA i82558 100BaseFX
o DE602-BA i82558 100BaseTX
o IntraServer i82558 Fast Ethernet
o DAPBA-FA (155m, MMF)
o DAPBA-UA (155m, UTP)
o DAPCA-FA (622m, MMF)
Images Affected:[SYSEXE]SYS$CONFIG.DAT
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database. To view these articles, open the appropriate
product database and perform a query using either of the following
search strings: 'VMS721_LAN-V0400' or 'VMS721_LAN'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
This kit requires a system reboot. Compaq strongly recommends that
a reboot is performed immediately after kit installation to avoid
system instability
If you have other nodes in your OpenVMS cluster, they must also be
rebooted in order to make use of the new image(s). If it is not
possible or convenient to reboot the entire cluster at this time, a
rolling re-boot may be performed.
INSTALLATION INSTRUCTIONS:
Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:
PRODUCT INSTALL VMS721_LAN /SOURCE=[location of Kit]
The kit location may be a tape drive, CD, or a disk directory that
contains the kit.
Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt
Special Installation Instructions:
o Scripting of Answers to Installation Questions
During installation, this kit will ask and require user
response to several questions. If you wish to automate the
installation of this kit and avoid having to provide responses
to these questions, you must create a DCL command procedure
that includes the following definitions and commands:
- $ DEFINE/SYS NO_ASK$BACKUP TRUE
- $ DEFINE/SYS NO_ASK$REBOOT TRUE
- Add the following qualifiers to the PRODUCT INSTALL
command and add that command to the DCL procedure.
/PROD=DEC/BASE=AXPVMS/VER=V4.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS721_LAN-V0400 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$!
$ PROD INSTALL VMS721H1_LAN/PROD=DEC/BASE=AXPVMS/VER=V4.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| APB.EXE | 5F8974C5 | X-8 | 12-JUL-2002 |
| | | 22:07:40.91 |
+----------------------------+----------+-----------------+--------------+
| DEBUG_APB.EXE | 5F8974C5 | X-8 | 12-JUL-2002 |
| | | 22:12:42.55 |
+----------------------------+----------+-----------------+--------------+
| CSMACD.EXE | 8A5879B6 | X-17 | 12-JUL-2002 |
| | | 22:25:17.43 |
+----------------------------+----------+-----------------+--------------+
| FDDI.EXE | 6F128DCC | X-17 | 12-JUL-2002 |
| | | 22:25:24.77 |
+----------------------------+----------+-----------------+--------------+
| SYS$EBDRIVER.EXE | 0739FAE1 | X-12 | 12-JUL-2002 |
| | | 22:28:10.97 |
+----------------------------+----------+-----------------+--------------+
| SYS$EIDRIVER.EXE | BEAE8D59 | X-25 | 12-JUL-2002 |
| | | 22:28:21.42 |
+----------------------------+----------+-----------------+--------------+
| SYS$ERBTDRIVER.EXE | 7B79173E | X-4 | 12-JUL-2002 |
| | | 22:08:02.64 |
+----------------------------+----------+-----------------+--------------+
| SYS$ERDRIVER.EXE | CAEA11B4 | X-3 | 12-JUL-2002 |
| | | 22:18:27.93 |
+----------------------------+----------+-----------------+--------------+
| SYS$EW1000A.EXE | E5436A32 | X-31 | 12-JUL-2002 |
| | | 22:27:55.20 |
+----------------------------+----------+-----------------+--------------+
| SYS$EWBTDRIVER.EXE | B7B5F745 | X-4 | 12-JUL-2002 |
| | | 22:09:45.11 |
+----------------------------+----------+-----------------+--------------+
| SYS$EWDRIVER.EXE | 6D7F0F75 | X-3 | 12-JUL-2002 |
| | | 22:19:33.11 |
+----------------------------+----------+-----------------+--------------+
| SYS$DE500BADRIVER.EXE | 1E76504E | X-3 | 12-JUL-2002 |
| | | 22:20:00.96 |
+----------------------------+----------+-----------------+--------------+
| SYS$EZDRIVER.EXE | 411E371A | X-3 | 12-JUL-2002 |
| | | 22:21:25.77 |
+----------------------------+----------+-----------------+--------------+
| SYS$FADRIVER.EXE | 4170096A | X-3 | 12-JUL-2002 |
| | | 22:22:04.12 |
+----------------------------+----------+-----------------+--------------+
| SYS$FCBTDRIVER.EXE | 6CDAA88F | X-1 | 12-JUL-2002 |
| | | 22:14:05.06 |
+----------------------------+----------+-----------------+--------------+
| SYS$FCDRIVER.EXE | A459CBE8 | X-3 | 12-JUL-2002 |
| | | 22:22:24.19 |
+----------------------------+----------+-----------------+--------------+
| SYS$FRBTDRIVER.EXE | 6D56215B | X-1 | 12-JUL-2002 |
| | | 22:14:43.53 |
+----------------------------+----------+-----------------+--------------+
| SYS$FRDRIVER.EXE | 27641BAB | X-3 | 12-JUL-2002 |
| | | 22:22:44.55 |
+----------------------------+----------+-----------------+--------------+
| SYS$FWBTDRIVER.EXE | 7250FCC8 | X-1 | 12-JUL-2002 |
| | | 22:15:16.68 |
+----------------------------+----------+-----------------+--------------+
| SYS$FWDRIVER.EXE | 3AA8254E | X-3 | 12-JUL-2002 |
| | | 22:23:08.98 |
+----------------------------+----------+-----------------+--------------+
| SYS$FXDRIVER.EXE | 1E76D5C0 | X-3 | 12-JUL-2002 |
| | | 22:23:26.80 |
+----------------------------+----------+-----------------+--------------+
| SYS$ICDRIVER.EXE | 384EBF6D | X-39 | 12-JUL-2002 |
| | | 22:24:00.68 |
+----------------------------+----------+-----------------+--------------+
| SYS$IRDRIVER.EXE | 0754EEC9 | X-39 | 12-JUL-2002 |
| | | 22:23:42.07 |
+----------------------------+----------+-----------------+--------------+
| SYS$IWDRIVER.EXE | B5A76D5D | X-39 | 12-JUL-2002 |
| | | 22:24:19.60 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN.EXE | 91468293 | X-3 | 12-JUL-2002 |
| | | 22:05:07.78 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN_ATM.EXE | 391514B9 | X-27 | 12-JUL-2002 |
| | | 22:11:41.89 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN_CSMACD.EXE | 4DCCD7B8 | X-3 | 12-JUL-2002 |
| | | 22:07:57.28 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN_FDDI.EXE | 86067A98 | X-3 | 12-JUL-2002 |
| | | 22:14:35.95 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN_TR.EXE | FD741DD8 | X-3 | 12-JUL-2002 |
| | | 22:15:26.61 |
+----------------------------+----------+-----------------+--------------+
All trademarks are the property of their respective owners.
|
