Proposed Quality Acceptance Tests for Windows CE Network Interface Cards

re: Proposed Quality Acceptance Tests for Windows CE Network Interface Cards

Freddy — Wed, 05 Dec 2007 04:10:07 GMT

I tried the Two-Card Network Card Miniport Driver Test with two WM 6 devices and I got the following error. What is the error?

26d3cf3a: ndt_2c Msg: Querying if test miniport is wireless

26d3cf3a: ndt_2c Msg: Miniport SDIO86861 is ** Wireless-LAN **

26d3cf3a: ndt_2c ERROR: NDTStartup for 'SDIO86861@192.168.1.106' failed with hr=0x80072751

26d3cf3a: ndt_2c ERROR: NDTBindProtocol for 'SDIO86861@192.168.1.106' failed with hr=0x8007276d

"\ndt_2c.dll" returned SPR_FAIL while handling the SPM_SHELL_INFO message.

This DLL has been unloaded as requested.

Freddy

Hi Freddy,

This means that your test device cannot see the support card. The ndis tests unbind tcpip before they begin, so that might be why. If you are using just two cards to run the test (one on the test machine and one on the support machine - no extra support cards to set up a backchannel), then try running the test with -c"-t <TESTCARD> -s <SUPPORTCARD>@<IPADDRESS> -nounbind"

re: Proposed Quality Acceptance Tests for Windows CE Network Interface Cards

Jonny — Mon, 14 Jul 2008 12:55:15 GMT

Hi, now i encouter a problem about wi-fi test on ce6.0, i follow the settings of msdn, but i can't find dummywzcsvc.cab, or this file isn't essential ?

when i run the one-wlan-card test,

and the command line is "tux –o –d ndt_1c_wlan –c"-t mycard -nounbind" "

The first case is fail , test log is

"063d028a: ndt_1c_wlan Msg: Variation 1: Testing Association with ssid NDTEST_WEP_AP1

063d028a: ndt_1c_wlan ERROR: Failed to receive NDIS_STATUS_MEDIA_CONNECT Error : 0x103

063d028a: ndt_1c_wlan Msg: Miniport adapter mycard failed to connect to NDTEST_WEP_AP1"

If there's any suggestion, please help!!!

re: Proposed Quality Acceptance Tests for Windows CE Network Interface Cards

Larry Zhang — Tue, 22 Jul 2008 20:43:58 GMT

At this moment, we don’t require OEMs to run the ndt_1c_wlan/ndt_2c_wlan tests, so you should just skip these tests for now

Author Larry Zhang

re: Proposed Quality Acceptance Tests for Windows CE Network Interface Cards

alon — Sun, 07 Sep 2008 18:30:05 GMT

hi, i tried to run the two card test with the

command tux -o -d ndt_2c -c"-t SDIO86881 -s CF8385PN1@169.254.2.2 -nounbind"

and i get the following messege:

8258f6fe: ndt_2c ERROR: Failed register the NDT test protocol driver (code 2)

8258f6fe: ndt_2c ERROR: NDTStartup for 'SDIO86881' failed with hr=0x80070002

8258f6fe: ndt_2c ERROR: Failed close the NDT test protocol driver (code 6)

8258f6fe: ndt_2c ERROR: Failed deregister the NDT test protocol driver (code 1168)

"\ndt_2c.dll" returned SPR_FAIL while handling the SPM_SHELL_INFO message.

This DLL has been unloaded as requested.

i think i have a problem with setting up the connection

can you help me figure out the diagram on the manual?

re: Proposed Quality Acceptance Tests for Windows CE Network Interface Cards

Reshmi Nair — Wed, 06 May 2009 22:57:48 GMT

I tried running the Ndis Performance test for a wifi driver and got the following results in the desktop

tux -o -d perf_ndis -c "-ndisd -nounbind \Device\{B8C4C71C-0CBD-413C-9ACB-B33B08039BCA}"

ShellProc(SPM_LOAD_DLL, ...) called

Command Line: "-ndisd -nounbind \Device\{B8C4C71C-0CBD-413C-9ACB-B33B08039BCA}".

ShellProc(SPM_REGISTER, ...) called

ShellProc(SPM_START_SCRIPT, ...) called

ShellProc(SPM_BEGIN_GROUP, ...) called

ShellProc(SPM_BEGIN_TEST, ...) called

perf_ndis Msg: Waiting for new client connection....

perf_ndis Msg: Offer timeout so return to wait loop

perf_ndis Msg: Accepted client: 1 connection

perf_ndis Msg: Daemon: Timeout when wait for 'PARAMS' packet

ShellProc(SPM_END_TEST, ...) called

ShellProc(SPM_END_GROUP, ...) called

ShellProc(SPM_UNLOAD_DLL, ...) called

and the following in the final result logs:

*** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv

*** TEST STARTING

***

*** Test Name: Test 1

*** Test ID: 1001

*** Library Path: \perf_ndis.dll

*** Command Line: -s TESTCARD -mode send

*** Random Seed: 16563

*** Thread Count: 0

*** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv

BEGIN TEST: " Test 1", Threads=0, Seed=16563

perf_ndis Wrn: Timeout on 'OFFER' packet

END TEST: " Test 1", PASSED, Time=18.279

*** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

*** TEST COMPLETED

***

*** Test Name: Test 1

*** Test ID: 1001

*** Library Path: \perf_ndis.dll

*** Command Line: -s TESTCARD -mode send

*** Result: Passed

*** Random Seed: 16563

*** Thread Count: 1

*** Execution Time: 0:00:18.279

*** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

</TESTCASE RESULT="PASSED">

Even though the results show passed I think there is something wrong because I do not see any numbers to indicate the performance of the driver. Also the logs show some warnings which I am sure indicate troub