B188.8.131.52 Devices meet requirements in related USB device class specifications
[USB-0088; SDG3:60; see also FAQ B184.108.40.206]
B220.127.116.11 Hub or device that supports USB 2.0 complies with USB 2.0 Specification
B18.104.22.168 USB devices install and perform at least some functions expected by end users for that class of device, without preloading software
Without loading a specific driver, USB devices having native operating system class driver support provide the typical functions supported by devices within each class, as defined in the USB device class specifications. After device specific driver installation, the device must be fully functional.
Driver packages can force re-enumeration by pointing to their INF file; see UpdateDriverForPlugAndPlayDevices in the Windows DDK for information.
B22.214.171.124 USB hubs are self-powered
This requirement does not apply for hubs integrated into USB keyboards.
Mobile PC Note: This requirement does not apply for hubs integrated into mobile systems.
B2.6.5 USB Controllers/Devices - FAQs
B126.96.36.199 Current USB-related FAQs
B188.8.131.52 USB device definition [Logo Program clarification]
Any device that plugs into a USB port is tested as a USB device—that is, the device provides the capabilities of one or more functions, a hub to the host, or both. As result, these requirements apply for any device that plugs into a USB port: the USBspecification and any related USB device class specification, plus the Windows Logo Program requirements for USB and the related device class.
FAQ Date: October 7, 1998
B2.6.R USB Controllers/Devices - Future Requirements
Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/usb/.
B2.6.R.1 USB isochronous devices do not request more than 25 percent of the total bandwidth at any time
B184.108.40.206 AC ‘97 devices on riser cards [Logo Program clarification]
AC ‘97 devices on riser cards such as AMR, CNR, and MR can be tested and receive the "Designed for Windows" Logo based on the following requirements:
The system BIOS must provide a unique PCI SID for any riser card, assigned by the codec manufacturer. This is identical to current Logo Program requirements for audio and modem devices on a PCI add-on card—except these are system-board devices, so the PCI SID must reflect that of the system-board manufacturer.
If an OEM chooses a riser card and driver from any riser card driver manufacturer, the BIOS must populate the fields as follows:
The PCI SVID must reflect the Vendor ID assigned by the PCI SIG to that OEM.
The SID must be unique for each AC ‘97 device configuration. For example, for a MoM, MR, or AMR device, each SID must be unique.
If an OEM chooses a system board from a manufacturer that works with one or more codecs, the following applies:
The SVID must reflect the Vendor ID assigned by the PCI SIG to that system-board manufacturer.
The SID must be unique for each AC ‘97 codec/device configuration. For example, for a MoM, MR, or AMR device, each SID must be unique.
The system BIOS must properly implement the detection algorithm from Intel to verify that the hardware on an AMR/MR riser extension is actually present.
For more information about WHQL testing for riser cards, see the WHQL web site at http://www.microsoft.com/hwtest/.
This is a recommendation, not a requirement. Replaced in B220.127.116.11.
FAQ Date: December 22, 1998; June 16, 2000
B18.104.22.168 PCI power management requirements [Clarification]
PCI Bus Power Management Interface Specification, Revision 1.1 or later, is the only industry specification that ensures compatibility with the power management capabilities of Windows 2000 and Windows XP.
FAQ Date: November 12, 1999
B22.214.171.124 WDM Audio Driver Requirements [Logo Program Clarification]
WDM audio driver requirements apply based on the preinstalled operating system:
Windows XP/Windows 2000 and Windows Me Audio Drivers: All devices are required to use WDM drivers.
Audio drivers for Windows 98 Second Edition: All audio devices are required to use WDM, with the exceptions noted below. There will be an operating system update released early next year that will address the technical deficiencies. As of July 1, 2000, devices in either of the following two categories cannot use VxD drivers:
Exception #1: Audio devices that also contain a game port: Windows 98 Second Edition does not support WDM game ports. Audio devices that use WDM drivers must provide a VxD module for the game port. Windows 98 Second Edition has known issues with the interconnection between WDM audio devices and the VxD game port services. The operating system update will address these issues.
Exception #2: Audio devices that use WavePCI and provide hardware acceleration of Microsoft DirectSound: There are two classes of WDM audio drivers, WaveCyclic and WavePCI. The former is intended for those devices that utilize looping memory buffers to transfer audio to the device. The latter is geared towards PCI devices that use scatter-gather to transfer data. Windows 98 Second Edition has known issues with WavePCI and DirectSound hardware acceleration. These issues have been addressed in later operating systems.
Audio drivers for the initial release of Windows 98: Systems that ship with Windows 98 may use VxD audio drivers indefinitely (due to WDM audio issues in Windows 98). This does not apply to Windows 98 Second Edition.
Audio drivers for Windows NT 4.0: Because Windows NT 4.0 does not support WDM, the WDM requirement does not apply for testing systems under Windows NT 4.0.
FAQ Date: November 29, 1999
B126.96.36.199 Audio subsystem supports basic data formats [Revision]
Hardware sample rate conversion (SRC) is not required when the Microsoft software SRC is used. Windows 98/Me and Windows 2000 provide software mixing and SRC, which eliminate the need for hardware to support any sampling rate other than 48 kHz.
FAQ date: February 28, 2001
B188.8.131.52 DRM legacy function calls [Clarification]
Windows XP: to pass Windows Logo testing for Secure Audio Path for Digital Rights Management as DRM compliant with DRM Level = 1200 (which is the security level for Windows XP), audio drivers for Windows XP must not call DrmForwardContentToFileObject. If an audio driver calls DrmForwardContentToFileObject, it will be qualified as DRM compliant with DRM Level = 1100, which is the security level for Windows Me.
B3.1.R General Audio - Future Requirements
Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/audio/.