Microsoft offers the Windows Logo Program to help customers identify systems and peripherals that meet a baseline definition of platform features and quality goals that ensure a good Windows experience for the end user. The Windows Logo is not intended to communicate the specific technical capabilities of any particular system.
Products that earn the Windows Logo have been tested to ensure that they meet Microsoft standards for compatibility on the Windows operating systems designated on the logo. System and peripheral manufacturers can license the Windows Logo for use on product packaging, advertising, collateral, and other marketing materials for all systems and components that pass compliance testing.
Products that carry the Windows Logo for hardware include these characteristics:
All components install and uninstall properly and do not interfere with other system components.
Each component interoperates well with other system components.
All components function normally after the operating system is upgraded to Windows XP or any later version of the operating systems for which the system or component carries the logo.
These characteristics yield these benefits for manufacturers:
Windows Logo Program requirements are intended to support a good user experience with the Windows operating system. In this context, a "good user experience" means a reliable, consistent experience with system hardware, firmware, drivers, and related software components. In particular:
The user is assured that a product that has the Windows Logo will be stable when running under the operating systems listed on the Windows Logo carried by that product or listed in the Windows Catalog.
The user can easily begin and complete component installation or removal. Installing and using a component that has the Windows Logo will not cause the system to stop working, or otherwise disrupt Windows or other Logo’d software running on the computer.
The user’s overall experience with the computer system and the operating system is the same or better after upgrading to a new Windows operating system.
Important: The presence of the Windows Logo on a hardware product does not mean that Microsoft endorses or certifies a product. The Windows Logo is not a quality assurance seal. Microsoft does not test the quality of each hardware product or ensure that it is bug free.
"Designed for Windows" Logo Options
Microsoft licenses different versions of the "Designed for Windows" logo for specific operating systems on servers, desktop PCs, mobile PCs, and their components, as described in this section. The Windows Logo explicitly identifies the versions of the operating system for which the product passed compliance testing. Testing is conducted by Windows Hardware Quality Labs, as described in Chapter 4 of this guide.
The specific Windows Logo for the system or device indicates which operating system versions the manufacturer supports for the system or device. The current, comprehensive listing of available logos is provided at http://www.microsoft.com/winlogo/hardware/.
Windows Logo Program requirements vary for different classes of products (for example, server, desktop, or mobile) and for different market segments (for example, enterprise server, commercial desktop, or consumer desktop). Where system design guides and other references refer to consumer and business PC system types, the following meanings apply for the Windows Logo Program:
Note: Test logs for Windows XP are required for all logos.
Dates for specific Windows Logo Program requirements are defined on the web at http://www.microsoft.com/winlogo/hardware/.
Windows Logo Program requirements become effective in these ways:
Operating System Support. Some requirements become part of the Windows Logo Program based on features in the operating system that the manufacturer preinstalls on the system.
For example, OnNow power management and multiple monitor support became Windows Logo Program requirements a few years ago when new support was introduced in Windows operating systems. These types of requirements depend on which operating system is preinstalled on the system. For example, in past years, a system with Windows NT 4.0 preinstalled was not required to fully support Windows Driver Model (WDM) requirements.
Industry Advances. Some technical requirements are market driven and take time to become broadly adopted because of cost or development time.
Based on industry feedback about time-to-market issues identified during the review cycle, these technical advances become part of the Windows Logo Program requirements on a timetable that the majority of the industry has agreed is technically possible and cost effective.
To plan for Windows Logo requirements based on new operating system features, participate in Microsoft design reviews and beta testing programs.
Version 2.1 of this document added the following new information:
Incorporation of design guideline references that previously quoted PC 2001 System Design Guide and Hardware Design Guide Version 3.0 for Microsoft Windows 2000 Server.
Extensive deletion of requirements that are no longer relevant because:
1) Version 2.0 excludes reference to requirements for Windows Me or Windows 2000;
2) Many capabilities or features are standard in the industry, and therefore do not merit reference in the Windows Logo Program requirements;
3) Some features are not tested in the “Designed for Windows” testing program, and so are no longer referenced in these requirements.
Version 2.1a of this document is an editorial release cleaning up the published edits of version 2.1 as well as some additional clarifications and corrections. No new requirements were added to version 2.1a.
In previous versions of this document, the detailed lists of WHQL tests in the “Quality” sections in Appendixes A and B were provided to help designers identify the test requirements related to a specific system or component. However, Microsoft now publishes the WHQL Test Specification, which provides extensive details about many tests in the HCT. In addition, the HCT documentation has been revised extensively to help designers and testers easily identify the test requirements for every system and component.
Therefore, the “Quality” sections now include only WHQL Test Specification and HCT documentation cross references, rather than lists of specific tests.
In addition, some requirements were erroneously included in the “Quality” sections in earlier drafts. These have been placed in correct locations under “Compatibility” and “Windows Experience” sections, with cross-references retained in their original locations.
System-related Requirement Notes
Unless otherwise noted, the requirements apply for all versions of the Windows operating system, and general system requirements apply to PC desktops, mobile PCs, and server systems.
General (lot. generalis - umumiy, bosh) - qurolli kuchlardagi harbiy unvon (daraja). Dastlab, 16-a.da Fransiyada joriy qilingan. Rossiyada 17-a.ning 2-yarmidan maʼlum. Oʻzbekiston qurolli kuchlarida G.
Mobile and Server Exceptions. In both the Mobile PC and Server sections in Appendix A, a specific list is provided of cross-references to exceptions for general device and system requirements. To view these lists, see:
A3.0 Mobile PC Client Requirements
A6.0 Server System Requirements
Client vs. Server Notations. Requirement titles clearly specify whether the item applies only for client PCs or servers. For example:
A1.4.2 x86-based client: System and all components correctly implement power management
A6.4.5 System that provides headless server capabilities meets minimum requirements
Windows Version Notations. Requirement titles clearly specify whether the item applies only for specific versions of Windows. For example:
B126.96.36.199 Windows Server 2003, Enterprise Edition: Data modem supports digital connection to support host-side V.90 operation
x86-based vs. Intel Itanium-based Notations. Requirement titles clearly specify whether the item applies only for 32-bit or 64-bit systems. For example:
A1.1.5 Multiprocessor system compatibility requirements
x86-based: Comply with ACPI 1.0b.
Itanium-based: Comply with Multiple APIC Description Table (MADT) in ACPI 2.0, Section 188.8.131.52.
Note: In earlier versions, the terms IA-32 and IA-64 were used to differentiate 32-bit and 64-bit systems.