Miscellaneous DirectDraw Tests
This automated test verifies locking, overlays, blt, and memory management capabilities of the display driver.
The DirectDraw test is a subset of the DirectDraw tests from the Display Driver test kit. The test jobs exercise the video adapter and verify basic DirectDraw compatibility.
This topic is applicable to the following test jobs:
DirectDraw Tests
DirectDraw Tests (WoW64)
Test details
Associated requirement(s) |
Device.Graphics.AdapterRender.MinimumDirectXLevel See the device hardware requirements. |
Platforms |
Windows 7 (x64) |
Run time |
~5 minutes |
Running the test
Before you run the test, complete the test setup as described in the test requirements: Graphic Adapter or Chipset Testing Prerequisites.
Troubleshooting
For troubleshooting information, see Troubleshooting Device.Graphics Testing.
This test assumes that it has an almost complete control of the system. Background processes that steal focus or change modes can cause false failures.
Some of the blt tests respond to the PAUSE key, giving you more time to view the results. This can aid in debugging blt failures.
Most of the blt tests can also log additional information about mismatching pixels if you increase the logging level from 1 to 2. You will need to run the test outside of the Driver Test Manager (DTM) to do this. Launch the test outside of the DTM: fnddraw dx_wdk.pro
Select Set Logging from the Options menu. Use the logging dialog box to change the logging level.
More information
Most of the Microsoft® DirectDraw tests (including the DDraw AGP Memory test) are located in Fnddraw.exe. You can run Fnddraw.exe outside of the Windiows HCK Studio, and select initial tests. On the Tests menu, click Select Tests.
The test titles that are listed in the DCT shell do not directly match the test names in Fnddraw.exe. In fact, the names in the Windows HCK often refer to a group of Fnddraw tests. You can obtain the Fnddraw test case names from the Windows HCK log file.
You can pause many Fnddraw tests (especially blt-related tests) to give you time to visually analyze the blt results. Use the Pause key to pause and resume.
Use the Esc key to stop a test run. Be patient because some tests are more responsive than others.
Command syntax
| Command option | Description |
|---|---|
Fnddraw dd_wdk.pro -l"fnswtt.dll" -r -c -p"m%MONITOR%" /WTTLogDevStr:$logfile |
Runs both the DirectDraw Tests test job and the DirectDraw Tests (WoW64) test job. Replace the %MONITOR% parameter with a 1-based index that corresponds to the display that you are testing. |
File list
| File | Location |
|---|---|
Configdisplay.exe |
<[testbinroot]>\nttest\windowstest\tools\ |
Dd_wdk.pro |
<[testbinroot]>\nttest\windowstest\graphics\d3d\conf\pro |
Fnddraw.exe |
<[testbinroot]>\nttest\windowstest\graphics\d3d\conf\ |
Fnswtt.dll |
<[testbinroot]>\nttest\windowstest\tools\ |
TDRWatch.exe |
<[testbinroot]>\nttest\windowstest\graphics\ |
Note
You do not need Fnswtt.dll to run this test. It is used only for Windows HCK logging.