Share via

Running the Adapter or Controller Tests

  • Article

After you prepare a test machine for adapter or controller testing, you can run the logo tests from the DTM Studio.

For more information, see Running the Logo Tests.

Submission Configuration

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. Add the machine to a machine pool.

    Note  For more information, see Grouping Client Computers into Machine Pools.

  2. Click Explorers, and then click Device Console.

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

  4. Type a name for your submission, select the machine pool that you created earlier, and then click Next.

  5. Select Storage > Adapter or Controller when you are prompted for the logo program, and then click Next.

  6. If you are testing a driver, browse to the driver, and then load that driver when you are prompted. Otherwise, select the I am not providing an INF or Driver Package check box, and then click Next.

  7. If you selected the I am not providing an INF or driver package check box, select your test device from the list when you are prompted, and then click Next.

    The Create New Submission dialog box appears.

  8. From the Bus type connecting adapter to storage list, select the appropriate bus type for your adapter, and then select the check boxes for any additional features that your adapter implements. For more information about features, see the following "Submission Features" section.

    Note  For SATA Controllers in PATA emulation mode, select ATA as the bus type.

  9. Click Next, and then click Finish to complete the submission configuration.

Many of the tests in the Microsoft Windows Driver Kit (WDK) require that a test system restart (often more than once) to complete a test run. To enable this restart, DTM configures the client to automatically log on by using the DTMLLUAdminUser account. This configuration occurs when you first create your submission. DTM also turns off workstation locking and prevents the machine from automatically hibernating or sleeping. If you want to open a remote desktop connection to the client after you start a submission, use the DTMLLUAdminUser account.

Submission Features

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.

  • Implements Non-Volatile cache: NV Cache is a storage controller caching feature. Select this feature if your device responds to NV Cache Management operations. For more information, see IOCTL_SCSI_MINIPORT_NVCACHE in the MSDN Library.
  • Implements RAID: Redundant Array of Inexpensive Disks (RAID) is a feature that enables you to combine multiple drives into arrays for increased reliability (redundancy) or performance (striping). Select this feature if your adapter supports any of the common RAID levels (0, 1, 5, 10).
  • Implements VDS Provider: Virtual Disk Service (VDS) is a service that unifies and extends existing storage capabilities under a single API as an end-to-end solution for managed storage hardware and disks. Select this feature if your adapter implements the VDS API as a hardware provider. For more information, see About VDS in the MSDN Library.

Scheduling Tests

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.

When a yellow exclamation mark (!) appears next to a job in the DTM, the DTM requires more information. You must enter that information in a dialog box when you schedule the job by right-clicking the job and clicking Add Information.

  • All iSCSI tests require that you configure communication between the HBA (initiator) and the iSCSI targets.

  • The Separated Cache Solution Evaluation Test requires that you direct the logo test to the results file that was created during a manual test execution.

  • The Disk Verification test is a 72-hour test. We recommend that you run this test last or over the weekend, so that you can collect and analyze the results from other tests without waiting for the whole test pass to finish.

  • The Optical Media Burning Test and Disk Stress test write to any optical recording drives on the test controller. If writable media is not present, these tests wait and notify you that you need writable media. Therefore, it requires manual intervention to continue testing. To enable a smooth automated experience, make sure that you have re-writable media in the drive before you run these tests.

  • The Boot Test, Optical Media Burning Test, and iSCSI Ping Test (HBA) require user intervention, so you must run them individually. We recommended that you run the other tests in a group because they are automated.

 

 

Build date: 9/14/2012