Share via

Preparing for Display Adapter and Chipset Testing

  • Article

Before you run the Display Adapter and Chipset tests on a test computer or computers, you must install and configure the computer hardware, choose the target Microsoft Windows operating system, and install and configure Driver Test Manager (DTM). This section summarizes the requirements and procedures for display adapter and chipset testing. For information about how to install and configure DTM, see Driver Test Manager.

Test System Configuration

Use the following procedure to configure the test computers to test display adapters for your target operating system.

  1. Install the test devices on two (or more) test computers that are configured differently from each other. For more information about minimum system requirements, see Display Adapter and Chipset Testing.

  2. Install the multi-sync display data channel standard, level 2B (DDC2B)-capable monitor with EDID 1.3 support on the test computers.

Note The secondary head of a multiple headed Display Adapter/Chipset must be connected to a monitor and enabled before you start testing. Not all devices that are able to support multiple heads have to be enabled, but at least one device for each ASIC family that is listed in the INF file must be enabled. To test outside of the submission process, make sure that all secondary heads are connected to a monitor and enabled; otherwise, when a test is selected for the unattached secondary head, it will run on the primary head.

  1. On each test computer, install the target Microsoft Windows operating system.

Note If the target operating system is Microsoft Windows XP, you must also install Microsoft Windows Media Player 10.

  1. Install the test device driver on each computer.

  2. On each test computer, install the DTM client. For information, see Driver Test Manager.

  3. On the DTM Controller, edit the Displaygroups.xml file to match the agreed-upon ASIC family breakout. The file is located in <InstallationDrive>\Program Files\Microsoft Driver Test Manager\Tests\x86fre\nttest\windowstest\graphics

  4. After you have installed the DTM client software, copy the updated DisplayGroups.xml file to the <InstallationDrive>\Program Files\Microsoft Driver Test Manager\client folder on the client computer, and restart the computer.

  5. Disable any active applications that, by default, are the top window. Examples of such applications are pop-up balloons or on-screen keyboards for Tablet PCs.

The Display Adapter/Chipset logo program has manual logo jobs, and you must configure a client computer to accept these jobs. For any jobs with (Manual) in the title, you must pick a test machine in the machine pool that meets all the requirements to run the manual tests. Make sure that this machine can run all manual tests that are required for a logo. Depending on the type of submission, you might need the following features or configurations:

  • TV-out support
  • Multimon
  • Hot plug detection support

For additional requirements for each test, see the individual test descriptions.

Because the manual jobs require user intervention, you should schedule them together, either before or after the automated jobs are run. This helps to make sure that the manual jobs are sent to the specified client computer instead of having them mixed in with the automated jobs.

For the manual jobs to run, apply the following constraints to the machine that you intend to run the jobs on:

  • Display\PrimaryMachine = True

To set this dimension for the manual jobs, you can do one of the following:

  • From a Command Prompt window, type WTTCmd.exe /ConfigReg /Add /Value:Display\PrimaryMachine /Data:"True" and then press Enter.
  • Complete this procedure:
    1. Open DTM Studio.
    2. In the Job Monitor window, right-click the appropriate machine in the pool, and then click Edit .
    3. Add the "Display\PrimaryMachine" dimension to the list.
    4. Click Save.

Before you start a display test, close any active application (including Windows Explorer and Microsoft Internet Explorer) on the test computer.

Send feedback on this topic
Built on December 10, 2009