Share via


IR Port Test (Winsock 2.0)

The IR Port Test (Winsock 2.0) is designed to test the functionality a driver for an infrared (IR) device using Winsock 2.0. The test is a client-server test that requires a pair of IR devices.

The following table shows the hardware requirements for the IR Port Test (Winsock 2.0).

Requirements Description
Two installed IR devices You must install one IR device on a test server and another IR device on a test client. You should position the IR devices in close proximity to one another. You should point each IR device directly at the other IR device.

You can run the IR Port Test (Winsock 2.0) using either IR or a TCP/IP network as a control channel. If you use a TCP/IP network, the client and server must be on the TCP/IP network and must be able to communicate with each other.

Note   You can run the IR Port Test (Winsock 2.0) without a server.

The following table shows the software requirements for the IR Port Test (Winsock 2.0).

Requirements Description
Tux.exe Tux test harness, which is required for executing the test.
Kato.dll Kato logging engine, which is required for logging test data.
Tooltalk.dll Application required by Tux.exe and Kato.dll. Handles the transport between the target device and the development workstation.
Irapi22.dll Test .dll file.
Irapisrv22.exe Test .exe file.

To run the IR Port Test (Winsock 2.0), you must include support for Winsock 2.0 and IR in your Microsoft® Windows® CE OS image.

Note   When you run the IR Port Test (Winsock 2.0), the CETK temporarily copies files to the root directory of the target device. Before running the test, verify that there is at least 0.4 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.

See Also

Running the IR Port Test (Winsock 2.0)

 Last updated on Friday, October 08, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.