################################################################################
Name: Window NT4.0 Diagnostic Program
Version: 1.01
Released By: Clifford Chiang
Release Date: 1999.3.12
Changed File: NT4Diag.exe
Packet.sys
Reason: This program will indicate packet with test pattern to AP only
####################################################################
Name: Window NT4.0 Diagnostic Program
Version: 1.02
Released By: Clifford Chiang
Release Date: 2000.1.24
Changed File: NT5Diag.exe
Reason: Modifying for Win2000
####################################################################
Name: Window NT4.0 Diagnostic Program
Version: 1.03
Released By: Clifford Chiang
Release Date: 2000.7.31
Changed File: NT4Diag.exe
Reason:
1. Provide better user interface for Magic Packer sender.
2. Provide online help.
3. Modify new test packet.
####################################################################
Name: Window NT4.0 Diagnostic Program
Version: 1.04
Released By: Clifford Chiang
Release Date: 2000.9.7
Changed File: NT4Diag.exe
Hellowin.rc
Reason: Add Target MAC Address Load and Save functions in Magic
Packet Sender.
####################################################################
Name: Window NT4.0 Diagnostic Program
Version: 1.60
Released By: Owen Wei
Release Date: 2000.10.16
Changed File: testapp.c
HELLOWIN.RC
packet32.c
Reason: The diagnostic program can install the protocol driver
automatically and the user does not have to install the
protocol driver anymore before execute the diagnostic
program.
####################################################################
Name: Window NT4.0 Diagnostic Program
Version: 1.70
Released By: Clifford Chiang, Owen Wei
Release Date: 2000.10.26
Changed File: testapp.c
HELLOWIN.RC
Reason: 1. Change "Reset" function to driver counter reset. (Clifford)
2. Add duplex mode to link status. (Clifford)
3. Fix the following bug:
The diagnostic program can not work anymore after being
executed several times. (No adapters can be binded.) (Owen)
4. The diagnostic program can install the protocol driver
automatically and the user does not have to install the
protocol driver anymore before execute the diagnostic
program. (Owen)
####################################################################
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.