Display Monitor Testing Prerequisites
This section describes the tasks that you must complete before you test a display monitor or projector by using the Windows Hardware Certification Kit (Windows HCK):
Review the hardware requirements.
Review the software requirements.
Configure the test computer.
The following hardware is required for testing a CRT or flat panel display monitor or a projector.
Two test computers. These test computers must meet the Windows HCK prerequisites and must be included in the same computer pool. For more information, see Windows HCK Prerequisites.
Two test display devices.
We recommend that you test two different display adapters that use different IHV drivers when you test the display device. You might need additional hardware if the test device offers other features, such as a USB port or built-in audio capabilities. To determine whether additional hardware requirements apply, see the test description for each test that appears for the device in Windows HCK Studio.
To certify your product for use on servers, the test computer must support four processors and a minimum of 1 GB of RAM. These system capabilities are required to test the Rebalance, D3 State, and Multiple Processor Group functionality of the device and driver. You do not need a computer that actually has more than 64 processors to test your device. Additionally, the server system(s) being used for device or driver testing must have Server Core installed prior to testing. For more information see Windows Server Installation Options.
If you use a pool of test computers to test devices, at least one computer in the pool must contain four processors and a minimum of 1 GB of RAM. Additionally, that computer must contain the device and the driver that you want to test. As long as the driver is the same on all the computers in the pool, the system creates a schedule to run against all test computers.
For tests that do not include a driver to test, such as hard disk drive tests, the Windows HCK scheduler constrains the tests that validate the device’s and driver’s Rebalance, D3 State and Multiple Processor Groups functionality to run on the default test computer. You must manually configure this computer to have multiple processor groups. The default computer is the first test computer in the list. Test personnel must make sure that the first test computer in the list meets the minimum hardware requirements.
Except for para-virtualization drivers (as defined by Logo Program Requirement Policy-0020), you may not use any form of virtualization when you test physical devices and their associated drivers for server certification or signature. All virtualization products do not support the underlying functionality that is required to pass the tests that relate to multiple processor groups, device power management, device PCI functionality, and other tests.
The following software is required for testing a display device:
Any drivers that are not included with the operating system.
A setup information file (INF) for the device that you are testing.
An Image Color Management (ICM) file, if applicable.
The latest Windows HCK filters or updates.
Test computer configuration
To configure the two test computers for display monitor testing, follow these steps:
Install the appropriate Windows operating system on the test computers, and then add these computers to your test network.
Connect the display monitor or projector to each test computer.
Install the manufacturer-supplied INF or ICM files, if either of these files is required for the display device, on the test computers.
Make sure that the display monitor or projector functions correctly on both test computers.
Install the Windows HCK client application on the test computers.
Use Windows HCK Studio to create a machine pool and move the test computers to that pool.
Make sure that the test computer is in the ready state before you begin your testing. If a test requires parameters to be set before it is run, a dialog box will be displayed for that test. Review the specific test topic for more information.
Some Windows HCK tests require user intervention. When running tests for a submission, it is a best practice to run the automated tests in a block separately from manual tests. This prevents a manual test from interrupting completion of an automated test.