Prerequisites for the MS Bluetooth 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 MS Bluetooth Test.
| Requirements | Description |
|---|---|
A pair of Bluetooth devices, one installed on a Windows Embedded CE–based test server and the other installed on a Windows Embedded CE–based test client. |
The client and server are Windows Embedded CE–based devices and should be on a TCP/IP network and be able to communicate with one another. |
Note
The MS Bluetooth Test can also be run without a server. See Command Line Parameters for the MS Bluetooth Test for more details.
The following table show the software requirements for running the MS Bluetooth Test on the Windows Embedded CE–based test client.
| Requirements | Description |
|---|---|
Tux.exe |
Tux text harness, required for executing the test |
Kato.dll |
Kato logging engine, required for logging test data |
Btw22.dll |
Test .dll file for the test client |
The following table show the software requirements for running the MS Bluetooth Test on the Windows Embedded CE–based test server.
| Requirements | Description |
|---|---|
Kato.dll |
Kato logging engine, required for logging test data |
Netall.dll |
Module that provides functions that generate random numbers, output data, and parse command lines |
Btwsvr22.exe |
Test .exe file for the test server |
To run the MS Bluetooth Test, you must include Winsock and Bluetooth in the operating system (OS) design. Depending on the type of Bluetooth devices used, you may also need to include in the OS design items such as a USB driver.
Note
When you run the MS Bluetooth Test, the CETK temporarily copies files to the root directory of the target device. Before running the test, verify that there is at least 0.6 megabytes (MB) of free space in the root directory of the target device. If there is not sufficient space in the root directory of the target device, the test cannot run.