Guidelines for products that work well with the Microsoft® Windows® xp and Windows Server 2003 operating systems




Download 0.7 Mb.
bet15/22
Sana21.03.2017
Hajmi0.7 Mb.
1   ...   11   12   13   14   15   16   17   18   ...   22

B5.0 Input and HID

B5.1 General Input


All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.

B5.1.1 General Input - Windows Compatibility

B5.1.1.1 "Human Input Devices" in the Windows DDK

Note: This is a general reference, not a requirement.
B5.1.1.2 DELETED
B5.1.1.3 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/tech/input/

Note: This is a general reference, not a requirement.
B5.1.1.4 Input Device Drivers and Windows

http://www.microsoft.com/hwdev/tech/input/drv.asp

Note: This is a general reference, not a requirement.

B5.1.2 General Input - Industry Standards


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.1.2.1 IBM Personal System/2 Common Interfaces

Part No. S84F-9809: Order from IBM Customer Publications Support:
1-800-879-2755.
B5.1.2.2 USB HID references

http://www.usb.org/developers/docs.htm
B5.1.2.2.1 USB Device Class Definition for Human Interface Devices (HID), V. 1.0 or later.
B5.1.2.2.2 USB HID Usage Tables, V. 1.0 or later.
B5.1.2.2.3 USB Usage Tables for HID Power Devices, Release 1.0 or later.
B5.1.2.3 Input Device Class Power Management Reference Specification, Version 2.0 or later

http://www.microsoft.com/hwdev/resources/specs/pmref/PMinput.asp
B5.1.2.4 Legacy Plug and Play Guidelines

http://www.microsoft.com/hwdev/platform/pcdesign/desguide/

B5.1.3 General Input - Quality


WHQL Test Specification References:
Chapter 1: Introduction to HCT Test Specifications
plus technology-specific test specifications
B5.1.3.1 Pass WHQL tests - See B1.3

See “Input and HID” in the HCT documentation.
B5.1.3.2 - See B5.1.4.7

B5.1.4 General Input - Windows Experience


Design Guideline References:
"Input and HID" at http://www.microsoft.com/hwdev/tech/input/
B5.1.4.1 Any power management buttons implemented are ACPI compliant

See A1.1.2
B5.1.4.2 See B1.4.12
B5.1.4.3 DELETED
B5.1.4.4 DELETED
B5.1.4.5 All Human Interface Devices (HIDs) meet USB HID specifications

All USB keyboards, pointing devices, game pads, and their connections must comply with the Universal Serial Bus (USB) Device Class Definition for Human Interface Devices (HID), Version 1.1, and USB HID Usage Tables, Version 1.1. This is required whether the devices are implemented as wired or wireless. For HID implementation requirements under Windows, see the DDK.
B5.1.4.6 DELETED
B5.1.4.7 DELETED

B5.1.5 General Input - FAQs

B5.1.5.1 Current input device FAQs

See http://www.microsoft.com/winlogo/hardware/
B5.1.5.2 DELETED

Related requirement deleted.

B5.1.R General Input - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/

B5.2 Keyboard


All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.
All general input requirements in B5.1 are included by reference.

B5.2.1 Keyboard - Windows Compatibility

B5.2.1.1 "Human Input Devices" in the Windows DDK

Note: This is a general reference, not a requirement.
B5.2.1.2 DELETED
B5.2.1.3 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/tech/input/

Note: This is a general reference, not a requirement.
B5.2.1.4 Scan Code Mapper for Windows

http://www.microsoft.com/hwdev/tech/input/w2kscan-map.asp

Note: This is a general reference, not a requirement.
B5.2.1.5 Keyboard Scan Code Specification

http://www.microsoft.com/hwdev/tech/input/Scancode.asp

Note: This is a general reference, not a requirement.
B5.2.1.6 Legacy Support for USB Keyboards and Mice and the Host Controller Driver

http://www.microsoft.com/hwdev/tech/input/usbhost.asp

Note: This is a general reference, not a requirement.

B5.2.2 Keyboard - Industry Standards


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 Keyboard - Quality

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/
B5.2.4.1 Any power management buttons implemented are ACPI compliant

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
B5.2.4.4 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.
B5.2.4.5 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.


