Prerequisites for the Two-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 Two-Card Network Card Miniport Driver Test.
| Requirement | Description |
|---|---|
Network card |
Your Windows Embedded CE-based device must have an installed network card for which the miniport driver is to be tested. .gif "Bb203300.note(en-US,WinEmbedded.60).gif") Note:
Do not use the Vmini network interface with this test. Running the test over the Vmini interface disables the KITL connection between the development workstation and the Windows Embedded CE–based device.
|
Second network card |
The target device must have a second installed network card that functions as a support card. The support card can be identical to the test card. You should connect the test and support cards to an isolated test network with no other network traffic. |
Third network card |
The target device should also have a third network card that establishes a TCP/IP connection to the development workstation with 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 the second card to the test network. The second network card on the development workstation is not required to run the Two-Card Network Card Miniport Driver Test but can assist in troubleshooting problems that may arise.
The following tables show the software requirements for the Two-Card Network Card Miniport Driver Test.
| Requirement | Description |
|---|---|
Tux.exe |
Test harness, required for executing the test |
Kato.dll |
Logging engine, required for logging test results |
Ndt.dll |
Test protocol driver |
Ndt_2c.dll |
Tux test binary file |
The network cards that you use must be recognized by the Network Driver Interface Specification (NDIS) architecture. You must assign a name to each network card prior to running the test. The run-time image that you download to the target device must use shared miniport drivers on control cards. You must bind the TCP/IP protocol to one of the miniport drivers.
Note
When you run the Two-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.