Command Line Parameters for the MS Bluetooth Test (Windows Embedded CE 6.0)
1/6/2010
The MS Bluetooth Test executes the unedited command line tux –o –d btw22 on default execution. This command line skips all server-related and connection-related test cases.
To run the MS Bluetooth Test with a server, the client and the server must be Windows Embedded CE–based devices that are able to communicate using TCP/IP. You must edit the command line for the client by specifying the host name or IP address of the server. The following procedure shows the steps you must take to run the MS Bluetooth Test with a server.
Procedures
To run the MS Bluetooth Test with a server
Copy the Btwsvr22.exe, Netall.dll, and Kato.dll files to the Windows directory on the Windows Embedded CE-based device that you want to use as a server. Alternatively, if Platform Builder is connected to the Windows Embedded CE–based device that you want to use as server, copy the Btwsvr22.exe, Netall.dll, **and Kato.dll files to the release directory.
You can find the Btwsvr22.exe, Netall.dll**, and Kato.dll files in the Cepb\Wcetk\Ddtk\%_TGTCPU% directory in the directory where you installed Platform Builder.
On the Windows Embedded CE–based server, run the Btwsvr22.exe file.
If Btwsvr22.exe fails to run, verify that you copied the Netall.dll, **, and Kato.dll files to the correct location.
In the Windows Embedded CE 6.0 Test Kit (CETK) window, right-click on MS Bluetooth Test, and then choose Edit Command Line.
Modify the command line to pass to the test client the host name or IP address of the Windows Embedded CE–based device running Btwsvr22.exe.
For example, if the Windows Embedded CE–based device running Btwsvr22.exe has a host name of Cetest1 and an IP address of 4.3.2.1, type -c "cetest1" or -c "4.3.2.1" at the end of the existing tux -o -d btw22 command line.
From the Windows Embedded CE 6.0 Test Kit (CETK) window, start the MS Bluetooth test.