Windows Logo Program
|
|  Yüklə 1.03 Mb.
|
B12.2 UPSAll general requirements in B1.0 are included by reference. All bus-specific requirements in B2.0 are included by reference. Note: This document assumes that the device will be run with Windows XP/Windows 2000; however, for devices that are designed to also run with Windows 98/Me, these items specify some requirements that are tested only under Windows 2000. B12.2.1 UPS - Windows CompatibilityB12.2.1.1 Windows XP/Windows 2000: "Human Input Devices" in the Windows DDK"UPS Applet for Windows 2000" at http://www.microsoft.com/hwdev/onnow/ups.htm B12.2.1.2 Windows compatibility and implementation noteshttp://www.microsoft.com/hwdev/onnow/ups.htm B12.2.1.3 Device drivers comply with Windows DDK requirementsSee “Overview of System Battery Management” and “BATTERY_INFORMATION” in the Windows DDK. Third-party applications implemented as defined in the Microsoft Platform SDK. B12.2.2 UPS - Industry StandardsSee B1.2. B12.2.3 UPS - QualityB12.2.3.1 SEE B12.2.4.5B12.2.3.2 Pass WHQL testsSee B1.3. Windows Whistler Server/Windows XP: See “UPS” in the HCT documentation. B12.2.4 UPS - Windows ExperienceDesign Guideline References: UPS Applet for Windows 2000 at http://www.microsoft.com/hwdev/onnow/ups.htm B12.2.4.1 Device can take over and properly notify the user that the device is on battery and/or shut down applications and the systemB12.2.4.2 Device load is measured accuratelyB12.2.4.3 Battery modules on larger units are hot swappableB12.2.4.4 Device can notify the user via email and/or pager that the power is downB12.2.4.5 Built-in functionality can properly support the deviceB12.2.4.5 Device can correctly compensate for voltage irregularitiesB12.2.5 UPS - FAQsSee http://www.microsoft.com/winlogo/hardware/unclassified/. B12.2.R UPS - Future RequirementsAnnouncement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/unclassified/. Appendix C - Designing for SuccessThis appendix presents a series of guidelines to help you ensure that your new designs are compatible with Microsoft operating systems, and to help you ensure the design meets Windows Logo Program requirements and passes all HCTs and other Windows Logo Program testing. Microsoft does not guarantee that complying with the Windows Logo Program requirements, or the related design guidelines provided in PC System Design Guide and similar publications, will ensure hardware or chipset compatibility with any versions of the Windows operating systems. Manufacturers who are designing new system or component hardware, chip sets, or firmware are encouraged to work directly with Microsoft to ensure compatibility of new designs. To do this, manufacturers should work with their Microsoft program manager or technical evangelist to arrange design reviews. If you are not working with Microsoft, please send mail to ihv@microsoft.com with "Program Contact Request" in the Subject line. Note that Microsoft cannot guarantee that it can schedule reviews for all manufacturer requests. Microsoft support to help manufacturers achieve device and application compatibility fall into these basic categories:
Microsoft provides the following guidelines for system and peripheral manufacturers to create hardware and drivers that are compatible with Windows operating systems and that meet Windows Logo Program requirements. Design Hardware for Windows CompatibilityDesign Using Current Information. Manufacturers can get up-to-date information about developing hardware and drivers for Windows: Know the Current Windows Compatibility Guidelines. Read and understand Guidelines for Bus and Device Specifications, a paper that clarifies what Windows needs from hardware so it can interoperate successfully: http://www.microsoft.com/hwdev/issues/SpecGuide1.htm
Check the web site for Hardware and Driver Developers. This web site provides tools, information, and services for driver developers and hardware designers who create products that work with the Microsoft Windows family of operating systems: http://www.microsoft.com/hwdev/ Submit Hardware Prototypes and New Systems and Devices to Windows Labs. Systems that pass testing in the Windows test labs receive the “compatible” designation on the Hardware Compatibility List. For information, write to: wintrack@microsoft.com. Participate in Plugfests. Microsoft Plugfests, Meltdown compatibility testing, and industry events such as USB Implementers Forum Plugfests help identify firmware and driver issues. Request Early Technical Design Reviews. Contact your Microsoft program manager or technical evangelist to request a technical review for new chipset or system designs; Microsoft architects can work with you in early phases to identify issues and ensure optimal design.
Design for the Windows Logo ProgramUse the Windows Logo Program Requirements as a Design Guide. Confirm that all hardware and software components comply with the Windows Logo Program guidelines to ensure that all components in the system work together to provide the optimal end-user experience under Windows. Use the WHQL Test Specification as a Design Guide. The WHQL Test Specification defines the precise test assertions that are validated by the HCTs. Study the WHQL Test Specification to understand exactly what portions of industry specifications and DDK driver guidelines are required in the compatibility tests. Use the HCTs to Design for Compatibility. Use the HCTs in your product test suites to ensure compatibility as part of your development process. Manufacturers can get current and beta versions of HCTs and WHQL Test Specifications. Attend Microsoft Review Events for the Industry. Microsoft offers design reviews, the Windows Hardware Engineering Conference (WinHEC), and other events to provide system planners and designers with technical information to help keep their products in sync with Windows system and component architectures. Some events are by invitation only. Review and Comment on Proposed New Requirements:
Participate in Industry Standards Efforts. Microsoft bases new capabilities in the operating system on industry standards and specifications. Participate in the industry forums, and in committees that develop strategic specifications and interfaces. Design for Performance and Legacy Reduction:
Develop, Test, and Distribute Compatible Windows DriversDevelop Drivers Based on Windows DDK:
Use the Current DDK. Receive the Windows DDK as part of the beta release, or download from the web: http://www.microsoft.com/ddk/ Test to Ensure a Smooth Upgrade Path. Your test matrix should include upgrading your shipping client PC systems to Windows XP, which will help to identify constraints that might prevent a smooth transition for your customers. Run Regular, Complete Testing Suites. Use the tools and guidelines from Microsoft to ensure that your testing suites exercise all the operating system features and functions used by your hardware and drivers. Run test tools on a regular basis to ensure drivers are free of errors. Submit Bugs and Follow Up with Microsoft. Use the reporting mechanism defined in the beta package. Ensure Users Can Get BIOS and Driver Updates
|