DirectDraw Test (Windows CE 5.0)
The Microsoft® DirectDraw® Test analyzes basic DirectDraw functionality including block image transfers (blits), scaling, color keying, color filling, flipping, and overlaying. This test runs only if the display hardware on the target device supports DirectDraw. The test does not cover multiple pixel formats or changes of display mode.
The following table shows the hardware requirements for the DirectDraw Test.
| Requirements | Description |
|---|---|
| Video Card | A video card that supports DirectDraw. |
The following table shows the software requirements for the DirectDraw Test.
| 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. |
| DDrawTK.dll | Test .dll file. |
Before you run the DirectDraw Test, you must include Microsoft DirectX® and DirectDraw in your OS design. The SYSGEN_DDRAW Sysgen variable adds the required functionality to your OS design.
Note When you run the DirectDraw Test, the CETK temporarily copies files to the root directory of the target device. While the test runs, the test dynamically consumes program memory on the target device. Before running the test, verify that there is at least 0.9 megabytes (MB) of free storage memory on the target device. Also verify that there is at least 1.5 MB of free program memory on the target device. If there is not sufficient space in the root directory of the target device or there is not sufficient program memory, the test cannot run.
See Also
Modifying the DirectDraw Test | Troubleshooting: DirectDraw Test Failed
Send Feedback on this topic to the authors