Generic Logo Submission exercise

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

The information in this topic provides a general overview of the logo testing and submission processes. The following instructions assume that you have successfully installed DTM controller, DTM Studio, and DTM client. If you have not already installed these three DTM components, refer to the Install.htm file on your installation medium for installation instructions. For more information about how to set up DTM, see the Setting Up DTM topic.

Important   If you rerun a job, switch to the Device Console window and repeat the tasks in Step 8 in the following procedure.

Note  The monitor test was selected for this exercise because it uses drivers that are shipped with Windows and thus provides a simple scenario.

For this exercise, the computer on which DTM client is installed is referred to as client computer.

To configure a client computer for logo testing, run tests, and then create a submission package

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

  1. Open DTM Studio and switch to the Job Monitor window.

    You can also open a new Job Monitor window by clicking Explorers, and then clicking Job Monitor.

  2. In the Machine Pool pane, click Default Pool, and then locate the client computer in the Machines pane.

    Note   The status column for the client computer shows that it is in the Manual state. This is the default state for any client computer that has been automatically added to the default pool as a result of installing DTM client.

  3. Create a new machine pool.

    1. In the Machine Pool pane, right-click the root pool (indicated by the '$' symbol), and then click Add Machine Pool.

    2. Type the name Test Pool, and then click OK.

      Your new machine pool, Test Pool, now appears in the Machine Pool console tree.

  4. Move the client computer to the new machine pool.

    1. Drag the client computer from the Machines pane and drop it onto Test Pool in the Machine Pool pane.

    2. Click Test Pool to make sure that the client computer now appears in the Machines pane for that machine pool.

      If you do not see your client computer in the Machines pane, click Refresh or press F5.

  5. Change the status of the client computer to the Ready state.

    1. Right-click the client computer, and then click Change Status.

    2. Select Reset.

    3. The Status column for the client computer should show that the client is in the Reset state.

    4. Wait a few seconds, and then click Refresh or press F5. The client computer's status column should now show the Ready state.

      Note   The "Preparing for the Xxx Test" topics will tell you whether or not you must apply a dimension to the machine pool before running certain jobs. If the job you are about to schedule and run requires a dimension to be applied, you must apply the dimension at this stage in the procedure. Refer to the Configuring the Test Environment topic for instructions about how to apply a dimension to a machine pool.

  6. Next, select a logo program.

    Important  If you have an INF file or a driver for your device, make sure that you copy the INF file or driver to the hard drive of the client computer before you begin the logo submission process. Make a note of the location of the file or driver and browse to it in Step 7. If the INF file or driver is on a removable storage device, like a floppy disk or a flash drive, and this storage device is removed before you attempt to create a submission package, the process will fail and you will receive an error message.

    1. Click Explorers, and then select Device Console.

    2. When Device Console finishes loading, confirm that Test Pool is selected in the Machine Pool drop-down list box.

      Note   If you are testing a device that is, by default, hidden by Device Manager, you must first select the Show Hidden Devices check box before you complete the next step.

    3. From the Submission drop-down list box, select <New Submission>.

    4. In the Create New Submission dialog box, select your operating system, and then click Next.

    5. Click Device Submission, and then click Next.

    6. Click Display > Monitors > CRT, and then click Next.

      If you are using a portable computer, click Display > Monitors > LCD, and then click Next.

    7. Select a submission level (Premium or Basic), and then click Next.

    8. Provide a name for your submission: Type Display submission.

    9. In the Machine Pool pane, click Test Pool, and then click Next.

      Note  You select Test Pool because it contains the client computer.

  7. Select a driver for your monitor.

    1. If you are not providing an INF or Driver Package, then select the I am not providing an INF or Driver Package check box, and then click Next.

      Note   If you are testing a para-virtualization driver, you must also select the Para-virtualization Driver check box, and then click Next.

      Para-virtualization drivers are device drivers present in a virtual machine instance of the Windows operating system that represent hardware and functionality similar to, but not necessarily identical with, the underlying physical hardware used by the system virtualization software layer.

      For example, the physical network interface adapter installed in the system can be either presented or abstracted to the virtual instance(s) of Windows. This is achieved using a para-virtualization driver that emulates a network adapter, but not necessarily the same network adapter as the actual physical device.

    2. Expand the Test Pool node, and then expand Monitors to select the device to be tested.

    3. Select the check box next to your monitor, and then click Next.

    4. If you see the message "ERROR: No Submission Drivers specified," click OK.

    5. In the summary that shows the submission name, machine pool name, and your monitor's identifier, click Finish.

  8. Select the job you are going to run.

    1. In the Available Jobs pane in the Device Console window expand the CRT or the LCD node.

    2. Select the check box for the EDID 1.3 and DDC (32-bit) job.

    3. At the bottom-left of the Device Console window, click Add Selected.

      Note   You might be required to edit some job parameters for some of the selected jobs before they can be scheduled against the machine pool for logo-related testing. The "Running the Xxx Tests" topics will tell you whether or not you must edit the required parameters. Refer to the Running the Logo Tests topic for instructions about how to edit parameters for a logo job.

    4. Click Schedule Jobs.

      Note  You can switch to the Job Monitor window, wait about 5 seconds, and then click Refresh or press F5. The Job Execution Status pane displays the job that is currently running. After a few moments, your monitor should start responding to the scheduled EDID 1.3 and DDC (32bit) job.

  9. Create a submission package after the job is completed.

    1. Switch to the Device Console window.

    2. In the Available Devices pane, right-click the submission name, which in our case is Display Submission, and click Create Submission Package.

      Important  You must make sure that all the computers that were used to run the logo tests are present in the machine pool before you select Create Submission Package. If any of these computers is missing from the machine pool when you try to create a submission package, a foreign key violation error message will appear. It is recommended that you leave the relevant computers in the machine pool until you have completed the submission package.

      And also, you can right-click anywhere in the Available Devices pane to create a submission package. The resulting submission package files will contain the same submission information.

    3. Save the submission package.

      Note   It will typically take a few minutes for the submission package file to be created. It is normal during this time for DTM Studio to appear as if it has stopped responding.

    Note  You can now upload your submission package to the Winqual team for review. For information about how to submit a package, refer to the Winqual Web site.

 

 

Build date: 9/14/2012