You should have a reasonable quality video and FM connections to the machine. Poor quality video feed might impact tests. If you are experiencing trouble running the tests, check the feed first.

See the Troubleshooting DTM Problems in the Getting Started Section of the Windows Logo Kit Help.

To run a single test in DTM Studio:

1. Open DTM Studio.
2. In DTM Studio, on the Main Menu, click Explorers, and click Job Explorer.
3. On the Job Explorer page, locate the job you want to run, right-click the Job, and click Schedule.
4. On the Schedule Jobs page, select the computer on which you want to run the test, make any other changes on each of the tabs on that page, and when finished, click Create Schedule in the Task Bar.
5. The test will execute shortly after clicking Create Schedule. Follow the prompts, and view results when the test has completed.

Running a Designed for Windows Logo Test at the Command Line

This section describes how to run a Designed for Windows Logo test at the command line. This involves running the following three executables:

• Tvwlpgraphicstests.exe
• Tvwlpsystemstests.exe
• Tvwlptunertests.exe

The command line syntax for tvwlpgraphicstests.exe is:

Usage: TvWLPGraphicsTests [/mobile ] TestName ["deviceid"]

TestName - must be one of the following test cases:

GRAPHICS-0043: Display driver supports minimum display timings and modes where applicable

GRAPHICS-0001: Display adapter supports output connectors with content protection features and provides control via PVP and COPP DDIs

GRAPHICS-0055: Display subsystem that supports Media Center functionality supports digital television (EIA

/CEA-861B) resolutions and timings over digital interfaces

TestName may also be 'display_tests' to run the graphics test cases

The command line syntax for tvwlpsystemstests.exe is:

Usage: TvWLPSystemsTests TestName

TestName - must be one of the following test cases:

SYSFUND-0065: System that ships a tuner meets CPU performance guidelines while recording programs

SYSFUND-0043: Systems implement a minimum of 2 user-accessible, fully powered USB 2.0 ports for desktop systems and 1 for mobile systems

SYSFUND-0064: System that ships a tuner enables DMA

The command line syntax for tvwlptunertests.exe is:

Usage: TvWLPTunerTests TestName ["deviceid"] LogoProgramId

LogoProgramID - must be one of the following:

BroadcastReceiver~ATSC

BroadcastReceiver~DVB-C

BroadcastReceiver~DVB-S

BroadcastReceiver~DVB-T

BroadcastReceiver~ISDB-T

BroadcastReceiver~ISDB-S

BroadcastReceiver~NTSC

BroadcastReceiver~NTSC_M_J

BroadcastReceiver~PAL

BroadcastReceiver~Proprietary

BroadcastReceiver~QAM

BroadcastReceiver~SECAM

TestName - must be one of the following test cases:

STREAM-0023: TV Tuner Analog Tests

STREAM-0057: TV tuner capture card supports automated capture graph building with Media Center video control

STREAM-0016: TV tuner detects signals from all input sources

STREAM-0014: Resources are not acquired until the Device Acquire state

STREAM-0015: TV tuner properly signals channel changes

STREAM-0021: Digital TV tuner uses the Broadcast Driver Architecture (BDA)

STREAM-0017: USB TV tuner has a unique serial number

STREAM-0060: PBDA Tuner Implements DRM

STREAM-0066: TV tuner can change channels 500 times

STREAM-0073: TV tuner can function after 5 reboots - *** This test should only be run from Microsoft Device Test Manager (DTM)

STREAM-0065: ALL TV Tuners must support at least 6 hours of uptime

C:\WD>

To run a Designed for Windows Logo test at the command line:

1. Create a working directory on the client/test machine. (for example c:\wd)
2. Copy the following files from DTM controller to the working directory:
   • tvwlpgraphicstests.exe
   • tvwlpsystemstests.exe
   • tvwlptunertests.exe
   • tvwlpvbimonitor.ax
   • tvwlpaudiomonitor.ax
   • tvwlpsourcefilter.ax
   • tvwlpmpeg2monitor.ax

   These files are typically located on the controller at the following default locations, and which you copy over, depend upon architecture of the test computer:

   • 32-Bit: [%SystemDrive%]\Program Files\Microsoft Driver Test Manager\Tests\x86fre\nttest\MultimediaTest\eHome\Tools\TvWLPTest
   • 64-Bit: [%SystemDrive%]\Program Files\Microsoft Driver Test Manager\Tests\amd64fre\nttest\Multimedia Test\eHome\Tools\TvWLPTest

3. Copy the following Logger binary from DTM controller to the working directory:
   • WTTLog.dll

   This DLL file is typically located on the controller at the default location of: [%SystemDrive%]\Program Files\Microsoft Driver Test Manager\Controller

4. Register TVWLP monitor filters on the test machine by running the following commands (using the example working directory of C:\WD:
   • regsvr32 C:\WD\TvWLPVBIMonitor.ax
   • regsvr32 C:\WD\TvWLPAudioMonitor.ax
   • regsvr32 C:\WD\TvWLPSourceFilter.ax
   • regsvr32 C:\WD\TvWLPMpeg2Monitor.ax

5. For each command, click OK on the RegSvr32 confirmation dialog box.
6. Launch a command window with admin privileges, and cd to your working directory created in Step 1 above.
7. Type the name of the executable containing the test you want to run, for example, tvwlptunertests.exe, followed by a space.
8. Type the subtest, for example STREAM-0023 followed by a space.
9. Get the Device Instance Path from Device Manager (in Control Panel) by doing the following:

   a. Open the Control Panel.

   b. Select Device Manager in the Control Panel.

   c. Select the device (usually under Sound, video…) and right-click for Properties.

   d. Click the Details tab.

   e. Select Device Instance Path in the drop-down list box.

   f. Select the Value, right-click, and click Copy.

10. In the command window, paste the copied Device Instance Path string between double quotes after the name of the test executable followed by a space (“tvwlptunertests.exe “ in this example, no double quotes; added to show space). Enter the LogoProgramID (BroadcastReceiver~NTSC in this example) specific to your test and platform, and press the Enter key.

    

11. On the Please Provide Tuning Parameters page (specific to the test and platform), enter the correct information, and click OK.

    

12. You should see a success notification, and if you don’t, please see the Troubleshooting section.

    

The following table describes the requirements that you can test individually.

Table 5: Test Requirements