Prerequisites for the One-Card Network Card Miniport Driver Test
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
The following table shows the hardware requirements for the One-Card Network Card Miniport Driver Test.
| Requirement | Description |
|---|---|
Network interface card |
The network card to be tested should be connected to an isolated test network with no other network traffic. |
Second network interface card |
The target device should also have a second network card that establishes a TCP/IP connection to the development workstation. When developing Windows Embedded CE target devices, the development workstation must be running Microsoft® Platform Builder. |
If you want to monitor traffic on the test network with network monitoring software, you can install a second network card on the development workstation and then connect it to the test network. The second network card on the development workstation is not required to run the One-Card Network Card Miniport Driver Test but can assist in troubleshooting problems that may arise.
The following tables show the software requirements for the One-Card Network Card Miniport Driver Test.
| Requirements | Description |
|---|---|
Tux.exe |
Test harness, required for executing the test |
Kato.dll |
Logging engine, required for logging test results |
Ndt.dll |
Protocol driver for the test |
Ndt_1c.dll |
Tux test binary file |
The miniport driver being tested should be recognized by NDIS. You should assign a name to the network card in order for the test to function correctly.
Note
When you run the One-Card Network Card Miniport Driver Test, the Windows Embedded CE 6.0 Test Kit (CETK) temporarily copies files to the root directory of the target device. While the test runs, the test dynamically consumes program memory on the target device. Before running the test, verify that there is at least 0.4 megabytes (MB) of free storage memory on the target device. Also verify that there is at least 1.0 MB of free program memory on the target device. If there is not sufficient space in the root directory of the target device or there is not sufficient program memory, the test cannot run.