NDIS Performance Test (Windows CE 5.0)

Windows CE 5.0
Send Feedback

The Network Driver Interface Specification (NDIS) Performance Test assesses, at the NDIS level, send and receive throughput of a network interface for the Microsoft® Windows® CE operating system (OS). You can also use the NDIS Performance Test to assess send and receive throughput of a network interface for a Windows–based desktop OS.

You can use the NDIS Performance Test to perform the following tasks:

  • Compare the send and receive throughput of a network interface at the NDIS level to the send and receive throughput at the Winsock level.

    For more information about the Winsock Performance Test, see Winsock Performance Test.

  • For a specified network interface, compare the send and receive throughput at the NDIS level in Windows CE to the throughput in a Windows-based desktop OS.
  • Find a performance bottleneck in a miniport driver or in NDIS.

The following table shows the hardware requirements for the NDIS Performance Test.

RequirementsDescription
Windows CE–based device with two network interfacesA Windows CE-based device with two network interfaces installed. One network interface is the interface for which performance is to be assessed. The second network interface is the interface over which the Windows CE–based device communicates with the development workstation running Microsoft Platform Builder and the Microsoft Windows CE 5.0 Test Kit (CETK).

To monitor traffic on the test network with network monitoring software, you can install a second network interface on the development workstation and then connect the second network interface to the test network. The NDIS Performance Test does not require a second network interface on the development workstation, but the second network interface can help you to troubleshoot problems that arise.

Supporting Windows-based desktop computer with one network interfaceA Windows–based desktop computer that functions as a supporting desktop computer. You can use the development workstation on which Platform Builder is installed as the supporting desktop computer.

On the supporting desktop computer, install a network interface that communicates with the tested network interface on the Windows CE–based device.

If the tested network interface for the Windows CE–based device is wireless, the network interface for the supporting desktop computer must be wireless. The wireless interfaces must associate with each other.

If the tested network interface for the Windows CE–based device is an RNDIS interface, the interface for the supporting desktop computer must be an RNDIS host.

If the tested network interface for the Windows CE–based device is an Ethernet interface, connect the Ethernet interface to a switch to which you also connect the Ethernet interface for the supporting desktop computer. If the tested interface is a 100-megabits per second (Mbps) adapter, use a 100-Mbps switch and use a 100-Mbps adapter for the supporting desktop computer.

If the supporting desktop computer is the development workstation on which the CETK runs, install two network interfaces on the development workstation. One network interface is the supporting network interface that communicates with the Windows CE–based device. The second network interface is the interface over which Platform Builder and the CETK communicate with the Windows CE–based device.

The following table shows the software requirements for the NDIS Performance Test on the Windows CE–based device.

RequirementsDescriptionPath
Tux.exeTux test harness, which is required for executing the test.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\<CPU>
Kato.dllKato logging engine, which is required for logging test data.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\<CPU>
Tooltalk.dllApplication required by Tux.exe and Kato.dll. Tooltalk.dll handles the transport between the target device and the development workstation.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\<CPU>
Ndp.dllMS_NDP protocol driver.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\<CPU>
Perf_ndis.dllTest .dll file.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\<CPU>

The following table shows the software requirements for the NDIS Performance Test on the supporting desktop computer.

RequirementDescriptionPath
Tux.exeTux test harness, which is required for executing the test.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\Desktop\Serial
Kato.dllKato logging engine, which is required for logging test data.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\Desktop\Serial
Tooltalk.dllApplication required by Tux.exe and Kato.dll. Tooltalk.dll handles the transport between the target device and the development workstation.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\Desktop\Serial
Perf_ndis.dllTest .dll file.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\Desktop
Ndp.pdbFile for MS_NDP protocol driver.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\Desktop
Ndp.sysFile for MS_NDP protocol driver.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\Desktop
Ndp.infFile for MS_NDP protocol driver.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\Desktop
Snetcfg.exeUtility to install or uninstall the MS_NDP protocol driver.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\Desktop
Msvcr71.dllC language run-time library.<Platform Builder installation path>\Cepb\Wcetk\Ddtk\Desktop
Note   When you run the NDIS Performance Test, the CETK temporarily copies files to the root directory of the Windows CE–based 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 storage memory or program memory available, the test cannot run.

See Also

CETK Tests | Running the NDIS Performance Test | Command-Line Parameters for the NDIS Performance Test


Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.


Show: