Command-Line Parameters for the Direct3D Mobile Driver Verification Test (Windows CE 5.0)
The Direct3D Mobile Driver Verification Test runs the tux –o –d D3DM_DriverVerif.dllcommand line by default. You can modify the behavior of the Direct3D Mobile Driver Verification Test by editing the command line for the test. To specify one or more of the following optional command-line parameters for this test, use the –c command-line parameter. The -c parameter forces Tux to pass the specified string into the test module. For more information about how to edit the command line for a test, see Editing the Command Line for a Test.
The following table shows a command-line parameter for the Direct3D Mobile Driver Verification Test.
| Command-line parameter | Description |
|---|---|
|
Validates a locally-hooked driver instead of the default system driver. The Direct3D Mobile Driver Verification Test uses the RegisterSoftwareDevice function before running a test case, and uses D3DMADAPTER_REGISTERED_DEVICE at the time that the CreateDevice function is called. |
See Also
Direct3D Mobile Driver Verification Test | Test Cases for the Direct3D Mobile Driver Verification Test
Send Feedback on this topic to the authors