Windows Logo Program

Appendix B - Device Requirements Checklist

The current versions of these requirements are provided on http://www.microsoft.com/winlogo/hardware/

Note that testing for all Windows versions must also include logs for Windows XP/Windows Whistler Server, even if the specific “Designed for Windows” you are seeking does not target Windows XP or Windows Whistler Server.

Requirements apply for all of the following tested operating systems unless otherwise indicated:

Windows XP Home Edition (32-bit)
Windows XP Professional (64-bit and 32-bit)
Windows Whistler Server (64-bit and 32-bit)
Windows 2000 Server and Professional (32-bit)
Windows Millennium Edition
Windows 98 Second Edition
See also:

• 
  Conventions Used in This Document
  
• 
  How to Use the Appendixes
  

B1.0 General Device and Driver Quality

B1.1 General Device/Driver - Windows Compatibility

B1.1.1 Device drivers comply with Windows DDK requirements

Third-party applications implemented as defined in the Microsoft Platform SDK.

B1.1.2 OnNow and ACPI compatibility and implementation notes

B1.1.3 WDM driver implementation notes (for device classes supported under WDM)

B1.2 General Device/Driver - Industry Standards

B1.2.1 Advanced Configuration and Power Interface Specification (ACPI)

B1.2.2 Device Class Power Management Reference Specifications

B1.2.3 Plug and Play specifications

B1.2.4 Each device or connection meets requirements for its bus class

B1.3 General Device/Driver - Quality

B1.3.1 Hardware and its drivers pass Windows Logo Program testing

• 
  Windows XP: Pass tests in HCT 10.0 (or later), as described in detail in the WHQL Test Specification and the Microsoft Windows Hardware Compatibility Test Kit 10.0 documentation.
  
• 
  Windows Me: Pass tests in HCT 9.6, as described in the HCT documentation.
  
• 
  Windows 2000, Windows 98, Windows NT 4.0: Pass tests in HCT 9.502, as described in the HCT documentation.
  

B1.3.2 Windows XP/Windows 2000: Vendor-supplied drivers pass Driver Verifier test

B1.3.3 Device driver installs via an INF; tested via INFCatReady.exe

B1.3.4 Vendor-supplied drivers have digital signatures

WHQL guidelines and processes for digital signatures are defined at http://www.microsoft.com/hwtest/signatures/.

B1.4 General Device/Driver - Windows Experience

B1.4.1 Device can be enumerated and automatically disabled

Device ID is present, device is properly enumerated, and correct driver is found; device can be disabled automatically by Windows.

B1.4.2 Software does not replace or bypass system components

Driver or software installation must not replace any Microsoft-authored operating system components, and the driver must not bypass any operating system components.

If the manufacturer’s INF copies any files supplied by the operating system, those files must be copied from the Windows product disk (or preinstalled source files), unless the component is a licensed, redistributable component.

Driver must not use initialization files (INI) for configuration settings.

B1.4.3 Installing and loading the driver does not reduce or eliminate functionality of other devices installed on the system

B1.4.4 Device is functional without restarting the system

Device installation does not cause the system to stop running or reboot (unless reboot is required by the operating system) without user interaction.

B1.4.5 Device and driver comply with ACPI and power management specifications

Device and driver comply with ACPI specification, Default Device Class Power Management Reference Specification, and other relevant device class power management specification

• 
  Windows 2000/Windows Me: Graphics adapter and all other devices correctly implement D3 state such that the operating system can correctly hibernate and resume from all sleep states supported on the system.
  
• 
  Any PCI devices that support wakeup capabilities correctly support wake from D3cold.
  

• 
  Windows XP client: Uniprocessor desktops that run Windows XP are required to support S3; therefore, every device must be tested on an S3-compliant system to verify that the device allows the system to successfully enter and resume from the S3 sleep state.
  

B1.4.6 Driver supports unattended installation

It must be possible to install the driver using a script or special software for supplying required parameters without the user being present during driver installation.

B1.4.7 Windows Help file is provided if special driver parameters are used

B1.4.8 Hardware management instrumentation, if implemented, is provided per WHIIG

B1.4.9 Device has an icon on any external connectors

Color-coding is not required. [see FAQ A1.5.9]

B1.4.10 Any supporting software included with the device is installed using Windows-based installation methods, without any manual steps or file editing

B1.4.11 Software installed as part of device driver installation can be removed using Windows-based software

At a minimum, any "virtual drivers" and software components (such as control panel applets) installed with the driver must be capable of being removed.

B1.5 General Device/Driver - FAQs

B1.5.1 Current general FAQ

B1.5.2 Windows 98/Me: Display Class and Other 16-bit Windows Software [Clarification]

For Windows 98/Me, see ”Graphics Device Interface” in the Windows Me DDK documentation for information about implementing driver setup functions in a separate installer to be used only during installation, instead of containing setup functions in the driver itself.

This clarification is related to the Windows Logo Program requirement that installation and loading of a driver must not interfere with other components on the system. As of July 1, 2000, this is part of Windows Logo Program compliance testing.
FAQ date: December 22, 1999

B1.R General Device/Driver Quality - Future Requirements

B1.R.1 Applications meet "Designed for Windows XP Application Specification" requirements