B5.2.4.6 Keys for Internet browser and multimedia use Microsoft APIs

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

B5.2.5 Keyboard - FAQs

B5.2.5.1 Current keyboard FAQs

See http://www.microsoft.com/winlogo/hardware/
B5.2.5.2 Updated at B5.2.4.5
B5.2.5.3 Updated at B5.2.4.5

B5.2.R Keyboard - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/

B5.3 Input/Pointing


All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.
All general input requirements in B5.1 are included by reference.

B5.3.1 Input/Pointing - Windows Compatibility

B5.3.1.1 "Human Input Devices" in the Windows DDK

Note: This is a general reference, not a requirement.
B5.3.1.2 DELETED
B5.3.1.3 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/tech/input/

Note: This is a general reference, not a requirement.
B5.3.1.4 Legacy Support for USB Keyboards and Mice and the Host Controller Driver

http://www.microsoft.com/hwdev/tech/input/usbhost.asp

Note: This is a general reference, not a requirement.

B5.3.2 Input/Pointing - Industry Standards


See B5.1.5

B5.3.3 Input/Pointing - Quality

B5.3.3.1 - See B5.3.4.1
B5.3.3.2 Pass WHQL tests - See B1.3

See “Pointing and Drawing Devices” in the HCT documentation.
B5.3.3.3, B5.3.3.4, B5.3.3.5 - See B5.3.4.1

B5.3.4 Input/Pointing - Windows Experience


"Input and HID" web page at http://www.microsoft.com/hwdev/tech/input/
B5.3.4.1 Device functions correctly
B5.3.4.1.1 Wheel support (scroll, auto-scroll, pan, and zoom) in Microsoft Office and Windows Explorer.
B5.3.4.1.2 In multimedia applications that require mouse support, such as Microsoft Encarta® and MS-DOS-based applications.
B5.3.4.1.3 When switching on-the-fly from MS-DOS-based applications to Windows.
B5.3.4.1.4 Plug and Play Device Manager validates serial devices.
B5.3.4.1.5 See B1.4.12; A1.1.4.13

Mobile PC Notes:
B5.3.4.1.6 Mobile PC external PS/2 pointing device detected at boot and installed correctly.
B5.3.4.1.7 Mobile PC internal pointing device disabled or dual operation enabled if external device is PS/2 -compatible.

The required default BIOS option is to provide an option to disable the internal pointing device when any external PS/2-type pointing device is detected at startup. In this case, the driver for the internal pointing device must not load.

B5.3.5 Input/Pointing - FAQs


See http://www.microsoft.com/winlogo/hardware/

B5.3.R Input/Pointing - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/

B5.4 Input/Game


All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.
All general input requirements in B5.1 are included by reference.

B5.4.1 Input/Game - Windows Compatibility

B5.4.1.1 "Human Input Devices" in the Windows DDK

Note: This is a general reference, not a requirement.
B5.4.1.2 DELETED
B5.4.1.3 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/tech/input/

Note: This is a general reference, not a requirement.
B5.4.1.4 HID Game Controllers and DirectInput

http://www.microsoft.com/hwdev/tech/input/hidgame.asp

Note: This is a general reference, not a requirement.

B5.4.2 Input/Game - Industry Standards


See B5.1.5.

B5.4.3 Input/Game - Quality

B5.4.3.1 - See B5.4.4.3
B5.4.3.2 Pass WHQL tests - See B1.3.

See “Game Devices” in HCT documentation.

B5.4.4 Input/Game - Windows Experience


"Input and HID" web page at http://www.microsoft.com/hwdev/tech/input/
B5.4.4.1 See B1.4.12; A1.1.4.13
B5.4.4.2 Device performs as expected with multimedia applications
B5.4.4.3 All input devices support Microsoft DirectInput® and work simultaneously

B5.4.5 Input/Game - FAQs

B5.4.5.1 Current game port FAQs

See http://www.microsoft.com/winlogo/hardware/
B5.4.5.2 Game pad requirements for systems [Clarification]

