B184.108.40.206 Video input image orientation identification meets requirements
B220.127.116.11 Windows Me—Requirement for IEEE 1394 camcorders
IEEE 1394 DV camcorders must implement mandatory VCR subunit commands. DV cameras must comply with the AV/C Digital Interface Command Set VCR Subunit Specification, Version 2.0.1. [see http://www.1394TA.org]
At a minimum, the device must support VCR subunit commands labeled "mandatory" in this specification.
B18.104.22.168 Video implementation preserves source quality during playback, storage, or processing of video streams and does not adversely affect overall PC performance
That is, any cropping, scaling, or frame dropping that the hardware or the driver is performing on the related video frames.
B22.214.171.124 No tearing or other artifacts (macroblocking, jaggies, and so on)
B126.96.36.199 IEEE 1394 DV camcorder implements mandatory VCR subunit commands
Digital video (DV) cameras must comply with the AV/C Digital Interface Command Set VCR Subunit Specification.
At a minimum, the device must support VCR subunit commands labeled as "mandatory" in this specification.
B188.8.131.52 Analog input supports 720 × 480 decode to 4:2:2
B184.108.40.206 Frame rate is within 0.2 percent of PAL 25.0fps or NTSC 29.97fps standard
B11.4.5 Video Input/Capture - FAQs
B220.127.116.11 Current video-related FAQs
B18.104.22.168 Test Clarification
The compatibility tests for PC systems determine whether there is excessive cross color, hanging dots, or other artifacts that could degrade the viewer experience. A DVD player with the Joe Kane Video Essentials disk with the Snell and Wilcox Zone plate test pattern is used to assess the video quality.
Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/video/.
B12.1 Multifunction Devices
All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.
All requirements for each specific device class implemented in the multifunction device are included by reference.
B12.1.1 Multifunction Devices - Windows Compatibility
Design Guideline References: PC 2001 System Design Guide: SYS-0032
Hardware Design Guide 3.0 for Windows 2000 Server, Chapter 3
B22.214.171.124 Separate drivers are required for separate functions with no start order dependencies between separate function drivers
The operating system must be able to configure and manage functions in any order, so no function on a multifunction device can depend on another function to be started before the function can be started by the operating system.
Functional units on a multifunction device do not have start-order dependencies.
Resource requirements of one functional unit are not expressed in terms of another functional unit.
Operation of one functional unit do not affect or interfere with the operation of another functional unit on the multifunction device or on the system as a whole.
Each functional unit is enumerated and its resource requirements communicated to the operating system, so Windows can load the necessary drivers and assign resources to the different units in any order.
B126.96.36.199 Each independent function can be used concurrently, with no hidden dependencies
B188.8.131.52 Each function can be power managed independently
Each functional unit in a multifunction device must separately meet the power management device class specifications for its device class and be independently power managed. Each functional unit must be able to successfully complete a system sleep/wake transition (where the unit transitions from D0 to D3 to D0) without losing functionality and without requiring user intervention to restore functionality. All functional units on PCI devices that support wakeup capabilities must correctly support wake from D3cold.
B12.1.5 Multifunction Devices - FAQs
B184.108.40.206 Current general FAQs
B220.127.116.11 Resource requirements for MFD [Logo Program Clarification]
The PC 99 exception for multifunction PCI devices that use only a single set of relocatable resources refers solely to multifunction devices of the same device class. If different functions within a multiple-function device require separate class drivers—for example, a combination PCI network adapter and modem—then each function must provide a unique PCI SID and SVID that will allow the proper driver to be loaded for each separate function.
Multifunction devices that contain functions from separate classes will not be properly recognized during an operating system upgrade—and therefore drivers will not be properly upgraded—unless unique IDs are provided for each device.
Note that a "supervisory" driver that loads different drivers for the individual functions does not work well with Windows. In particular, driver support is likely to be lost in cases of operating system re-installation or upgrade, or with distribution of new drivers via Windows Update. Therefore, these supervisory drivers should be avoided. The Logo Program requires separate drivers for separate functions.
FAQ Date: May 28, 1999
B18.104.22.168 Exceptions to individual ID requirement for MF devices [Logo Program Clarification]
Dependent video devices, such as a graphics accelerator on a video card.
Devices that are generated by an accelerator or auxiliary processor and that do not have independent hardware I/O. That processor must have an ID; under Windows XP/Windows 2000, Mf.sys must be used to enumerate the dependent devices.
FAQ Date: May 28, 1999
Future requirements for USB connected multifunction print (MFP) device drivers supporting composite implementations are posted at "Multifunction Print Device Design Guidelines" at http://www.microsoft.com/hwdev/mf/mfp.htm.