Prerequisites for the Graphics Device Interface Printer Test
.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.")
9/8/2008
This document describes the prerequisites for the Graphics Device Interface (GDI) Test.
The GDI Printer Test requires that the Windows Embedded CE-based device be equipped with a parallel, serial, IR, USB, or network connection to a printer. In addition, the operating system needs a printer driver, printer transport, and printing support in the GDI middleware. For example, to run this on a parallel printer using the shipped PCL printer driver, you would need the parallel port driver (SYSGEN_PARALLEL), the PCL printer driver (SYSGEN_PCL), and the OS printing component (SYSGEN_PRINTING). To use the test's ability to draw the printed page to the primary, you need a headed image with a shell available.
The following tables show the software required for the GDI Printing Test.
| Requirement | Description |
|---|---|
Tux.exe |
Test harness, required for executing the test |
Kato.dll |
Logging engine, required for logging the test data |
GDIPrint.dll |
Library containing the test code, loaded by the Tux test harness |
Observação
When you run the Graphics Device Interface Performance Test, the Windows Embedded CE 6.0 Test Kit (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.