Prerequisites for the Graphics Device Interface Test (Windows Embedded CE 6.0)
1/6/2010
The GDI Test requires that the Windows Embedded CE–based device be equipped with display hardware that corresponds to the driver being tested.
If you run the test and enable manual verification, the target device must be equipped with a display that you can view. In addition, the target device must have a keyboard, mouse, touch screen, or other hardware for data input. By default, manual verification is disabled.
The following tables show the software requirements for the GDI Test.
| Requirements | Description |
|---|---|
Tux.exe |
Test harness, required for executing the test |
Kato.dll |
Logging engine, required for logging the test data |
Gdiapi.dll |
Main test library |
Ddi_test.dll |
Graphics Primitive Engine (GPE)–based display driver that the GDI API uses to verify the success of each test case. If Ddi_test.dll is unavailable, run the test with manual verification. |
This test requires that you include a graphic display driver in the operating system design that is appropriate for the display hardware on your target device.
Note
When you run the GDI Test, the Windows Embedded CE 6.0 Test Kit (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 3.7 megabytes (MB) of free storage memory on the target device. Also verify that there is at least 2.0 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.