Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS721H1_LAN-V0300 Alpha V7.2-1H1 LAN ECO Summary
*OpenVMS] VMS721H1_LAN-V0300 Alpha V7.2-1H1 LAN ECO Summary
New Kit Date: 30-SEP-2002
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Compaq Computer Corporation 2002. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: LAN
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS721H1_LAN-V0300
DEC-AXPVMS-VMS721H1_LAN-V0300--4.PCSI
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 8992 Blocks
Kit Applies To: OpenVMS Alpha V7.2-1H1
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:
VMS721H1_UPDATE-V0500
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-1H1.
This kit addresses the following problems:
PROBLEMS ADDRESSED IN VMS721H1_LAN-V0300 KIT
o The system can crash when another instance in the Galaxy shuts
down and there is I/O outstanding to the EBA (Galaxy Shared
Memory LAN) device. 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 to the EBA (Galaxy
Shared Memory LAN) devic 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 condition in the driver.
Images Affected:[SYS$LDR]SYS$EBDRIVER.EXE
o If the cluster code (PEDRIVER) is using the EBA (Galaxy Shared
Memory LAN) 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 EIA (82558, 82559,
82559ER, DE600, DE602 PCI Ethernet) 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 With the EIA (82558,82559, 82559ER, DE600, DE602 PCI Ethernet)
device, 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
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 EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet)
device driver is treating the console environment variable
EIx0_MODE setting of "twisted-pair" as "Full-Duplex,
Twisted-pair", so it should select half-duplex 10 mbit mode,
but selects full-duplex instead.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o The EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet)
device driver is not processing the EIx0_MODE console
environment variable setting of "FastFD" setting correctly.
This can result in a duplex mode mismatch problem.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o The EIA (82558, 82559, 82559ER, DE600, DE602 PCI Ethernet)
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 in the EIA (82558, 82559, 82559ER, DE600, DE602 PCI
Ethernet) device driver. This now runs correctly on these
NICs.
Images Affected:[SYS$LDR]SYS$EIDRIVER.EXE
o 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 in the EIA
(82558, 82559, 82559ER, DE600, DE602 PCI Ethernet) device
driver. 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 Resolve a system crash with the EIA (82558, 82559, 82559ER,
DE600, DE602 PCI Ethernet) device driver and with IP traffic
(generally involving a lot of telnet connections). When the
number of segments comprising a transmit packet request exceeds
15, the driver copies the remaining segments into one
additional segment. If this segment is not physically
contiguous, therefore requiring two additional segments instead
of one, the driver corrupts the stack and causes an INVEXCPTN
system crash. The problem is that the check for maximum number
of segments is off by one.
Images Affected: [SYS$LDR]SYS$EIDRIVER.EXE
o Fix a few problems with auto-negotiation by DE500-BA PCI
Ethernet devices 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$EWDRIVER_DE500BA.EXE
o On rare occasions, it is possible for the Tulip 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. The Tulip driver includes support for the Tulip
chip, DE425 EISA NIC, and the PCI Ethernet NICs DE434, DE435,
DE500-XA, DE500-AA, DE500-BA, DE504-BA.
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
o Adjust interrupt handling changes that were done to the Tulip
driver for V7.2-1H1 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. The Tulip driver includes support for
the Tulip chip, DE425 EISA NIC, and the PCI Ethernet NICs
DE434, DE435, DE500-XA, DE500-AA, DE500-BA, DE504-BA.
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$EWDRIVER_DE500BA.EXE
o A transmit issued to the DE500-BA PCI Ethernet device driver
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.
Images Affected:[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o Return SS$_DISCONNECT error status on transmit requests to the
DE500-BA PCI Ethernet device driver which complete with a "loss
of carrier" error. This error occurs if the cable is
disconnected using the 10Base5 MAU on the Alpha Workstations.
Images Affected:[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 in the DE500-BA PCI
Ethernet device driver. 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.
Images Affected:[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.
Images Affected:[SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o The DEGPA firmware included in the device driver for the DEGPA
PCI Gigabit Ethernet NIC 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 by the DEGPA
PCI Gigabit Ethernet device driver of the Tigon II chip.. 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 by the DEGPA PCI Gigabit Ethernet device
driver. This results in an 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 DEGPA PCI
Gigabit Ethernet 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 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 with the DEFPA PCI FDDI device, 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$FWDRIVER.EXE
o Increase the time after a reset before touching the PDQ FDDI
LAN device (FCA - DEFTA Turbochannel, FAA - DEFRA - DEFEA EISA,
FWA - DEFPA PCI). 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 For the PDQ FDDI LAN devices (FCA - DEFTA Turbochannel, FAA -
DEFRA - DEFEA EISA, FWA - DEFPA PCI), 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 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 For all LAN devices, 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 For all LAN devices, 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 For all LAN devices, Remove the limitation of 255 multicast
addresses enabled for a device. This may improve efficiency
somewhat by decreasing the multicast filtering work done by the
LAN driver. Only the Gigabit Ethernet devices take advantage
of this capability.
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 Add initial hardware support for the Fore Networks HE155
(DAPBA) and HE622 (DAPCA) NICs, including the ForeThought LAN
emulation code ported to OpenVMS, located in SYS$LAN_ATM4.EXE.
Images Affected:[SYS$LDR]SYS$ELDRIVER4.EXE
[SYS$LDR]SYS$HWDRIVER4.EXE
[SYS$LDR]SYS$LAN_ATM4.EXE
[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 Fix the display of error messages displayed by LANCP and
LANACP. If there were multiple errors when validating a
command, not all of the error codes were saved properly,
resulting in difficulty deciphering what went wrong when a
command failed.
Images Affected:[SYSEXE]LANACP.EXE
o Increase the allowed length of the LAN$DLL logical name from 16
to 256 characters. This is used by LANACP to locate the
default directory containing downline load images.
Images Affected:[SYSEXE]LANACP.EXE
o If the parent device name is not specified in the definition of
an ATM emulated LAN, other parameters specified in the command
are lost. So, if a series of parameters are specified, in
separate commands, the parameters are not saved until a command
specifying the parent device name was specified.
Images Affected:[SYSEXE]LANACP.EXE
o Decrease the number of receive buffers specified for use by MOP
from 6 to 4 to reduce the amount of bytlm quota required by the
LANACP process.
Images Affected:[SYSEXE]LANACP.EXE
o If LANACP fails to enable downline load service for a
particular device, at initial startup, it returns error status
to the system startup code which then terminates the image.
The result is that LANACP is not running after the system
boots. This change modifies LANACP so it continues to run
after being started, on any devices that it was able to start
on, despite a startup error on a device.
Images Affected:[SYSEXE]LANACP.EXE
o The message buffer for downline load service messages is too
small. this could cause it to be overrun, resulting in the
termination of LANACP with a stack dump.
Images Affected:[SYSEXE]LANACP.EXE
o Add support for automatic loading of the ATM emulated LAN
drivers, for the ELAN and CLIP emulated devices.
Images Affected:[SYSEXE]LANACP.EXE
o LANCP does not return the expected status to CLUSTER_CONFIG.COM
resulting in unexpected errors when attempting to configure the
satellite boot portion of cluster configuration.
Images Affected:[SYSEXE]LANCP.EXE
o Improve the boot messages for the EIA (82558, 82559, 82559ER,
DE600, DE602 PCI Ethernet), ERA (Tulip, DE422 EISA, DE425 EISA,
DE205 ISA Ethernet), and EWA (PCI Tulip, DE434, DE435,
DE500-XA, DE500-AA, DE500-BA PCI Ethernet) LAN devices, so that
more details are available to diagnose boot failures.
Images Affected:[SYS$LDR]SYS$EWBTDRIVER.EXE
[SYS$LDR]SYS$ERBTDRIVER.EXE
[SYS$LDR]SYS$EIBTDRIVER.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 for the DE500 PCI Ethernet device 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
[SYSEXE]APB.EXE
[SYSEXE]DEBUG_APB.EXE
o The embedded 21143 chip (10/100 Ethernet) 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
[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
for the TurboChannel DEFTA, EISA DEFEA, and PCI DEFPA FDDI
devices. 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 DE602-BA i82558 100BaseTX
o DE602-TA 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(s). To view these articles,open the appropriate product
database and perform a query using either of the following search strings:
'VMS721H1_LAN-V0300' or 'VMS721H1_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 VMS721H1_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=V3.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS721H1_LAN-V0300 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$!
$ PROD INSTALL VMS721H1_LAN/PROD=DEC/BASE=AXPVMS/VER=V3.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
All trademarks are the property of their respective owners.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| APB.EXE | CF6A4389 | X-8 | 27-AUG-2002 |
| | | 00:47:18.47 |
+----------------------------+----------+-----------------+--------------+
| DEBUG_APB.EXE | CF6A4389 | X-8 | 27-AUG-2002 |
| | | 00:49:11.13 |
+----------------------------+----------+-----------------+--------------+
| LANACP.EXE | D3A2C4FA | X-31 | 17-JUL-2002 |
| | | 04:09:52.13 |
+----------------------------+----------+-----------------+--------------+
| LANCP.EXE | 8422D9B2 | X-48 | 17-JUL-2002 |
| | | 04:09:34.89 |
+----------------------------+----------+-----------------+--------------+
| NET$CSMACD.EXE | 9FF3DB3C | X-17 | 17-JUL-2002 |
| | | 04:09:10.35 |
+----------------------------+----------+-----------------+--------------+
| NET$FDDI.EXE | 8C744FC3 | X-17 | 17-JUL-2002 |
| | | 04:09:19.91 |
+----------------------------+----------+-----------------+--------------+
| SYS$EBDRIVER.EXE | 28C7FAE3 | X-12 | 17-JUL-2002 |
| | | 04:11:53.04 |
+----------------------------+----------+-----------------+--------------+
| SYS$EIBTDRIVER.EXE | C8F819D2 | X-1 | 17-JUL-2002 |
| | | 03:48:29.97 |
+----------------------------+----------+-----------------+--------------+
| SYS$EIDRIVER.EXE | 91508D5B | X-25 | 17-JUL-2002 |
| | | 04:12:05.75 |
+----------------------------+----------+-----------------+--------------+
| SYS$ELDRIVER4.EXE | 72213319 | X-13 | 17-JUL-2002 |
| | | 04:01:39.14 |
+----------------------------+----------+-----------------+--------------+
| SYS$ERBTDRIVER.EXE | 237677CD | X-4 | 17-JUL-2002 |
| | | 03:54:06.04 |
+----------------------------+----------+-----------------+--------------+
| SYS$ERDRIVER.EXE | 7663209F | X-3 | 17-JUL-2002 |
| | | 04:02:58.61 |
+----------------------------+----------+-----------------+--------------+
| SYS$EW1000A.EXE | CABD6A37 | X-31 | 17-JUL-2002 |
| | | 04:11:40.81 |
+----------------------------+----------+-----------------+--------------+
| SYS$EWBTDRIVER.EXE | EDEB8BB6 | X-4 | 17-JUL-2002 |
| | | 03:55:22.09 |
+----------------------------+----------+-----------------+--------------+
| SYS$EWDRIVER.EXE | 42810F70 | X-3 | 17-JUL-2002 |
| | | 04:03:50.46 |
+----------------------------+----------+-----------------+--------------+
|SYS$EWDRIVER_DE500BA.EXE | 65DAC24F | X-3 | 17-JUL-2002 |
| | | 04:04:12.34 |
+----------------------------+----------+-----------------+--------------+
| SYS$EZDRIVER.EXE | CD89936C | X-3 | 17-JUL-2002 |
| | | 04:05:31.39 |
+----------------------------+----------+-----------------+--------------+
| SYS$FADRIVER.EXE | 0A2E6780 | X-3 | 17-JUL-2002 |
| | | 04:06:12.81 |
+----------------------------+----------+-----------------+--------------+
| SYS$FCBTDRIVER.EXE | 7088CD52 | X-1 | 17-JUL-2002 |
| | | 03:58:19.93 |
+----------------------------+----------+-----------------+--------------+
| SYS$FCDRIVER.EXE | 96897C1A | X-3 | 17-JUL-2002 |
| | | 04:06:27.80 |
+----------------------------+----------+-----------------+--------------+
| SYS$FRBTDRIVER.EXE | 84DE6521 | X-1 | 17-JUL-2002 |
| | | 03:58:48.54 |
+----------------------------+----------+-----------------+--------------+
| SYS$FRDRIVER.EXE | E2E4E2C4 | X-3 | 17-JUL-2002 |
| | | 04:06:50.74 |
+----------------------------+----------+-----------------+--------------+
| SYS$FWBTDRIVER.EXE | 4FF2CB82 | X-1 | 17-JUL-2002 |
| | | 03:59:12.88 |
+----------------------------+----------+-----------------+--------------+
| SYS$FWDRIVER.EXE | 1556254B | X-3 | 17-JUL-2002 |
| | | 04:07:05.77 |
+----------------------------+----------+-----------------+--------------+
| SYS$HWDRIVER4.EXE | F661382C | X-15 | 17-JUL-2002 |
| | | 04:12:16.85 |
+----------------------------+----------+-----------------+--------------+
| SYS$ICDRIVER.EXE | 17B0BF68 | X-39 | 17-JUL-2002 |
| | | 04:07:56.43 |
+----------------------------+----------+-----------------+--------------+
| SYS$IRDRIVER.EXE | 28AAEECC | X-39 | 17-JUL-2002 |
| | | 04:07:40.12 |
+----------------------------+----------+-----------------+--------------+
| SYS$IWDRIVER.EXE | 9A596D58 | X-39 | 17-JUL-2002 |
| | | 04:08:09.96 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN.EXE | FB8050EA | X-3 | 17-JUL-2002 |
| | | 03:49:09.53 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN_ATM.EXE | 16EB14BB | X-27 | 17-JUL-2002 |
| | | 03:56:26.34 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN_ATM4.EXE | D666F0FD | X-5 | 17-JUL-2002 |
| | | 03:56:46.04 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN_CSMACD.EXE | 774F9E8E | X-3 | 17-JUL-2002 |
| | | 03:52:11.29 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN_FDDI.EXE | 88667260 | X-3 | 17-JUL-2002 |
| | | 03:59:22.41 |
+----------------------------+----------+-----------------+--------------+
| SYS$LAN_TR.EXE | D28A1DDA | X-3 | 17-JUL-2002 |
| | | 04:00:05.98 |
+----------------------------+----------+-----------------+--------------+
|
