• A1.1.2.3 Windows driver support: “Power Management” in the Windows DDK.
  • A1.1.4 System BIOS requirements
  • A1.1.4.2 DELETED
  • Microsoft Windows Logo Program System and Device Requirements




    Download 0.89 Mb.
    bet32/188
    Sana21.03.2017
    Hajmi0.89 Mb.
    #429
    1   ...   28   29   30   31   32   33   34   35   ...   188
    Mobile PC Note
    Mobile PCs are required to support S1 or S3, in addition to S4 and S5. Mobile PCs are not required to wake from S3 or S4.

    Server Note
    Server systems are not required to support wake from D3. At a minimum, SOHO servers must support S1.

    A1.1.2.2.3 If software fan control is implemented, thermal design and fan control comply with ACPI 1.0b. A thermal model and fan control must be implemented as defined in Section 12 of the ACPI 1.0b specification as a means of running the PC quietly while it is working and of turning the fan off while it is sleeping. Notice that hardware override is permitted only to handle thermal conditions when the operating system is not running, the operating system has put the system in a sleep state, or safe operating parameters have been exceeded.


    A1.1.2.3 Windows driver support: “Power Management” in the Windows DDK.

    See Appendix B for device class-specific requirements for power management in drivers.
    A1.1.3 All components correctly implement Plug and Play

    A1.1.3.1 Each bus and device provided in a system must meet the current Plug and Play specifications related to its class, including requirements defined in Section 6 of the ACPI 1.0b specification and clarifications published for some Plug and Play specifications. This guideline includes requirements for automatic device configuration, resource allocation, and dynamic disable capabilities.

    A1.1.3.2 Any legacy components remaining in a legacy-reduced system must meet the requirements defined in Legacy Plug and Play Guidelines.

    PCI components implement System IDs (SIDs) and Subsystem Vendor IDs (SVIDs) as defined in "Specification for Use of PCI IDs with Windows Operating Systems" at http://www.microsoft.com/hwdev/bus/pci/pciidspec.asp.

    For Windows XP, SIDs and SVIDs are not required for PCI-PCI bridges and some other core chipset classes. For the specific list of exceptions, see Appendix D of PCI 2.2.


    A1.1.4 System BIOS requirements

    For complete Itanium-based firmware requirements, see A5.0.
    A1.1.4.1 Correctly configure PCI-to-PCI bridges if the system has a VGA device behind a bridge.

    The system BIOS must correctly configure PCI-to-PCI bridges if the system has a VGA device behind a bridge. Specifically, the BIOS must correctly set the VGA Enable and ISA Enable bits on the bridges, to avoid causing the bridges to be in conflict with each other. See http://www.microsoft.com/hwdev/bus/pci/pcibridge-cardbus.asp
    A1.1.4.2 DELETED
    A1.1.4.3 Support booting from CD or DVD device per El Torito v. 1.0 No Emulation mode.

    BIOS supports booting the system from CD or DVD. The system BIOS or option ROM must support the No Emulation mode in “El Torito”—Bootable CD-ROM Format Specification, Version 1.0, by IBM and Phoenix Technologies, for installing Windows from optical media, such as bootable CD media.

    The primary optical device must be bootable. This applies to the primary optical storage provided and the primary bus to which the device is attached.


    A1.1.4.4 Windows XP Professional desktop/Windows Server 2003: Support Preboot Execution Environment (PXE) based on PXE Specification, v. 2.1:

    A1.1.4.4.1 x86-based servers: Provide PXE-based support if a network adapter with remote boot capabilities is provided with the system.

    A1.1.4.4.2 x86-based Windows Professional desktop and Itanium-based clients: Provide PXE-based support in all cases.





    Download 0.89 Mb.
    1   ...   28   29   30   31   32   33   34   35   ...   188




    Download 0.89 Mb.

    Bosh sahifa
    Aloqalar

        Bosh sahifa



    Microsoft Windows Logo Program System and Device Requirements

    Download 0.89 Mb.