|
B5.2.2 Keyboard - Industry Standards
|
| bet | 113/188 | | Sana | 21.03.2017 | | Hajmi | 0,89 Mb. | | #429 |
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.
B5.2.2.1 Keyboard Scan Code Specification
http://www.microsoft.com/hwdev/tech/input/Scancode.asp
B5.2.3.1 Pass WHQL tests - See B1.3
See “Keyboard” in the HCT documentation.
B5.2.3.2 - See B5.1.4.7 B5.2.4 Keyboard - Windows Experience
"Input and HID" web page at http://www.microsoft.com/hwdev/tech/input/
See A1.1.2
B5.2.4.2 See B1.4.12; A1.1.4.13 B5.2.4.3 USB keyboard installation does not require reboot
See B1.4.4
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.
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.
If a keyboard or peripheral implements multimedia or Internet browser keys, they must use the registry keys associated with the WM_APPCOMMAND API to access those functions as described in the Windows DDK. Registry keys can be programmed using INF files to install special entries as defaults or through a customized interface provided to the user.
See WM_APPCOMMAND in the Microsoft Platform SDK.
B5.2.4.7 See B5.6.4.5
|
| |
