Microsoft Windows Logo Program System and Device Requirements — 105
Note: This list provides complete titles and web locations for references cited. The listing of a reference here does not imply that complete compliance with that reference is a Windows Logo Program requirement.
B18.104.22.168 Keyboard Scan Code Specification
B5.2.3 Keyboard - Quality
B22.214.171.124 Pass WHQL tests - See B1.3
See “Keyboard” in the HCT documentation.
B126.96.36.199 - See B188.8.131.52
B5.2.4 Keyboard - Windows Experience
"Input and HID" web page at http://www.microsoft.com/hwdev/tech/input/
B184.108.40.206 Any power management buttons implemented are ACPI compliant
B220.127.116.11 See B1.4.12; A18.104.22.168
B22.214.171.124 USB keyboard installation does not require reboot
B126.96.36.199 No interference occurs between multiple keyboards
If the system includes more than one keyboard, there must be no conflicts.
Mobile PC Note: For example, a docked mobile PC can have more than one keyboard attached to the system. The keyboard ports on a mobile PC and a docking station must be able to resolve conflicts between the two ports when the mobile PC is docked. Windows supports multiple configurations through the registry and will determine which keyboard to enable.
B188.8.131.52 Scan codes conform to industry standard
The following are requirements for a keyboard design that includes any Windows logo keys:
The keyboard must be developed according to technical requirements in "Key Support, Keyboard Scan Codes, and Windows" at http://www.microsoft.com/hwdev/tech/input/Scancode.asp.
The keyboard must be compatible at the Windows virtual key-code level.
The Windows Logo key must function as a modifier (Ctrl, Shift, or Alt).
The Windows Flag trademark must be clearly distinguished on the key top according to the requirements at http://www.microsoft.com/hwdev/tech/input/Scancode.asp.
Microsoft has defined extended scan codes for PS/2-compatible multimedia keyboards, and the USB HID Device Working Group has defined the consumer controls page. Hardware vendors should conform to these defined values and use their default functionality in order to ensure a good user experience following an upgrade or if the user doesn’t install any supplemental software. Additional software/drivers can be written to provide software remapping functionality.
Keyboard manufacturers must use consumer control or vendor-specific, top-level collections for HID hot buttons.
© 1999-2002 Microsoft Corporation. All rights reserved.