Command Line Parameters for the Graphics Device Interface 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 Graphics Device Interface (GDI) Test executes the tux –o –d gdiapi.dll command line on default execution. You can modify the test by editing the command line. See Editing the Command-Line for a Test.
The following table shows the command line parameters for the Graphics Device Interface Test.
| Command line parameter | Description |
|---|---|
-c "/?" |
Displays information about command-line options for the GDI Test. |
-c "/OutputBitmaps" |
Instructs the GDI Test to save a bitmap image for each failure. The .bmp file can assist you in debugging the problem that caused the unexpected output. |
-c "/BitmapDestination path" |
Specifies where to save the bitmap image for a failure. |
-c "/NoVerify" |
Instructs the GDI Test to not use driver verification. By default, the GDI Test uses driver verification. |
-c "/ForceVerify" |
Forces the GDI Test to perform verification. If you specify this option, the GDI Test performs verification even if there is little memory available. If the Ddi_test.dll module is not available, test cases fail. |
-c "/ManualVerify" |
Instructs the GDI Test to support manual verification. During manual verification, to step through test cases, press the left SHIFT key. |
-c "/Monitor n" |
Specifies the screen to run the GDI Test on. The parameter n is an integer from 1 to 4. This option applies only to the Win_Primary surface and only to a Windows Embedded CE–based device with multiple screens. If you specify this option and the option does not apply, the GDI Test ignores the option. |
-c "/MonitorSpread" |
Runs the GDI Test spread across multiple screens. This option applies only to the Win_Primary surface and only to a Windows Embedded CE–based device with multiple screens. If you specify this option and the option does not apply, the GDI Test ignores the option. |
-c "/Width size /Height size" |
Specifies the width and height of the surface that the GDI Test uses. Minimum width is 176. Minimum height is 176. Width and height must each be a multiple of 2. |
-c "/Surface All" |
Instructs the GDI Test to cycle through all known surfaces. This cycling can require significant time. The cycling requires significant storage space on the target device because the Windows Embedded CE 6.0 Test Kit (CETK) stores test results in a file on the target device. |
-c "/Surface surfacename" |
Specifies a type of surface to test. For surfacename, use one of the following values:
|
-c "/SetDisplay driver.dll" |
Runs the GDI Test on a secondary display driver. |
-c "/AlwaysVerify" |
Forces a driver verification against the test display driver for every operation. This option is time-consuming and may significantly increase the overall test duration. |
-c "/NoRotate" |
Disables dynamic screen rotation during the GDI Test, if such is supported by the display driver. |
-c "/NoResize" |
Disables dynamic resolution resize, if such is supported by the display driver. |