Microsoft Windows Logo Program System and Device Requirements — 17
The compatibility and quality guidelines include requirements for devices, drivers, and software included with the system or retail component.
For specific feature and functionality requirements for each type of system, see Appendix A, "System Requirements Checklist."
Any buses, devices, or other components offered with a Logo’d system or offered as a retail product carrying the "Designed for Windows" logo must pass related feature tests and operating system compatibility tests published by WHQL.
For the complete checklist of device and bus requirements, see Appendix B, "Device Requirements Checklist."
Driver and Software Requirements
These requirements ensure a good user experience when installing and using any component:
Windows-compatible driver support. Each device must have drivers for Windows XP or Windows Server 2003.
Windows-based driver installation. Driver installation and removal must use Windows-based methods, as defined in the Windows DDKs. For Windows XP/Windows Server 2003 family, this means only INF-based installation routines.
System component and installation integrity. Driver or software installation must not replace any Microsoft-authored system components and the driver must not bypass any operating system components. See http://www.microsoft.com/hwdev/driver/sfp/wfp.asp.
Loading of a driver must not reduce or eliminate the functionality of other devices installed on the system.
Minimum driver compatibility. Each driver must pass minimum compatibility, functionality, and stress testing as verified by the testing suites published by Microsoft WHQL for the related class.
Driver Verifier. For each Windows XP or Windows Server 2003 family driver, no errors can occur under the Driver Verifier facility provided with the operating system.
Poorly written kernel-mode drivers have the potential to cause the system to become unstable or stop working. Therefore, it is critical that all kernel-mode drivers be thoroughly tested to minimize this risk. For information about using Driver Verifier and diagnosing driver problems, see http://www.microsoft.com/hwdev/driver/verifier.asp.
Driver signing. All drivers installed on the system as shipped to the customer must be signed. Drivers submitted for Microsoft Windows Logo Program testing must meet the guidelines for driver signing as defined at http://www.microsoft.com/hwdev/driver/digitsign.asp.
Other WHQL test programs that require digital signatures include the following:
Hardware Abstraction Layers (HALs): The purpose of the HAL test kit is to test third-party (non-Microsoft) HALs intended for use in server-class systems.
For details about what is tested for HALs, see Chapter 26, “HAL Test Specification,” in WHQL Test Specification.
© 1999-2002 Microsoft Corporation. All rights reserved.