Running the Two-Card in Two Machines NDIS Test for Media Sense (Windows CE 5.0)
To test an NDIS miniport driver, run all the test cases provided in the NDIS Two Card Network Test or Two Card in Two Machines Test for Media Sense. You must run this test for Wireless LAN NICs to verify if your miniport driver supports media sense.
Note Skip this test, if your test NIC is an RNDIS function driver or a Wired LAN NIC and does not support media sense.
Setup and configuration for this test is same as Two-Card Network Card Miniport Driver Test and Two Card in Two Machines Test. Currently, you cannot run this test using the CETK. You must use Microsoft Windows CE Platform Builder because the test requires user intervention.
To run the Two Card test for Media Sense in Platform Builder
Open the CE Target Control Window by choosing the Target -> Target Control menu option. For more information about the Target Control, see Target Control Debugging Commands.
Run one of the following commands after the setup is ready.
Two Card Test commands
s tux -o -d ndt_2cm.dll -c "-t <Test NIC instance> -s <Support NIC instance>"<Test NIC instance> is the name of instance of the test NIC on the Windows CE-based device.
<Support NIC instance> is the name of instance of support NIC on same Windows CE-based device.
For example,
s tux -o -d ndt_2cm.dll -c "-t PCI\RTL81391 -s PCI\RTL81392"Two Card Test in Two Machines
s ndtserver s tux -o -d ndt_2cm.dll -c "-t <Test NIC instance> -s <Support NIC instance>@<IP Address>.<Test NIC instance> is the name of instance of the test NIC on the Windows CE-based device.
<Support NIC instance> is the name of instance of support NIC on the support Windows CE-based device.
<IP Address> is the IP address of the Windows CE-based device with the support card.
For example,
s tux -o -d ndt_2cm.dll -c "-t CISCO1 -s CISCO1@11.22.33.44For a Wireless LAN NIC, if the test fails on data transfer, re-run the test with the -msewait nn switch, where nn is the number of minutes the test should wait for the test NIC to reconnect to the Access Point. The default wait is 1 minute.
For example,
s tux -o -d ndt_2cm.dll -c "-t CISCO1 -s CISCO1@11.22.33.44 -msewait 10
After running the command verify the result in the Debug window.
If the Debug Window displays Disconnect, unplug the network cable from the test NIC on the Windows CE-based device. If you are testing a Wireless LAN NIC, power down the Access Point to which the test card and the support card are connected.
When the Debug Window displays Connect, plug in the network cable to the test NIC or power up the Access Point in case of a Wireless LAN NIC.
See Also
How to Develop a Connectionless NDIS Miniport Driver | How to Test an NDIS Miniport Driver
Send Feedback on this topic to the authors