If a game pad or joystick is included in a system, it should be implemented using USB. It is not required to include any such devices on a system.

Note: No devices that use legacy or proprietary ports can be included in a system.
FAQ Date: October 7, 1998

B5.4.R Input/Game - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/

B5.5 Input/Keyboard-Video-Mouse


All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.
All general input requirements in B5.1, B5.2, and B5.3 are included by reference.

B5.5.1 Keyboard/Video/Mouse - Windows Compatibility

B5.5.1.1 "Human Input Devices" in the Windows DDK

Note: This is a general reference, not a requirement.
B5.5.1.2 DELETED
B5.5.1.3 Windows compatibility and implementation notes

http://www.microsoft.com/hwdev/tech/input/

Note: This is a general reference, not a requirement.

B5.5.2 Keyboard/Video/Mouse - Industry Standards


See B5.1.5.

B5.5.3 Keyboard/Video/Mouse – Quality

B5.5.3.1 - See B5.5.4.7
B5.5.3.2 - See B5.5.4.8
B5.5.3.3 - See B5.5.4.8
B5.3.3.4 Pass WHQL tests - See B1.3

See “Keyboard-Video-Mouse Switch” in HCT documentation.

B5.5.4 Keyboard/Video/Mouse - Windows Experience


"Input and HID" web page at http://www.microsoft.com/hwdev/tech/input/
B5.5.4.1 Cascading switch boxes
B5.5.4.2 On-screen display for switching between machines
B5.5.4.3 Ability to switch between machines using a keyboard
B5.5.4.4 System recognizes any Plug and Play keyboard, mouse, or monitor connected to the KVM
B5.5.4.5 System resets the device ports in case a corruption results in an incorrect output signal sent from a connected device to the operating system
B5.5.4.6 All devices and cables connected to the KVM are hot pluggable
B5.5.4.7 All the commands listed in the device’s user manual work correctly
B5.5.4.8 Only documented commands are provided
B5.5.4.9 All buttons on the Keyboard-Video-Mouse (KVM) work properly

B5.5.5 Keyboard/Video/Mouse - FAQs


See http://www.microsoft.com/winlogo/hardware/

B5.5.R Keyboard/Video/Mouse - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/

B5.6 Smart Card Readers


All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.
All general input requirements in B5.1 are included by reference.

B5.6.1 Smart Card - Windows Compatibility

B5.6.1.1 “Smart Card Devices” in the Windows DDK

Note: This is a general reference, not a requirement.
B5.6.1.2 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/tech/input/smartcard/

Note: This is a general reference, not a requirement.

B5.6.2 Smart Card - Industry Standards


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.6.2.1 ISO/IEC DIS 7816 Identification Cards—Integrated circuit(s) cards with contacts

ISO/IEC 7816-1:1998 Identification cards—Integrated circuit(s) cards with contacts—Part 1: Physical characteristics
http://www.iso.ch/cate/d29257.htm

ISO/IEC 7816-2:1999 Identification cards—Integrated circuit(s) cards with contacts—Part 2: Dimensions and location of the contacts


http://www.iso.ch/cate/d26536.html

ISO/IEC 7816-3:1997 Information technology—Identification cards—Integrated circuit(s) cards with contacts—Part 3: Electronic signals and transmission protocols


http://www.iso.ch/cate/d14735.html

Power Down command for ISO 7816-3 is optional, but Reset command is mandatory.


B5.6.2.2 Interoperability Specification for ICCs and Personal Computer Systems, Version 1.0 (PC/SC Specifications)

http://www.pcscworkgroup.com/
B5.6.2.3 ISO/IEC Specifications

ISO/IEC 7811-1:1995 Identification Cards—Recording technique—Part 1: Embossing

ISO/IEC 7811-3:1995 Identification Cards—Recording technique—Part 3: Location of embossed characters on ID-1 cards

ISO/IEC 7813:1995 Identification Cards—Financial transaction cards

ISO/IEC 10373:1993 Identification cards—Test methods

ISO 13491-1:1998 Banking—Secure cryptographic devices (retail)—Part 1: Concepts, requirements and evaluation methods.

B5.6.3 Smart Card - Quality

