Preparing Your System for Logo System Testing

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.

Before running system tests, you must configure the test system and install the operating system. This section summarizes the related procedures.

For a complete list of required hardware and software requirements, see System Requirements for the Targeted Logo System.

Many of the tests in DTM require a test system to restart (often more than once) to complete a test run. The test description and the running instructions specify whether a test requires a system restart. Although these tests programmatically restart the test system, you must manually log on to the test system after each system restart so that the test run can resume. You can avoid this requirement by enabling autologon functionality on the test system. For more information about autologon, see How to turn on automatic logon in Windows XP.

To configure the test system

When you use DTM for system testing, you must complete the following system configuration tasks to prepare the system for logo system testing.

Important   Before you begin testing, make sure that you enable all of the devices in the test system and load all of the related drivers.

To assemble the test environment for DTM system testing, do the following:

  1. On the test system, install a network adapter.

  2. Connect the test system to a network hub.

  3. Connect the additional system to the network hub.

  4. Set the test system BIOS to support the S3 sleep state.

  5. On the test system, install the appropriate Microsoft Windows operating system.

  6. During this installation of the operating system, delete any existing partitions, and create a boot partition. Note, for Business Logo see note at bottom of page.

  7. During installation of the operating system, you must also add the test system to a domain or workgroup.

  8. Install any manufacturer-supplied drivers that devices in the test system require.

  9. On the test system, install the DTM client software from the DTM controller.

  10. On the additional system, install the appropriate Windows operating system.

  11. During installation of the operating system, add the additional system to the same domain or workgroup that the test system belongs to.

  12. Install one serial loopback connector on the serial port of the test system.

To configure the computers in the test environment for DTM system testing, do the following:

  1. Use the following procedure to configure the power options on the test system:

    • Click Start, click Control Panel, and then double-click Power Options.
    • In the Power Options Properties dialog box, click the Power Schemes tab and do the following:
      • In the Turn off monitor list, click Never.
      • In the System standby list, click Never.
      • If there is a System hibernates list, click Never.
    • In the Power Options Properties dialog box, click the Hibernate tab, and clear the Enable hibernation check box.
  2. Repeat step 1 on the additional system.

  3. Insert a valid data CD into the CD or DVD drive of the test system.

    Important   The data CD must remain in the test system's disk drive while you complete testing.

Note  Additional installation procedures for the operating system are required to test for business level logos in order to pass BitLocker partition settings.

To partition a drive with no operating system for BitLocker

Windows Vista

  1. Start the computer from the nextref_vista product DVD.

  2. In the initial Install Windows screen, choose your Installation language, Time and currency format, and Keyboard layout, and then click Next.

  3. In the next Install Windows screen, click System Recovery Options, located in the lower-left of the screen.

  4. In the System Recovery Options dialog box, choose your keyboard layout, and click Next.

  5. In the next System Recovery Options dialog box, make sure no operating system is selected. To do this, click in the empty area of the Operating System list, below any listed entries, and then click Next.

  6. In the next System Recovery Options dialog box, click Command Prompt.

  7. Use the Diskpart application to create the partition for the operating system volume. At the command prompt, type diskpart, and then press ENTER.

  8. Type select disk 0.

  9. Type clean to erase the existing partition table.

  10. Type create partition primary size=1500 to set the partition you are creating as a primary-type partition.

  11. Type assign letter=S to give this partition the S: designator.

  12. Type active to set the new partition as the active partition.

  13. Type create partition primary to create another primary-type partition. You will install Windows on this larger partition.

  14. Type assign letter=C to give this partition the C: designator.

  15. Type list volume to display all the volumes on this disk. You will see a listing of each volume, volume numbers, letters, labels, file systems, types, sizes, status, and information. Make sure that you have two volumes that are formatted as NTFS, and that you know the labels for both volumes.

  16. Type exit to close the diskpart application.

  17. Type format c: /y /q /fs:NTFS to format the C volume.

  18. Type format s: /y /q /fs:NTFS to format the S volume.

  19. Type exit to close the command prompt.

  20. In the System Recovery Options window, use the close window icon in the upper-right (or press ALT+F4) to close the window to return to the main installation screen.

    Important  Make sure that you do not shut down or restart the computer.

  21. Click Install now and proceed with the nextref_vista installation process. Install nextref_vista on the larger partition, C: (the operating system volume).

Windows 7

A separate, active system partition will automatically be created when you install Windows 7 to a drive without any partitions.

After you have configured your test systems, you can run the logo tests for systems testing.

 

 

Build date: 9/14/2012