WHQL Logo Program Responsibilities
|
Last
updated on May 28, 1999
|
In the Windows Logo program, the OEM and WHQL have
very different responsibilities. Understanding these responsibilities is critical for your
systems to move smoothly through the logo process. Below is a list outlining the major OEM
and WHQL responsibilities:
OEM
- Run
the System Tests
Most OEM systems
are eligible for PC 99 testing, therefore, the responsibility of
running the tests falls to the OEM. These tests take some time to run,
and MUST be run on all Microsoft operating systems that are
required. For a list of the operating systems that are rquired for each OS, see System Submission Procedures.
- Debug
and fix problems found by WHQL tests
Test failures should always
be taken seriously. Some test failures are acceptable, these are listed in the HCT Testing Errata. The OEM is ultimately responsible for fixing the
problem if it is determined to be a hardware or driver issue.
- Manage
IHV devices and drivers
OEMs must work closely with
their IHV to manage driver updates and device changes. WHQL logos only
device/driver combinations, so if the driver is changed, it must be
resubmitted to WHQL for retesting. This process works best if the IHV
shares the responsibility by submitting the device/driver combination
for testing before the OEM ships the system. WHQL will always attempt
to help wherever possible in this process by working directly with IHVs.
- Ship only logo'd components
to customers
After the initial logo process
is complete, additional work needs to be done if the preinstall is going
to be updated with bug fixes or feature enhancements. Make sure your system ships with correctly tested and logo'd drivers.
- Communicate with WHQL
on a regular basis
Communication is very important
for WHQL to address OEM needs. The OEM should never hesitate to contact
the appropriate support alias with questions or concersn. For a list of the WHQL aliases, see Support and Problem Resolution.
WHQL
- Deliver tests
to measure logo compliance on a regular schedule
WHQL is responsible for providing
tools that measure system compatibility with Microsoft operating systems
and compliance to Microsoft hardware initiatives. These tests are comprehensive,
but may not provide 100% coverage of these requirements, and are subject
to updates.
- Provide documentation
for the tests
A key tool to assist the OEM in
debugging test failures is good test documentation that provides detailed
information of how the test works and what is tested. For the most current HCT documentation, check out the WHQL Systems Website: http:\\www.microsoft.com\hwtest\sysdocs\
- Provide
technical assistance for the tests
Occasionally, a problem may
arise that the OEM has difficulty debugging. When this happens, WHQL
will provide as much assistance as possible by giving additional insight
into what the test is testing, and facilitate communication with the
OS development teams.
- Assist
in working with IHV devices and drivers
WHQL has many current programs
for testing a variety of devices. WHQL will make every attempt to respond
to OEM requests and provide as much information as possible.