B5.6.3.1 - See B1.4.12; A1.1.4.13
B5.6.3.2 Pass WHQL tests - See B1.3.

See “Smart Card Readers” in HCT documentation.

B5.6.4 Smart Card - Windows Experience


Design Guideline References:
Smart Card for Windows web site at http://www.microsoft.com/hwdev/tech/input/smartcard/
B5.6.4.1 Driver does not cause system to stop running if required resources are not available
B5.6.4.2 Driver supports multiple instances of the same device on system without problems
B5.6.4.3 See B1.4.5
B5.6.4.4 Reader supports required capabilities
B5.6.4.4.1 Direct and Inverse-convention smart cards.

A smart card reader must support both inverse and direct convention smart cards either in hardware or in the driver for the operating system.
B5.6.4.4.2 258 byte packets in T=0 and 259 byte packets in T=1.

A smart card reader must support the exchange of the following in a single transmission:

  • 258 byte packets in T=0—that is, 256 data bytes plus the two status words SW1 and SW2.

  • 259 byte packets in T=1—that is, 254 information bytes plus node address, packet control bytes, length, and two Error Detection Code bytes.
B5.6.4.4.3 Smart card insertion/removal monitor.

A smart card reader must be able to detect and report smart card insertions and removals without any user intervention other than removing or inserting the smart card itself. The reader must use an interrupt mechanism to report the smart card insertion or removal to the system. A driver polling method to detect smart card insertion and removals is not an acceptable method for meeting this requirement.
B5.6.4.4.4 Reader must support negotiable and specific modes according to ISO/IEC 7816-3 (1997-12-15) Sections 5.4 and 7.

To support multi-protocol smart cards and smart cards using higher data rates and higher clock frequencies, the reader must support negotiable and specific modes according to ISO/IEC 7816-3 (1997-12-15), Sections 5.4 and 7.

Power Down command for ISO 7816-3 is optional.

PTS is not required.

B5.6.4.4.5 Support 3.5795 MHz minimum clock frequency.

A smart card reader must support a minimum clock frequency of 3.5795 MHz.
B5.6.4.4.6 Support minimum data rate of 9600 bps.
B5.6.4.4.7 Reset command.

A smart card reader must support the asynchronous protocols T=0 and T=1 as described in ISO/IEC 7816-3, either in hardware or in the driver. Both protocols must be supported fully. The smart card reader and the driver must support cards that can handle both protocols.

The following protocol rules apply for the T=1 protocol:



  • A transmission is defined as sending a command to a smart card using one or more T=1 blocks and receiving the corresponding answer using one or more T=1 blocks as defined in ISO/IEC 7816-3.

  • For cards that support Information Field Size integrated circuit Card (IFSC) requests, the first transmission—after a reset of the smart card—must start with an Information Field Size Device (IFSD) request, as defined in ISO/IEC 7816-3, Amendment 1, Section 9.5.1.2.

For cards that do not support an IFSD request (that is, the card replies with an R-Block indicating “Other error”), the transmission must continue with an I-Block.

After a successful RESYNCH request, the transmission must restart from the beginning with the first block with which the transmission originally started.



  • Support for protocols other than T=0 and T=1 is not required.
B5.6.4.5 Input device implementing a PIN data-entry keyboard complies with ISO 13491-1

An input device that uses a keyboard for personal identification number (PIN) entry must comply with ISO 13491-1:1998 Banking—Secure cryptographic devices (retail)—Part 1: Concepts, requirements and evaluation methods.
B5.6.4.6 See B1.4.12; A1.1.4.13

B5.6.5 Smart Card – FAQs

B5.6.5.1 Current smart card FAQs

See http://www.microsoft.com/winlogo/hardware/
B5.6.5.2 Updated at B5.6.4.4

B5.6.R Smart Card - Future Requirements


Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/
1   ...   11   12   13   14   15   16   17   18   ...   22


Download 0.7 Mb.

Bosh sahifa
Aloqalar

    Bosh sahifa


Guidelines for products that work well with the Microsoft® Windows® xp and Windows Server 2003 operating systems

Download 0.7 Mb.