ࡱ> ` bjbj N A%IXHn+>l<>Dz^R=======$@hiB=-<<=4=B==fxJ }kV$~*=0+>HCmCHJCbRRRR==SHRRR+>nnnQDBnnnQ&" Hardware Design Guide Version3.0forMicrosoft Windows2000Server A Reference for Designing ServersandPeripherals for the MicrosoftWindows2000 Server Familyof OperatingSystems Intel Corporation and Microsoft Corporation Publication DateJune 30, 2000 The information contained in this document represents the current view of Intel Corporation and Microsoft Corporation on the issues discussed as of the date of publication. Because Intel and Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Intel and Microsoft, and Intel and Microsoft cannot guarantee the accuracy of any information presented. This document is for informational purposes only. INTEL AND MICROSOFT MAKE NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Intel Corporation and Microsoft Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property rights. Intel and Microsoft do not make any representation or warranty regarding specifications in this document or any product or item developed based on these specifications. Intel and Microsoft disclaim all express and implied warranties, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and freedom from infringement. Without limiting the generality of the foregoing, Intel and Microsoft do not make any warranty of any kind that any item developed based on these specifications, or any portion of a specification, will not infringe any copyright, patent, trade secret, or other intellectual property right of any person or entity in any country. It is your responsibility to seek licenses for such intellectual property rights where appropriate. Intel and Microsoft shall not be liable for any damages arising out of or in connection with the use of these specifications, including liability for lost profit, business interruption, or any other damages whatsoever. BackOffice, DirectShow, DirectX, Microsoft, MSDOS, NetShow, Win32, Win64, Windows, Windows NT, and the Windows logo are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Intel and Pentium are registered trademarks, and Intel486, Itanium, MMX, and Xeon are trademarks of Intel Corporation. Other product and company names herein may be the trademarks of their respective owners. 19972000 Intel Corporation and Microsoft Corporation. All rights reserved. This document is not for sale. Review copies are provided to individuals who register by completing the reviewer request form at http://www.microsoft.com/hwdev/serverdg.htm. To obtain additional copies of this final version of this document, please download the source files from the web sites at http://developer.intel.com/design/servers/desguide/index.htm or http://www.microsoft.com/hwdev/serverdg.htm. Contents Welcome v Broadening of Coverage for Large Systems vi Future Technology Directions vi Legacy Reduction and Removal ix How to Use This Guide x Conventions Used in This Guide x Conventional Terms x Required vs. Recommended Features in This Guide xi Requirements by Server Class and Operating System Product xii References and Resources xiii Hardware Design Guide Compliance and Testing Programs xiii Information Resources and Technical References xiv Acknowledgments xix Chapter 1 Overview of Server DesignIssues 1 Introduction to Design Issues 1 Server Classes and Operating System Editions 3 Designing Systems for Windows2000 Server 4 ACPI and OnNow Design 5 IA-32 vs. IA-64 Design 6 ACPI 1.0b vs. ACPI 2.0 6 Boot and Firmware Support: BIOS vs. EFI 7 IA-32 vs. IA-64 Miscellaneous Design Issues 7 Chapter 2 System Component Requirements 8 General Component Requirements 9 System Microprocessor Requirements 9 Memory Requirements 11 ACPI and Power Management Requirements 13 Startup Support Requirements 19 Plug and Play Requirements 25 Headless Server Requirements 27 Other Requirements 31 Chapter 3 Bus and Device Requirements 33 I/O Bus Requirements 33 USB Requirements 43 Other Bus Requirements 45 Device Requirements 47 Chapter 4 Networking and Communications Requirements 55 Network Adapter Requirements 56 Connectionless Networking Requirements 62 Modem Requirements 64 Unimodem-supported Modem Requirements 65 ATM Adapter Requirements 69 ADSL Device Requirements 72 Cable Modem Requirements 74 ISDN Requirements 75 IrDA Communications Requirements 79 Wireless Networking Requirements 80 Chapter 5 Storage Device Requirements 82 Storage Device General Requirements 82 SCSI Controllers and Peripherals 86 ATA Controllers and Peripherals 89 Fibre Channel Controllers and Peripherals 92 Erasable Disk Drives 93 CD and DVD Drives 93 CD Drive Requirements 94 DVD Drive Requirements 95 Backup Devices 98 Media Changers 99 CD Changers 99 Tape and Optical Disk Changers 99 Chapter 6 Physical Design and Hardware Security Requirements 101 Physical Design Requirements 101 Hardware Security Requirements 104 Chapter 7 Reliability, Availability, and Serviceability Requirements 106 Backup and Reliability Requirements 106 Backup Hardware 106 Power Supply 106 Fault-Tolerant Hardware 108 Serviceability Requirements 109 High Availability Requirements 110 Manageability Baseline Requirements 112 General Manageability Baseline Requirements 112 Manageability Component Instrumentation Requirements 113 Appendix A Server Requirements Checklist 116 IA-32 Server Requirements Checklist 116 IA-64 Server Requirements Checklist 132 Glossary 148 Index 157 Welcome Hardware Design Guide Version 3.0 for Windows 2000 Server is for engineers whobuild server systems, expansion cards, and peripheral devices that use the Microsoft Windows2000 Server (and later) operating system. This guide is co-authored by Intel Corporation and Microsoft Corporation. Therequirements and recommendations in this guide indicate features that the hardware industry should consider in designing servers and peripherals for various price levels and performance levels. This guide includes design guidelines for servers that will run any version of the Windows2000 Server or later operating systems, including the next release of Windows, code-named Windows Whistler. These guidelines address the following design issues: Features for basic commodity server design alternatives for small office/home office (SOHO) and Enterprise servers. Requirements for implementing the OnNow design initiative, including those related to the Advanced Configuration and Power Interface (ACPI) specification, Plug and Play device configuration, and power management in server systems. Implementation of devices supported under Windows 2000 Server. Manageability features that help to reduce total cost of ownership (TCO) under Windows 2000 Server by providing support for maximum automation of administrative tasks with centralized control and maximum flexibility. Important: Implementing these guidelines results in servers that deliver an enhanced user experience with the Windows2000 Server or later family of operating systems. These requirements are not related to the minimum, most-optimal, or best system requirements for running any version of the Windows2000 Server operating systems. For information about the minimum system requirements for running Windows2000 Server, see http://www.microsoft.com/windows2000/guide/server/sysreq/. Broadening of Coverage for Large Systems In previous versions of Hardware Design Guide for Microsoft Windows NT Server, the guide encompassed the standard high volume server with up to and including four processors in a symmetric multiprocessing configuration. However, systems with up to eight processors are now shipping from many vendors. Due to this broadening of the standard high volume server market, systems with up to eight processors are now included in the servers that are covered by the Hardware Design Guide Version 3.0. As previously stated, there is no one to one mapping of the number of processors in a server to a specific server class or usage model (for example, one could certainly have a SOHO Server with more than one processor); however, in general, it is anticipated that most servers with four or more processors will be most likely viewed as designed to the Enterprise Server system considerations. Future Technology Directions The standard high volume server is evolving rapidly to meet the pace of customer expectations for ever-increasing reliability, availability, serviceability, scalability, usability, and manageability. These increasing customer expectations for the abilities on industry-standard servers mean that future versions of the Hardware Design Guide for servers must address ever more complex topics. This section of the document is meant to provide some vision into what those future directions might be and to invite feedback from the industry on these topics. Feedback is also requested for any other issues and topics that should be addressed in the quest for servers that can achieve the highest possible levels of uptime and functionality for any particular segment of server usage. (It is recognized that the balance of cost against features is also an important part of this analysis.) Some of topic areas that are seen as future work areas for the Hardware Design Guide for servers include: ACPI 2.0 and its facilitation of capabilities such as hot plug of processors, memory, and I/O subsystems, as well as system partitioning. System capabilities to isolate failing components at boot time. The concept of fault domains, both at system startup and, where possible, at run time. Future advancements in I/O bus technologies and architectures. Much exciting work is ongoing in the realm of I/O bus technologies. Future design guides will undoubtedly provide specific requirements and recommendations for each technology area. However, early implementers and adopters of all new bus technologies must comply with all relevant bus specifications, including bus and device power management specifications, for each specific technology as they become available. Additionally, for servers running a Windows 2000 Server family operating system, new bus technologies and devices must comply with the relevant general-case guidelines for devices and drivers as articulated in the Hardware Design Guide for servers. Enhancements to support for Fibre Channel in Windows operating systems. As Fibre Channel adoption continues to grow, Microsoft is seeking feedback and input from the industry on the enhancements needed to best support this storage channel in Windows 2000 operating systems. Guidelines relating to use of any enhanced Fibre Channel capabilities in Windows operating systems will appear in future versions of the Hardware Design Guide for servers. Use of flash memory as an emergency boot/recovery file system. With the advent of the Windows 2000 Recovery Console, system designers may want to consider providing an area of flash memory as an alternate boot device for use with the Recovery Console as an emergency recovery aid. The Recovery Console provides secure local access to Windows 2000 installations on a specific system, and is NTFS-aware, eliminating the need for Microsoft MS-DOS as a system maintenance or recovery tool. Multi-pathing for storage and network connections. As part of the efforts to increase platform reliability and availability, eliminating single points of failure wherever possible is extremely valuable. Two areas of future opportunity are allowing multiple paths to storage and network connections from servers. Future versions of the Hardware Design Guide for servers will provide guidelines on how to implement these capabilities with future Windows operating systems. Advanced usage and support of the Windows 2000 NMI crash dump capture capability. A clarification to guideline #222. IA-32 system includes protected forced dump switch or other mechanism for system diagnosis provides some detailed information on the Windows 2000 capabilities to capture crash dump information on nonmaskable interrupts (NMI). One way to take advantage of this feature is in hung system debugging where a crash capture is triggered via a switch that produces an NMI signalthe technique called out in the guideline previously cited. However, this capability can also be tied to other platform health monitoring capabilities as well. Some possible areas where this feature could be further leveraged would be in the case where a platform health watchdog timer was present. If a watchdog circuit and associated platform management determine that the host platform was in a hung state, the watchdog circuit could, as part of the recovery process, ensure that an NMI was asserted to cause a system dump prior to resetting or restarting the system. This process would be a part of root cause analysis support. Increasingly sophisticated uses of this feature with various forms of remote platform management can also be envisioned; one example might be allowing this feature to be available to system administrators monitoring platform health via remote out-of-band management connections. Other future areas of growth include support for a similar type of capability on 64-bit platforms. Enhanced platform health monitoring capabilities. Customers also have increasing expectations in the area of platform health monitoringboth in terms of monitoring the status of the platform and of its physical health, such as internal temperatures, chassis intrusion, fan status, predictive failure analysis, and so on. With the Windows Management Instrumentation (WMI) infrastructure in the Windows family of operating systems, providing such enhanced platform health and monitoring capabilities is made simpler. Future versions of the design guide will continue to enhance requirements and recommendations in these areas. Run-time diagnostics capabilities. Another core WMI capability is the ability to flag data as expensive to collect, which provides a simple mechanism to allow run-time diagnostic capabilities. Future versions of the Hardware Design Guide for servers may have additional requirements and recommendations as to the use of these capabilities for enhanced platform self-diagnosis and system health monitoring. Enhancements to remote management capabilities. As industry standard servers running Windows family of operating systems increase their penetration to many more environments with high reliability and availability requirements, customer demands and expectations are increasing for remote management and manageability of these systems. Certain key capabilities that are being addressed in this version of the Hardware Design Guide for servers, and that will likely be enhanced in future versions, include requirements for headless (that is, without a local display, keyboard, or pointing device) operations. Some of the concerns that will need to be addressed to fully support headless operation include: Remote power on and reboot capabilities Redirection of pre-operating system firmware displays, such as a pre-operating system BIOS boot or setup screen Remoteable screen displays for system startup, normal operation, and crash/error recovery Fully-remoteable access to platform management data while the operating system is running, as well as while it is not As with all of these technology areas, feedback and input from the industry on directions in these areas are actively requested for future Hardware Design Guides for servers. Other future areas of growth include support for a similar type of capability on Intel Architecture (IA)-64 platforms. EFI on IA-32 systems. Extensible Firmware Interface (EFI) is a requirement for IA-64 systems, but there is interest from many in the server industry in using EFI as a choice for the firmware model on IA-32 platforms as well. Future versions of the Hardware Design Guide are likely to address requirements for IA-32 systems that wish to use EFI with Windows. Emergence of new server segments. As servers based on industry-standard technologies continue to be deployed more broadly and in support of new tasks, new server designs are emerging. Some of the considerations for these new segments include form factor, consolidation of field-replaceable units, and general physical design issues. Some of these new segments may diverge in some of their serviceability/availability requirements from the standard high volume servers currently addressed by the Hardware Design Guide. Intel and Microsoft welcome and invite input from the industry on the new server segments, and on issues that are pertinent for their design and may need to be considered in future versions of the Hardware Design Guide. Legacy Reduction and Removal The PC platform that is part of the heritage of todays server systems has evolved by adding and retaining technologies. As a result, the evolution and history cycle for many technologies imposes a burden that impacts cost, performance, and supportparticularly in the server marketplace where PC legacy items reduce the advantages brought by newer technologies. These legacy technologies are present in hardware, firmware, BIOS code, and operating systems. The Hardware Design Guide for Windows 2000 Server continues to address the transition to newer technologies with the introduction of alternatives to serial port based debug for IA-32 platforms, Universal Serial Bus (USB), and other technologies.. In the future, more guidelines will be published to facilitate the continuing migration of older technologies out of the server platform. Intel and Microsoft welcome and invite input from the industry on legacy reduction in servers, and on issues that may need to be considered in future versions of the Hardware Design Guide. How to Use This Guide Read the first chapter for an overview, and read Chapters 2 and 3 to gain an understanding of the overall system requirements. Study the other chapters to understand details about specific device classes and issues for server hardware. ChapterContentsChapter 1: Overview of ServerDesign IssuesPresents overview of server classes and design issues.Chapter 2: System Component RequirementsPresents general system requirements.Chapter 3: Bus and Device RequirementsPresents general bus and device requirements for server systems.Chapter 4: Networking and Communications RequirementsDefines basic feature requirements for network adapters and other related communications hardware. Chapter 5: Storage DeviceRequirementsDefines requirements for controllers, hard drives, tapedrives, CD drives, and related devices.Chapter 6: Physical Design and Hardware Security RequirementsDefines requirements for physical design and hardware security, such as requirements for connectors, case and component locks, and so on.Chapter 7: Reliability, Availability, and Serviceability RequirementsProvides design guidelines related to ease of use and ease of maintenance issues. Appendix A: Server Requirements ChecklistProvides a summary checklist of requirements defined in these guidelines.GlossaryDefines technical terms and acronyms related to hardware and Windows operating systems. As co-authors of this design guide, Intel and Microsoft provide clarification and interpretation of the requirements and recommendations in this document. Please send questions or requests for clarification by e-mail to: designguide@intel.com serverdg@microsoft.com Conventions Used in This Guide The following conventional terms, symbols, abbreviations, and acronyms are used throughout this guide. In addition, see the Glossary later in this guide. Conventional Terms Add-on devices Devices that are traditionally added to the base server system to increase functionality, such as audio, networking, graphics, and so on. Add-on devices fall into two categories: devices built onto the system board set and devices on expansion cards added to the system through a system-board connector such as Peripheral Component Interconnect (PCI). Intel Architecture, IA-64, and IA-32 Refers to computers based on 64-bit and 32bit microprocessors that use the Intel Architecture instruction set, such as Intel Pentium, Intel Pentium with MMX technology, Pentium Pro, Pentium II, Pentium II Xeon, Pentium III, Pentium III Xeon, Itanium, or compatible processors. System devices Also on-board devices. Refers to devices on the system board set such as interrupt controllers, keyboard controller, real-time clock, direct memory access (DMA) page registers, DMA controllers, memory controllers, floppy disk controller (FDC), AT-Attachment (ATA) ports, serial and parallel ports, PCI bridges, and so on. In todays servers, these devices are typically integrated with the supporting chipset. Windows 2000 or Windows2000 Server Refers to the Microsoft Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 Datacenter operating system, including any add-on capabilities and any later versions of these operating systems. The following describes the product name changes for operating systems based on Windows NT technology offered after Windows NT 4.0. Old New Windows NT Windows 2000 Windows NT Server Windows 2000 Server Windows NT Server, Enterprise Edition Windows 2000 Advanced Server (no equivalent) Windows 2000 Datacenter Server For a list of acronyms and definitions of technical terms, see the Glossary later in this guide. Required vs. Recommended Features in This Guide The system requirements defined in this publication provide guidelines for designing servers that deliver an enhanced user experience when implemented with Windows2000 Server. These design requirements are not the basic system requirements for running the Windows2000 Server operating system. In this guide, hardware features are described as Required, Recommended, or Optional as follows: Required. These basic hardware features must be implemented in order for hardware to qualify as being in compliance with Hardware Design Guide Version 3.0 for Windows 2000 Server requirements. Recommended. These features add functionality supported by the Windows2000 operating system. Recommended features take advantage of the native capabilities of hardware device drivers included with the operating system, usually without imposing major cost increases. Notice that for compliance testing, if a recommended feature is implemented, it must meet the requirements for that feature that are defined in this guide. Some recommended features could become requirements in the future. Optional. These features are neither required nor recommended, but if the feature is implemented in a system, it must meet the specified requirements to be in compliance with these guidelines. These features are not likely to become requirements in the future. In this guide, the following terms are used in regard to the requirements: Must: Required Should: Recommended Note: It is recognized that original equipment manufacturers (OEMs) supply systems with specific feature requirements to corporations, where customers integrate the desired solution on site. For example, a customer could specify a minimum configuration without disk drives. Systems designed for specific corporate customers are exempt from related minimum requirements defined in this guide. Such exemptions are noted in this document. However, for compliance testing of these requirements, the system must include at least the minimum required components. Requirements by Server Class and Operating System Product Requirements for four different Windows2000 operating system products and three server classes are designated in these guidelines. The operating system products include: Microsoft Windows 2000 Server Microsoft Windows 2000 Advanced Server and Microsoft Windows 2000 Datacenter Server Microsoft Small Business Server (formerly known as Microsoft BackOffice Small Business Server) The server classes in this guide are the same as in Hardware Design Guide Version 2.0: Basic Server, Enterprise Server, and SOHO Server. (For more information, see Chapter1, Overview of Server DesignIssues.) For ease of use in this guide, Basic, SOHO, and Enterprise class requirements are all defined together in the main body of the document, rather than in separate chapters. Any class of server can run any server operating system product. Furthermore, there are no direct relationships that define which operating system product can or should run on each specific class of server. However, server platforms might need to meet additional requirements to meet the goals of a specific server class or to be a good target platform for a specific operating system. The following examples show the format for differentiating server class-specific or operating system-specific requirements in this guideline. The first example is the simplest, where the requirement (or recommendation) applies to all classes of servers and all operating systems. Ex.1. System and components support dates beyond 2000 Required The BIOS, real time clock, CMOS, and the system as a whole must work correctly for dates from now to past the year 2000. The second, more complex example presents specific requirements for different server classes and operating system products. The server types are defined in the left column, and the column headings designate specific operating system products. Ex. 2. System includes intelligent RAID controllerWindows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedSOHO:OptionalRequiredOptionalEnterprise:RequiredRequiredRequiredAn intelligent Redundant Array of Independent Disks (RAID) controller provides the benefit of reduced demands on the host processor or processors. References and Resources The following represents some of the information resources, services, and tools available to help build hardware optimized to meet the requirements defined in this guide. This section also lists technical references for the specifications cited in this guide. Hardware Design Guide Compliance and Testing Programs A specific hardware model is compatible with Windows2000 if it has a Windows2000 device driver designed to interact with that hardware model, and if Windows2000 and that driver interoperate with the hardware in a stable manner. Hardware Compatibility Tests (HCTs). Microsoft evaluates hardware compatibility using the Windows2000 HCTs, which are run to test the interaction between device drivers and hardware. These tests issue the full range of commands available to applications and operating system software, and they stress hardware beyond the level of most real-world situations. The Windows2000 HCT team runs the tests and reports results to the manufacturer. You can obtain a Windows2000 HCT kit from the Windows Hardware Quality Labs (WHQL) web site at http://www.microsoft.com/hwtest/testkits/. Hardware Compatibility List (HCL). Hardware that passes the HCTs is eligible to be included on the Windows2000 HCL, available to customers by way of the World Wide Web and other sources. The HCL helps interested parties identify hardware and software that has been verified to run on Windows2000 Server. WHQL administers the hardware compliance testing programs at Microsoft. Hardware developers whose products pass the WHQL testing program receive adetailed report about how the system runs Windows 2000 Server based on the results of the testing. Hardware that passes testing is included on the Windows HCL at http://www.microsoft.com/hcl/. Compliance Dates. Typically, these hardware design requirements go into effect on July1, 2001, and are applicable to servers that are designed and built after this documents initial publication date. Compliance testing for some requirements may begin later because of the time required for technology changes to become widely available. For information about actual compliance testing dates for specific requirements, or about any of the hardware testing programs at Microsoft, contact WHQL: Windows Hardware Quality Labs Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399 USAhttp://www.microsoft.com/hwtest/ E-mail: whqlinfo@microsoft.com Fax: (425) 703-3872 Information Resources and Technical References Server Design Information from Intel and Microsoft Information from Intel. Additional information relating to server hardware design is available from Intel Corporation at: http://www.intel.com/ebusiness/server/resources/index.htm http://developer.intel.com/platforms/enterprise/ E-mail: designguide@intel.com Information from Microsoft. Additional information about related hardware design guide issues and Windows2000 Server hardware is available from the Microsoft web sites at: http://www.microsoft.com/hwdev/ http://www.microsoft.com/Windows2000/guide/server/ E-mail: serverdg@microsoft.com Information Resources Common Information Model (CIM) http://www.dmtf.org/work/cim.html Distributed Management Task Force (DMTF) http://www.dmtf.org Intel developer information http://developer.intel.com Microsoft hardware developer information http://www.microsoft.com/hwdev/ Microsoft Developer Network (MSDN) Professional membership http://msdn.microsoft.com/subscriptions/ Microsoft Windows Hardware Quality Labs http://www.microsoft.com/hwtest/ Technical References 1394 Open Host Controller Interface Specification, Release 1.1 http://www.microsoft.com/hwdev/1394/download/ohci_11.zip http://developer.intel.com/technology/1394/download/ohci_11.htm 1999 Version of National ISDN Basic Rate Interface Terminal Equipment Generic Guidelines, Document Number SR4620 http://www.telcordia.com/ Advanced Configuration and Power Interface Specification, Version 1.0b http://www.teleport.com/~acpi/ Version 2.0 will also be published here when released ANSI NCITS T10 Multi-Media Command Set-2 ATA/ATAPI-5 Standard ATA Packet Interface for CD-ROM, SFF 8020i Other SFF publications Global Engineering Documents http://global.ihs.com/ ATAPI Removable Media BIOS Specification (ARMD) http://www.ptltd.com/techs/specs.html ATM User-Network Interface Specification, Version3.1 Prentice Hall, 1995; ISBN 0-13-393828-X http://www.atmforum.com/atmforum/specs/approved.html Boot Integrity Services (BIS) API, Version 1.0 http://developer.intel.com/ial/wfm/wfmspecs.htm Compaq, Intel, Phoenix BIOS Boot Specification, Version 1.01 (CIP BIOS Boot 1.01) http://www.ptltd.com/techs/specs.html Data-Over-Cable Service Interface Specification (DOCSIS) http://livelink.cablelabs.com/Livelink/ livelink.exe?func=ll&objId=49623&objAction=browse&sort=name http://www.cablelabs.com/ Debug Port Specification http://www.microsoft.com/hwdev/NewPC/debugspec.htm Desktop Management Interface Specification, Version 2.0 DMI Compliance Guidelines, Version 1.0 http://www.dmtf.org/tech/specs.html Device Class Power Management Specifications http://www.microsoft.com/hwdev/specs/PMref/ DSL Architecture: An Interoperable End-to-End Broadband Service Architecture over ADSL System http://www.microsoft.com/hwdev/network/dsl/ DVD Specification, Version 1.0, Toshiba Corporation. http://global.ihs.com El Torito Bootable CDROM Format Specification, Version 1.0 http://www.ptltd.com/techs/specs.html EPS Power Supply: A Server System Infrastructure (SSI) Specification for Entry Chassis Power Supplies http://www.ssiforum.org/docs/entrylevelpowersupply.pdf European Telecommunications Standards Institute (ETSI) or Global System forMobile (GSM) standards Phone: +33-92 94 42 00 FAX: +33-93 65 47 16 E-mail: secretariat@etsi.fr Extensible Firmware Interface Specifications http://developer.intel.com/technology/efi/download.htm http://www.microsoft.com/hwdev/efi/ Extensions to VT100 Terminal Definition To be published at http://www.microsoft.com/hwdev/headless/ Fibre Channel Physical (FCPH), Revision4.3 http://www.fibrechannel.com I2O (Intelligent I/O) Architecture Specification, Version 1.5 http://www.intel.com/design/iio/i2osig.htm http://www.i2osig.org (special interest group) IBM Personal System/2 Common Interfaces, Part No. S84F-9809 IBM Personal System/2 Mouse Technical Reference, Part No. S68X-2229 International Business Machines Corporation IBM Customer Publications Support: (800) 879-2755 Or contact an IBM sales representative IEEE 1394 Standards http://standards.ieee.org/catalog/ InfiniBand Trade Association http://www.sysio.org Interoperability Specification for ICCs and Personal Computer Systems http://www.pcscworkgroup.com/ ITU Communications Standards Phone: (41) (22) 730-6141 Fax: (41) (22) 730-5194 E-mail: sales@itu.ch http://www.itu.ch Legacy Plug and Play Guidelines http://www.pcdesguide.org/legacypnp/ MCNS Documents http://www.cablemodem.org Media Status Support Notification, Version 1.03 http://www.microsoft.com/hwdev/respec/storspec.htm Microsoft Extensible Firmware Interface FAT32 File System Specification, Microsoft Extensible Firmware Interface Long File Name Specification, Microsoft Portable Executable and Common Object File Format Specification, plus other EFI-related specifications and guidelines http://www.microsoft.com/hwdev/efi/ Microsoft Platform SDK, including Win32 and Win64"! APIs http://msdn.microsoft.com/downloads/sdks/platform/platform.asp Also provided through MSDN Professional subscription Microsoft Windows 2000 Driver Development Kit (DDK) http://www.microsoft.com/ddk/ Also provided through MSDN Professional subscription Microsoft Windows Hardware Compatibility List (HCL) http://www.microsoft.com/hcl/ MMC-2 Multi-Media Command Set-2 standard ftp://ftp.t10.org/t10/drafts/mmc2/mmc2r11a.pdf MultiProcessor Specification, Version 1.4 http://developer.intel.com/design/intarch/MANUALS/242016.htm NCITS Reduced Block Commands Standard http://www.ncits.org/standards/standards.htm OnNow and ACPI implementation guidelines under Windows operating systems http://www.microsoft.com/hwdev/onnow/ Open Host Controller Interface (OpenHCI) Specification for USB, published by Compaq, Microsoft, and National Semiconductor http://www.microsoft.com/hwdev/respec/busspecs.htm OSTA MultiRead Specification for CDROM, CDR, CDR/RW, and DVDROM Devices, Version 1.11 http://www.osta.org/html/mrspec.html PCI Bus Power Management Interface Specification, Revision 1.1 PCI Hot-Plug Specification, Revision 1.0 PCI Local Bus Specification, Revision 2.2 (PCI 2.2) PCI to PCI Bridge Specification, Revision1.1 PCI-X Addendum to the PCI Local Bus Specification, Revision 1.0 http://www.pcisig.com/members/ http://www.pcisig.com/tech/availspecs.html Plug and Play specifications http://www.microsoft.com/hwdev/respec/pnpspecs.htm Preboot Execution Environment (PXE) Specification, Version 2.1 http://developer.intel.com/ial/wfm/wfmspecs.htm RS-IA-64 System Abstraction Layer (SAL) Specification, Revision 2.7 http://developer.intel.com/design/ia-64/downloads/245359.htm Serial Port Console Redirection Table To be published at http://www.microsoft.com/hwdev/headless/ Simple Boot Flag Specification, Version 1.0 http://www.microsoft.com/hwdev/desinit/simp_bios.htm System Management BIOS Reference Specification, Version 2.3 http://www.phoenix.com/products/specs-smbios.pdf Unimodem Diagnostics Command Reference SpecificationDraft http://www.microsoft.com/hwdev/respec/commspec.htm Universal HCI (UHCI) Specification, published by Intel http://developer.intel.com/design/usb/ Universal Serial Bus, Version 1.1 or later Universal Serial Bus PC Legacy Compatibility Specification, Version 0.9 USB Device Class Definition for Mass Storage Devices and other USB device class specifications http://www.usb.org/developers/docs.html Universal Disk Format Specification, Version 1.5 and 2.0 http://www.osta.org Web-Based Enterprise Management (WBEM) information http://www.dmtf.org/ Windows Hardware Instrumentation Implementation Guidelines, Version1.0 http://www.pcdesguide.org/whiig.htm Windows Management Instrumentation (WMI) and Win32 Extensions schema http://msdn.microsoft.com/downloads/sdks/wmi/ http://www.microsoft.com/hwdev/wmi/ Windows NT Removable Storage Manager Programming Documentation http://msdn.microsoft.com/library/psdk/zaw/proguide_912q.htm Wired for Management Baseline Specification Version 2.0 http://developer.intel.com/ial/wfm/ Acknowledgments Microsoft and Intel would like to acknowledge the special contributions of the following companies to this document: Compaq Computer Corporation Dell Computer Corporation Fujitsu Siemens Computers Hewlett-Packard Company International Business Machines Corporation NEC Corporation Chapter 1 Overview of Server DesignIssues This chapter is an introduction to the system classes and issues related to serverhardware guidelines for systems designed to work with the Microsoft Windows2000 Server family of operating systems. This document addresses design issuesfor commodity servers; in general, these servers contain up to eight microprocessors and use a variety of industry-standard technologies. Introduction to Design Issues The intent of this guide is to provide information about designing servers, hardware, and software that take best advantage of the Windows2000 Server operating system. This guide represents a collection of system definitions and requirements for bus and device design. The requirements and recommendations emphasize features and attributes of a system that can perform extremely well under Windows2000 Server. These guidelines emphasize the following areas: Performance. The ideal way to specify performance capabilities would be to specify performance against specific benchmark tests. However, the available benchmark tests do not allow directly comparing systems unless tests are conducted with identical client setup and software configurations, which are not currently defined. Wherever possible, requirements in this guide are defined according to the benchmark performance goals. When reliable benchmark tests are not available, specific hardware configurations are defined for servers so they achieve the performance capabilities necessary to meet the requirements defined in this guide. Reliability. To fulfill its function, the server system must run all the time, with fault-tolerance capabilities and features that smoothly replace a failed drive. High availability is an extremely important feature for all servers, although this feature can be manifested differently according to how the server is used. However, certain baseline goals are desirable for each class of server, so various elements of these requirements address reliability and high-availability needs for servers. Robustness and capacity. For many server applications, good scalability and serviceability become extremely important. This guide specifies some requirements related to components, such as RAM expansion capabilities, to address robustness issues. Additional requirements or recommendations provide for expansion capabilities in the server system. Ease of use and ease of maintenance. Various requirements seek to address issues related to ease of use and ease of maintenance two factors that strongly affect the TCO for servers. Security. Some requirements ensure security of user data or access to system components. When working to meet these requirements and when choosing to support additional hardware design recommendations, the designer must continually weigh cost versus performance. In defining these guidelines, extra attention has been given to this concern. Intel and Microsoft are dedicated to strategic industry relationships that deepen and strengthen support for evolving the platform. Both companies work with industry groups to define standards for new technologies. In support of this evolution of server platforms, Microsoft has become involved in the following efforts: Designing operating system support for new bus and device classes to ensure that new technologies can quickly reach a broad market. Enhancing the Windows2000 Server and later operating systems to make it easy for both hardware and software developers to exploit operating system capabilities. Offering the HCL and other programs to help customers identify hardware and software designs that take advantage of the Windows2000 Server operating system. The system design requirements defined in this guide support a synergy among server hardware, the Microsoft Windows2000 Server operating system, and Win32-based and Win64-based software. These requirements for systems and components are based on the following goals: System platforms, buses, and devices meet industry standards and specifications for each bus type and device class. Systems and devices meet minimum performance requirements. Systems and devices meet ease-of-use and physical design guidelines. Systems and devices are supported by device drivers that follow guidelines defined in the Windows2000 DDK for behavior, installation, and removal. Systems and devices support Plug and Play configuration and OnNow power management for configuring and managing all system components under the Windows2000 Server operating system. Server Classes and Operating System Editions Servers perform a huge variety of tasks and combinations of tasks, resulting in many configurations. To specify requirements in a meaningful way, this guide first defines a basic set of requirements for a generic (or basic) server platform. This guide then provides additional recommendations and requirements for the server usage models described here: Basic server. This server can beused in any environment. This server is described by a set of requirements and recommendations that seek to define a well-rounded, general-purpose server platform used solely as a server. Such a server can beused in small businesses or for a variety of uses in larger businesses, rangingfrom departmental use to clustered applications in the enterprise. Administration can be local or remote. This servers baseline capabilities include high availability, serviceability, scalability, ease of use, and ease of administration. This platform and its requirements are used as a basis for other types of servers defined by this guideline. Small office/home office (SOHO) server. Although it can be used in any environment, this server platform has features that increase its ease of use and deployment in small businesses, which usually do not have great experience using and deploying server systems. This general-purpose platform handles file, print, and client-server application requirements. This server must haveabroad set of attributes to handle all typical server tasks in a limited environment. Quick recovery is required, because downtime will immediately impact the small offices ability to conduct business. The system must be easy to set up and manage from a remote location, such as the headquarters for a value-added retailer (VAR), or directly by the server owner, who may have little or no computer knowledge. To increase ease of use and availability, the system should be capable of exploiting the reliability features of Windows2000, such as disk mirroring and clustering. The system should have low entry costs and low recurring costs, because cost is often a driving issue in SOHO environments. The SOHO server has additional requirements driven by the usage and deployment model for this platform. The SOHO server could also serve as a client workstation, while simultaneously performing its normal role as a server. This dual usage imposes additional requirements for power management and configuration. Enterprise server. This server can also be used in any environment, but is frequently deployed as thebuilding block for a large organization where it often performs special-purpose tasks, such as handling and routing email, or storing financial data. Because this server is an indispensable part of the organization, it must be highly available. Therefore, software and hardware mechanisms must be in place to eliminate unplanned downtime. The Microsoft Windows 2000 Server operating system is available in four editions: Windows 2000 Server: The successor to Windows NT Server 4.0, it is a multipurpose network operating system for businesses of all sizes. Windows 2000 Advanced Server: The successor to Windows NT Server 4.0, Enterprise Edition, it is the operating system for e-commerce and line-of-business applications, providing load balancing and clustering services as well as enhanced symmetric multiprocessing (SMP) capabilities. Windows 2000 Datacenter Server: The newest member of the Windows Server family, it is the operating system for business solutions that demand the highest degree of scalability, availability, and reliability. Microsoft Small Business Server: Provides small businesses with essential tools, including file and printer sharing, business-critical applications, e-mail and scheduling, and support for Internet and communications services such as Internet, remote access, and fax. Designing Systems for Windows2000 Server The requirements and recommendations in this guide are defined in relation to classes of server systems and components used with the Microsoft Windows2000 Server operating system. Windows2000 Server is a preemptive, multitasking operating system that includessecurity and networking services as fundamental components of the baseoperating system. Windows2000 Server also supports high-performance computing by providing kernel support for computers that havesymmetric multiprocessor configurations. Under Windows2000 Server, Plug and Play and power management capabilities are made available for ACPI-compliant server systems. Other major hardware initiatives for Windows2000 include the following: Support for bus and device classes such as USB, IEEE 1394, Human Interface Device (HID) class, and Fibre Channel. Support for Microsoft Cluster Server and up to four nodes in a Microsoft Cluster Server (MSCS) cluster in Windows 2000 Datacenter Server. Online volume management, hierarchical storage management (HSM), Removable Storage Manager, and improvements in backup and recovery support. Support for Web-Based Enterprise Management (WBEM) and WMI as part of the Zero Administration initiative for Windows, reducing hardware ownership costs. Support for I2O architecture. Support for System Area Networking. Support for large physical memory (more than 4 GB). Support for Windows2000 Server running on IA-64 systems. Note that only the 64-bit version of Windows 2000 and later versions will be supported by Microsoft on IA-64 systems. In other words, 32-bit versions of Windows will not be supported on IA-64 systems by Microsoft. For information about Windows2000 Server features and capabilities, see http://www.microsoft.com/Windows2000/guide/server/. ACPI and OnNow Design Windows2000 Server includes support for ACPI, which supports operating systembased power management and Plug and Play systemconfiguration capabilities. This guide summarizes some of the system and device capabilities for hardware used with Windows2000. The goal of the OnNow design initiative is to ensure that all system components work together to enable robust and reliable system configuration and power management. The operating system and applications work together intelligently todeliver effective power management. All devices connected to the system or added by the user participate in the device power-management scheme. The OnNow design initiative includes requirements for the operating system, applications, device drivers, and hardware in order to deliver transparent power management and improve integration of components. The changes include: Enhanced core operating system functionality for power management. A system interface for operating systemdirected power management andPlug and Play. The ACPI design also provides future extensibility and improved system integration. Windows Driver Model (WDM), which supports power management and Plug and Play, and provides a common set of I/O services and binary-compatible device drivers among Windows 98 and Windows2000 for targeted device classes (audio, input, video, and still imaging) and bus classes (for example, USB and IEEE1394). Device and bus hardware power management interfaces and state definitions. An application architecture that allows applications to integrate into power management of the system. The ACPI specification defines a flexible and abstract hardware interface that enables a wide variety of server systems to implement power and thermal management functions while meeting the cost and feature requirements of the target market. ACPI also provides device configuration and generic system-event mechanisms for Plug and Play, unifying the power management interface with the Plug and Play interface. The ACPI implementation is independent of the processor architecture and enables the operating system to direct power management throughout the system. For more information about ACPI and the OnNow design initiative, see the OnNow web site at http://www.microsoft.com/hwdev/onnow.htm. IA-32 vs. IA-64 Design Windows2000 is designed to run on platforms with processors that use the Intel Architecture instruction set, including: IA-32 platforms, such as Intel Pentium, Intel Pentium with MMX technology, Pentium Pro, Pentium II, Pentium III, Pentium II Xeon and Pentium III Xeon, or compatible processors. IA-64 platforms, such as Intel Itanium or compatible processors. This section summarizes design issues for IA-32 versus IA-64 systems that meet the requirements in this guide. ACPI 1.0b vs. ACPI 2.0 In this version of the Hardware Design Guide, ACPI version 1.0b is the version of the ACPI specification that addresses related requirements for IA-32 systems. It also serves as a key component of PCI hot plug implementations in all systems that can be natively supported by Windows. ACPI version 2.0 will address requirements for both IA-32 and IA-64 systems. In this version of the Hardware Design Guide, ACPI Version 2.0 is required for all IA-64 systems, because it is the first version of the ACPI specification that addresses the specific requirements for IA64 systems with regard to ACPI firmware, hardware, and motherboard support. In particular, the ACPI 2.0 specification defines expanded interfaces to support IA-64, with extended Table definitions and new ACPI Source Language (ASL) and ACPI Machine Language (AML) 64-bit functions. Boot and Firmware Support: BIOS vs. EFI Firmware issues. In this design guide, firmware boot support for IA-32 is assumed to be BIOS based (as Windows EFI support for IA-32 systems has not yet been defined). Firmware support for IA-64 systems must comply with the Extensible Firmware Interface Specification, Version 1.0 (EFI 1.0) or later. BIOS-based boot is not supported and will not work with 64-bit Windows. In addition, in this guideline, PXE_BC (remote/network boot), SERIAL_IO, and SIMPLE_NETWORK protocols as defined in the EFI specification are required for EFI systems. Other boot support. IA-32 systems must support standard BIOS mechanisms for determining the boot drive and must support Int 13h. IA-64 systems provide a globally unique identifier (GUID) Partition Table (GPT) partitioned hard drive for boot, compliant with the EFI specification. IA-32 vs. IA-64 Miscellaneous Design Issues Memory. In this guide, IA-32 systems must support minimum memory capacity of 2 GB (for systems that provide support for fewer than 4 processors) or 8 GB (for systems with 4 or more processors). IA-64 systems must support a minimum RAM expansion capacity of 16 GB (for systems that provide support for fewer than 4 processors) or 32 GB (for systems with 4 or more processors). APIC support. In this guide, IA-32 systems must include Advanced Programmable Interrupt Controller (APIC) support that complies with ACPI 1.0b. IA-64 systems must include Streamlined APIC (SAPIC) support that complies with the 64-bit extensions defined in ACPI 2.0 Headless servers. In this design guide, Enterprise class IA-32 systems are required to support capabilities for headless server functionality; this is a recommendation for basic and SOHO class servers in this version of the design guide. Headless support is likely to become a requirement for all IA-32 systems in future versions of these guidelines. IA-64 systems are not required to support this capability. However, headless support is expected to become a requirement for IA-64 systems in future versions of these guidelines, when related support is provided in a future version of 64-bit Windows. Manageability. IA-32 systems must support manageability as defined in this document and in Windows Hardware Instrumentation Implementation Guide. In addition to this, IA-64 systems must implement hardware and firmware support for IA-64 Machine Check Architecture. Devices. IA-64 systems must not include legacy parallel ports and must provide a legacy serial port for use as a debug port. Chapter 2 System Component Requirements This chapter presents requirements and recommendations that apply to the whole server system, including key components such as memory and power management. They apply to standard, high volume (or commodity) servers that run the Microsoft Windows2000 Server operating system. Tips for selecting high-performance system components. For manufacturers who want to select high-performance components for server systems, the following are design features to look for when selecting components to improve memory performance: Implement PCI controllers as peer bridges to improve I/O bandwidth. Support fast, large, expandable memory. Support the largest possible caches. Note: The system requirements defined in this publication provide guidelines for designing servers and peripherals that deliver an enhanced user experience when implemented with Windows2000 Server. These requirements are not the basic system requirements for running any versions of the Windows2000 Server operating system. General Component Requirements This section lists requirements and recommendations for system components such as memory and power management. 1. System and components properly support all dates Required The firmware, real-time clock, system clocks, and the system as a whole must work correctly for all dates. System Microprocessor Requirements This section summarizes processor requirements for server systems. Note: It is recognized that OEMs supply systems with specific feature requirements to corporations, which can include providing servers that do not include any processors pre-installed before shipping. 2. Multiprocessor-capable system meets Windows requirements and minimum expansion requirements Required 2.1 Enterprise class server system supports expansion to at least four processors 2.2 IA-32 multiprocessor-capable system supports ACPI 1.0b For systems in which more than one processor can be installed, the system must employ those processors symmetrically; that is, all processors must be able to access all I/O buses and system memory, and cache coherency must be maintained. The system must also comply with the ACPI 1.0b specification. In addition, Advanced Programmable Interrupt Controller (APIC) support must comply with ACPI 1.0b by including the Multiple APIC Description Table defined in Section 5.2.8. Note that Windows 2000 and later versions of Windows use ACPI on all ACPI-based systems, and therefore compliance with MultiProcessor Specification, Version 1.4 (MPS1.4) is no longer required. For information about the requirements for PCI IRQ routing on a multiprocessor ACPI system, see http://www.microsoft.com/hwdev/onnow/acpi-mp.htm. Note on Multiprocessor Wake-up: A problem has been uncovered with certain multiprocessor systems that will prevent them from properly waking up from a Sleep state under Windows 2000. This pertains to dual-processor or multi-processor systems that transition all processors from an active state to a STPCLK state, and more specifically to systems where all processors receive their STPCLK# request from one source. Prior to transitioning from a STPCLK state to a Sleep state or lower power state, all processors must generate a Stop Grant Bus cycle. It is essential that all processors have transitioned into the STPGNT state before it is safe to: 1) transition to a lower power state such as Sleep, or 2) externally shut off the processor clocks to allow for flushing buffers, cache maintenance, and other internal activities. For dual-processor and multiprocessor systems using a single STPCLK to all processors and a single SLP pin to all processors, the transition to the Sleep state should not be used. Behavior of the system during removal of the processor clock-such as transitions from STPCLK to Sleep state-cannot be guaranteed unless all STPGNT bus cycles are received. For example, Intel Xeon II Specification, Section 4.2.5 Sleep State-State 5, specifies that for a multiprocessor system, all processors are required to complete the Stop Grant bus cycle before the subsequent 100 BCLK waiting period and before the assertion of SLP# can occur. When multiple processors are serviced by a single STPCLK# request to all processors and a single SLP#, there is no provision to guarantee that all Stop Grant bus cycles are received before the assertion of SLP#. As another example, in 450NX-based platforms from Intel, the STPCLK# from PIIX4E is connected to all processors, and SLP# from PIIX4E is connected to all processors. The following sequence occurs: t0. Operating system writes PMCNTRL register. t1. PIIX4E asserts STPCLK#, then waits for Stop Grant acknowledgment. t3. The processor acknowledges with Stop Grant ACK cycle. t4. PIIX4E asserts SLP# after receiving this. This sequence works for uniprocessor systems (which is what the PIIX4E was originally designed for). However, in multiprocessor systems, SLP# might be asserted to a processor that is not in Processor Sleep State 3 (that is, not yet acknowledged). This premature SLP# assertion might result in a wake-up problem. Intel provides additional information about this issue through the Intel Technical Support Hotline at 1-800-628-8686 or 916-377-7000. 2.3 IA-64 multiprocessor-capable system complies with ACPI 2.0 For an IA-64 system in which more than one processor can be installed, the system must employ those processors symmetrically; that is, all processors must be able to access all I/O buses and system memory, and cache coherency must be maintained. The system must also comply with the ACPI 2.0 specification. In addition, an IA-64 system must include a Multiple SAPIC Description Table that complies with ACPI 2.0. Note that MPS 1.4 support is not a requirement for systems with 64-bit processors and will not be used by any version of the 64-bit Windows operating system. Memory Requirements This section defines minimum memory requirements for server systems. Note: It is recognized that OEMs supply systems with specific feature requirements to corporations, which can include providing servers that do notinclude any memory pre-installed before shipping or otherwise fulfill specific customer requirements for installed memory. 3. For IA-32 system, installed memory meets minimum requirements Windows 2000 Server, Small Business ServerWindows 2000 Advanced Server, Windows 2000 Datacenter Server For 12 installed processors, 512 MB requiredFor 14 installed processors, 1 GB requiredFor more than 2 installed processors, 256 MB per installedprocessor requiredFor more than 4 installed processors, 256MB per installed processor, required Memory requirements are defined in relation to the installed operating system. There are no requirements defined in relation to the server type. All memory visible to the operating system as system memory must be cacheable. All system memory except for 4MB must be completely available for the system to use at boot time and cannot be locked from use by the operating system. This minimum requirement for memory available to the operating system does not preclude applications that use dynamically-allocated memory for temporary uses. Recommended: Larger installed memory configurations, which will increase performance. 4. For IA-64 system installed memory meets minimum requirements Required The minimum installed memory requirement for IA-64 systems is 1 GB of system memory. All memory visible to the operating system as system memory must be cacheable. All system memory except for 4MB must be completely available for the system to use at boot time and cannot be locked from use by the operating system. This minimum requirement for memory available to the operating system does not preclude applications that use dynamically allocated memory for temporary uses. Recommendation Recommended: Larger installed memory configurations, which will increase performance. 5. For IA-32 system, memory capacity meets minimum requirements Systems that provide support for <4 processors: 2GB requiredSystems that provide support for 4 or more processors: 8 GB required  This requirement defines minimum RAM expansion capabilities for an IA32 system. All memory visible to the operating system as system memory must be cacheable. 6. For IA-64 system, memory capacity meets minimum requirements Systems that provide support for <4 processors: 16 GB requiredSystems that provide support for 4 or more processors: 32 GB required  This requirement defines minimum RAM expansion capabilities for an IA-64 system. All memory visible to the operating system as system memory must be cacheable. 7. System memory includes ECC memory protection Required The system memory and cache must be protected with Error Correction Code (ECC) memory protection. All ECC RAM visible to the operating system must be cacheable. The ECC hardware must have the ability to detect at least a double-bit error in one word and to correct a single-bit error in one word, where word means the width in bits of the memory subsystem. A detected error that cannot be corrected must result in a system fault. 8. NUMA and NUMA-lite system design maintains near:far memory access time ratios of 1:3 or less Recommended For optimal performance with Windows 2000 and later operating systems, it is recommended that system designers building platforms that present memories with different access times keep the ratio for access to near versus far memories relative to a given microprocessor at a 1:3 ratio or less as seen by the operating system. ACPI and Power Management Requirements This section defines the system and BIOS requirements for ACPI and power management. 9. System design meets ACPI and related requirements Required for all server types, with additional requirements for SOHO servers IA-64 system board sets must support ACPI 2.0 or later. IA-32 system board sets must support ACPI 1.0b or later. This requirement ensures that the system correctly supports the Plug and Play and power management functionality described in this guide. 9.1 Server system implements basic ACPI and power management capabilities ACPI support for all server systems must include the following required capabilities: Power management timer. System control interrupt and necessary Status and Enable (STS/EN) bits must be provided. Support for a description table that defines the complete hierarchy for system-board devices, including host PCI bridges. The description table must include all non-Plug and Play devices to be enumerated and all other devices for which power management or removal capabilities have been added by the system-board design. Each bus and device enumerated using ACPI includes the ACPI control methods necessary to configure these devices. This includes requirements defined in these guidelines for automatic device configuration, resource allocation, and dynamic disable capabilities. For information about Plug and Play support under Windows 2000, see Setup, Plug & Play, Power Management in the Windows 2000 DDK. Standard system devices are excluded from related requirements, as described in guideline #16. System and device configuration meet Plug and Play requirements. Thermal model and fan control, if implemented, comply with ACPI. IA-64 systems must comply with Section 12 of ACPI2.0. IA-32 systems must comply with Section 12 of ACPI 1.0b. Notice also that a server that supports thermal controls must have active thermal control such as a fan and cannot use passive thermal control under normal operating circumstances. This requirement, however, does allow proprietary value-added features that cannot be implemented using ACPI. For example, systems are permitted to use out-of-band methods to provide cooling when the operating system is not booted. Support for at least one processor power state. This can be either C1, C2, or C3. No capabilities for the end user to disable system ACPI support using CMOS or other means. Disabling ACPI will cause boot failures because Windows 2000 relies on ACPI to identify and initialize system devices. This requirement, however, does allow proprietary value-added features that cannot be implemented using ACPI. 9.2 SOHO server implements additional ACPI and power management capabilities The following ACPI support is required for SOHO servers and recommended for other server types: Power button complies with ACPI. IA-64 systems must comply with ACPI 2.0. IA-32 systems must comply with ACPI 1.0b. This is described in guideline #10. Hardware design supports OnNow initiative. Note: Very large, or rack-mountable, or partitionable systems may face challenges with actual physical ACPI power buttons. A possible alternative for server systems is a virtual ACPI power button which acts as an ACPI power button but which is activated via a service processor action or other form of remote management (instead of via an actual administrator pressing a button physically located on the server). Real-time clock alarm that supports wake-up based on a scheduled time and day of the month. IA-64 systems must comply with ACPI 2.0. IA-32 systems must comply with ACPI 1.0b. If this feature is implemented, the day-of-month feature is required under these guidelines, although it is an optional feature in the ACPI specification. Also, if this feature is implemented, system control interrupt and necessary STS/EN bits must be provided. ACPI-compliant support for the S5 soft-off state. IA-64 systems must comply with ACPI 2.0. IA-32 systems must comply with ACPI 1.0b. If a soft-off feature is supported, it must meet the requirements for the S5 state defined in the ACPI specification. Support for either the S1, S2, or S3 sleep state. Support for at least one of the S1, S2 or S3 sleep states must be provided by SOHO servers. Support for the S3 state (Suspend to RAM), which provides the optimal user experience and power savings, is likely to become a requirement in a future version of this design guide. USB host controller can wake the system. If a USB host controller is present in the system, it must support wake-up capabilities in one of the following system states: S1 or S2. If the system contains multiple USB host controllers, all host controllers integrated on the system board (that is, not add-on cards) must meet this requirement. USB devices and USB client software and drivers must not fail over system suspend and resume cycles. Recommendation Recommended: Support wake-up from the S3 state. Notice that if wake-up from the S2 or S3 state is supported, wake-up must be supported for all higher power sleep states. For example, if the controller supports wake-up from the S2 state, it must also support wake-up from the S1 state. Note: For IA-64 systems, a server system implementing system-board power management or configuration features that are defined in the ACPI 2.0 specification must comply with ACPI 2.0, even if those features are not specific requirements orrecommendations in these guidelines. This requirement, however, does allow proprietary value-added features that cannot be implemented using ACPI. For IA-32 systems, a server system implementing system-board power management or configuration features that are defined in the ACPI 1.0b specification must comply with ACPI 1.0b, even if those features are not specific requirements orrecommendations in these guidelines. This requirement also allows proprietary value-added features that cannot be implemented using ACPI. 10. Hardware design supports OnNow initiative Required for all server types, with additional requirements for SOHO servers Elements of the OnNow design initiative ensure that the operating system and device drivers control the state of individual devices and the system board set. 10.1 Buses on system that supports S1S3 meet bus power management requirements SOHO servers and any Basic or Enterprise server that supports any one of the S1, S2, and S3 sleep states mustand all servers shouldprovide PCI, USB, and IEEE 1394 buses that support power management requirements, as defined in the related bus standards. 10.2 All devices and drivers support D0 and D3 power states All devices and drivers must support the D0 and D3 power states consistent with the definitions in the Default Device Class Power Management Specification and the relevant device class power management reference specification. This requirement must be implemented so that each device can successfully survive a system sleep/wake transition (device D3 to D0 transition) without requiring user intervention to restore functionality. This requirement applies whether or not system power is removed while the computer is in an S1S4 state. The operating system supports the S4 state without system-board support, so all devices and drivers must meet this requirement. It should be noted that when PAE mode is used to allow access to more than 4GB of physical memory on servers running either Windows 2000 Advanced Server or Windows 2000 Datacenter Server, S4 hibernation will not be supported by the operating system. This is because the time and disk space needed to save and restore the system image for a system with 4 GB or more of system memory will typically greatly exceed the amount of time needed to reboot such a system. However, all systems, devices, and drivers must still meet the requirements within this guideline as it is always possible that even a large system may have less than 4GB of physical memory or not be running in PAE mode. Notice that there is no power consumption requirement for devices in the D3 state. It is recommended, however, that devices implement the D3 state so that device power consumption is reduced to near zero, with the recognition that there is no requirement to retain any device context because it will be preserved or restored by the driver when returning to the D0 state. Recommendation Recommended: Devices and drivers should support the D1, D2, or both low-power states, and they should support the defined wake events as designated in the relevant device class power management reference specification. 10.3 System provides software-controlled, ACPI-based power switch For SOHO servers, the system must provide an easily accessible power switch that can be controlled by software. Recommendation Recommendation: This is a recommendation for Basic and Enterprise servers. The following provides implementation guidelines for the power switch. IA64 systems must comply with ACPI 2.0. IA-32 systems must comply with ACPI 1.0b. A single ACPI button design is preferred. This button must be the users primary switch interface, and must be implemented as a power button as defined by the ACPI specification. If a two ACPI button design is used, the sleep button must be the users primary switch interface, and be easily distinguishable from the power button. The preferred implementation in a two-button design is to hide the power button behind a door or on the rear of the system. The function of these buttons is determined by the operating system. In case of a hardware or software failure that prevents normal operation of the software-controlled buttons, the switch capabilities must include an override mechanism for turning off the server. Recommendation Recommended: A 4-second override mechanism as described in Section4.7.2.2.1 of ACPI 1.0b and in Section 4..7.2.12.1.3 of ACPI 2.0. The override must be associated with the users primary switch interface, in order to establish an industry-standard implementation. Notice that the override mechanism is not an alternative way for the user to turn off the server in normal operation; it is only a fail-safe function for fault conditions. If the power switch is provided on the keyboard, the key must be clearly labeled and must consist of a single keystroke for turning on the server, to ensure accessibility for persons with disabilities. (Two keystrokes can be used to turn off the server.) For information about scan codes for keyboard power switches, see http://www.microsoft.com/hwdev/desinit/scancode.htm. 10.4 System that support S1S3 provides one or more indicators to show whether the system is in the working or sleep state This capability is required for all SOHO servers and any other server systems that support S1, S2, and S3. Recommendation Recommended: A non-flashing, light-emitting diode (LED) sleep indicator that is a different color than the wake indicator. A slowly blinking LED indicator (less than 1Hz) is also an acceptable implementation. This applies for S1, S2, and S3 system states. The nonvolatile sleep state, S4, should appear to the user as the off state (S5); therefore, both of these states should have the same indicator. 10.5 For SOHO server and any other server that supports S3, the system power supply provides standby power for wake-up events The system must supply adequate standby power to support wake-up events. The system must provide, at a minimum, power for the core chipset including memory and all integrated wake devices, wake-up from the keyboard, a pointing device, and a single network device such as a local area network (LAN) or wide area network (WAN) adapter connected via an external bus or open PCI slot when the system is in the S3 or S4 state. Additional information about this requirement can be found in EPS Power Supply: A Server System Infrastructure (SSI) Specification for Entry Chassis Power Supplies, at http://www.ssiforum.org/docs/entrylevelpowersupply.pdf. This capability is required for SOHO servers. If a Basic or Enterprise server supports the S3 sleep state, this capability is required, otherwise, it is optional. 11. System startup meets requirements for OnNow support Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:OptionalOptionalOptionalEnterprise:OptionalOptionalOptionalSOHO:RequiredRequiredRequired The intention of this recommendation is to ensure that the end user is not presented with unnecessary visual displays and to ensure that access to error information remains available using a hot key. The following is required for SOHO servers. IA-64 systems must comply with ACPI 2.0. IA-32 systems must comply with ACPI 1.0b. System firmware supports fast POST. The system should be available to the user as quickly as possible. Although a specific time limit is not established, the basic recommendation is that power on to the bootstrap loader should occur within 5 seconds, plus hard-disk ready time, option ROMs, and time required for memory subsystem initialization and ECC. The following are recommended ways to reduce processing overhead to make system boot time as fast as possible: No video memory test and limited test for dynamic RAM (DRAM) size No tests for serial or parallel ports No floppy disk test or media check (boot from hard disk only) No tests for hard disk controller or drive type (if the system does not include swappable drives) Fast Power-On Self Test (POST) mode for system firmware can be disabled by the user for troubleshooting. Resume from sleep state(S1S3) to operating system handoff should occur within 500 ms. This recommendation does not apply to the S4 state. For all other sleep states, the time to operating system handoff means when the processor starts running (first instruction) until the system firmware jumps to the Waking Vector in the ACPI firmware control structure table, as described in Section 5.2.6 in ACPI 1.0b or in Section 5.6.2.1 in ACPI 2.0. Minimal startup display. System startup should draw the end users attention only when errors occur or when user action is needed. The default configuration should allow a beep during the boot process only in case of an error, and the only screen display should be the OEM splash screen, which can include information such as copyright notices. By default, the system should be configured so the screen display does not show memory counts, device status, and so on. The display should present a clean system firmware startup so that the end user is not presented with cryptic and unnecessary information. However, the system start-up process can include the following: A blank start-up screen. A hot-key override to display screen messages for troubleshooting or to display user-definable CMOS settings. Text-based, end-user action messages. Examples are: messages to display the setup hot key, the system help hot key, password entry, network log-on for remote booting, and so on. Manufacturer branding messages. A CMOS option to turn the clean start-up screen off and on. Recommendation Recommended for SOHO servers: Compliance with Simple Boot Flag Specification, Version 1.0 or later. This enables the BIOS to boot quickly when the last boot was successful and to perform diagnostics only if a problem occurred on the previous boot. Startup Support Requirements This section defines the firmware and other requirements to support system startup. 12. System firmware meets general boot support requirements Required Notice that the Extended System Configuration Data (ESCD) calling interface is not supported by Windows2000. The requirements for boot support are summarized in the following items. 12.1 System firmware supports SMBIOS 2.3 This mechanism is required to provide platform specific information at boot time, including the servers Universally Unique Identifier (UUID). System Management BIOS Reference Specification, Version 2.3, is available at http://www.phoenix.com/products/specs-smbios.pdf. In addition, the UUID must be provided to the user in printed form, for assistance in environments where it could be used as part of pre-staging systems. This mechanism is left up to the system manufacturer, but suggested means include posting the UUID on the system chassis or case, or printing it the shipping carton. 12.2 Firmware implements security, such as a preboot password This is provided to protect enable and disable capabilities for hardware components before the operating system boots. At a minimum, User and Administrator levels of password protection must be provided in the system firmware. This capability prevents end users from accidentally or purposefully circumventing operating system-level security and control as applied by an administrator. 12.3 Firmware supports BIS For systems that include integrity or authentication services for downloaded remote boot images, the systems firmware must provide these capabilities as defined in Boot Integrity Services (BIS), Version 1.0, available at http://developer.intel.com/ial/wfm/wfmspecs.htm. In addition to the management data required by SMBIOS 2.3, BIS requires inclusion of Type 31 (BIS Entry Point) in the table of exported SMBIOS structures. 12.4 Firmware provides boot support for CD and DVD drives The system firmware or option ROM must support the No Emulation mode in El Torito, Version 1.0. For related information for IA-64 systems, see guideline #14.5 EFI IA-64 system firmware provides boot support for CD and DVD drives. 12.5 System supports firmware update mechanism System administrators must be able to upgrade system firmware to a new image. The following methods can be used to meet this requirement: Remote new-system setup mechanism based on PXE capabilities allowing programs to be downloaded and executed at boot time. Normal file access and execution methods when the system is fully booted into the normal operating system environment. Recommendation Recommended for all system types: If option ROMs are provided, they should also be capable of being updated. Implement a mechanism to authenticate the requester of the update programming. Implement a mechanism to validate that the program arrived intact after download. See also the BIOS requirements and recommendations for ATA support in guideline #177. ATA controller and peripherals comply with ATA/ATAPI-5 standard commands for features implemented and support Ultra-DMA (ATA/33, minimum). 13. IA-32 BIOS boot system supports remote/network boot, USB boot devices, and firmware update Required 13.1 IA-32 BIOS boot system supports PXE 2.1 If a server provides support for network adapters that provide remote boot capabilities using Dynamic Host Configuration Protocol (DHCP) and Trivial File Transfer Protocol (TFTP), the server must also provide support for the preboot execution environment. For IA-32 BIOS boot systems, this is described in PXE 2.1, available at http://developer.intel.com/ial/wfm/wfmspecs.htm. 13.2 IA-32 BIOS boot system supports CIP BIOS Boot 1.01 for network-based boot BIOS supports booting the system from the network, with a mechanism for setting the order of precedence for boot devices. If a server provides support for BIOS boot from a network adapter, the system BIOS must comply with the requirements defined in Sections 3 and 4 (as they apply to Plug and Play devices) of CIP BIOS Boot 1.1, which describes the requirements for Initial Program Load (IPL) devices. The BIOS must allow all boot devices to be configured according to order of precedence for boot. This mechanism must clearly show how the system will order boot devices when end users are making configuration choices. For example, in a system that permits booting from floppy drive, hard drive, CD or DVD drive, and network adapter, it must be clear to the end user how to set a boot order that favors a specific device, such as the CD drive. In addition, for any system that includes a network adapter capable of PXE-based remote boot, a key sequence must be provided to allow the user to force a boot initiated from the network adapter, either directly or via a pop-up screen. This key sequence must be enabled by default. Configuration of this feature may be provided through a CMOS configuration setting. When this feature is enabled, the boot display must indicate the key sequence that will invoke the pop-up screen allowing a network boot. This display must appear for a duration sufficient to be read by users, but must not lengthen the overall time needed to boot the machine. This feature must be implemented in accordance with Appendix C of CIP BIOS Boot 1.01. Note that this feature is a requirement in this Hardware Design Guide, although it is optional in CIP BIOS Boot 1.01. For consistent user experience across all system brands and types, it is suggested that system and BIOS manufacturers standardize on the F12 key to perform this action. It is expected that F12 or another standard key sequence will become a requirement in a future version of this design guide. 13.3 IA-32 BIOS boot system supports USB keyboards, pointing devices, and hubs as boot devices For a server that includes a USB keyboard as the only keyboard in the system, the system BIOS must provide support during the bootstrap process for USB keyboards, pointing devices, and hubs. This BIOS support is defined in the USB Device Class Definitions for Human Interface Devices, Version 1.1 (HID 1.1), with particular attention to the Keyboard Boot Protocol. This BIOS support must provide the ability for the user to enter the BIOS setup utility; it must also provide enough functionality to install and boot an operating system that recognizes USB peripherals. USB keyboards built as standalone devices, part of a composite device, or part of a compound device must be recognized and usable. The BIOS is required to support keyboards behind at least one level of external hub. For systems with multiple USB host controllers, BIOS support for USB keyboards and hubs is required for all host controllers that are integrated on the system board (that is, not add-on cards). Keyboard and pointing devices must be functional for all modes of the operating system, including the bootstrap process, loading, recovery console, and operating system installation. USB external connectors and USB input device support must be enabled by default in the BIOS, and the BIOS must make USB input devices such as keyboards and pointing devices available at boot time. 13.4 IA-32 BIOS boot system firmware supports console redirection to a serial port, if serial headless server support is implemented in the system If serial port based headless server support is provided by the system, the system must provide support for redirection of all BIOS driven console I/O to the serial port. The driver for the serial console must be capable of supporting the capabilities documented in Extensions to the VT100 Terminal Definition, available at http://www.microsoft.com/hwdev/headless/. An IA-32 BIOS boot system must provide information about the location and configuration of this serial port via ACPI and the methods described in Serial Port Console Redirection Table available at http://www.microsoft.com/hwdev/headless/. The BIOS must release the serial port as soon as the Windows loader is called. Additionally, if the system BIOS supports localization, it must meet the requirements specified in Extensions to the VT100 Terminal Definition. Recommendation Recommended: IA-32 BIOS boot system support should include the following, where appropriate: An IA-32 BIOS boot system should use the E820 interface to report memory. The E820 interface allows systems to report (and test) memory, and also allows memory to be reclaimed. Information about this interface can be found in Paragraph 2 of Section 9.3.2, BIOS Initialization of Memory, in ACPI 1.0b, which states that the E820 specification has been updated and lists the new memory range types. System BIOS on an IA-32 BIOS boot system or option ROM provides ARMD-compliant boot support for ATAPI bootable floppy disk drive. Complying with the ATAPI Removable Media BIOS Specification (ARMD), Version 1.0 or later specification provides Int 13h and Int 40h support for bootable floppy drives as the primary or secondary floppy device. 14. IA-64 system complies with EFI 1.0 or later, with support for USB boot devices, firmware update, and PXE_BC, SERIAL_IO, and SIMPLE_NETWORK protocols Required The only boot mechanism supported for platforms running 64-bit Windows is defined in EFI 1.0 or later. BIOS-based boot is not supported and will not work with 64-bit Windows. Note: Although the PXE_BC (remote/network boot), SERIAL_IO, and SIMPLE_NETWORK protocols are defined as optional implementation elements in the EFI specification, in this guideline they are requirements for EFI systems. 14.1. EFI IA-64 system supports network-based boot via EFI boot manager EFI systems must provide support for booting systems from the network as defined in EFI 1.0 or later. This support includes the capability, via the EFI boot manager, to configure boot devices in order of preference by the administrator of the server, plus a method for forcing a network-based boot. These mechanisms must be available to the administrator in the pre-boot state of the system. 14.2. EFI IA-64 system provides boot support for USB keyboard and bus The system firmware must provide EFI boot support for USB keyboards, pointing devices, and hubs. The system firmware must also support the keyboard behind at least one level of external hub. This support must provide the ability for the user to enter the systems firmware-based configuration utilities and provide sufficient functionality to get EFI-aware versions of Windows installed and booted. USB keyboards built as standalone devices, part of a composite device, or part of a compound device must be recognized and usable. For systems with multiple USB host controllers, firmware support for USB keyboards, pointing devices, and hubs is required for all host controllers that are integrated on the system board (that is, firmware support is not required for add-on cards). Keyboard and pointing devices must be functional for all modes of the operating system, including booting, loading, recovery console, and operating system installation. USB external connectors and USB input device support must be enabled by default in the firmware, and the firmware must make USB input devices such as keyboards and pointing devices available at boot time. 14.3. EFI IA-64 system implements SAL, including firmware update method The System Abstraction Layer (SAL) is a firmware layer provided by OEMs. The implementation of this layer must conform to RS-IA-64 System Abstraction Layer (SAL) Specification, Revision 2.7 or later, including implementation of a call that will allow the firmware to be updated. SAL abstracts platform uniqueness by providing a consistent interface to a higher level of the software stack to discover and control an IA-64 system. It exports components and their associated access details to the operating system through EFI using the SAL System Table. 14.4. EFI IA-64 system firmware supports console redirection to a serial port The system must provide support for redirection of all console I/O to the serial port. The driver for the serial console must be capable of supporting the capabilities documented in Extensions to the VT100 Terminal Definition. Note that unlike BIOS, EFI firmware must indicate which serial port is used for console I/O and the configuration of that serial port through the console device path for the serial port as specified in EFI 1.0. 14.5. EFI IA-64 system firmware provides boot support for CD and DVD drives The system firmware must support the No Emulation mode in El Torito, Version 1.0, and the additional requirements for EFI as defined in Section 16.2.2, ISO-9660 and El Torito, in EFI 1.0. 14.6. EFI IA-64 system provides minimum required boot list variable storage The minimum required non-volatile storage for boot list variables (used by the EFI boot manager) is 4K. Note that this is storage reserved solely for use by boot list variables and may not be used for any other variables or purposes. 14.7. EFI IA-64 system provides a minimum, firmware-based driver set sufficient to allow boot, installation, and recovery operations without the presence of loadable media-based EFI drivers The minimum set of capabilities required under this guideline include EFI console capabilities and sufficient other EFI drivers to permit access to devices needed for boot, installation, and recovery operations. Note: An example of a specific problem that this guideline addresses is the possible case of a system that, in order to reach a given disk drive, must load a driver off that particular disk drive. It can readily be seen that such cases would result in an uninstallable system. 15. System provides a debug port solution Required All systems are required to provide a debug port solution, including the necessary hardware and system firmware to fully implement the solution. This capability provides support for debugging and troubleshooting activities. 15.1. IA-32 system meets debug port and configuration requirements IA-32 system designers may choose to support one or more of the following debug port technologies: Legacy serial port. The system firmware must configure at least one serial port to use either 2F8h or 3F8h. This allows the port to be treated as a boot device by the firmware and to be used by components as a diagnostic port if system debugging is required by either the firmware or the operating system. Note that systems designed to implement a legacy serial port for debug purpose must not share this function with a serial port utilizing the Windows native serial port headless server functionality; in such a case, two serial ports are required. Non-legacy debug ports. A system designed to implement an alternative Windows-compatible debug port must implement a debug solution that complies with the Debug Port Specification, available at http://www.microsoft.com/hwdev/NewPC/debugspec.htm. 15.2. IA-64 system meets debug port and configuration requirements IA-64 system designers must provide a legacy serial port for use as a debug port. The platform firmware must configure at least one serial port to use either 2F8h or 3F8h. This allows the port to be treated as a boot device by the firmware and to be used by components as a diagnostic port if system debugging is required by either the firmware or the operating system. Plug and Play Requirements This section defines the specific requirements for Plug and Play. 16. System and device configuration meet Plug and Play requirements Required Windows 2000 Server implements complete support for Plug and Play configuration. Each bus and device provided in a server system must meet the current Plug and Play specifications related to its class, including: Requirements defined in Section 6 of ACPI 2.0 (for IA-64 systems) or Section 6 of ACPI 1.0b (for IA-32 systems). Bus class specifications, such as PCI Local Bus Specification, Revision 2.2 (PCI 2.2), USB 1.1 or later, and so on. Requirements and clarifications for automatic device configuration, resource allocation, and dynamic disable capabilities for legacy components such as serial and parallel ports, as defined in Legacy Plug and Play Guidelines, available at http://www.pcdesguide.org/legacypnp/. Note: Standard system devices are excluded from the Plug and Play requirement. The system can reserve static resources for devices such as programmable interrupt controllers (PICs) 1 and 2, timer (82542), keyboard controller (8042), real-time clock, DMA page registers, and DMA controllers 1 and 2. For IA-32 systems, these fixed resources are located at I/O addresses under 100h and can also include a NMI. Also, this requirement does not apply to devices that are completely invisible to the operating system, such as out-of-band systems management devices or I2O hidden devices; however, these devices still must properly reserve resources using ACPI methods to avoid potential conflicts. 17. Unique Plug and Play ID is provided for each system device and addon device Required Each device connected to an expansion bus must be able to supply its own uniqueidentifier, as defined in the current Plug and Play specification for the bus that it uses. The following defines the specific requirements for Plug and Play device IDs: Each separate function or device on the system board set must be separately enumerated. Therefore, each must provide a device identifier in the manner required for the bus it uses. If a device on an expansion card is enumerated by the system firmware, it must have a unique ID and its own resources according to the device-ID requirements forthe bus to which the card is connected. This includes devices that are separately enumerated on multifunction cards or multifunction chips. The following are exceptions to the requirements for a unique Plug and Play ID: Legacy devices attached to the Industry Standard Architecture (ISA) bus on the system board set do not have unique Plug and Play IDsfor example, serial ports, parallel ports, or PS/2-compatible port devices. The method for device identification is defined in Plug and Play ISA Specification, Version 1.0a, and the ACPI specification. IA-64 systems must comply with ACPI 2.0. IA-32 systems must comply with ACPI 1.0b. Some multifunction devices (such as Super I/O) might include devices that do not have unique Plug and Play IDs or unique PCI Subsystem IDs, but that are supported by drivers provided with the Windows 2000 operating system. A device such as a multifunction PCI device that supports a number of functions but uses only a single set of relocatable resources does not have to provide separate identifiers for each function included on the device. Some devices are completely invisible to or are not managed by the operating system, such as out-of-band systems management devices or I2O system and I2O hidden devices. Such devices are exempt from this requirement, but these devices still must properly reserve resources using ACPI methods to avoid potential conflicts. In addition, if an OEM uses a proprietary mechanism to assign asset or serial numbers to hardware, this information must be available to the operating system using Windows hardware instrumentation technology. 18. PNP vendor code is used only to define a legacy devices Compatible ID Required All legacy devices not enumerated by the system board set interface must not use PNP in their vendor and device codes. The PNP vendor code is reserved for Microsoft and vendors whose hardware is specifically assigned a particular ID. Other hardware can use a PNP code only when defining a devices Compatible ID (CID) and only after first indicating the devices Hardware ID in the Plug and Play header. Recommendation Recommended: Use CIDs for devices that use device drivers provided with the Windows 2000 operating system, such as a standard COM port (PNP0500). Headless Server Requirements Windows Whistler provides native support for headless server operation on IA-32 platforms. Support for full headless server operation for IA-64 platforms will be available in a future version of Windows after Windows Whistler. The following guidelines describe requirements for hardware leveraging these capabilities. 19. IA-32 system provides headless server capabilities meeting Hardware Design Guide requirements Required for Enterprise class systems Recommended for Basic and SOHO class systems To permit remote management of a system, it is required that all Enterprise class IA-32 servers provide headless server capabilities complying with at least one of the solutions described in guidelines #20, 21, and 22. This is recommended for Basic and SOHO class systems, and is expected to become a requirement for these classes in a future version of this guide. The three cases that these guidelines describe are, respectively: 1: The case where headless out-of-band remote management is provided by serial port hardware only. 2: The case where such capabilities are provided by a management service processor that provides external serial support, either as a sole connection or in addition to other types of connections. 3: The case where such capabilities are provided by a management service processor that provides no external serial connection capabilities. 20. IA-32 system that implements headless capabilities without management service processor provides serial headless support Required if system implements headless support without a management service processor This guideline addresses the minimum capabilities needed for serial headless server support if a system implements a solution for headless support but does not include a management service processor. This requirement is an optional solution to the basic requirement stated in #19, IA-32 system provides headless server capabilities meeting Hardware Design Guide requirements. 20.1. IA-32 system without management service processor supports BIOS redirection of console output to the headless serial port IA-32 systems must provide the redirection capabilities documented in #13.4 IA-32 BIOS boot system firmware supports console redirection to a serial port, if serial headless server support is implemented in the system. Recommendation Recommended: Use COM1 as the headless serial port. 20.2. IA-32 system without management service processor provides properly configured legacy serial port For use with the headless server capabilities of Windows Whistler, IA-32 systems must provide a legacy serial port that is addressable at either COM1 (03F8h) or COM2 (02F8h), configured to the default settings of 9600bps, 8bits, no parity, and 1 stop bit. This port must also comply with the requirements for legacy serial ports elsewhere in this document. Note: Future versions of Windows will provide additional physical connection choices for headless servers. 20.3. IA-32 system headless connections are null modem cables that support Carrier Detect signal Cables used for connection to a Windows Whistler headless server on a serial port must be null modem cables that provide support for the Carrier Detect signal. Carrier Detect is required because Windows will not provide console I/O if Carrier Detect is not active. 21. IA-32 system that implements management service processor and external serial headless capability supports required external serial port and remote system reset Required if the service processor exposes a UART interface via hardware to the operating system or if the serial port is the only full-time management connection This guideline addresses the minimum capabilities needed for headless server support with service processors that provide external serial capabilities. This requirement is an optional solution to the basic requirement stated in #19, IA-32 system provides headless server capabilities meeting Hardware Design Guide requirements. Management service processors that provide both serial and LAN-based full-time management connections but do not provide an internal 16550 UART hardware interface (i.e. Service Processor does not provide a serial port interface or the serial port interface is provided by a Windows driver and is not available before Windows is loaded) must provide at least the capabilities in this guideline for the serial connection (except 21.2), or must provide the capabilities outlined in #22 IA-32 system that implements a management service processor but no external serial connection meets reset and display redirection requirements for the alternate LAN-based management connection. It is recommended that service processors with both types of the above ports provide both sets of capabilities. 21.1. IA-32 system with management service processor and external serial headless capability supports BIOS redirection of console output, plus serial port and serial headless cabling requirements Systems with service processors that provide external serial support must meet the requirements in guideline #20. IA-32 system that implements headless capabilities without management service processor provides serial headless support, plus the additional requirements listed in this guideline. 21.2. IA-32 system with management service processor and external serial headless capability supports sharing of the service processor serial port with Windows If a management service processor provides a serial port interface externally, this port must allow unconstrained communication between an external device (such as a management platform) and Windows. This communication path must be available as soon as the loader is called. The shared serial port must be locatable via the mechanism described in Serial Port Console Redirection Table. Additionally, the service processor must comply with the requirements of Extensions to the VT100 Terminal Definition. The service processor may interrupt Windows use of the shared port per the mechanisms required in Extensions to the VT100 Terminal Definition. The serial port must not appear altered in any fashion from the perspective of Windows when the port is in use by the service processor. Also, the service processors output to the serial port must comply with Extensions to the VT100 Terminal Definition. 21.3. IA-32 system with management service processor and external serial headless capability supports remote system reset capabilities The management service processor must support a remote system reset capability as described in Extensions to the VT100 Terminal Definition. 22. IA-32 system that implements a management service processor but no external serial connection meets reset and display redirection requirements Required if system implements headless support with a management service processor This requirement is an optional solution to the basic requirement stated in #19, IA-32 system provides headless server capabilities meeting Hardware Design Guide requirements. For enhanced out-of-band management capabilities, systems can provide a management service processor. This processor can enable such advanced capabilities as remote system reset and assistance with disaster recovery. Note that an IA-32 system is not required to provide a management service processor. This guideline addresses the minimum capabilities needed for headless server support with service processors but no external serial connection capabilities. The management service processor must support a remote system reset capability. This capability may be provided through OEM-specific mechanisms. Recommendation Recommended: Systems with service processors provide display redirection capabilities for both text and graphics modes. 23. Uninterruptible power supply that has pass-through legacy serial port supports sharing of pass-through serial port with Windows headless capabilities Recommended If an uninterruptible power supply (UPS) uses an external pass-through serial port interface, this port should allow unconstrained communication among the system for which the UPS provides backup power, a management platform, and Windows. The UPS may interrupt Windows use of the pass-through port per the mechanisms required in Extensions to the VT100 Terminal Definition. Additionally, the UPS should comply with the requirements of Extensions to the VT100 Terminal Definition. The entire end-to-end pass-through serial path should present the serial signals from the platform under management to the management console as though from a serial port through a null modem cable as described in #20.3 IA-32 system headless connections are null modem cables that support Carrier Detect signal. Other Requirements 24. IA-32 system includes APIC support Required IA-32 servers must include Advanced Programmable Interrupt Controller (APIC) support that complies with ACPI1.0b, implemented by including the Multiple APIC Description Table defined in Section5.2.8 of ACPI 1.0b. Features such as targeted interrupts, broadcast interrupts, and prior-owner interrupts must be supported. The local APIC in a processor must be hardware enabled, all hardware interrupts must be connected to an IOAPIC, and the IOAPIC must be connected to local APIC in the processor (or processors). If multiple APICS, processors, or IOAPICs are present, then all components must meet this requirement. Implementation of APIC support on server systems provides a greater number of IRQ resources, even within traditional server architectures. 25. IA-64 system includes SAPIC support Required An IA-64 system must include SAPIC support that complies with the 64-bit extensions to ACPI, implemented by including the Multiple SAPIC Description Table as defined in ACPI 2.0, Section5.2.10.4. 25.1. IA-64 core chipset interrupt delivery mechanisms use SAPIC-compatible programming model IA-64 interrupt delivery mechanisms must use a SAPIC-compatible programming model. 25.2. IA-64 system uses SAPIC-compatible programming model Regardless of the hardware interrupt delivery mechanism, interrupt controllers in IA-64 servers must use a programming model compatible with the SAPIC extension for IA-64 processors defined in ACPI 2.0, Section 5.2.10.4. 26. IA-64 system supports message-signaled interrupts Recommended As the I/O subsystems in servers become more complex, the requirement to provide each PCI slot and device access to a nonshared interrupt line becomes increasingly more difficult and expensive to implement on the system board. Thus, providing support for message-signaled interrupts (MSI) as specified in PCI 2.2 provides an infrastructure to help alleviate this burden. It is expected that the physical (non-MSI) interrupt mechanism will be supported in the system, but that the MSI will be present to facilitate enhanced expandability. This recommendation will become a requirement in a future version of this guide. 27. System with no 8042 or other port 60h and port 64h based keyboard controller meets Hardware Design Guide requirements Required System designs that remove legacy (port 60h/port 64h) keyboard controllers, typically implemented using 8042 or similar controllers, must meet these requirements to function with Windows. Specifically, these systems must properly set Fixed ACPI Description Table Boot Architecture Flags as described in the ACPI specification and Proposed ACPI Specification Changes for Legacy Free, available at http://www.microsoft.com/hwdev/onnow/download/LFreeACPI.doc. IA-64 systems must comply with ACPI 2.0. IA-32 systems must comply with ACPI1.0b. 28. IA-32 system provides necessary ISR support Required IA-32 system designs that reduce the amount of legacy ISR support in conjunction with other legacy removal efforts (such as 8042 removal) must still provide the necessary ISRs required to boot IA-32 systems using BIOS. The minimum requirements include support for ISR 8h, 13h, and 19h (all functions), and ISR 15h, function E820h. Chapter 3 Bus and Device Requirements This chapter defines specific requirements for buses and devices provided in a Basic server system. Tips for selecting I/O performance components. For manufacturers who want to select high-performance components for server systems, the following are design features to look for in I/O components: The system has minimal or no reliance on embedded ISA or low pin count (LPC) and no ISA or LPC slots. Adapter supports bus mastering. PCI adapter properly supports higher-level PCI commands for efficient data transfer. Drivers are tuned for 32bit performance on an IA-32 system, and tuned for 64-bit performance on an IA-64 system. For example, 32bit alignments on the adapter do not interface with 16bit alignments on odd addresses, nor do 64-bit alignments interface with 32-bit alignments. All devices and controllers must be capable of being identified and configured by software through the defined bus mechanisms. I/O Bus Requirements This section summarizes requirements for the I/O bus, with emphasis on requirements related to the PCI bus. 29. System provides an I/O bus based on industry standard specification Required Currently, for most systems, this requirement is met with PCI. 30. All PCI adapters function properly on system supporting more than 4GB memory Required On IA-32 and IA-64 systems that provide support for more than 4 GB of system memory, all 32-bit and 64-bit PCI adapters in the system must be able to function properly. In addition, certain classes of adapterssuch as those on the primary data path where the majority of network and storage I/O occursmust also be able to address the full physical address space of the platform. For 32-bit PCI adapters that will be used on the primary data path, this means that the adapter must be able to support the PCI Dual Address Cycle (DAC) command. Note that 10/100 Ethernet adapters and embedded 10/100 Ethernet devices do not need to support DAC; however, such devices must still function properly in these systems even if they do not implement DAC support. Any other 32-bit devices that do not support DAC and are configured on the same 32bit PCI bus must not interfere with the ability of the devices that support DAC to address all of memory. Additionally, all 32-bit PCI buses, host bridges, and PCI-to-PCI bridges must support DAC. There are special considerations that system designers must address when using legacy devices, adapters, and bridges in systems that provide support for more than 4GB of memory. For information about how Windows 2000 Advanced Server and Windows 2000 Datacenter Server behave in the case where a non-DAC capable bus is detected on a system that supports more than 4 GB of memory, please see the white paper at http://www.microsoft.com/hwdev/newPC/PAEdrv.htm. 31. All PCI bridges in an IA-64 system support DAC Required For IA-64 systems, all PCI bridges on the motherboard must support DAC for inbound access, and DAC-capable devices must not be connected below non-DAC-capable bridges, for example, on adapter cards. New 64-bit adapters must be DAC capable. This DAC requirement does not apply to outbound accesses to PCI devices. However, for systems where DAC is not supported on outbound accesses to PCI devices, the system firmware must not claim that the bus aperture can be placed above the 4GB boundary. 32. System supports a 64bit PCI bus architecture Required for all IA-64 systems Required for all IA-32 systems that support more than 4 GB of system memory All 64bit PCI adapters must be able to address any location in the address space supported by the platform. The server system must support a 64-bit PCI bus if the server has 64-bit processors or has the capability to support more than 4GB of physical memory. Recommendation Recommended: Support for a 66 MHz PCI bus. 33. PCI bus and devices comply with PCI 2.2 and other requirements Required If PCI is present in the system, the PCI bus and PCI expansion connectors must meet the requirements defined in the PCI2.2 specification, plus any additional PCI requirements in this guide. The system must also support the addition of PCI bridge cards, and all PCI connectors on the system board set must be able to allow any PCI expansion card to have bus master privileges. All server systems also must meet the PCI requirements defined in this section, which include requirements to ensure effective Plug and Play support. In particular, see the required implementation for PCI2.2 Subsystem Vendor IDs in guideline #45. Device IDs include PCI Subsystem IDs. Servers that provide support for more than 4GB of physical memory and that provide 32-bit PCI bus capabilities must provide support for the PCI DAC command on 32-bit PCI buses, host bridges, and PCI to PCI bridges, and specific classes of PCI adapters as described in guideline #30. All PCI adapters function properly on system supporting more than 4 GB memory. Recommendation Recommended: PCI controllers should be implemented as peer bridges to provide more effective bus bandwidth. Note on PCI to PCI bridge configuration: The system firmware must correctly configure PCI-to-PCI bridges if the system has a VGA device behind a bridge. Specifically, the system firmware must correctly set the VGA Enable and ISA Enable bits on the bridges, to prevent the bridges from conflicting with each other. Additional details with illustrated examples of correct configurations of PCI-to-PCI bridge devices are provided in the white paper, Configuring PCI-to-PCI Bridges with VGA Cards, available on the web at http://www.microsoft.com/hwdev/pci/vgacard.htm. 34. PCI devices in an IA-64 system support message-signaled interrupts Recommended As the I/O subsystems in servers become more complex, the requirement to provide each PCI slot and device access to a nonshared interrupt line becomes increasingly more difficult and expensive to implement on the system board. Thus, requiring the PCI devices in IA-64 systems to provide support for MSI as specified in PCI 2.2 will provide an infrastructure to help alleviate this burden. This recommendation will become a requirement in the next version of this guide. 35. System makes a best effort to provide each PCI slot and device type access to a non-shared interrupt line Required System designers must make a best effort to provide access to non-shared interrupt lines by meeting these conditions: The system design enables all PCI slots and PCI device types to obtain exclusive use of an interrupt line when exclusive access increases performance. Dedicated PCI interrupts must not use vectors from ISA bus interrupts. The high-end and low-end commodity server platforms present certain design challenges. For high-end servers, PCI 2.2 taken by itself imposes a limitation for Intel Architecture-based systems because the values written to the Interrupt Line register in configuration space must correspond to IRQ numbers 015 of the standard dual 8259 configuration, or to the value 255 which means unknown or no connection. The values between 15 and 255 are reserved. This fixed connection legacy dual 8259 configuration, if examined alone, constrains Intel Architecture-based systems, even when they use sophisticated interrupt-routing hardware and APIC support. For low-end servers, some core logic offerings provide little or no interrupt-routing support, and designers implement rotating access to interrupt resources using simple wire-OR techniques, such as those illustrated in the implementation note in Section 2.2.6 of PCI 2.2. Windows 2000, with its support for both MPS 1.4 and ACPI on 32-bit platforms and ACPI on IA-64 systems, uses mechanisms beyond the legacy methods of routing all PCI interrupts through the legacy cascaded 8259 interrupt controllers to determine proper allocation and routing of PCI bus IRQs. This Windows 2000 capability allows use of interrupts beyond the 015 range permitted by the strict reading of the current PCI 2.2 specification language for Intel Architecture systems. System designers should include sufficient interrupt resources in their systems to provide at least one dedicated interrupt per PCI function for embedded devices and one interrupt per PCI INTA# INTD# line on a PCI slot. This will become a requirement for all servers in a future version of this guideline. When system designers cannot provide a non-shared interrupt line to a particular PCI device or slot because of the situations cited, the server systems documentation must explain clearly to the end user of the system how interrupt resources are allocated on the platform and which devices cannot avoid sharing interrupts. System designers may provide this documentation or information as they deem most appropriate for their product. Some possible mechanisms include: Documenting slots according to the order in which cards should be inserted to prevent interrupt sharing for as long as possible Providing information on interrupt routing and sharing via system setup programs Some instances need additional clarification to fit within the context of this guideline. At the system designers discretion, PCI devices can share an interrupt line under the following conditions: One system interrupt line can be shared by all PCI devices on an expansion card. In other words, PCI INTA# INTD# may share the use of a single system interrupt directed to a given PCI expansion slot. This instance of line sharing applies to both expansion card designs based on PCI multifunction devices and to expansion card designs using PCI-to-PCI bridges. Devices can share an interrupt in a design where a system-board set has multiple instances of a given PCI device performing a specific function. For example, two embedded PCI small computer system interface (SCSI) controllers on a system board can share a single system interrupt line. A single line can be shared when the functions of the devices are very similar, such as a case where one embedded SCSI controller may be dedicated to narrow (8-bit wide) SCSI devices and the other is dedicated to wide (16-bit wide) SCSI devices. On the other hand, an embedded SCSI controller may not share an interrupt with an embedded network adapter on a system board, because they perform two different functions within the system and could contend for the shared interrupt in ways that will reduce overall system performance. 36. System does not contain ghost devices Required A computer must not include any ghost devices, which are devices that do not correctly decode the Type 1/Type 0 indicator. Such a device will appear on multiple PCI buses. A PCI card should be visible through hardware configuration access at only one bus/device/function coordinate. 37. PCI-to-PCI bridges comply with PCI to PCI Bridge Specification 1.1 Required PCI-to-PCI bridges must comply with PCI to PCI Bridge Specification, Revision1.1. 38. System uses standard method to close BAR windows on nonsubtractive decode PCI bridges Required Setting the base address register (BAR) to its maximum value and the limit register to zeroes must effectively close the I/O or memory window references in that bridge BAR. 39. PCI devices do not use the <1 MB BAR type Required Devices must take any 32bit BAR address. Recommendation Recommended for Enterprise class servers: Devices on a 64-bit PCI bus must take any 64-bit BAR address. 40. PCI devices decode only their own cycles Required PCI devices must not decode cycles that are not their own to avoid contention onthe PCI bus. Notice that this requirement does not in any way prohibit the standard interfaces provided for by the PCI cache support option discussed in PCI2.2, which allows the use of a snooping cache coherency mechanism. Auxiliary hardware that is used to provide non-local console support is permitted within the scope of this requirement. 41. VGA-compatible devices do not use non-video I/O ports Required A VGA-compatible device must not use any legacy I/O ports that are not set aside for video in the PCI2.2 specification. Recommendation Recommended: Device includes a mode that does not require ISA VGA ports to function. 42. PCI chipsets support Ultra DMA (ATA/33, minimum) Required For servers that implement PCI ATA connectivity, PCI chipsets must implement DMA as defined in ATA/ATAPI-5, and implement Ultra DMA (also known as UltraATA) as defined in the ATA-5 standard. 43. Functions in a multifunction PCI device do not share writable PCI configuration space bits Required The operating system treats each function of a multifunction PCI device as an independent device. As such, there can be no sharing between functions of writable PCI configuration space bits (such as the Command register). 44. Devices use the PCI configuration space for their Plug and Play IDs Required PCI2.2 describes the configuration space used by thesystem to identify and configure each device attached to the bus. The configuration space is made up of a 256byte address space for each device, and it contains sufficient information for the system to identify the capabilities of the device. Configuration of the device is also controlled from this address space. The configuration space is made up of a header region and a device-dependent region. Each configuration space must have a 64byte header at offset0. All the device registers that the device circuit uses for initialization, configuration, and catastrophic error handling must fit within the space between byte64 and byte255. All other registers that the device uses during normal operation must be located in normal I/O or memory space. Unimplemented registers or reads to reserved registers must complete normally and return zero. Writes to reserved registers must complete normally, and the data must be discarded. All registers required by the device at interrupt time must be in I/O or memory space. 45. Device IDs include PCI Subsystem IDs Required The Subsystem ID (SID) and Subsystem Vendor ID (SVID) fields are required to comply with PCI 2.2. The device designer is responsible for ensuring that the SID and SVID registers are implemented. The adapter designer or system-board designer who uses this device is responsible for ensuring that these registers are loaded with valid non-zero values before the operating system accesses this device. To be valid, the SVID must be provided by the PCI SIG. Values in the SID field are vendor-specific, but to be valid must be unique to a subsystem configuration. For example, if two system boards have the same graphics chipset, but one supports an internal expansion connector while the other has added functionality such as a TV output function, then each must load the SID field with a different, unique value. For implementation details, see PCI Device Subsystem IDs and Windows at http://www.microsoft.com/hwdev/devdes/pciids.htm. 46. Interrupt routing is supported using ACPI Required The system must provide interrupt routing information using a _PRT object, as defined in Section6.2.3 of ACPI 1.0b (for IA-32 systems) and Section 6.2.8 of ACPI 2.0 (for IA-64 systems). It is important to note that the _PRT object is the only method available for interrupt routing on IA-64 systems. 47. System that supports hot swapping or hot plugging for any PCI device uses ACPI-based methods Required Windows Whistler supports dynamic enumeration, installation, and removal of PCIdevices if the implementation strictly complies with the hardware insert/remove notification mechanism as defined in Section 5.6.3 of ACPI 1.0b. Other hot-plug implementations will work under Windows 2000 only if there is a supported hardware insert/remove notification mechanism, such as a bus standard. An example of an implementation based on an appropriate standards-based notification mechanism is a CardBus bus controller. Note that systems implementing hot-pluggable PCI capabilities compliant with the PCI HotPlug Specification, Revision 1.0 must still provide the hardware insert/remove notification mechanism as defined in Section 5.6.3 of ACPI 1.0b. For more information about Windows 2000 and PCI Hot Plug, see http://www.microsoft.com/hwdev/pci/hotplugpci.htm. 48. All 66MHz and 64bit PCI buses in a server system comply with PCI 2.2 and other requirements Required If PCI buses that are 66 MHz, 64-bit, or both are present in a server system, all devices connected to these buses must meet the requirements defined in PCI2.2 or later. Recommendation Recommended: 33MHz/32bit PCI devices and 66MHz/64bit PCI devices should be placed on separate PCI buses to allow the best use of I/O bandwidth in a server system. 49. All PCI devices complete memory write transaction (as a target) within specified times Required All devices must comply with the PCI 2.2 Maximum Completion Time requirement. Complying with this requirement ensures shorter transaction latencies on PCI, allowing more robust handling of isochronous streams in the system. 50. All PCI components comply with PCI Bus Power Management Interface specification Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedEnterprise:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedSOHO:RequiredRequiredRequired The PCI bus, any PCI-to-PCI bridges on the bus, and all add-on capable devices on the PCI bus must comply with PCI Bus Power Management Interface Specification, Revision 1.1 or later. This includes correct implementation of the PCI configuration space registers used by power management operations, and the appropriate device state (Dx) definitions for the PCI bus, any PCI-to-PCI bridges on the bus, and all add-on-capable devices on the PCI bus. ACPI is not an acceptable alternative. 51. System that supports S3 or S4 state provides support for 3.3Vaux Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRecommendedRecommendedEnterprise:RecommendedRecommendedRecommendedSOHO:RequiredRequiredRequired System support for delivery of 3.3Vaux to a PCI bus segment must be capable of powering a single PCI slot on that bus segment with 375 mA at 3.3V and it must also be capable of powering each of the other PCI slots on the segment with 20 mA at 3.3V whenever the PCI bus is in the B3 state. In the case of systems with multiple PCI bus segments, delivering 3.3Vaux to one PCI bus segment does not mean that all PCI bus segments will be required to implement delivery of 3.3Vaux. However, if a system with multiple PCI bus segments provides 3.3Vaux to one or more segments and not to all segments in the system, these capabilities must be clearly marked and documented so that the end user can determine which slots support this capability. Examples of methods for indicating which slots support 3.3Vaux include icons silk-screened on system board sets, slot color-coding, and chassis icons. Systems must be capable of delivering 375 mA at 3.3V to all PCI slots on a power-managed bus segment whenever the PCI bus is in any bus powered state: B0, B1, or B2. 52. PCI bus power states are correctly implemented Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedEnterprise:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedSOHO:RequiredRequiredRequired The PCI bus must be in a bus state (Bx) no higher than the system sleeping state (Sx). This means that if the system enters S1, the bus must be in B1, B2, or B3. If the system enters S2, the bus must be in B2 or B3, and if the system enters S3, the bus must be in B3. Of course, in S4 and S5, the system power is removed, so the bus state is B3. A PCI bus segment must not transition to the B3 state until all downstream devices have transitioned to D3. Control of a PCI bus segments power is managed using the originating bus bridge for that PCI bus segment. For CPU-to-PCI bridges, these controls must be implemented using ACPI or the PCI Power Management Interface Specification, Revision 1.1 (PCI-PM 1.1) or later. For PCI-to-PCI bridges, these controls must be implemented in compliance with PCI-PM 1.1 orlater. 53. Software PCI configuration space accesses on an IA-64 system use SAL procedures Required In particular, access to PCI configuration space must use mechanisms that do not directly reference PCI configuration space but that instead use the services provided by the SAL or other services which in turn call SAL services. 54. PCI-X buses and devices, if present, meet requirements for device and driver support Required Systems are not required to provide PCI-X capabilities. However, a system that implements PCI-X must comply with the PCI-X Addendum, Revision 1.0 or later specification, plus other relevant PCI device and driver requirements defined in this guide. Recommendation Recommended: PCI-X devices should not be mixed with PCI devices on a PCI-X bus in order to ensure optimum use of system I/O bandwidth. 55. InfiniBand fabric connections, fabrics, and devices, if present, meet requirements for device and driver support Required Systems are not required to provide InfiniBand capabilities. However, a system that implements InfiniBand must comply with the requirements defined in the version 1.0 or later specification, plus other relevant InfiniBand device and driver requirements as defined by this guide. USB Requirements This section summarizes requirements for Universal Serial Bus. 56. System includes USB controller with at least one USB port Required To facilitate the eventual migration away from legacy connections for keyboards, pointing devices, serial devices, and parallel devices, server designers must integrate USB functionality into their server platforms with the minimum support being one USB controller with at least one available USB port. USB ports must comply with the related USB requirements in this guide. 57. All USB hardware complies with USB 1.1 Required All USB hardware present on a server system and USB devices, including hubs, must comply with USB 1.1 or later. When a system has more than one host controller, each host controller must provide full bandwidth and isochronous support. Host controllers should be located on PCI to meet this requirement. The host controller providing USB 1.1 functionality must comply with the specifications for either Open Host Controller Interface (OpenHCI), published by Compaq, Microsoft, and National Semiconductor, or Universal HCI (UHCI), published by Intel. Hardware manufacturers who design to one of these specifications are not required to provide an additional Windows2000 device driver for their host controller. Multiple OpenHCI and UHCI USB controllers are supported concurrently by the operating system. 58. USB devices and drivers support maximum flexibility of hardware interface options Required Device and driver designs must provide maximum flexibility for interface options to allow user-preference coordination by the operating system or other resource managers. This flexibility allows graceful use of multiple simultaneous devices and applications in a dynamic environment. Minimum requirements consist of the following: Must provide multiple alternate settings for each interface where any alternate setting consumes isochronous bandwidth. Must not use isochronous bandwidth for alternate setting 0. Devices must consume bandwidth only when they are in use. 59. System and devices comply with USB power management requirements Required The server system must comply with the power management requirements in USB 1.1 or later. In addition, USB devices must comply with the Interface Power Management feature in the USB Common Class Specification, Revision 1.1 or later. 60. USB devices comply with their related USB device class specifications Required A USB peripheral that fits into one of the USB device class definitions must comply with the related USB device class specification. USB class drivers in the operating system are implemented tosupport compliant devices in each particular class. Class driver extensions andWDM allow hardware manufacturers to innovate and differentiate their products while still complying with class specifications in their base operational modes. 61. USB hubs are self-powered Required This requirement does not apply for hubs integrated into keyboards. To minimize USB power consumption requirements, bus-powered hubs must provide ports that can be individually power switched. This contributes to the goal of reducing overall system power consumption. 62. USB devices install without pre-loading software Required A user must not be required to install software before hot-plugging a USB device. Instead, the user must be able to hot-plug the USB device, and then load any software in response to the operating system detection of the newly-attached device. Other Bus Requirements This section summarizes requirements related to other buses. 63. Any subsystems implementing I2O comply with standards and other requirements Required If I2O is implemented in a system, it must meet the requirements defined in this guide and in the I2O Architecture Specification, Version 1.5 or later, available at http://www.i2osig.org. If I2O is implemented on a system, the system firmware must support I2O devices for the following configurations: An I2O-capable system that includes no I2O-intelligent devices, whether provided on the system board set or as add-on devices. The system can have aninstalled adapter that is I2O-ready or I2O-compliant, and the system firmware must initialize the device as a multifunction device. The system cannot boot from this I2O device, because the system firmware does not support initialization of I2O bootable device. An I2O-ready system that has some sort of intelligence on the system board set oronan add-on adapter that enables sending and receiving messages, asdefinedin the I2O specification. This intelligence can be an off-the-shelf processor, an application-specific integrated circuit (ASIC) when it is on thesystemboard set, or it can be included as an add-on adapter. In these cases, the systemfirmware must support initializing and configuring the device, including support for multifunction PCI. Initialization and configuration of a PCI device does not imply that the system firmware supports compliant I2O initialization of boot devices or that the system can boot from an I2O device. An I2O-compliant system that includes support for initializing and booting from I2O devices, whether provided on the system board set or as add-on devices. The system as a whole must be able to pass I2O compliance testing with Windows2000. 64. System does not include ISA or LPC expansion slots Required No ISA or LPC expansion slots are allowed in servers designed to comply with these guidelines. The benefits of an ISA-free system include improved performance, easier and more stable system configuration, and lower support costs. There are no permitted exemption cases. 65. System does not include embedded ISA or LPC network adapters, storage controllers, or graphics adapters Required The benefits of an ISA-free system include improved performance, easier and more stable system configuration, and lower support costs. 66. System does not include ISA or LPC expansion devices Required An ISA or LPC expansion device in this context is defined as being an expansion adapter or device installed in an ISA or LPC slot. No ISA or LPC expansion devices are allowed. There are no permitted exemptions to this requirement. 67. System that supports Winsock Direct connectivity meets requirements for device and driver support Required Systems are not required to provide Winsock Direct (WSD) connectivity capabilities. However, those systems that do must meet the following guidelines: Provide a reliable transport through the combination of WSD hardware and software. The Winsock Direct Specification is provided in the Windows 2000 DDK, and is available online at http://www.microsoft.com/DDK/DDKdocs/Win2k/wsdpspec_1h66.htm. Provide the necessary hardware, software, and driver support to facilitate access via the fast alternate paths. This would include the normal Network Driver Interface Specification (NDIS) 5.0-compliant miniport, plus a System Area Network Windows Sockets (Winsock) provider and a System Area Network Management driver. Installers for these components and any needed network management software components must also be provided. Hardware characteristics and provider guidelines are defined in the Windows2000 DDK, and are available online at http://www.microsoft.com/DDK/DDKdocs/Win2k/wsd_hw_0aur.htm. Additionally, hardware must have page tables to translate user addresses to physical addresses. This allows direct user-mode access to the hardware, permitting endpoint resources to be mapped directly into the address space of a user-mode process. This permits application processes to post messaging requests directly to the hardware, with no system calls and no intermediate data copying. Notes: 1. Winsock Direct and associated hardware are targeted for use in physically secure computer systems and environments, such as those associated with back end or glass house computing environments. 2. Vendors who are sizing their page table hardware should take into account the number of simultaneous connections expected to be supported by the hardware in conjunction with the applications using this connection. The number of simultaneous connections may range widely (from thousands to hundreds). In addition to the number of simultaneous connections, designers need to take into account the page size (specific to the host computer system) and whether the connection is registering memory for RDMA operations in addition to memory registered for messages. Cards that support thousands of simultaneous connections will need to map tens of thousands of page table entries. Device Requirements This section summarizes requirements for the system devices and peripherals provided with server systems. Note: It is recognized that administrators might not want a keyboard, mouse, ormonitor attached directly as a local console to working servers. However, these devices, headless server capabilities, or ability to install the operating system using the Windows Remote Install Server are minimum requirements for installation of the operating system. Additionally, local console, headless server, or both capabilities are necessary to provide maintenance, diagnostic, and troubleshooting capabilities throughout the life of a server. 68. Device driver and installation meet Hardware Design Guide requirements Required Each device must have drivers for the Windows2000 operating system. The manufacturer does not need to supply a driver if the device functions fully and correctly using a driver provided with the operating system. If the manufacturer supplies drivers, the device drivers and installation requirements include the following. 68.1 All devices and drivers meet requirements defined in the guide. Each device included in a server system must comply with the requirements defined in this section and must have supporting32bit (for IA-32 systems) or 64-bit (for IA-64 systems) device drivers. The installation and loading of a driver must not reduce or eliminate functionality of other devices installed on the system. The following are also required: Every driver (or minidriver) must support Plug and Play and power management I/O request packets(IRPs). Real-mode or 16bit protected-mode components must not be provided to operate under Windows2000. Only 32bit protected-mode components are installed on IA-32 systems. All devices in IA-64 systems must have 64-bit Windows2000-compatible drivers. Any device with WDM-based operating system support must have a manufacturer-supplied WDM minidriver or use the driver support provided with the operating system. 68.2 All configuration settings are stored in the registry. The driver must not use INI files for configuration settings. The driver must also include correct provider, version, and copyright entries. This information is displayed in the user interface. 68.3 Files have correct identifiers and are stored in the correct locations. The correct minidriver and any other manufacturer-supplied files specified in the devices INF must be installed in the correct location. For manufacturer-provided files, the vendor must not be identified as Microsoft; all other copyright and version information must be correct for the manufacturer. Driver files provided by the vendor must not use the same file names used by files included in Microsoft operating systems and provided as either retail or OEM products, unless specifically agreed upon with Microsoft. 68.4 Driver installation and removal use methods defined in the Windows2000DDK. The device driver must be removable using Windows-based software by using either the Windows Control Panel option for removing devices or its own remove utility. For information, see Setup, Plug & Play, Power Management in the Windows2000DDK. However, any software applications included with the device can be installed using an alternate Windows-based installation method as defined in the Microsoft PlatformSoftware Development Kit (SDK). Also, any software components and registry entries installed during driver installation must be removed during driver removal. 68.5 Driver supports unattended installation. It must be possible for a user to install a devices driver without being present. This unattended installation can be done using a mechanism such as a script or special software for supplying the required parameters. 68.6 Windows Help file is provided if special driver parameters are used. This requirement ensures that the user can correctly change settings. The devices installation routine must install the Help file as part of the setup program. The user interface for the devices dialog boxes must display the correct Help file; the Help file must contain relevant information to assist the user. The guidelines for implementing Help are defined in the Microsoft Platform SDK. 69. Keyboard and mouse connections meet requirements for bus and device classes Required These requirements, which depend on the type of connection designed into the system, ensure that all Plug and Play requirements are met and that Microsoft drivers support this device. If a PS/2-style keyboard port is used, the following requirements must be met: Comply in full with requirements in the IBM Personal System/2 specifications Use IRQ 1 (via PIC or APIC) to interrupt the processor Map the I/O address ports to 60h and 64h. Return expected scan codes, including send ID (0F2h) and response ACK (0FAh), plus 2byte ID. If a PS/2-style mouse port is used, the following requirements must be met: Comply in full with requirements in the IBM Personal System/2 specifications. Use a device with an 8042-compatible interface to the keyboard controller function to ensure compatibility with Windows2000. In most cases, the existing 8042 keyboard port is sufficient. The mouse port must assert an interrupt that is distinct from the keyboard interrupt. Return expected codes, including send ID (0F2h) and response ACK (0FAh) + 1byte ID. If a USB connection is used, the following requirements must be met: Comply with USB 1.1 or later. Comply with USB Human Interface Device Class Specifications, Version 1.1 or later. Implement minidriver support based on WDM HID class support in the operating system, as defined in Drivers for Input Devices the Windows2000 DDK. If a USB keyboard is the sole keyboard implementation, the system must provide boot support as specified in Startup Support Requirements of Chapter2, System Component Requirements, and as defined inUniversal Serial Bus PC Legacy Compatibility Specification, Version 0.9 or later. This support must provide the ability for the user to enter the systems firmware-based setup program and provide enough functionality to get a USB-aware operating system installed and booted. 70. Serial port adapter meets device class specifications for its bus Required A serial port implementation that uses a nonlegacy bus must meet the specific device class requirements for that bus. For example, a USB to serial adapter must comply with all related USB specifications, including: USB 1.1 or later. USB Class Definition for Communication Devices, Version1.0 (CDC 1.0)or later. The Standard Serial Interface Circuit Emulation appendix in USB CDC 1.0 specifically addresses serial-port compatibility. If a legacy serial port is implemented in a server system, it must meet the following requirements: A 16550A buffered Universal Asynchronous Receiver/Transmitter (UART) orequivalent buffered legacy serial port is required to support high-speed communications while reducing the CPU requirements for servicing the device. The device must be able to support 115.2K baud. A legacy serial port must provide flexible resource configuration and complete dynamic disable capabilities as defined in Plug and Play External COM Device Specification, Version 1.0. Two IRQs are required for each port implemented. In the event of an irreconcilable conflict with other serial ports on the system, a legacy serial port must be capable of being disabled by Plug and Play software. This capability allows at least one of the two conflicting serial ports to operate correctly. The firmware must configure at least one serial port to use either 2F8h or 3F8h. This requirement allows the port to be treated as a boot device by the firmware so that components can use the port for diagnostic purposes in the event that system debugging is required by either the BIOS or the operating system. Recommendation The following are the recommended resource settings for non-PCI devices: Four I/O locations for each port (standard ISA I/O addresses are 3F8h, 2F8h, 3E8h, and 2E8h). Using the standard addresses ensures the proper functioning of software that directly addresses these locations. Two IRQ signals (standard is PIC-based IRQ3, IRQ4). Support of the standard IRQ signals ensures the proper functioning of software written for systems that use standard IRQ signals. If two serial ports are implemented in the system, the following IRQ assignments are recommended: For serial port A: selection between PIC-based IRQ4 and IRQ11. For serial port B: selection between PIC-based IRQ3 and IRQ10. 71. IA-64 system does not include parallel port Required 64-bit Windows does not provide native legacy parallel port support. Parallel ports must not be present in IA-64 systems. 72. If present on IA-32 system, legacy parallel port meets requirements for bus and device classes Required for all IA-32 server types, with ECP support required for SOHO servers This requirement presents information that is useful for system designers who want to incorporate parallel port support in their server designs. There is no requirement that a parallel port be present on a server; designers are strongly discouraged from incorporating parallel ports based on legacy parallel port technologies. However, if a parallel port is present on a server, then it must meet the applicable requirements in this guideline. In addition to other capabilities listed here, the parallel port on a SOHO system must support the ECP protocol as defined by the IEEE 12841994 specification. This capability allows connections with higher-speed parallel peripherals. If implemented in a server system, a legacy parallel port must provide flexible resource configuration following the Plug and Play Parallel Port Device Specification, Version1.0b. Resource requirements must be met for each device of this type on the system. The requirements cannot be split between two ports on the system. For non-PCI devices, the minimum resource requirements for each parallel port on the system are as follows: The parallel port must support ISA I/O addresses of 378h and 278h, plus 3BC or a vendor-assigned I/O address. Using these standard I/O addresses ensures proper functioning of software written for operating systems that directly address these locations. Recommendation Recommended: Map the base I/O address to four additional locations. The parallel port must support PIC-based IRQ5 and IRQ7. Using these standard IRQs ensures proper functioning of software written for operating systems that use standard IRQ signals. Recommendation Recommended: Support five additional IRQ signals. The parallel port must support two unique DMA channel selections if its design supports block data transfers to memory using DMA controllers. Notice also that the DMA function will not work on a parallel port without anIRQ because the end of a DMA transfer is signaled by an interrupt. To ensure Plug and Play support for resolution of resource conflicts, a full list ofoptions for all possible configuration combinations must be enumerated, including: Options for both extended capabilities port (ECP) mode, which requires an I/Oaddress, an IRQ, and a DMA selection, and standard LPT mode, which requires only an I/O address. Options that specify only the I/O address, which allows Windows2000 to assign the IRQ and DMA channel. On all ACPI-based systems, Windows2000 obtains information on the parallel port base addresses through the ACPI tree (for parallel ports implemented on the system board set rather than on an expansion card on an expansion bus). A legacy parallel port implemented in a server system must also meet the following requirements: Enhanced parallel port (EPP) support does not use restricted I/O addresses. Some EPP implementations require eight contiguous I/O ports. If EPP support is implemented, the hardware cannot use the ISA I/O address 3BCh as a base I/O address because VGA devices require use of port 3C0h. Compatibility, nibble mode, and ECP protocols meet IEEE 12841994 specifications. Support for a parallel port must include the compatibility mode and nibble mode protocols required by the IEEE 12841994 specification for minimum compliance. This support allows other IEEE 1284-compliant devices to be connected without problems. Recommendation Recommended: Legacy parallel port supports the ECP protocol as defined by IEEE 1284, allowing connections with higher-speed parallel peripherals. However, if the port can support the compatibility and nibble mode protocols as described earlier, it complies with the Basic and Enterprise class guidelines that allow connection of other IEEE 1284-compliant devices. Port connectors meet the minimum requirements defined in the IEEE 1284I specifications. IEEE 1284Icompliant ports must use a standard DB25 connector found on existing system parallel port designs. This connector is called an IEEE 1284A connector in the specification. IEEE 1284IIcompliant ports must use an IEEE 1284C connector. This connector is used on both the port and the peripheral device. IEEE 1284 peripherals have Plug and Play device IDs. The device ID is described fully in the IEEE 1284 specification. All characters in the device identification string must consist only of ASCII values 20h7Fh. The device identification string consists of a leading zero, a hexadecimal value that represents the length of the string, and then a set of fields, in ASCII, with a unique identification string. In addition to the requirements specified in the Plug and Play Parallel Port Device Specification, Version 1.0b, the device ID string must contain the following keys, at a minimum. The keys are case sensitive and can be abbreviated in INF files as indicated. Required keyAbbreviated stringMANUFACTURERMFGMODELMDLCLASSCLSDESCRIPTIONDES All MANUFACTURER and MODEL key values must remain unique for each manufacturer. All MANUFACTURER, MODEL, CLASS, and DESCRIPTION key values must remain static for a specific unit; ID values do not change for different hardware configurations. For example, a user adding a memory module to a printer should not change the MODEL key value reported as part of the device identifier. However, if the user adds memory by installing an upgrade kit that requires a different driver or requires the existing driver to behave differently, then changing the MODEL value is acceptable as part of the upgrade installation process. The CLASS key describes the type of parallel device. The CLASS key can contain the values PRINTER, MODEM, NET, HDC, PCMCIA, MEDIA, FDC, PORTS, SCANNER, or DIGCAM. HDC refers to hard disk controller. MEDIA refers to any multimedia device. FDC refers to floppy disk controller. The DESCRIPTION key is an ASCII string of up to 128 characters that contains adescription of the device that the manufacturer wants to have presented if a device driver is not found for the peripheral. For information, see How Does Setup Select a Driver For a Device? in the Windows2000 DDK. Recommendation Recommended: The CID key can provide a value that exactly matches a peripheral name supported by a device driver shipped with Windows2000 Server. The value must match a value listed in the devices INFfile. 73. USB-to-printer port adapters comply with USB specifications Required A USB to printer port (IEEE 1284, or parallel) adapter must comply with all related USB specifications, including: USB 1.1 or later. Universal Serial Bus Class Definition for Printing Devices, Version1.0 or later. 74. System includes emergency repair support Required If an OEM does not provide a floppy disk drive for this purpose, an alternate emergency repair method must be provided. Recommendation Recommended: Floppy disk support is recommended for emergency repair disk purposes. If a floppy disk drive is provided, the recommended support should be a solution based on an external bus, supporting migration away from legacy devices. If implemented as an ATA floppy drive, the drive must comply with ARMD 1.0 or later. 75. Primary graphics adapter on IA-64 system meets minimum requirements Required At a minimum, the adapter must support 800נ600נ256color, following the VESA monitor timing standards and guidelines for this mode. The adapter must also work normally with the default VGA mode driver, which is required for installing the operating system, so the primary adapter must support 4bit planar VGA mode. 76. Primary graphics adapter on IA-32 system, if present, meets minimum requirements Required Server systems which meet the requirements in this design guide for 32-bit Windows headless server capabilities are not required to supply a local console primary graphics adapter. However, if a primary graphics adapter is present in the system, at a minimum, the adapter must support 800נ600נ256color, following the VESA monitor timing standards and guidelines for this mode. The adapter must also work normally with the default VGA mode driver, which is required for installing the operating system, so the primary adapter must support 4bit planar VGA mode. Chapter 4 Networking and Communications Requirements This chapter defines basic feature requirements for network adapters and other communications hardware. See also the related requirements for remote new system setup and service boot support using DHCP and TFTP as defined in Manageability Requirements of Chapter7, Reliability, Availability, and Serviceability Requirements. In this guide, all network communications devices are based on the same NDIS 5.0 requirements, which includes requirements for power management and Plug and Play capabilities. NDIS 5.0 represents a number of extensions to the interface described in NDIS 3.0 and 4.0. The basic requirements, services, terminology, and architecture of these earlier versions also apply to NDIS 5.0. The NDIS architecture is included in Windows2000 and is documented in Network Drivers in the Windows2000 DDK. For additional background information about NDIS 5.0, see the web site at http://www.microsoft.com/hwdev/network/. Notes: 1. References to adapters, network interfaces, and so on in this chapter should be taken to apply to add-on network adapter cards, network implementations on the system board, and external network interfaces equally and without preference for any of these types of implementation, unless otherwise noted. 2. This design guide does not contain requirements for Bluetooth devices. However, future versions of Windows operating systems will use Bluetooth technology as a wireless external bus, rather than as a wireless networking technology. Therefore, Bluetooth devices are not subject to the requirements contained in this chapter; in particular, they do not require NDIS drivers. Network Adapter Requirements This section describes the requirements for network adapters. Many of these requirements also apply to other network communications devices such as Integrated Service Digital Network (ISDN), cable modem, and Asymmetric Digital Subscriber Line (ADSL), as indicated later in this guide. Note: It is recognized that OEMs supply server systems to customers in situations where the customer will insert network adapters at the end-user site. Systems designed for specific customers are exempt from including a network adapter. However, if a network adapter is included in the system, it must meet these requirements. Also, references in this chapter to adapters, network interfaces and so on should be taken to apply equally to add-in network adapter cards, network implementations on the system motherboard, and external network interfaces, without preference for any of these types of implementation unless otherwise noted. 77. System includes non-ISA/non-LPC NDIS 5.0 network adapter Required An ISA or LPC-based network adapter solution is not allowed for a server system. 78. Network adapter uses NDIS 5.0 miniport driver Required A network adapter must use an NDIS 5.0 miniport driver and meet the following requirements. 78.1 The network adapter driver must be based on and comply with NDIS 5.0 in order to take advantage of Windows 2000 operating system capabilities. The driver must follow the NDIS miniport driver model defined in Network Drivers in the Windows2000 DDK. Important: The development of full MAC drivers is no longer supported. Support for full MAC drivers will be removed in future versions of Windows. 78.2 If the network device is for connection-oriented media, it must meet connection-oriented miniport driver and call manager driver requirements. This is required for connection-oriented media such as Asynchronous Transfer Mode (ATM), ISDN, Frame Relay, or X.25. Drivers for such devices must follow the guidelines in Connection-Oriented NDIS in the Windows2000 DDK. In some cases, such as ATM, the call manager driver is included in the operating system and the vendor needs to provide only an NDIS 5.0 connection-oriented miniport driver. For other connection-oriented media, such as ISDN or X.25, the call manager is not included in the operating system and must be provided with the hardware. The call manager support can be integrated in the connection-oriented miniport driver or implemented as a separate NDIS 5.0 call manager driver. The documentation for both integrated or separated call manager driver is included in Connection-Oriented NDIS in the Windows 2000 DDK. 78.3 An intermediate NDIS 5.0 miniport driver is required for network adapters that connect to the system using IEEE 1394 or USB buses. This driver exposes its media type to NDIS at its upper edge and interfaces with the appropriate bus driver, IEEE 1394 or USB, at its lower edge. The NDIS 5.0 miniport driver must also meet these requirements: 78.4 Driver works correctly with Microsoft network clients and protocols This includes the 32-bit Microsoft client and NetWarecompatible clients provided with Windows, whether connected to a Windows 2000based server, a Novell NetWare 3.x, 4.x, or 5.x server, or a Windowsbased peer server. In all cases, this includes connections using Microsoft Transmission Control Protocol/ Internet Protocol (TCP/IP), IPX/SPXcompatible protocol, and NetBIOS Extended User Interface (NetBEUI) in LANs. In WANs, connections must work correctly using TCP/IP. 78.5 Driver makes only NDIS library calls or WDM system calls NDIS conformance must be validated over single and multiple network connections. For Windows 2000, this must be validated on a multiprocessor system as part of the testing process. 78.6 Driver uses Windows 2000 INF format All network components must use the Windows 2000 INF format. For information, see Creating an INF File in the Windows2000 DDK. For Windows2000, there is no legacy INF support. 78.7 Driver is deserialized NDIS 5.0 introduces support for deserialized miniports, enabling performance improvements and scalability on Windows 2000 multiprocessor systems. 79. NDIS 5.0 miniport driver supports high-performance send and receive calls Required NDIS drivers for server-side network adapters must support the higher performance send (NdisSendPackets) and receive (NdisMIndicateReceivePacket) calls as documented in the Windows 2000 DDK. 80. Full-duplex adapter automatically detects and switches to full-duplex mode Required The network adapter must negotiate full duplex operation by default when both the network adapter and switch port in a link pair support full duplex and the networking technology provides a standard way for each to detect and/or negotiate the duplex mode. Half duplex can be used if that is the only mode supported by one or both link partners or if it can be configured manually when warranted by special conditions. The goal is to configure this setting automatically without end-user intervention. 81. Network adapter automatically senses presence of functional network connection Required Where the network media allows it, the network adapter must be capable of dynamically determining whether it is connected to a functional link partner such as a hub, switch, or router. The device must indicate the link state in the following cases: At boot time After returning to D0 power state When the link state changes while in the D0 power state (no time limit is specified for the required detection or status indication) If the adapter is on an expansion card not used as a boot device, then the device drivers can determine the presence of the functional link. If the device is not connected toa functional link partner, the miniport driver must provide appropriate NDIS status indication, using support for cable sense in NDIS 5.0. For information about NDIS status codes and indication mechanisms, see Reporting Hardware Status in the Windows 2000 DDK. 82. Network adapter automatically senses transceiver type Required Network adapters that support multiple transceivers must be capable of automatically detecting which transceiver type is connected to the network unless this is not possible with the network media at hand. The network adapter then must automatically drive the correct connection. In all cases, the user must not be required to set jumpers or manually enter information to inform the operating system of the transceiver type. 83. Network adapter can transmit packets from buffers aligned on any boundary Required Buffer alignment refers to whether a buffer begins on an odd-byte, word, double word, or other boundary. Adapters must be able to transmit packets any of whose fragments are on an odd-byte boundary. For performance reasons, packets should be received into contiguous buffers on a double word boundary. 84. Network adapter communicates with driver across any bridge Required If the adapter uses a bridge, all communications must be free of errors across any bridge, such as a PCI bridge adapter. 85. Network adapter supports configuration capabilities and registry settings for performance tuning Required Some network adapters and drivers might support additional configuration capabilities for performance tuning when used in special environments or applications. Any tuning parameters that are set by the user, an application, or the operating system must be controlled through registry variables. An example of such performance optimizations might be adjustment of interrupt moderation or the number of receive buffers for systems used as dedicated routers. In addition to Dynamic Interrupt Moderation, there are other techniques that can be implemented on network adapters to maximize system performance for special environments or applications. User-tunable parameters must be set through registry variables as parameters for network adapters and must not be set in .INI files, configuration files, or in other locations. These parameters can be accessed using the Advanced Page in the Device Manager. The variables should be set through standard user interfaces provided in Windows. 86. PCI network adapter properly supports higher-level PCI commands Required Specifically, network adapters must properly support the Memory Read Multiple (MRM), Memory Read Line (MRL), and Memory Write and Invalidate (MWI) commands. PCI commands are defined in the PCI 2.2 specification. This requirement ensures efficient data transfer. 87. PCI network adapters are bus masters Required To improve the system performance by decreasing the load on the system processor, the PCI network adapters must be bus masters. 88. USB or IEEE 1394 network device complies with related device class specifications Required External networking devices attached using a serial bus (USB, USB 2.0, or IEEE1394) must support standard control interface specifications where applicable. All external USB networking devices must support USB CDC 1.1 and must support one of the following: Ethernet connection model (CDC 1.1) Remote NDIS over CDC 1.1 Communications API (CAPI) over CDC 1.1 (ISDN modems) External IEEE 1394 networking adapters must support Remote NDIS over SBP2. 89. Network device and driver meet Plug and Play and power management requirements. Required The additional Plug and Play and power management requirements for network communications devices include the following: Plug and Play capabilities support multiple adapters. For network communications devices, the Plug and Play IDs and resource support must be sufficient to automatically support the addition of multiple network communications devices to the system. This is true for the same and different types of network communications devices. All resource settings are reported in the user interface. All resource settings must be viewable in the Device Manager and in adapter properties dialog boxes. All resource settings that can be changed by the user must be changed using the standard Windows user interface and not by way of INIfiles or other setting files. This implies that all device resources must be set and read through the devices standard bus interfaces. For PCI devices, this interface is the PCI configuration space. Further, device parameter settings must be stored in the registry. 90. Network communications device supports wake-up events Recommended This recommendation applies specifically to the following network communications devices and their associated NDIS 5.0 miniport drivers: Ethernet and Token Ring network adapters Integrated Data-Over-Cable Service Interface Specification (DOCSIS) cable modems Other or future devices that transfer 802.3/DIX Ethernet framed packets Note: The Network Device Class Power Management Reference Specification, Version 1.0 or later, does not yet define wake-up mechanisms for ISDN adapters or any network communications adapter that uses ATM signaling. The system must be capable of being awakened from a lower power state based on network events specified by the local networking software. This capability yields the result that any standard Windows network accesssuch as connections to shared drives and Winsock connections, plus service and management applicationscan awaken a system from lower powerstates transparently. As defined in Network Device Class Power Management Reference Specification, a network adapter and its driver must support wake-up on receipt of a network wake-up frame. Support for wake-up on detection of a change in the network link state or on receipt of a Magic Packet event is optional. Implementation details are described in the Network Wake-up Frames and Network Wake-up Frame Details sections of Network Device Class Power Management Reference Specification, Version 1.0a and in the Windows2000 DDK. See also the implementation notes at http://www.microsoft.com/hwdev/devdes/netpm.htm. The packet patterns that define the wake-up frames are provided to the NDIS 5.0 miniport driver by the operating system. To enable Wake-On-LAN capability for basic networking scenarios, the network interface card must be capable of storing information describing a minimum of four wake-up packet patterns, and it must be able to recognize wake-up packets based on pattern matches anywhere in the first 128 bytes of the packet. The network adapters should be capable of storing information describing at least eight wake-up packet patterns to enable more advanced applications such as Wake-On-LAN capability on multi-homed systems or on receipt of multicast packets, in addition to the basic scenarios described here. PCI-based network adapters must support the generation of a power management event (PME# assertion) from the D3 cold device state if the physical layer technology is generally capable of operating under the voltage and current constraints of the D3 cold device state. For example, 100Base-TX adapters can meet this requirement based on the state of the art in mid-1988. 1000Base-SX, 1000Base-LX, or 1000Base-TX (gigabit Ethernet using optical fiber or copper media) cannot meet this requirement because of the power required to operate the optical physical layer. Connectionless Networking Requirements This section lists the design guidelines that apply to all connectionless networking media, such as IEEE 802 LAN adapters (except for wireless) and Fiber Distributed Data Interface (FDDI) adapters. 91. Network adapter offloads TCP/IP checksum, IP Security encryption, and TCP message segmentation Recommended Server-side network adapters should support task-offload mechanisms to offload TCP/IP checksum calculation, IP Security encryption, and TCP message segmentation to intelligent hardware. This provides better utilization of computing resources on the server system. Mechanisms for off-loading these tasks are documented in the Task Offload topic in the Windows 2000 DDK. 92. Network adapter supports filtering for at least 32multicast addresses Required This requirement applies to those networking technologies that support multicast, such as Ethernet, but it does not apply to those which do not support multicast, such as Token Ring, which distributes IP multicast traffic using the functional address as specified in RFC 1469. This capability is needed to support push technology applications such as Microsoft NetShow, Active Desktop, and Internet Explorer 5.0 and later. The minimum required capability is for filtering 32 multicast addresses (also known as channels). 93. Server network adapter supports Load Balancing and Failover capabilities Recommended Server network adapters should support the bundling of multiple physical network links into a single logical link for the purpose of bandwidth aggregation and physical link failure protection. This capability is dependent on the features of the network switching elements and should support commonly implemented network switches and their respective link aggregation and fail-over techniques. 94. Server network adapter supports remote system setup capabilities Recommended It is strongly recommended that server network adapters support remote new system setup capabilities as defined in PXE 2.1. 95. Network connections used for remote boot meet PXE requirements Required On server systems that support remote new system setup, network connections used for remote boot must comply with remote new system setup capabilities as described in PXE 2.1 or later (for IA-32 systems), or EFI 1.0 (for IA-64 systems). It must be possible to enable and disable the remote boot (remote new system setup) capabilities through administrative control in order to maintain server security. Note: Multiport network adapters can supply remote system setup capabilities on none, any, or all ports. 96. Network adapter and driver support promiscuous mode Required This ensures that the adapter can be used with Microsoft Network Monitor Agent. This requirement applies only to LAN (non-switched) media. Notice that, by default, promiscuous mode is not turned on. Enabling promiscuous mode should be possible only by using the Microsoft Network Monitor Agent or another similar administrative application. 97. Network adapter and driver support multicast promiscuous mode Required By supporting this feature, the adapter and the driver enable performance improvements for special-purpose servers and applications, such as multicast routers. This requirement applies to those networking technologies that support multicast, such as Ethernet, and not to those that do not support multicast, such as Token Ring. Notice that, by default, multicast promiscuous mode is not turned on. 98. Network adapter and driver support priority for IEEE 802-style networks Required Windows Quality of Service (QoS) components provide link layer priority information to NDIS 5.0 miniport drivers in each transmitted packets NDIS_PER_PACKET_INFO structure. Priority values are derived by mapping Internet Engineering Task Force (IETF) Integrated Services (intserv) service types to 802.1p priority values (referred to as the user priority object in http://search.ietf.org/internet-drafts/draft-ietf-issll-is802-svc-mapping-01.txt, which is likely to be superceded by a later draft or final specification). The intserv service type used for the mapping is determined by QoS-aware applications or on behalf of the application, by QoS-aware operating system components. 802.1p/q-capable Ethernet drivers are expected to use the priority level indicated in the NDIS_PER_PACKET_INFO structure to generate the corresponding field in the 802.1p/q MAC headers of transmitted packets. Similarly, these drivers are expected to extract the appropriate information from the MAC headers of received packets and to copy the priority to the NDIS_PER_PACKET_INFO structure before indicating the packet to higher protocol layers. Note that any link layer driver may interpret the priority information in the NDIS_PER_PACKET_INFO structure and use it as appropriate for the particular media. For more information, see Packet Support for 802.1p Priority in the Windows 2000 DDK. See also QoS: Assigning Priority in IEEE 802-style Networks, available at http://www.microsoft.com/devdes/qos802.htm. Modem Requirements This section presents general requirements for modems. There are two types of modems to consider. Traditional serial modems These modems, originally designed for PCs, are connected to the server system by a serial port, or are implemented as a driver that emulates a traditional modem. The fundamental design principle for compatibility with Windows 2000 is for a serial modem to be supported by the Universal Modem Driver (Unimodem), which uses INF files to characterize device operation. Unimodem INF design is described in the Modem Developers Kit (MDK), included in the Windows 2000 DDK. Networking modems (Public Switched Telephone Network (PSTN) modem configured as networking devices, ADSL modems, cable modems) These modems are designed for large servers and connected to the system using networking driversfor example, NDIS 5.0 miniports. The fundamental design principle for compatibility with Windows 2000 is for a networking modem to be supported by NDIS 5.0, as defined in Network Drivers in the Windows 2000 DDK. Server Types and PSTN Modem Usage. SOHO servers typically have a small number of serial modems, used for Remote Access (in or out), shared ISP access, fax (in or out) and interactive voice response (IVR). The modems used are traditional serial modems. These modems are typically connected by individual PSTN phone lines or by ISDN BRI lines. In an enterprise, the modem servers may support hundreds of modems, used primarily for inbound remote data access such as for an ISP or corporate network. The modems are typically connected to public networks on high-speed digital lines (T1, ISDN, or PRI). Different servers may be used for dedicated incoming fax reception or IVR. Note that Windows 2000 Unimodem and Telephony Application Program Interface (TAPI) can be used to support hundreds of modems for each server. Design Issues for Server PSTN Modems. The following are the design issues to consider, based on server types: For modems designed for Basic servers, the most important additional design issues are: Support for V.90, as host side modems where possible, which requires an ISDN BRI or other digital network connection. Do not migrate the modem signaling function, for example, V.90 or V.34, into the system. For SOHO Server modems, the most important design issues are: Adaptive answering features: V.8, V.8bis, V.251. Full duplex voice strongly recommended, using V.253, to support small scale Interactive Voice Response. For Enterprise Server modems, the most important design issues are: The NDIS 5.0 miniport interface is preferred. Fax is optional, not mandatory, because the most common solutions use separate hardware and drivers, on separate public network connections. 99. System includes WAN communications device Recommended The following device options, as defined later in this chapter, can meet this requirement: Serial modem with V.34 and V.90 capabilities, supporting server fax capabilities (two or more ports recommended) ISDN adapter (NDIS driver) or ISDN modem (Unimodem driver) ATM adapter (NDIS driver) ADSL adapter (NDIS driver) Cable modem (NDIS driver) Note: It is recognized that OEMs supply systems to customers in situations where the customer will insert modem devices at the end-user site or where the customer has particular feature demands. Server systems designed for specific customers are exempt from these requirements. Unimodem-supported Modem Requirements The following requirements apply to modems connected as logically serial modems, using Unimodem as the TAPI service provider. 100. Modem controller meets minimum requirements Required The following are minimum requirements for the modem controller, in addition tosupporting V.250: Unimodem Diagnostics command, AT#UD Software-upgradeable modem controller (upgradable ROM or Windowsmodem) AT command buffer of at least 60 characters Semicolon (;) character dial string modifier, unless prohibited by national regulations 101. PSTN modem supports ITU-T V.250 command set Required ITU V.250 (formerly V.25 ter) is a superset of TIA-602. TIA-602 codifies the most common data modem commands and responses. If the AT command for a particular function is implemented, the corresponding V250 AT command must be supported. The essential V.250 commands are the following: All basic modem commands from TIA-602 (no + prefix) Identification: +GMI, +GMM, +GMR, +GCI Port control: +IPR, +IFC, +ILRR Modulation: +MS, +MR Error control: +ES, +ER Data compression: +DS, +DR 102. Device complies with device class power management Required The Communications Device Class Power Management Reference Specification, Version 1.0 or later, provides definitions for the OnNow device power states (D0D3) for modems. The specification also covers the device functionality expected in each power state and the possible wake-up event definitions for the class. Power states D0 and D3 cold, including wake-on-ring support, are required for modems on power managed buses, including PCI and USB. Modem adapters that use the PCI bus must be capable of generating a power management event (PME# assertion) from the D3 cold device state. Recommendation Recommended: Modem adapters should also support capture of Caller ID with hardware support for the AT+VRID resend caller ID voice modem command. 103. Device supports wake-up events Required A modem must be able to cause a wake-up event on an incoming ring as defined in Communications Device Class Power Management Reference Specification. This applies for modems on all power-managed buses, including PCI and USB. PCI devices are required to support D3 cold on a PCI 2.2-based system with auxiliary power. On all other power-managed buses (such as USB), support for either D2 or D3 is acceptable. 104. Data modem supports v.90 and v.34 modulation and other requirements Required The requirements for a data modem include the following: V.90 modulation V.34 modulation V.42 LAPM error control V.42bis data compression V.80 synchronous data access protocol 105. Data modem supports digital connection to support host-side V.90 operation Windows2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RequiredRequiredRequiredSOHO:RecommendedRequiredRecommended V.90 depends on a digital connection for the host-side modem to the public telephone network, typically using T1 or ISDN. Server modems should be designed for digital connection, to support host side V.90, where digital connections are available. 106. Fax modem supports 14.4 Kbps (V.17) with Class 1 (T.31) command set Required for PSTN connected modems, recommended for ISDN connected modems If fax modem capabilities are implemented, the fax modem must support 14.4 Kbps (V.17) with the Class 1 (ITU T.31) commandset. If fax modems include fax/data media detection (for example, T.32 +FAA command), the INF must include the necessary registry keys, as defined in the MDK in the Windows 2000 DDK. Recommendation The following are recommended: Class 1.0 (ITU T.31) +FAR support, which allows the hardware to perform adaptive carrier detection Class 2.0 (ITU T.32 or TIA592) for server modems, which offloads the T.30 session protocol to the modem 107. Modem supports call control signaling, controlled using V.251 modem commands Required Modems must support the ITU V.251 standard for PC-controlled call control, including: Support Data Communications Equipment (DCE) controlled V.8 operation with DTE notification Support DTE-controlled V.8 operation ( values of 2, 3 and 4) Support DTE-controlled V.8bis operation Support backward compatibility for media detection with terminals using V.25 signaling, for example, data calling tone and fax calling tone Support backward compatibility for media detection with older modems, for example, V.32 and V.32 bis Provide a means for turning on the V.8 Calling Indicator (CI) signal for originating calls 108. Modem supports blacklisted and delayed number clearing Required where applicable During certain international Post, Telephone, and Telegraph (PTT) certification processes, modems must support the blacklisted and delayed numbers feature. That means that when the modem fails to connect to a specific number for a certain number of times, the dialed number is stored in an internal list. Any subsequent automated dialing operation to this number is then either delayed for atime (delayed) or forbidden until some form of manual intervention occurs (blacklisted). The international certification processes specify that manual intervention using an external device is required in order to clear these numbers. Recommendation Recommended: The modem should clear its blacklisted and delayed number tables if the associated handset goes off hook. 109. Voice modem support is provided Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:OptionalOptionalOptionalEnterprise:OptionalOptionalOptionalSOHO:RecommendedRecommendedRecommended Voice capability is recommended for SOHO server modems to support Interactive Voice Response and 3-way DATA/FAX/Voice call classification on the same phone lines. This support, if implemented, must meet the requirements documented in guideline #110. Voice modem supports ITU V.253 (AT+V). 110. Voice modem supports ITU V.253 (AT+V) Required for PSTN connected modems; recommended for ISDN or T1 connected modems Voice capability is not mandatory, but if support for voice modem is implemented in a server system, it must meet the following requirements: V.253 compliance Voice recording and playback (+VTX, +VRX, +VTR) DTMF generation and detection during voice I/O Voice I/O support of 8bit, 8kHz pulse coded modulation (PCM) formats: unsigned linear, G.711 (Alaw and ulaw) Programmable gain control for all audio channels Caller ID Detection and Reporting (+VCID) ATM Adapter Requirements This section summarizes requirements for ATM hardware. The NDIS 5.0 extensions provide kernel-mode NDIS 5.0 client drivers with direct access to connection-oriented media such as ATM. The architecture for Windows2000 extends native ATM support to Winsock 2.0, TAPI, and applications based on Microsoft DirectShow by providing system-level components that map the applicable Winsock, TAPI, and DirectShow APIs to NDIS 5.0, extending direct ATM access to user-mode applications. ATM is not required for any of the server classes. If an ATM adapter is designed for operation under Windows2000 in the server system, itmust meet the requirements defined in this section. For more details about the following requirements, see ATM Layer Specification inATM User-Network Interface Specification, Version3.1. This specification also includes references to other relevant specifications. 111. ATM adapter meets network adapter requirements Required ATM adapters must meet all requirements listed in Network Adapter Requirements earlier in this guide. 112. ATM adapter supports a minimum number of simultaneous connections Required The Virtual Path Identifier (VPI) and Virtual Channel Identifier (VCI) ranges supported by the adapter affect the maximum number of simultaneous connections supported on a system. This affects the applicability of the adapter to ATM applications such as LAN Emulation, where at least one dedicated virtual channel is created between each pair of communicating ATM hosts. System typeSimultaneous connectionsClient (ATM adapter)64 or moreClient (Integrated ATM/ADSL-adapter)16 or moreServer 2048 or more A sample driver is provided in the Windows2000 DDK to guide developers in properly supporting resources to meet this requirement. 113. ATM adapter supports all service types defined by the ATM Forum Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended The ATM adapter should support the constant bit rate (CBR), variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) service types asdefined by the ATM Forum. 114. ATM adapter supports UBR service type Required UBR is used by default for standard ATM services such as LAN Emulation and IP over ATM. In addition, Point-to-Point Protocol (PPP) is a widely used model for residential network access and UBR is used by default for PPP over ATM virtual circuits. Therefore, it is required that ATM adapters support the UBR service type. 115. ATM adapter supports a minimum number of simultaneously active VBR or CBR connections Required Support for at least two simultaneously active VBR or CBR connections is required for basic ATM signaling and management. Support for additional VBR/CBR connections is needed for ATM adapters that support multimedia or other traffic that demands QoS. These are listed in the following table. System typeSimultaneous active VBR/CBR connectionsClient 6Server 500 116. ATM adapter supports traffic shaping Required The ATM adapter must support and enforce all the traffic-shaping rules specified for each service type it supports, including CBR, VBR, ABR, and UBR. Note: This includes enforcement of peak cell rate on UBR virtual circuits. 117. ATM adapter enforces PCR on UBR virtual circuits Required ATM adapters will be used to connect router, remote access, and content servers to the public ATM network. High-speed residential broadband access networks such as ADSL and cable modem will use an ATM virtual circuit from home or small office computers to connect directly to these servers. When the Windows Dial-Up Networking UI is used to connect from a home or small business computer to a remote router or server, a PPP link is established over an ATM virtual circuit. The service type used on this PPP-over-ATM virtual circuit is UBR. When creating the UBR virtual circuit, Windows requests upstream and downstream line rates, or Peak Cell Rates (PCR), equal to the upstream and downstream line rates provisioned for the user. Windows uses the ATM Interim Local Management Interface (ILMI) protocol to obtain information, such as getting the users provisioned line rates from the public network. To avoid packet loss and ensure efficient network utilization, it is critical that all ATM, integrated ATM/ADSL adapters, and ATM/cable modem adapters enforce requested PCR on UBR virtual circuits. Because any ATM adapter might be installed in a server to which clients connect through the public network, this requirement applies to all ATM adapters. 118. ATM adapter and driver support dynamic link speed configuration Required When connected to a residential broadband network, ATM adapters must restrict the aggregate transmission rate across all active virtual circuits so that it does not exceed the provisioned upstream bandwidth of the residential broadband network. All integrated ATM/ADSL and ATM/cable modem adapters must support aggregate shaping of upstream bandwidth according to the provisioned upstream bandwidth or the trained bandwidth, whichever is lower. Some implementations can support rate adaptation, and lower-than-provisioned rates may be negotiated due to poor line conditions. All 25-Mbps ATM adapters must support this as well, because any 25-Mbps ATM adapter could be used to connect by way of an external ADSL modem to an ADSL network. This support is optional for ATM adapters with line rates higher than 25 Mbps. The Windows ATM Call Manager uses ILMI to query the public network to discover the provisioned maximum line rates for incoming and outgoing traffic. The Call Manager then uses the OID_GEN_CO_LINK_SPEED NDIS request (in SET mode) to set the line rate for both incoming and outgoing traffic. The adapter must shape the aggregate of ATM traffic within these incoming and outgoing rates. 119. ATM adapter supports OAM Required Operation and maintenance (OAM) is needed for diagnostics. This capability is required for a server system. At minimum, the ATM adapter must respond to received F4 and F5 loopback OAM cells. Support for other layers, F1F3 is optional. 120. ATM adapter supports buffer chaining (Tx + Rx) Required This feature is needed for large packets. This capability is required for server systems, but is recommended for client systems. ADSL Device Requirements This section summarizes requirements for ADSL hardware. Support is provided in the Windows2000 Server operating system for ADSL adapters and external ADSL modems, such as those using USB, which provide a faster method for moving data over regular phone lines. ADSL adapters are not required for any server type, but if an adapter is included in a server, it must meet the requirements in this section. ADSL is not required in a server system, but if present, it must comply with these requirements. Please review the white paper, An Interoperable End-to-End Broadband Service Architecture over ADSL Systems, Version 3.0, which discusses end-to-end service interoperability over ADSL. This paper, which is available from the web site at http://www.microsoft.com/hwdev/publicnet/, was jointly developed by over 30 leading ADSL vendors. The core idea of this white paper (PPP-over-ATM over ADSL) has been adopted by the ADSL Forum. 121. ADSL device is implemented as an integrated ADSL modem Recommended System designers should integrate the ADSL modem and higher-layer transmission and media access functions on a single network device. A typical implementation integrates an ADSL modem and ATM interface on a single PCI network adapter. Another example is a device that connects to the server using the USB or IEEE 1394 bus. If external ADSL modems are provided (other than IEEE 1394 or USB), they should have an ATM interface for the ADSL modem to server connection. In addition, an Ethernet interface can also be included. 122. Integrated ADSL modem meets network adapter requirements Required Integrated ADSL modems must meet all requirements listed in Network Adapter Requirements earlier in this guide. An integrated ADSL modem exposing an Ethernet interface must also meet the requirements in guideline #92. Network adapter supports filtering for at least 32multicast addresses. 123. ATM/ADSL solution is implemented for integrated ADSL modems Recommended An integrated ADSL modem should expose ATM to the operating system. For ATM-specific requirements when an ATM/ADSL solution is implemented, see the requirements in ATM Adapter Requirements earlier in this chapter. This should comply with the PPP over ATM architecture discussed earlier. Note: ATM/ADSL is a requirement for Universal ADSL implementations. Currently there are both ATM/ADSL-based and Ethernet/ADSL-based implementations to provide full rate ADSL services in the market. For compatibility with the Universal ADSL-based services that will be rolled out within the next couple of years, PPP/ATM/ADSL is the required implementation. 124. ADSL modem supports DMT line encoding Recommended The ADSL modem must support discrete multi-tone (DMT) line encoding, which is recognized as the industry standard for ADSL by American National Standards Institute (ANSI) as the T1.413 Issue 2 specification and also by the Universal ADSL Working Group. For information, see the web site at http://www.uawg.org. Note: DMT is a requirement for Universal ADSL implementations. The Universal ADSL Working Group has adopted DMT specified by T1.413, with modifications being made to work in a splitterless environment. 125. ADSL modem supports rate adaptation Recommended On a rate adaptive digital subscriber line (RA-ADSL), the downstream and upstream data rates are independently set either by an automatic adaptive algorithm or by manual selection. RA-ADSL provides the capability to optimize the transmission speed and performance over a wide range of telephone-line loop distances. Adaptive channel equalization ensures more robust performance in the presence of channel impairments and narrow-band interference. This also helps telephone companies to provision RA-ADSL access on their existing networks. RA-ADSL products can be provisioned on many telephone lines without costly and time-consuming network upgrades. Cable Modem Requirements Cable modems are not required on servers. If they are implemented, they must meet the requirements in this section. Cable modem provides two-way services: Data flows downstream from the cable operators head end and upstream from the customers PC. At the head end, the cable data system is terminated by the cable modem termination system (CMTS), which terminates the upstream and downstream radio frequency (RF), MAC layer, and possibly Layer 3 protocols from the cable side. CMTS provides the internetwork connection between the cable system and the rest of the network at the head end. CMTS can be implemented on a proprietary hardware platform or a PC platform running Windows2000 to provide different networking functions such as routing, QoS support, such as Resource Reservation Setup Protocol (RSVP), and so on. Some implementations transmit upstream using narrow-band networks such as ISDN or analog modem, but as cable companies upgrade their networks, an increasing number of RF return modems, for example, two-way modems, are being deployed. Two-way modems are preferred, because they are always connected, perform better, and do not tie up phone lines or require modem banks. The three current cable modem specifications are: DOCSIS, developed by the Multimedia Cable Network System (MCNS) consortium. IEEE 802.14, developed by IEEE. Digital Video Broadcasting/Digital Audio-Visual Council (DVB/DAVIC), developed by DAVIC and DVB and adopted by European Telecommunication Standards Institute (ETSI) and International Telecommunication Union (ITU). Industry support for DOCSIS is growing rapidly in North America. In present form, its upper layers fully describe IP traffic encapsulated by 802.3/DIX Ethernet framing. ATM is left for future study. External Ethernet DOCSIS cable modems provide IEEE802.1d bridging for one or more Customer Premises Equipment (CPE); a system attaches to the cable modem indirectly through its 10Base-T network adapter. Integrated cable modems attach directly to the system over buses such as USB, PCI, and IEEE1394, and require a vendor-supplied NDIS 5.0 miniport driver. This driver exposes an 802.3/DIX Ethernet adapter interface to the operating system and it interfaces to the cable modem hardware using the appropriate bus (PCI) or bus interface driver (USB or IEEE1394) at its bottom edge. In contrast to DOCSIS, both the 802.14 and the DVB/DAVIC efforts are focused on using ATM, typically implementing an ATM adapter interface and using an NDIS 5.0 ATM miniport driver. 126. Device is implemented as an integrated cable modem Recommended An integrated cable modem should be used for servers. This recommendation means integrating everything from the cable modems physical interface layer, such as an RF coax connector, up through a standard PC 802.3/DIX Ethernet or ATM adapter MAC interface onto a single device. In other words, the software perceives the integrated cable modem as a standard Ethernet or ATM network adapter. An example of this is a USB-attached DOCSIS implementation that integrates cable modem Physical Media Dependent, downstream convergence, cable MAC, link security, 802.3/DIX MAC adapter filtering, and USB device interface functions in the same box. Similar devices can be implemented that are attached using PCI or IEEE 1394 buses. 127. Integrated cable modem meets network adapter requirements Required Integrated cable modems must meet all requirements listed earlier in Network Adapter Requirements. Integrated cable modems exposing an Ethernet interface must also meet the requirements in guideline #92. Network adapter supports filtering for at least 32multicast addresses. 128. Integrated cable modem exposes an ATM or Ethernet interface Required Refer to ATM Adapter requirements for ATM-specific requirements if an ATM/cable modem solution is implemented. ISDN Requirements This section summarizes requirements for ISDN hardware. ISDN is recommended, but not required, for high-speed connections under these guidelines. If implemented in a server system, ISDN must meet the requirements defined in this section. There are two classes of ISDN adapters: Serial port devices, supported by Unimodem with INFs Parallel bus devices, supported by NDIS WAN drivers In this section, internal ISDN device refers to the ISDN terminal adapter, which exposes raw access to its B channels using NDIS miniports. WDM-supported bus classes, such as USB or IEEE 1394, can also be used to attach external devices using NDIS miniports. ISDN modem refers to an internal or external ISDN device that exposes itself as a modem controlled by the AT command set. To the operating system, these devices look like and can be used as modems, provided that the hardware manufacturer has done the work needed to ensure that these devices have the following capabilities: Interpretation of the standard modem AT command set, either in the ISDN device itself or in a serial port driver. For more information, see the TIA602 specification, which is a subset of ITU V.250. A modem INF file for installing the device and for telling Unimodem which commands to use to control the ISDN device. Serial ISDN Modem Requirements The requirements in this section apply for a serial ISDN modem designed for orincluded with a server system that complies with Hardware Design Guide. ISDN modems share the following features: ISDN Basic Rate interface (2B+D) Serial AT command language, with proprietary ISDN extensions ISDN modems also share the following differences from wireline PSTN modems: User (or device) must configure for switch type and service profileID (SPID) Data only, in increments of one or two 64,000 bps B channels Fax not available V.42 and V.42bis usually not available 129. ISDN modem supports required command set Required An ISDN modem must support basic AT commands as defined in TIA602, which is a subset of ITU V.250. The ISDN modem shall support commands to select the end-to-end protocol used over the ISDN; synchronous PPP, V.110, V.120, and so on. Also, commands must be included to set the switch type, subscriber numbers or directory numbers (where applicable), and service profile identifier (SPID) or EAZ (where applicable), to allow user selection if auto-detection fails. These can be implemented inthe device or in the communications driver. 130. ISDN modem exposes both B channels Recommended ISDN modems should expose both B channels so that they can leverage the multilink PPP support included in the operating system. Multilink PPP, as defined in RFC 1717, combines several ISDN B channels to increase the bandwidth of PPP links. When using ISDN modems connected to the server using a single serial port, the capabilities included in the operating system cannot be leveraged and the users may not be able to fully benefit from the features in the ISDN device, such as supporting two B-channels and combining them into one fast link. This is because Windows2000 cannot see both B channels of the ISDN connection unless each B channel is exposed to the operating system, either as a COM port, or by way of NDIS. External ISDN modems should be on a port fast enough to expose the full bandwidth of both B channels, such as USB. Providing two separate COM-port cables is not an acceptable solution. 131. ISDN modem supports asynchronous-to-synchronous conversion Required These types of ISDN devices are treated as modems, not as internal ISDN devices supported using NDIS WAN miniports. In the external case, the primary implication is that the operating system will send byte-level PPP, also known as asynchronous PPP. In the NDIS WAN case, the implication is that the operating system will send bit-level PPP, also known as synchronous PPP. Because ISDN is a synchronous service and an ISDN modem connects to an asynchronous port on the system, the device must provide some means of converting asynchronous data to synchronous data. 132. ISDN modem uses high-speed port Recommended Because of speed limitations inherent in a servers COM ports, the connection for ISDN modems should be high speed, such as USB or IEEE 1394. A specification for controlling an ISDN TA over USB is in development by the USB Communications Device Class working group. 133. ISDN modem driver supports unattended installation, with limitations Required Configuration of the dependent parameters, such as SPIDs and switchtype IDs, must be done using the ISDN Configuration Wizard included in the operating system. Parallel ISDN Device Requirements This section defines general requirements for ISDN and specific requirements for ISDN terminal adapters. 134. Internal ISDN device meets network adapter requirements Required Internal parallel ISDN devices must meet all requirements listed earlier in Network Adapter Requirements. 135. Internal ISDN device supports synchronous HDLC framing Required High-level data link control (HDLC) framing is a standard for sending synchronous data. Other framing methods are allowed if the miniport driver provides simple HDLC framed synchronous PPP packets to NDIS. 136. Internal ISDN device and driver support raw unframed synchronous B channel I/O Required The internal ISDN device and the driver must support raw unframed (non-HDLC) synchronous B channel I/O at 64 Kbps for each B channel, with each B channel individually accessible. This will enable H.320 and voice calls over ISDN without audio breakup. For these raw interfaces, the direct path to each B channel must support synchronous transmission and reception of H.221 frames, which are of 20ms duration. To achieve this without additional latency to H.221, there must be support for overlapped I/O buffers at intervals of less than or equal to 20ms in each direction. As underruns or overruns cause degraded audio, hardware buffering must be adequate to prevent B channel underruns and overruns. For Windows2000, 20ms is adequate. This can be achieved by making buffering software configurable with adequate range to handle foreseeable real-world conditions. The miniport driver should make I/O completion callbacks to NDIS for each I/O buffer as soon as the I/O for that buffer is complete and should not coalesce or delay callbacks. 137. Driver for ISDN internal device supports unattended installation, with limitations Required Configuration of the dependent parameters, such as SPIDs and switchtype IDs, must be done using the ISDN Configuration Wizard included in the operating system. 138. ISDN device with U-interface includes built-in NT1 capability Recommended Note: This recommendation applies only in the United States. A network terminator (NT1) splits the duplexed transmit and receive signals from the ISDN line into separate transmit and receive components. An ISDN device with a built-in NT1 can connect directly to the ISDN line. However, doing so prevents other devices from being attached to the ISDN line because only one NT1 can be connected to an ISDNline. If the ISDN device has a built-in NT-1, it also should have a connector for either analog phone or another ISDN device (S/T-interface), such as an ISDN phone. Adding an analog (POTS) port or S/T-interface to the ISDN device delivers convenience to the SOHO market, allowing customers to use one ISDN line to meet all their telecommuting needs at minimal cost. Many customers do not want a separate analog or digital phone line for their fax machines, modems, or phone when ISDN can do this with a device that has a POTS port or S/T-interface. 139. Internal ISDN device has software-selectable terminating resistors Required If the ISDN device has an S/T-interface for connecting additional ISDN devices and has configurable terminating resistors, they must be software configurable. The software selectable resistors can be selected on or off. The default value of termination is on in North America, but off in all countries where phone companies unconditionally provide the termination. IrDA Communications Requirements Infrared capabilities are neither required nor recommended on servers. If they are implemented, they must meet the requirements in this section. The interface between Infrared Data Association (IrDA) hardware (framers) and the Windows IrDA stack is through NDIS 5.0 miniport drivers, as described IrDA Miniport NIC Drivers in the Windows 2000 DDK. The Windows2000 IrDA stack expects that the hardware and NDIS drivers deal with framing, transparency, and error detection, and also support media sense and speed change commands. Miniport drivers are responsible for discarding incoming frames with bad cyclic redundancy checks. These frames must never be forwarded to the protocol. 140. Infrared network adapter meets network adapter requirements Required IrDA network adapters must meet all requirements listed in Network Adapter Requirements earlier in this design guide. 141. Infrared device supports both FIR and SIR Required All infrared devices must comply with approved IrDA specifications, including support for serial IR (SIR) and fast IR (FIR) data devices. 142. IrDA hardware reports a unique Plug and Play ID sufficient to support unattended driver installation Required FIR Plug and Play hardware must report a unique Plug and Play ID that matches the combination of the chipset, transceiver, and any other system-specific parameters, in order for the operating system to find and install the correct INF, and the associated driver for the IrDA hardware. In the best case, the IrDA hardware has only one Plug and Play ID, associated INF file, and a miniport driver that can auto detect the transceiver type and other system-specific parameters. This enables the installation and configuration of the hardware and the driver without any user intervention. In other cases, for example, where the driver can not autodetect the transceiver type, or any other system specific parameters, a unique Plug and Play ID for each combination of the chipset and the transceiver type must be reported, and an associated driver and INF file describing the configuration parameters must be provided by the vendor for each combination. Wireless Networking Requirements Wireless networking media types enable WAN, LAN and personal area network (PAN) connectivity. This section lists additional requirements for wireless media. Servers are not required to have wireless LAN connectivity. Note: This design guide does not contain requirements for Bluetooth devices. However, future versions of Windows operating systems will use Bluetooth technology as a wireless external bus, rather than as a wireless networking technology. Therefore, Bluetooth devices are not subject to the requirements contained in this chapter; in particular, they do not require NDIS drivers. 143. Wireless networking media adapters meets network adapter requirements Required Wireless network media adapters must meet all requirements for network adapters defined earlier in Network Adapter Requirements. 144. Wireless networking media adapters support wireless extensions to NDIS Required Wireless extensions to NDIS are documented in Network-Dependent Wireless Objects in the Windows 2000 DDK. These extensions are based on the work of the Portable Computer and Communications Association, published in PCCA-STD-201. 145. Wireless networking adapters support industry specifications Required IEEE 802.11 wireless networking adapters must support the following specifications: 11Mb/s signaling using Direct Sequence Spread Spectrum (DSSS) Wired Equivalent Privacy (WEP) for security. Chapter 5 Storage Device Requirements This section summarizes the requirements for storage devices used with servers. Tips for selecting high-performance storage components: For manufacturers who want to select high-performance components for server systems, the following are the design features to look for in storage components: System relies on the SCSI or Fibre Channel controller for primary storage. Controller supports bus mastering, which is a requirement in these guidelines. Disks support reduced latency and fast rotational speeds. Drivers are tuned for 32bit performance on a IA-32 platform, and tuned for 64-bit performance on an IA-64 system. For example, 32bit alignments on the adapter do not interface with 16bit alignments on odd addresses, nor do 64-bit alignments interface with 32-bit alignments. Components do not use ISA or LPC. SCSI High-Voltage Differential (HVD) differential devices must support DIFFSENS as described in SPI3. PCI burst mode reduces disk controller time spent on the PCI bus. Storage Device General Requirements This section presents general requirements for controllers and peripherals. Note: It is recognized that OEMs supply systems with specific feature requirements to corporations, which can include providing servers that do not include any disks installed before shipping to a particular corporate client. 146. Host controllers and devices support bus mastering Required Bus master capabilities must meet the related specification for the particular controller. The host controller must not use the ISA or LPC bus. Note: This requirement does not apply to legacy FDCs and will not become a requirement for the FDC in the future. 147. System and Option ROMs support Int 13h Extensions on IA-32 BIOS boot system Required On IA-32 BIOS boot systems, BIOS and option ROMs must support Int 13h Extensions as defined in Int 13h Extension APIs of the Windows 98 DDK. This support is needed during the Windows 2000 boot process on BIOS-based systems. 148. Block rewritable optical ATAPI device complies with SFF 8070i Required The SFF 8070i standard defines the requirements for block rewritable ATAPI devices (optical storage devices), including specifications for logical unit number (LUN) implementation, media status notification, and device write protection. This definition includes required support for the Read Format Capacities command. 149. Controller and peripherals support media status notification Required The following list shows the required specifications for implementing media status notification, depending on device type. Device Type Media Status Notification ImplementationCD or DVD devices Comply with ANSI NCITS T10 Multi-Media Command Set-2 (MMC-2) standard for Media Status Event Notification.ATAPI floppy/optical direct access drivesComply with either MMC-2 standard or SFF 8070i Version 1.1.IEEE 1394 storage devicesComply with NCITS Reduced Block Commands standard (RBC; T10/97-260r0) standard. ATA and non-ATAPI storage devicesComply with Media Status Notification Support, Version 1.03.Other ATA/ATAPI devices, including tape drivesIf implemented, comply with Media Status Notification Support Specification, Version 1.03, or SFF 8070i.Other types of SCSI removable devicesIf implemented, support based on NCITS Reduced Block Commands standard. 150. Operating system recognizes the boot drive in a multiple-drive system Required 150.1 IA-32 BIOS boot system uses CIP BIOS Boot 1.01 method to determine boot drive The implementation of boot-drive determination in multiple-drive systems is defined in Section 5.0 of the CIP BIOS Boot 1.01. This is the format that Windows2000 uses for determining the boot drive when new bootable devices are introduced for servers. 150.2 EFI IA-64 system complies with EFI 1.0 or later for detection of boot devices, plus Hardware Design Guide requirements The requirements for management of the EFI boot process are documented in EFI 1.0 or later. In addition, EFI-based systems must meet other EFI requirements in these guidelines. 151. IA-64 system provides GPT-partitioned hard drive for boot Required 64-bit Windows requires bootable hard drives to be partitioned using the GPT mechanism defined in EFI 1.0. This is also the 64-bit Windows default partitioning scheme for all non-removable storage media. At least one locally-attached hard drive must be available for booting an installed operating system image. 152. IA-64 system with GPT-partitioned bootable hard disks provide one ESP of correct size Required 64-bit Windows requires bootable hard drives to contain a single EFI System Partition (ESP) of size Max(100MB, min (1% of the physical disk size, 1GB)) as defined in EFI 1.0. This formula is to be read, in words, as the size of the ESP must be the larger of these two numbers, 100MB or 1% of the physical disk size (up to 1GB). The physical disk size is measured at the time of disk partitioning. 153. IA-64 system with ESP contains only components needed for system boot, installation, or recovery Required The ESP may only be used for components required for system boot, installation, or recovery. Examples of such components include operating system loaders, EFI drivers, firmware utilities, configuration tools, and diagnostics. 154. EFI IA-64 system provides restoration tool for recovery of critical ESP and OEM special partition contents Required An EFI system must provide a tool that will permit the user to restore the critical EFI System Partition contents and any OEM special partition contents in the event of a catastrophic failure. This tool does not need to restore any operating system or other non-OEMsupplied ESP contents. 155. For EFI IA-64 system, MSR partition of correct size is present on every physical or virtual hard disk manifested to the operating system when such disks are otherwise being partitioned by the provider of the system Required All entities that represent themselves as a hard disk to an EFI systemwhether single drives, or collections of drives behind an intelligent controller that represents the assembly as a whole as a single diskmust contain an Microsoft Reserved (MSR) partition of correct size. This guideline applies only to disks shipped with systems being partitioned by the provider of the system, such as disks that contain system utilities or are otherwise preinstalled with software for use by or with Windows. It is not required for disks that are blankin other words, those disks that have no partitions present on them when installed by the manufacturer and that will be configured by the user. The formula for calculation of the size of an MSR is as follows: if (disksize < 16 GB) { MSR = 32 MB; } else { MSR = 128 MB; } The GUID for such partitions is defined as follows: DEFINE_GUID(PARTITION_MSFT_RESERVED_GUID, 0xE3C9E316L, 0x0B5C, 0x4DB8, 0x81, 0x7D, 0xF9, 0x2D, 0xF0, 0x02, 0x15, 0xAE); 156. For IA-64 system, non-ESP partitions do not contain software required for boot Required No software required for system boot can be stored in an OEM-specific, non-ESP partition. Instead, such software must reside in an ESP or in system firmware. 157. For IA-64 system, ESP resides only on a device that can be reached through firmware-resident EFI drivers Required To prevent problems that can occur if a driver needs to reach a disk containing an ESP that is actually contained on that disk (resulting in a non-bootable system), ESPs must be placed only on devices that can be reached using firmware-resident EFI drivers. The system must also comply with #14.7 EFI systems provide a minimum, firmware-based driver set sufficient to allow boot, installation, and recovery operations without the presence of loadable media-based EFI drivers. 158. USB-based mass storage device complies with USB specifications Required If a USB-based mass-storage deviceincluding tape, UHD floppy drive, and CD driveis implemented in a server system, it must meet the requirements in this design guide and the requirements defined in Universal Serial Bus Mass Storage Class Specification Overview 1.0 or later. 159. IEEE 1394-based mass storage complies with 1394 OpenHCI 1.1 Required If an IEEE 1394 storage device is implemented in a server system, it must meet all IEEE 1394 requirements in this design guide and comply with OpenHCI 1.1. A removable IEEE 1394 mass storage device must not be the primary boot device. 160. Drivers for devices that use SBP-2 command protocols follow Windows 2000 guidelines Required Drivers for devices using the SBP-2 protocol must conform to the guidelines in SBP-2 Support and Windows 2000 at http://www.microsoft.com/hwdev/print/sbp2_w2000.htm. SCSI Controllers and Peripherals SCSI is a flexible I/O bus that is used in the design of a variety of peripherals, including disk drives, CD drives, tape drives, magneto-optical drives, and scanners. This section presents the requirements for SCSI hardware that is compatible with Windows2000, including adapters, peripherals, and any device that uses a SCSI controller. 161. System includes SCSI host controller and SCSI peripherals Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended The SCSI host adapter is the circuitry that serves as an interface between the system and one or more SCSI peripherals. A host adapter can be a card that plugs into the systems expansion bus, such as a PCI card, or it can be designed directly into the system board set. The host controller must support PCI bus mastering, with bus mastering enabled by default. Recommendation Recommended: Fibre Channel, especially for servers running Windows2000 Advanced Server or Datacenter Server. Note: Servers that implement Fibre Channel as the storage connection are not required to also provide SCSI capabilities. 162. SCSI controllers with external connectors that can function as cluster nodes provide multi-initiator support Required Multi-initiator support allows two SCSI controllerseach installed in a separate computer systemto coexist on a shared SCSI bus with a set of shared devices. For use in a system intended as a node in a cluster using shared SCSI, the SCSI IDs must be changeable from the default SCSI controller ID of 7, and the boot-time SCSI busreset operation must be able to be disabled on each controller attached to ashared bus. For any SCSI controller with external connectors that can be used as a node in a cluster, as described previously, the connector must be clearly labeled as available for cluster connections. This labeling must be positioned so that it is clearly visible to a user when attaching external devices to the affected external connector. 163. Bus type is clearly indicated on connectors for all adapters, peripherals, cables, and terminators Required Connectors for each Fibre Channel or SCSI adapter, peripheral, cable, and terminator must be clearly labeled to show the bus type. All external SCSI connectors must display the appropriate SCSI icon defined in SCSI3 Parallel Interface (SPI) specification, AnnexF, plus any clarifying abbreviations or acronyms. The following shows the related acronyms and their definitions: Single-ended (SGL or SE). The most commonly used signal type, such as found in home PCs and high-end workstations. Low voltage differential (LVD). A signaling method similar to Differential (DIFF) but with lower signaling voltages supporting higher transfer rates. High voltage differential (HVD). A signaling method similar to DIFF but with higher signaling voltages. Differential (DIFF). A signaling method that employs differential drivers and receivers to improve signal-to-noise rations and increase maximum cable lengths. This method includes both LVD and HVD types. 164. Differential devices support DIFFSENS as defined in SPI-3 standard Required Without DIFFSENS, the differential bus drivers or a single-ended device will suffer fatal thermal damage if a single-ended device is put on a differential bus. The specification for DIFFSENS is defined in Section 5.4.2 of the SPI-3 standard. 165. Automatic termination circuit and SCSI terminators comply with SCSI3 Required Parallel SCSI add-on adapters and on-board controllers must use automatic termination that allows a user to add external devices without removing the server case. Terminators used in the SCSI host adapter must be regulated terminators, which are also known as active, SCSI3 SPI, SCSI2 alternative2, or Boulay terminators. SCSI termination built onto internal cables must meet the SCSI-3 specification. 166. Terminator power is supplied to the SCSI bus, with over-current protection Required The host adapter must supply terminator power (TERMPWR) to the SCSI bus for system-board implementations using PCI or another expansion bus. All terminators on the external SCSI bus must be powered from the TERMPWR lines in the SCSI bus. In addition, the circuit that supplies TERMPWR must have overcurrent protection built into it. Devices that provide TERMPWR must also provide some means of limiting the current through use of a self-resetting device. For example, a positive-temperature coefficient device or circuit breaker can be designed into the circuit. These devices open during an over-current condition and close after the condition ends. 167. External connector complies with SCSI2 or later Required If an external connector is implemented, it must meet the requirements defined in SCSI2 or a later specification. 168. Controller and peripherals implement SCSI data protection signal Required All SCSI peripherals and the SCSI host adapter must implement the SCSI bus data protection signal defined in the SPI standard, and data protection must be enabled by default. 169. SCSI connections use keyed and shrouded connectors Required For internal and external configurations, the SCSI bus cable must be plugged into shrouded and keyed connectors on the host adapter and devices. This ensures that the cable is properly positioned so the user cannot plug in cables incorrectly. For internal configurations, pin 1 orientation must be designated on one edge of the ribbon cable and also on the keyed connector for the SCSI peripheral device. For an external configuration, the SCSI connector must not use the same connector type as any other non-SCSI connector on the system. 170. External devices provide SCSI-3-compliant termination Required External SCSI devices must provide termination compliant with the SCSI-3 specifications per the requirements in guideline #165. Automatic termination circuit and SCSI terminators comply with SCSI3. 171. SCAM support is not present Required SCSI Configured AutoMatically (SCAM) capabilities must not be present on server systems or peripherals. SCAM is not supported by the Windows2000 operating system; enabling SCAM can cause the system to become unstable or inoperable. 172. Hardware supports the STOP/START UNIT command as defined in SBC specification Required The hardware in SCSI peripherals must be able to fully recover from a software-initiated spin down without rebooting the system or cycling power. To properly support power management on SCSI drives and to ensure that the operating system responds to appropriate driver calls, be sure to correctly implement the STOP/START UNIT command as defined in the SCSI Block Commands specification. 173. STOP/START UNIT command can be used to decrease power consumption Recommended Wherever appropriate, for example, for storage disks, the STOP UNIT command can be used to decrease power consumption of the base platform. 174. SCSI devices that support hot-plugging comply with Annex D of SPI-3 Required Annex D of SPI-3 addresses SCSI device insertion and removal, with and without command activity. ATA Controllers and Peripherals This section presents requirements for ATA hardware that is compatible with Windows2000, including adapters, peripherals, and any device that uses an ATA controller. 175. System does not use ATA host controller or peripherals Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended ATA disks should not be present in a server. If ATA is implemented in a system, the ATA host controller and peripherals must meet all related requirements for devices and drivers, and they must meet the requirements defined in this section. ATA devices may not be used as the primary storage channel on a server running Windows 2000 Advanced Server or Datacenter Server. For these operating systems, the server can use an ATA device only as a boot or installation device. An exemption is allowed for Basic and SOHO class servers that are not designed for deployment with MSCS clustering. 176. Dual ATA adapters use single FIFO with asynchronous access or dual FIFOs and channels Required PCI dual ATA adapters must be designed so that either channel can be used at any time; the operating system must not have to serialize access between the primary and secondary channel. Therefore, either the two channels are totally independent or a hardware arbitrator protects anything shared, such as a programmed I/O (PIO) read pre-fetch buffer. A design implementing a single first in/first out (FIFO) with a hardware solution to synchronize access to both channels meets this requirement if the design does not require that a request on one channel be completed before another can be started. A software-based solution is not acceptable. ATA-based systems must be tested with ATA DMA enabled; the system must not have an embedded single-FIFO dual-channel ATA controller. EFI Note Section 5.0 of the CIP BIOS Boot 1.01 defines the implementation for dual asynchronous channels. Note that this particular issue is also relevant for EFI systems, and designers of these systems will also use this specification for clarification of this particular implementation issue even though the rest of this specification is superseded by EFI. Dual-channel controllers that require special software to serialize channel I/O for a single prefetch FIFO do not meet these requirements. Such designs require serial access to one of four devices, defeating the primary advantage of asynchronous dual-channel controllers. Furthermore, such devices are non-standard and require custom driver support. 177. ATA controller and peripherals comply with ATA/ATAPI-5 standard commands for features implemented and support Ultra-DMA (ATA/33, minimum) Required All controllers and ATA peripherals must support Ultra DMA (also known as Ultra-ATA) at transfer rates up to 33 MB per second as defined in ATA/ATAPI-5. In addition to improved transfer rates, Ultra DMA also provides error checking for improved robustness over previous ATA implementations. PCI chipsets must implement DMA as defined in SFF 8038i. ATA drives must comply with ATA-5, which defines the programming register set for PCI ATA bus master DMA, to ensure fully featured hardware and Windows-compatible device driver support. Support for ATA Bus Master DMA: Required for ATA controllers Required for ATA devices and ATAPI peripherals, including CD and DVD devices Recommended for ATA/ATAPI tape drives Recommended for ATAPI removable media drives Recommendation Recommended support includes: For all systems: Controller and peripherals support Ultra-DMA/66. For IA-32 BIOS boot systems: The system BIOS should configure the drive and host controller, optimized for Ultra DMA operation if possible, though the PIO mode must continue to work. The ACPI software should also support the restoration of these settings in ACPI control methods _GTM, _STM, and _GTF. There are no standard registers for these ACPI control methods if the controller loses timing context across a suspend and resume cycle. The BIOS pre-operating system boot disk services, INT13h read and write, need not actually use Ultra DMA for access to the drive prior to operating system boot. Definitions for these ACPI control methods can be found in Section 10 of ACPI 1.0b. For EFI systems: The system firmware should configure the drive and host controller, optimized for Ultra DMA operation if possible, though the PIO mode must continue to work. The ACPI software should also support the restoration of these settings in ACPI control methods _GTM, _STM, and _GTF. There are no standard registers for these ACPI control methods if the controller loses timing context across a suspend and resume cycle. These ACPI control methods are defined in Section 10.8 of ACPI 2.0. See also the BIOS recommendations in guideline #12. System firmware meets general boot support requirements. 178. ATA controller and peripheral connections include Pin1 cable designation with keyed and shrouded connectors Required Pin1 orientation must be designated by one edge of the ribbon cable and also on the keyed connector of the ATA or ATAPI controller and peripheral device. Designation of the keyed connector must be clearly indicated on or near the connector. 179. ATAPI peripherals comply with ATA/ATAPI-5 standard commands for features implemented Required The ATA/ATAPI-5 standard defines the fundamental hardware and software design guidelines for ATAPI devices. See also guideline # 147. System and Option ROMs support Int 13h Extensions on IA-32 BIOS boot systems. 180. ATAPI devices support DEVICE RESET command Required ATAPI devices must respond to the DEVICE RESET command regardless of their internal state, as defined in the ATA/ATAPI-5 standard. The controller can be reset by going into a power-on state (requests cleared, signature present), but any non-default mode values must be left in their current state with the DRV bit unchanged. Devices that do not implement the PACKET command feature set, such as hard disk drives, must not implement the DEVICE RESET command. 181. ATA/ATAPI device supports ATA STANDBY command Required The ATA drive must implement the ATA STANDBY command according to theATA standard. This command is defined in ATA/ATAPI-5. The hard disk drive should spin up and be able to complete a Read operation within 10 seconds of applying power or leaving ATA STANDBY mode and transitioning to ATA ACTIVE, as specified in the Storage Device Class Power Management Reference Specification, Version1.0 orlater. Fibre Channel Controllers and Peripherals This section presents requirements for Windows2000compatible adapters, peripherals, and any devices that use Fibre Channel technology. 182. System includes Fibre Channel controller and peripherals Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRecommendedRecommendedEnterprise:RecommendedRecommendedRecommendedSOHO:OptionalOptionalOptional Fibre Channel is a technology for 1 gigabit per second or greater data transfer that maps common transport protocols such as SCSI and IP, merging networking and high-speed I/O in a single connectivity technology. It is an open standard, defined by ANSI and Open System Interface (OSI) standards, that operates over copper and fiber-optic cabling at distances of up to 10 km. If implemented on a server system, Fibre Channel must use the X3T11 Private LoopDirect Attach (PLDA) profile as the storage base to use the native Windows2000 support. The Physical Layers implementation must comply with Fibre Channel Physical (FCPH), Revision4.3 or later. For more information from the FibreChannel Association, see http://www.fibrechannel.com. Erasable Disk Drives This section presents the requirements for erasable disk drives provided with a server system or designed for use with Windows2000 Server. This category includes 3.5inch, 5.25inch, and 12inch magneto-optical or phase-change drives and media. It does not include CD, CDR, CDRW, and DVD drives ormedia. 183. SCSI erasable drives support SCSI commands Required The following commands or features must be supported by the devices driver: Erase (2C): full side and selected block erase Format requirements reported with Format command Mode Select: write cache disable Mode Sense: total spare blocks available, write protect status Prevent/Allow Medium Removal, Start/Stop Unit Read (28), Verify (2F) Reassign Blocks, Read Defect Data Reserve, Release Seek (SCSI CDB Opcode 2B) Test Unit Ready, Request Sense, Read Capacity, Inquiry Write (2A), Write and Verify (2E) Write without pre-erase, for erasable optical only Recommendation Recommended: Inquiry with support for reporting serial number or other unique unit ID should be supported by the devices driver. CD and DVD Drives This section presents the requirements for CD and DVD drives. 184. System includes CD or DVD drive or other method for installing the operating system Required The server system must include either CD or DVD drive support or another method to enable the installation (or reinstallation) of the operating system. CD Drive Requirements This section summarizes requirements for CD drives. A CD drive isnot required if another method is provided to support operating system installation. However, if a CD drive is present, it must comply with these requirements. 185. CD drive provides 8x or higher performance Required This requirement is intended to set the minimum speed needed for production-level CD reading on Windows platforms. This requirement applies to the minimum read speed (8x) on any production level CD media, such as application software, at any location on the disc. This requirement does not apply to end-user recorded CD data discs, or discs being read in error-correcting, defect management mode. 186. CD drive is CD-Enhanced compatible Required The CD drive must be able to mount multisession CDROM discs, even if track 1 is Red Book audio. CD-Enhanced support must comply with Blue Book standards, as defined in the MMC2 standard. Recommendation Recommended: Use of the Sony ReadTOC method for SCSI2 multisession support, as noted in the MMC-2 standard. 187. CD drive supports specified logical and physical CD formats Required At a minimum, the CD device must be compatible with the following formats to ensure cross-media compatibility, based on compliance with the Optical Storage Technology Association (OSTA) MultiRead Specification for CD-ROM, CD-R, CD-R/RW, and DVD-ROM Devices, Version 1.11: Logical formats: CD Red Book (CD-Audio), Yellow Book (CD-ROM), Orange Book parts II and III (packet writing if recordable), White Book, Blue Book, and Universal Disk Format Specification, Version 1.5 and 2.0 Physical formats: ROM (stamped), and Orange Book part II (CD-R) and part II (CD-RW) Note: Any ATAPI CD drive designed to play back CDI content must return a minimum of two track entries for the READTOC (0x43) command. These two track entries must be a track 01 entry and a track 0xAA entry for the lead-out address. Drives that do not comply with this minimum requirement cannot play back CDI movies. 188. ATA/ATAPI CD drive complies with MMC-2 Required CD drives attached to the system using the ATA interface must support MMC-2. 189. CD drive supports multisession and compatibility forms of the READ_TOC command Required Both multisession forms (01b and 10b), as well as the compatibility form (00b) of the READ_TOC command, must be implemented. This requirement ensures complete support for CD multisession capabilities. 190. ATA/ATAPI CD changer meets MMC-2 standard Required If an ATAPI-compatible CD changer is present that has a capacity for seven or fewer discs, the device must comply with MMC-2 standard. DVD Drive Requirements This section summarizes requirements for supporting DVD drives. A DVD drive isnot required in a server system, but if present, it must comply with these requirements. Systems targeted for use with Windows 2000 Advanced Server or Datacenter Server should provide DVD drive capabilities. For more information about DVD support under Windows2000, see the articles at http://www.microsoft.com/hwdev/dvd/. 191. DVD device provides 2 MB minimum transfer rate or better performance anywhere on the disk Required This requirement is intended to set the minimum speed needed for DVD-Video playback during MPEG-2 decoding on Windows platforms. This requirement applies to the minimum read speed (2 MB/s) on any production-level DVD-Video media, at any location on the disc. This requirement does not apply to end-user recorded DVD data discs, or discs being read in error-correcting, defect management mode. 192. DVD drive meets minimum compatibility requirements Required DVD drives must support all the functionality of CD drives as outlined in this document. The DVD drive must also be compatible with the following formats toensure that the DVD drive can read earlier media: Physical formats: ROM (stamped), Orange Book part II (CD-R) and part III (CD-RW), and ECMA-267 and ECMA-268 (DVD-ROM). Conforming to OSTA MultiRead Specification, Version 1.11, indicates compliance with all of these CD compatibility requirements. 193. DVD drive supports defect management Required The drive must support the defect management that is transparent to the operating system, according to industry standards. Defect management for DVD-RAM media is defined in DVD Specifications for Rewritable Disc, Part 1: Physical Specifications, published by Toshiba Corporation. Defect management for DVD+RW is defined in ECMA-274. 194. DVD-Video playback, if present, meets DVD-Video playback requirements Required Servers that provide DVD drives only as storage devices do not have to include the additional capabilities required for DVD-Video playback on a local display device. Only servers that provide the specific feature of DVD-Video playback to the local server display must meet the DVD-Video playback requirements specified in these guidelines. The following capabilities are required for DVD drives that support DVDVideo playback: DVD decoder driver correctly handles media types, time discontinuity, and decode-rate adjustment. This requirement specifies that the vendor-supplied minidrivers for DVD, MPEG2, and AC3 decoders have the following capabilities: Use correct media types. This includes validating all format block fields on connection and on every IPin::QueryAccept message. Query for IMediaSample2 on every received media sample to test for a time discontinuity bit. It is also acceptable to query on every video/audio frame to reduce CPU overhead. Adjust decode rate in response to IPin::NewSegment() calls for video and subpicture. DVD decoder supports subpicture compositing and closed captioning. The system must be capable of displaying subpicture data as well as providing closed-captioning support for all such data stored on the disc. This requires YUV offscreen surface support, as defined later in this list. Subpicture streams must be supported as defined in the DVD Specification, Version1.0, from Toshiba Corporation. Alpha blending, or a simulation implemented in the driver, is required for static menus. Subpicture decoder correctly handles subpicture properties and other functions. The minidriver for the subpicture decoder must be able to correctly handle the following: Set the subpicture property Turn subpicture compositing on and off Set the highlight rect parameters For information, see the Microsoft DirectX SDK (provided in the Microsoft Platform SDK) and the DirectXinformation in Windows2000 DDK. System supports seamless DVDVideo 1.0 navigation. This requirement includes menu navigation and video selection, and language and subpicture track selection to support the users ability to navigate DVDVideo discs. Test sources include, but are not limited to, the following: Matsushita Electronics Incorporated (MEI) test disc Joe Kane Productions Video Essentials disc Microsoft test disc MPEG2 playback provides high-quality video output. MPEG2 solutions must provide high-quality video display output, as defined by the following: Smooth frame delivery, with all video fields and frames from the MPEG source decoded. Audio and video synchronized to within one and a half video frames, with synchronization not allowed to drift out over time. No tearingprovide proper video buffering, such as double buffering. Correct display of multiple-aspect ratio content. The material should be displayed according to the aspect ratio information in the MPEG header. This requires support for YUV offscreen surface and up/down interpolated scaling, as defined in the following requirement. Graphics adapter supports DVD movie playback features. Any system with a DVD drive that includes the ability to play back MPEG2 data streams must meet the requirements listed here. However, this requirement does not apply for systems that include DVD drive for storage purposes but do not include DVDVideo playback software. The following capabilities are required for solutions that use either hardware or software MPEG2 decoders: Up and down scaling with bilinear interpolation Recommendation Recommended: 5 taps, both vertically and horizontally YUV 4:2:2 and 4:2:0 planar offscreen surface support VGA destination color keying for video rectangle AGP or PCI bus mastering Backup Devices Backup devices are an important part of guaranteeing data availability at a corporate site. Windows2000 Server includes a graphical tool named Backup that supports backup of Windows2000 Server-based data. If a backup device is provided in a server system, it must comply with the requirements and recommendations in this section. 195. System includes device for local backup Recommended System administrators will commonly want offline backup capabilities to be available. If a backup device is provided with a server system, either as a built-in or peripheral add-on device, it must meet the minimum requirements defined in this section. 196. Single-backup device meets minimum capacity requirements Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:10 GB required10 GB required10 GB requiredEnterprise:20 GB required20 GB required20 GB requiredSOHO:10 GB required10 GB required10 GB required Minimum uncompressed, formatted storage capacity is required for any backup device designed to comply with these guidelines. Recommendation Recommended: 20 GB minimum capacity for Basic and SOHO servers. 197. Backup device meets industry standards Required A SCSI tape or SCSI backup peripheral must comply with the appropriate SCSI command set and with the requirements defined in SCSI Controllers and Peripherals earlier in this chapter. ATA is not recommended for servers, but if an ATA backup peripheral is implemented, it must comply with the appropriate ATA/ATAPI 5 standard sections covering that devices operation. 198. Driver integrated with Removable Storage Manager Required For a backup device designed for Windows 2000 Server, the manufacturer must provide a Windows 2000 driver that integrates with Removable Storage Manager (RSM), formerly Windows NT Media Services. This ensures that applications which are RSM-aware (such as the native Windows 2000 backup and hierarchical storage management applications) will be properly able to utilize the backup device. RSM is intended to allow software that accesses backup devices to be independent of the specific device. A hardware vendor can also choose to include a backup application. However, such software should also be integrated with and use the RSM infrastructure. Media Changers This section defines requirements for media changers. CD Changers This section provides requirements for CD changers. There is no requirement or recommendation for providing a CD changer with a server system, but if present or designed to be compatible with Windows2000, it must comply with these requirements. 199. If present, CD changer for seven or fewer discs meets MMC-2 standard Required If an ATAPI-compatible CD changer is present that has a capacity for seven or fewer discs, the device must comply with MMC-2 standard. Tape and Optical Disk Changers This section provides requirements for tape and optical disk changers. There is norequirement or recommendation for providing a tape or optical disk changer, but if a device is present or is designed to be compatible with Windows2000, itmust meet the requirements defined in this section. This includes changers that support the following drive/media types: 3.5inch, 5.25inch, and 12inch magneto-optical or phase-change drives andmedia All magnetic tape drives and media It does not include changers that support CDROM, CDR, CDRW, or DVD drive/media types. 200. SCSI changer and drive support auto-configuration Required To meet requirements for auto-configuration of changers and their associated drives, the following changer requirements and configuration restrictions are defined: For changers where autoconfiguration under RSM control is a targeted feature, all changer tape or optical disk drives must be connected to the same SCSI bus as the changer. Changer systems thatare not configured this way will not be autoconfigurable under RSM inWindows 2000 and must provide documentation that describes the appropriate manual configuration process for use with RSM. Examples of proper documentation are available in Appendix A of Windows NT Removable Storage Manager Programming Documentation, at http://www.highground.com/developer/documents/ntmsdocu.htm. The Removable Storage Manager functions are documented in the Microsoft Platform SDK at http://msdn.microsoft.com/library/psdk/zaw/ntms_api_5nz9.htm. The changers Read Element StatusData Transfer Element Descriptor must support the reporting of the SCSI Bus Address and LUN of each drive in the library unit. If drive cleaning is required and can be automated, a specific slot that is accessible by way of a Move Medium command must be designated in the Operators Guide. The changer must be able to report if a bar-code reader is installed in the unit. The changer must be able to report on the current of (magazine) slots and drives by using the Read Element Status command. Recommendation Recommended for changers: SCSI changers should avoid behaviors as a side effect of SCSI bus reset which unduly delay operations of the changer and availability of media via the changer. An example would be a lengthy auto-inventory process which delays media loading. 201. SCSI tape and optical disk changers support SCSI commands Required The following commands or features must be supported by the changer: Initialize Element Status (with/without bar-code reading) Mode SensePages 1D, 1E, 1F Move Medium Prevent/Allow Media Removal (door access and IEPORT locking) Read Element Status Reserve, Release Send Volume Tag, Request Volume Element Address Test Unit Ready, Request Sense, Inquiry Recommendation Recommended: Inquiry with support for reporting serial number or other unique unit ID should be supported by the changer. Chapter 6 Physical Design and Hardware Security Requirements This chapter summarizes physical design and hardware security requirements and recommendations. Physical Design Requirements This section presents the requirements related to the physical design of servers. 202. Icons are provided for all external connectors Required This requirement helps ensure that the end user can correctly make the physical connections required for adding a device to a system. This requirement includes the following: Wherever possible, keyed or shrouded connectors or other configurations should be used to prevent misconnection. The physical design of the connector must ensure that the user cannot mistakenly insert the connector into the wrong port. Icons are provided for all external connectors. The icons can be molded, printed, or affixed as permanent stickers, which can include text. Icons can bebased on existing vendor designs or on the examples shown at http://www.pcdesguide.com/documents/icons.htm. Systems and peripherals must use a color-coding scheme for connectors and ports. Recommendation The following list displays the recommendation for standard color-coding of connectors and ports. The selection of these specific colors was done using criteria established by Human Factors and Industrial Design professionals from multiple companies who are involved in the design of computer hardware. ConnectorRecommended colorPantoneAnalog VGABlue 661CAudio line inLight blue 284CAudio line outLime 577CDigital monitor/flat panelWhite IEEE 1394Grey 424CMicrophonePink701CMIDI/gameGold 131CParallelBurgundy235CPS/2-compatible keyboardPurple 2715CPS/2-compatible mouse Green 3395CSerialTeal or Turquoise 322CSpeaker out/subwooferOrange 157CRight-to-left speakerBrown 4645CUSBBlack 426CVideo outYellow 123CSCSI, network, telephone, modem, and so onNone It is recommended that retail peripherals also implement color-coding, and those that do are required to use the colors in order to correspond with servers that adopt this scheme. Note: It is recognized that the design for legacy ports, such as the PS/2-compatible mouse and keyboard ports, analog audio and video jacks, and the microphone and speaker jacks, will not change and therefore cannot fully meet this requirement. However, icons and labels must be provided wherever possible to help the user make the correct connections. Color coding is required for server systems, but the color codes listed earlier are only recommended. The intent is to standardize the industry on a single color-coding scheme; these specific colors will become a requirement for systems in future versions of the design guidelines. For the following classes of retail peripherals, color-coding is required and must follow the color codes listed earlier. These classes are: Audio peripherals Display peripherals USB peripherals IEEE 1394 peripherals 203. All expansion slots in the system are accessible for users to insert cards Required The space for expansion cards that will reside in associated expansion slots cannot be physically blocked by components or devices provided with the system. However, this requirement does not exclude configurations that provide half-height cards for some slots, passive back planes for connectors, and so on. It is understood that in order to install expansion cards in some expansion slot implementations, users might have to temporarily move other system components to gain access to the slot. In general, designers should minimize this juggling as much as possible. 204. System and device design include protected switches Recommended Switches can be covered with a hood or other protection to prevent inadvertent switching. Locks can also be provided to prevent unauthorized access. 205. System design includes locking case Recommended The computer case can be protected with key locks to prevent unauthorized access. Other recommended features include: Key lock removes the computer case without additional toolsif this can be done while maintaining compliance with othersafety standards. Software management of physical components as documented in WHIIG 1.0, which also defines the Windows-specific requirements of the Wired for Management Baseline Specification, Version2.0, for hardware instrumentation. 206. System and device design include positive retention connectors Recommended Positive retention mechanisms should be implemented to ensure connections. The retention mechanism should be operated by hand, requiring no tools for mating and breaking the connection. It is recognized that certain legacy connector implementations, such as PS/2-compatible pointing devices and keyboards, will not generally allow this. However, locking cable connections provide a valuable feature for end users. 207. If present on an IA-32 system, parallel port design provides sufficient space for connector assembly Required The parallel port design must provide enough space between the connectors and the surrounding enclosure to allow for a mating connector, connector shell, and latch assembly. Recommendation The IEEE 1284 specification recommends an IEEE 1284C connector for all new ports and devices. Note: Parallel ports must not be present on IA-64 systems. Hardware Security Requirements This section summarizes the system hardware security requirements and recommendations. 208. C2 evaluation for hardware Recommended C2evaluated hardware meets requirements defined in the Orange Book. For hardware designed for customers outside the U.S., equivalent evaluation might be defined in local standards, such as FC2/E3 ratings in Europe. 209. Peripherals follow hardware security recommendations Recommended OEM-specific solutions can be implemented to meet these recommendations. Thefollowing hardware security features are recommended: External drive devices should have locking capabilities. Each removable media device on a server system should be capable of being locked to prevent unauthorized access to data. A single locked door covering the drives is sufficient. The locking mechanism must render the device useless, whether locking is done electronically or mechanically. Computer case and switches should have locking capabilities to prevent unauthorized internal access. An OEM-specific method can be implemented, either electronically or mechanically. Remote software management should be supported for physical components. Controls and remote alerts should be provided for chassis-open intrusion. For servers running either Windows 2000 Server or Windows 2000 Advanced Server or Datacenter Server, smart card readers and cards should be provided. If provided with a server system, smart card devices must be compatible with Interoperability Specification for ICCs and Personal Computer Systems, available at http://www.pcscworkgroup.com/. In addition, smart card readers and device drivers must be Plug and Play-compliant and must be implemented as described in Smart Card Drivers in the Windows2000 DDK. Smart card applications and service-provider dynamic link libraries (DLLs) must adhere to the Microsoft Smart Card SDK that is part of the Microsoft PlatformSDK. Chapter 7 Reliability, Availability, and Serviceability Requirements These requirements and recommendations relate to ease of use, ease of maintenance, manageability, and failure tolerance. Design guidelines that make server configuration, management, and servicing easier for end users and administrators are defined to help reduce the total cost of ownership for servers. Reducing the total cost of ownership is an important goal for servers; a key priority in this effort for servers is minimizing downtime. This goal is achieved through mechanisms for backup and reliability, remote management, and emergency and preboot management. Backup and Reliability Requirements This section summarizes the backup and reliability requirements and recommendations for servers. Backup Hardware This section defines the requirements for backup hardware for servers. 210. System includes integrated backup solution Recommended An integrated tape drive or other device should be included in the system. Although the recommended method to back up files on a server is to use a backup service under Windows2000 Server, system administrators will commonly want offline backup capabilities to be available. For information about hardware requirements related to backup capabilities, such as tape drives and so on, see Chapter5, Storage Device Requirements. Power Supply This section defines the guaranteed power requirements for servers. 211. System includes UPS provided with system Recommended For servers deployed in many corporate environments, the more common choice will be to provide guaranteed power for the server room. 212. System includes power supply protection using N+1 (extra unit) Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRecommendedRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRecommendedRecommended The system overvoltage/undervoltage protection and power supply switch-over circuitry should have the capability to regulate according to the system load. For each voltage used in the system, the output voltages of the redundant power supplies should be within the range of values that can guarantee the proper operation of the system, no matter which supply is active. Power-supply switch-over should occur swiftly enough to maintain normal server system operation. 213. System supports replacement of power supplies Required Systems are required to allow for the replacement of the module (or modules) constituting their source of power by a qualified individual in the field. The minimum requirement is that this capability be provided when the system is powered off, that is, when the server is in a down condition. Recommendation Recommended: Hot-swapping capabilities for power supply replacement and power supply redundancy. 214. System supports replacement of fans Required Systems are required to allow for the replacement of the fan (or fans) by a qualified individual in the field. The minimum requirement is that this capability be provided when the system is powered off, that is, when the server is in a down condition. Recommendation Recommended: Hot-swap fans should be implemented to maximize server up time. 215. System includes local hot-swap power supply replacement indicators Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended Any system that provides hot-swap power supply replacement and power supply redundancy should have local indicators that unambiguously indicate the supplies that must be replaced. These indicators guide service personnel to replace the correct power supply. Automatic retention mechanisms that prevent incorrect supply removal also satisfy this guideline. Fault-Tolerant Hardware This section provides design guidelines for fault-tolerance features and capabilities. 216. System supports multiple hard drives Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended Bus mastering is required for the drive controllers. Use of multiple hard drives and controllers in a server system provides both performance and reliability benefits. It is not a requirement that the drives all be physically housed in the server system chassis. Recommendation Recommended: Hot-swappable drives. 217. System includes intelligent RAID controller with adequate storage capacity Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering An intelligent RAID controllerwhere the controller itself has the capability to run the array management software locally rather than simply executing disk accesses for host-based array softwareprovides the benefit of reduced demands on the host processor or processors, thereby freeing those computing resources and allowing their use by other tasks. The intelligent RAID controller may be internal to the server chassis, or within an external drive enclosure. If an intelligent RAID controller is provided in a system, it should be capable of handling sufficient amounts of disk storage to fulfill the needs of the targeted usage model for that server. These needs will vary based on the storage-intensive nature of the servers tasks. 218. System supports at least one of RAID 1, 5, or 1/0 Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering RAID 1 and RAID 1/0 are recommended. RAID5 is also acceptable. RAID0 (forenhanced performance but no added reliability) is optional. 219. RAID support includes notification of failed drive Required If RAID support is implemented, notification of a failed drive must be provided by the disk subsystem, with notification sent to the system administrator. 220. RAID subsystem supports automatic replacement of failed drive Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering The RAID subsystem must provide automatic replacement of a failed drive by a standby disk and must rebuild lost data without interfering with system operations. 221. RAID subsystem supports manual replacement of failed drive Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering The RAID subsystem must provide for manual replacement of a failed drive without shutting down or halting the system. The subsystem must also allow lost data to be rebuilt without interfering with system operations beyond some decreased performance of drive array access. Serviceability Requirements This section provides design guidelines for serviceability features and capabilities. 222. IA-32 system includes protected forced dump switch or other mechanism for system diagnosis Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RequiredRequiredRequiredSOHO:RecommendedRequiredRecommended The system should include a protected switch or other mechanism to force an NMI on a stalled system. This device permits the system to perform a memory dump that can then be used for diagnosis of system failures. If implemented, this device must be protected in such a way that only an authorized administrator can perform this action. For additional information on the dump switch support in Windows 2000, which may be helpful for designers of IA-32 systems, please see http://www.microsoft.com/hwdev/debugging/dmpsw.htm. Note that this white paper presents only concept suggestions for designers and is not intended to provide precise implementation detail. High Availability Requirements This section summarizes the requirements for high availability. Through ACPI and OnNow power management capabilities, Windows 2000 allows more control of dynamic configuration changes and power state changes. These features help implementers in handling event-based issues such as lights that are keyed to system failures, pending failures, or system power states. 223. System includes alert indicators for occurrence of failure Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended Alert indicators should be provided that indicate hard failure. In addition to visual alerting mechanisms, a design can also provide software alerts such as paging, fax, or e-mail notifications. The following are required sources of alert indicators for hard failures for systems running Windows 2000 Advanced Server and Datacenter Server. These indicators are recommended for servers running other server versions of Windows 2000. Cooling fan malfunction, including system fans and power supply fans System and processor over-temperature Power supply over-temperature (if implemented) Disk drive error N+1 power module (if implemented) failure Recommendation Recommended: These sources of alert indicators for hard failures are recommended for all servers: Chassis cover open (intrusion) NMI, processor internal error, and time-out of watchdog timer Processor power failure 224. Hot-swappable drive includes a local disk drive replacement indicator Required A hot-swappable drive must have a local indicator that shows which drive or drives are ready for replacement, facilitating the servicing process and improving reliability by reducing possible errors. This indicator should be on the drive chassis, not on the screen. The Device Bay eject signal can be used to activate a replacement indicator. Designers can choose to use existing LEDs for dual purposes to fulfill this requirement, but the LED display should clearly show when a drive is ready for removal, as opposed to other information the display would normally provide. For systems with multiple drives, an individual replacement indicator should be physically associated with each hot-swappable drive slot. 225. System includes alert indicators for imminence of failure Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended Alert indicators that indicate informative failure are required for servers running Advanced Server or Datacenter Server and should be provided for all servers. The hard failure and informative failure indicators cannot be on simultaneously. In addition to visual alerting mechanisms, a design can also provide software alerts such as paging, fax, or e-mail notifications. The following are required sources of alert indicators for imminent failures for systems running Windows 2000 Advanced Server and Datacenter Server. These are recommended for servers running other server versions of Windows 2000: Abnormal temperature of processor or inside chassis AC power line failure (operated by UPS if present) 226. IA-64 system supports monitoring for power and down conditions Required The following monitoring capabilities are required for the hardware, SAL and firmware on IA-64 systems. Platform supports platform-down monitoring. Platform-down detection is a hardware mechanism in the platform that supports the detection of system software or processor hangs. A hardware watchdog timer is one way to implement this capability. For example, a common hardware watchdog implementation would allow system software to periodically access the timer in order to keep it from expiring. Upon expiration, the timer would typically provide a selectable set of actions, such as system power down, hard reset, power cycle, priority interrupt, and so on. Platform supports power supply fault monitoring. The platform must monitor the status of the primary power source. This includes redundant (for example, distributed) power supplies. Manageability Baseline Requirements This section presents server requirements related to the Wired for Management (WfM) initiative and the Zero Administration initiative for Windows. The WfM initiative seeks to raise the level of management capabilities on mobile, desktop, and server platforms. The Zero Administration initiative seeks to ensure a controlled, highly manageable enterprise. The baseline for these requirements is WHIIG 1.0, which also defines the Windows 2000-specific requirements of the WfM 2.0 specification for hardware instrumentation. Collectively, the items in this section represent the Manageability Baseline requirements. Tips for implementing management capabilities. For manufacturers who want to implement management capabilities for server systems and components, these are the design steps to pursue: Implement the recommended component instrumentation features defined for servers in WHIIG. For those components that require WMI, ensure that WMI is enabled in device minidrivers as defined in Supporting WMI in the Windows2000 DDK. Refer to WHIIG for other driver requirements and design tips. For all instrumented components, test against the baseline features required inWHIIG. For each component, extend the WBEM and CIM schemas to expose the devices custom features in any CIM-ready management browser. General Manageability Baseline Requirements This section defines requirements related to centralized control and configurability and BIOS support for system manageability. 227. Remote new system setup and service boot support use DHCP and TFTP Recommended The complete mechanism for remote new system setup is defined in PXE 2.1 or later. If remote new system setup capabilities are implemented, there must be a way for this capability to be enabled or disabled by way of administrative control to maintain server security. See also the requirement for the preboot execution environment in guideline #13. IA-32 BIOS boot system supports remote/network boot, USB boot devices, and firmware update, and guideline #14 IA-64 system complies with EFI 1.0 or later, with support for USB boot devices, firmware update, and PXE_BC, SERIAL_IO, and SIMPLE_NETWORK protocols. 228. Expansion devices can be remotely managed Recommended Devices provided as expansion devices should be capable of being remotely managed, ensuring that control and TCO policies can be realized. The requirements for remote management capabilities are defined in Manageability Component Instrumentation Requirements later in thischapter. For example, for any implementation of a floppy drive, the floppy drive should becapable of being remotely disabled as a boot selection and should be able to be locked. Certain devices are not required to have remote disabling capabilities, including the primary hard disk drive, the network adapter, and any standard devices that use legacy connections, such as a keyboard or pointing device that uses a PS/2 connection. However, it must be possible to use permissions, policies, or other methods to remotely manage capabilities such as hard disk access or to control certain users ability to change the MAC address or configuration settings for the network adapter. If implemented, there must be a way to enable and disable this capability by way of administrative control to maintain server security. See also the requirement for the firmware to ensure secure preboot access to hardware components in guideline #12. System firmware meets general boot support requirements. Manageability Component Instrumentation Requirements Platform management information requirements are defined for two key areas: Component instrumentation: Interfaces through which information is supplied by platform management components. Management information providers: Interfaces used by applications to access platform management information. 229. System supports Windows Hardware Instrumentation Implementation Guidelines Required These guidelines are defined in WHIIG 1.0. 230. IA-64 hardware and firmware support IA-64 Machine Check Architecture Required Many features of 64-bit Windows depend on platform support for IA-64 Machine Check Architecture. IA-64 systems must implement hardware and firmware that support IA-64 Machine Check Architecture. 230.1. IA-64 system uses Machine Check Architecture for error reporting and logging The IA-64 Machine Check Architecture has a complete method for reporting processor errors and many system errors. System designers must use the Machine Check Architecture for system-wide error reporting and logging. The Machine Check Architecture must be used to report platform errors, including errors within the system processors, memory, internal buses, and expansion buses. Note: Certain established interfaces, such as TCP/IP in the networking space and SCSI in the storage space, have extensive error reporting and recovery mechanisms in their protocol stacks. Some interfaces (for example, serial ports, LPC, and so on) may have limited or no hardware support for reporting errors. Subsystems such as this are excluded from this requirement. 230.2. IA-64 firmware implements support for Machine Check Architecture IA-64 system firmware must implement the IA-64 Machine Check Architecture. Using Machine Check Architecture, every firmware layer in the system may check for recoverable errors and log errors, and perform error recovery where possible. All machine check recovery code must use Machine Check Architecture firmware hooks. Discontinue use of Platform Management Interrupt (PMI) for doing machine check and recovery. 230.3. IA-64 Machine Check Architecture supports code resources All IA-64 Machine Check recovery code must use Machine Check Architecture firmware hooks as specified in SAL 2.7 or later. Platform machine check hardware must provide relevant status bits for all sources of hardware errors that need to be handled in Machine Check Abort code. Discontinue use of PMI and NMI for performing machine check and error recovery. 231. IA-64 system supports event logging for critical events Required The hardware, SAL, and firmware on IA-64 systems must provide the capability to log all critical events. It is required that an event log be made available that can be accessed by management software. Appendix A Server Requirements Checklist This appendix summarizes all the requirements listed for server systems in this guide. If a recommended feature is implemented, it must meet the requirements defined in this guide for that feature. IA-32 Server Requirements Checklist IA-32 General Component Requirements 1. System and components properly support all dates Required IA-32 System Microprocessor Requirements 2. Multiprocessor-capable system meets Windows requirements and minimum expansion requirements Required IA-32 Memory Requirements 3. For IA-32 system, installed memory meets minimum requirements Windows 2000 Server, Small Business ServerWindows 2000 Advanced Server, Windows 2000 Datacenter Server For 12 installed processors, 512 MB requiredFor 14 installed processors, 1 GB requiredFor more than 2 installed processors, 256 MB per installedprocessor requiredFor more than 4 installed processors, 256MB per installed processor, required 5. For IA-32 system, memory capacity meets minimum requirements Systems that provide support for <4 processors: 2GB required Systems that provide support for 4 or more processors: 8 GB required 7. System memory includes ECC memory protection Required 8. NUMA and NUMA-lite system design maintains near:far memory access time ratios of 1:3 or less Recommended IA-32 ACPI and Power Management Requirements 9. System design meets ACPI and related requirements Required for all server types, with additional requirements for SOHO servers 10. Hardware design supports OnNow initiative Required for all server types, with additional requirements for SOHO servers 11. System startup meets requirements for OnNow support Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:OptionalOptionalOptionalEnterprise:OptionalOptionalOptionalSOHO:RequiredRequiredRequired IA-32 Startup Support Requirements 12. System firmware meets general boot support requirements Required 13. IA-32 BIOS boot system supports remote/network boot, USB boot devices, and firmware update Required 15. System provides a debug port solution Required IA-32 Plug and Play Requirements 16. System and device configuration meet Plug and Play requirements Required 17. Unique Plug and Play ID is provided for each system device and addon device Required 18. PNP vendor code is used only to define a legacy devices Compatible ID Required IA-32 Headless Server Requirements 19. IA-32 system provides headless server capabilities meeting Hardware Design Guide requirements Required for Enterprise class systems Recommended for Basic and SOHO class systems 20. IA-32 system that implements headless capabilities without management service processor provides serial headless support Required if system implements headless support without a management service processor 21. IA-32 system that implements management service processor and external serial headless capability supports required external serial port and remote system reset Required if the service processor exposes a UART interface via hardware to the operating system or if the serial port is the only full-time management connection 22. IA-32 system that implements a management service processor but no external serial connection meets reset and display redirection requirements Required if system implements headless support with a management service processor 23. Uninterruptible power supply that has pass-through legacy serial port supports sharing of pass-through serial port with Windows headless capabilities Recommended IA-32 Other Requirements 24. IA-32 system includes APIC support Required 27. System with no 8042 or other port 60h and port 64h based keyboard controller meets Hardware Design Guide requirements Required 28. IA-32 system provides necessary ISR support Required IA-32 I/O Bus Requirements 29. System provides an I/O bus based on industry standard specification Required 30. All PCI adapters function properly on system supporting more than 4GB memory Required 32. System supports a 64bit PCI bus architecture Required for all IA-64 systems Required for all IA-32 systems that support more than 4 GB of system memory 33. PCI bus and devices comply with PCI 2.2 and other requirements Required 35. System makes a best effort to provide each PCI slot and device type access to a non-shared interrupt line Required 36. System does not contain ghost devices Required 37. PCI-to-PCI bridges comply with PCI to PCI Bridge Specification 1.1 Required 38. System uses standard method to close BAR windows on nonsubtractive decode PCI bridges Required 39. PCI devices do not use the <1 MB BAR type Required 40. PCI devices decode only their own cycles Required 41. VGA-compatible devices do not use non-video I/O ports Required 42. PCI chipsets support Ultra DMA (ATA/33, minimum) Required 43. Functions in a multifunction PCI device do not share writable PCI configuration space bits Required 44. Devices use the PCI configuration space for their Plug and Play IDs Required 45. Device IDs include PCI Subsystem IDs Required 46. Interrupt routing is supported using ACPI Required 47. System that supports hot swapping or hot plugging for any PCI device uses ACPI-based methods Required 48. All 66MHz and 64bit PCI buses in a server system comply with PCI 2.2 and other requirements Required 49. All PCI devices complete memory write transaction (as a target) within specified times Required 50. All PCI components comply with PCI Bus Power Management Interface specification Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedEnterprise:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedSOHO:RequiredRequiredRequired 51. System that supports S3 or S4 state provides support for 3.3Vaux Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRecommendedRecommendedEnterprise:RecommendedRecommendedRecommendedSOHO:RequiredRequiredRequired 52. PCI bus power states are correctly implemented Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedEnterprise:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedSOHO:RequiredRequiredRequired 54. PCI-X buses and devices, if present, meet requirements for device and driver support Required 55. InfiniBand fabric connections, fabrics, and devices, if present, meet requirements for device and driver support Required IA-32 USB Requirements 56. System includes USB controller with at least one USB port Required 57. All USB hardware complies with USB 1.1 Required 58. USB devices and drivers support maximum flexibility of hardware interface options Required 59. System and devices comply with USB power management requirements Required 60. USB devices comply with their related USB device class specifications Required 61. USB hubs are self-powered Required 62. USB devices install without pre-loading software Required IA-32 Other Bus Requirements 63. Any subsystems implementing I2O comply with standards and other requirements Required 64. System does not include ISA or LPC expansion slots Required 65. System does not include embedded ISA or LPC network adapters, storage controllers, or graphics adapters Required 66. System does not include ISA or LPC expansion devices Required 67. System that supports Winsock Direct connectivity meets requirements for device and driver support Required IA-32 Device Requirements 68. Device driver and installation meet Hardware Design Guide requirements Required 69. Keyboard and mouse connections meet requirements for bus and device classes Required 70. Serial port adapter meets device class specifications for its bus Required 72. If present on IA-32 system, legacy parallel port meets requirements for bus and device classes Required for all IA-32 server types, with ECP support required for SOHO servers 73. USB-to-printer port adapters comply with USB specifications Required 74. System includes emergency repair support Required 76. Primary graphics adapter on IA-32 system, if present, meets minimum requirements Required IA-32 Network Adapter Requirements 77. System includes non-ISA/non-LPC NDIS 5.0 network adapter Required 78. Network adapter uses NDIS 5.0 miniport driver Required 79. NDIS 5.0 miniport driver supports high-performance send and receive calls Required 80. Full-duplex adapter automatically detects and switches to full-duplex mode Required 81. Network adapter automatically senses presence of functional network connection Required 82. Network adapter automatically senses transceiver type Required 83. Network adapter can transmit packets from buffers aligned on any boundary Required 84. Network adapter communicates with driver across any bridge Required 85. Network adapter supports configuration capabilities and registry settings for performance tuning Required 86. PCI network adapter properly supports higher-level PCI commands Required 87. PCI network adapters are bus masters Required 88. USB or IEEE 1394 network device complies with related device class specifications Required 89. Network device and driver meet Plug and Play and power management requirements. Required 90. Network communications device supports wake-up events Recommended IA-32 Connectionless Networking Requirements 91. Network adapter offloads TCP/IP checksum, IP Security encryption, and TCP message segmentation Recommended 92. Network adapter supports filtering for at least 32multicast addresses Required 93. Server network adapter supports Load Balancing and Failover capabilities Recommended 94. Server network adapter supports remote system setup capabilities Recommended 95. Network connections used for remote boot meet PXE requirements Required 96. Network adapter and driver support promiscuous mode Required 97. Network adapter and driver support multicast promiscuous mode Required 98. Network adapter and driver support priority for IEEE 802-style networks Required IA-32 Modem Requirements 99. System includes WAN communications device Recommended IA-32 Unimodem-supported Modem Requirements 100. Modem controller meets minimum requirements Required 101. PSTN modem supports ITU-T V.250 command set Required 102. Device complies with device class power management Required 103. Device supports wake-up events Required 104. Data modem supports v.90 and v.34 modulation and other requirements Required 105. Data modem supports digital connection to support host-side V.90 operation Windows2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RequiredRequiredRequiredSOHO:RecommendedRequiredRecommended 106. Fax modem supports 14.4 Kbps (V.17) with Class 1 (T.31) command set Required for PSTN connected modems, recommended for ISDN connected modems 107. Modem supports call control signaling, controlled using V.251 modem commands Required 108. Modem supports blacklisted and delayed number clearing Required where applicable 109. Voice modem support is provided Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:OptionalOptionalOptionalEnterprise:OptionalOptionalOptionalSOHO:RecommendedRecommendedRecommended 110. Voice modem supports ITU V.253 (AT+V) Required for PSTN connected modems; recommended for ISDN or T1 connected modems IA-32 ATM Adapter Requirements 111. ATM adapter meets network adapter requirements Required 112. ATM adapter supports a minimum number of simultaneous connections Required 113. ATM adapter supports all service types defined by the ATM Forum Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 114. ATM adapter supports UBR service type Required 115. ATM adapter supports a minimum number of simultaneously active VBR or CBR connections Required 116. ATM adapter supports traffic shaping Required 117. ATM adapter enforces PCR on UBR virtual circuits Required 118. ATM adapter and driver support dynamic link speed configuration Required 119. ATM adapter supports OAM Required 120. ATM adapter supports buffer chaining (Tx + Rx) Required IA-32 ADSL Device Requirements 121. ADSL device is implemented as an integrated ADSL modem Recommended 122. Integrated ADSL modem meets network adapter requirements Required 123. ATM/ADSL solution is implemented for integrated ADSL modems Recommended 124. ADSL modem supports DMT line encoding Recommended 125. ADSL modem supports rate adaptation Recommended IA-32 Cable Modem Requirements 126. Device is implemented as an integrated cable modem Recommended 127. Integrated cable modem meets network adapter requirements Required 128. Integrated cable modem exposes an ATM or Ethernet interface Required IA-32 Serial ISDN Modem Requirements 129. ISDN modem supports required command set Required 130. ISDN modem exposes both B channels Recommended 131. ISDN modem supports asynchronous-to-synchronous conversion Required 132. ISDN modem uses high-speed port Recommended 133. ISDN modem driver supports unattended installation, with limitations Required IA-32 Parallel ISDN Device Requirements 134. Internal ISDN device meets network adapter requirements Required 135. Internal ISDN device supports synchronous HDLC framing Required 136. Internal ISDN device and driver support raw unframed synchronous B channel I/O Required 137. Driver for ISDN internal device supports unattended installation, with limitations Required 138. ISDN device with U-interface includes built-in NT1 capability Recommended 139. Internal ISDN device has software-selectable terminating resistors Required IA-32 IrDA Communications Requirements 140. Infrared network adapter meets network adapter requirements Required 141. Infrared device supports both FIR and SIR Required 142. IrDA hardware reports a unique Plug and Play ID sufficient to support unattended driver installation Required IA-32 Wireless Networking Requirements 143. Wireless networking media adapters meets network adapter requirements Required 144. Wireless networking media adapters support wireless extensions to NDIS Required 145. Wireless networking adapters support industry specifications Required IA-32 Storage Device General Requirements 146. Host controllers and devices support bus mastering Required 147. System and Option ROMs support Int 13h Extensions on IA-32 BIOS boot system Required 148. Block rewritable optical ATAPI device complies with SFF 8070i Required 149. Controller and peripherals support media status notification Required 150. Operating system recognizes the boot drive in a multiple-drive system Required 158. USB-based mass storage device complies with USB specifications Required 159. IEEE 1394-based mass storage complies with 1394 OpenHCI 1.1 Required 160. Drivers for devices that use SBP-2 command protocols follow Windows 2000 guidelines Required IA-32 SCSI Controllers and Peripherals 161. System includes SCSI host controller and SCSI peripherals Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 162. SCSI controllers with external connectors that can function as cluster nodes provide multi-initiator support Required 163. Bus type is clearly indicated on connectors for all adapters, peripherals, cables, and terminators Required 164. Differential devices support DIFFSENS as defined in SPI-3 standard Required 165. Automatic termination circuit and SCSI terminators comply with SCSI3 Required 166. Terminator power is supplied to the SCSI bus, with over-current protection Required 167. External connector complies with SCSI2 or later Required 168. Controller and peripherals implement SCSI data protection signal Required 169. SCSI connections use keyed and shrouded connectors Required 170. External devices provide SCSI-3-compliant termination Required 171. SCAM support is not present Required 172. Hardware supports the STOP/START UNIT command as defined in SBC specification Required 173. STOP/START UNIT command can be used to decrease power consumption Recommended 174. SCSI devices that support hot-plugging comply with Annex D of SPI-3 Required IA-32 ATA Controllers and Peripherals 175. System does not use ATA host controller or peripherals Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 176. Dual ATA adapters use single FIFO with asynchronous access or dual FIFOs and channels Required 177. ATA controller and peripherals comply with ATA/ATAPI-5 standard commands for features implemented and support Ultra-DMA (ATA/33, minimum) Required 178. ATA controller and peripheral connections include Pin1 cable designation with keyed and shrouded connectors Required 179. ATAPI peripherals comply with ATA/ATAPI-5 standard commands for features implemented Required 180. ATAPI devices support DEVICE RESET command Required 181. ATA/ATAPI device supports ATA STANDBY command Required IA-32 Fibre Channel Controllers and Peripherals 182. System includes Fibre Channel controller and peripherals Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRecommendedRecommendedEnterprise:RecommendedRecommendedRecommendedSOHO:OptionalOptionalOptional IA-32 Erasable Disk Drives 183. SCSI erasable drives support SCSI commands Required IA-32 CD and DVD Drives 184. System includes CD or DVD drive or other method for installing the operating system Required IA-32 CD Drive Requirements 185. CD drive provides 8x or higher performance Required 186. CD drive is CD-Enhanced compatible Required 187. CD drive supports specified logical and physical CD formats Required 188. ATA/ATAPI CD drive complies with MMC-2 Required 189. CD drive supports multisession and compatibility forms of the READ_TOC command Required 190. ATA/ATAPI CD changer meets MMC-2 standard Required IA-32 DVD Drive Requirements 191. DVD device provides 2 MB minimum transfer rate or better performance anywhere on the disk Required 192. DVD drive meets minimum compatibility requirements Required 193. DVD drive supports defect management Required 194. DVD-Video playback, if present, meets DVD-Video playback requirements Required IA-32 Backup Devices 195. System includes device for local backup Recommended 196. Single-backup device meets minimum capacity requirements Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:10 GB required10 GB required10 GB requiredEnterprise:20 GB required20 GB required20 GB requiredSOHO:10 GB required10 GB required10 GB required 197. Backup device meets industry standards Required 198. Driver integrated with Removable Storage Manager Required IA-32 CD Changers 199. If present, CD changer for seven or fewer discs meets MMC-2 standard Required IA-32 Tape and Optical Disk Changers 200. SCSI changer and drive support auto-configuration Required 201. SCSI tape and optical disk changers support SCSI commands Required IA-32 Physical Design Requirements 202. Icons are provided for all external connectors Required 203. All expansion slots in the system are accessible for users to insert cards Required 204. System and device design include protected switches Recommended 205. System design includes locking case Recommended 206. System and device design include positive retention connectors Recommended 207. If present on an IA-32 system, parallel port design provides sufficient space for connector assembly Required IA-32 Hardware Security Requirements 208. C2 evaluation for hardware Recommended 209. Peripherals follow hardware security recommendations Recommended IA-32 Backup Hardware 210. System includes integrated backup solution Recommended IA-32 Power Supply 211. System includes UPS provided with system Recommended 212. System includes power supply protection using N+1 (extra unit) Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRecommendedRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRecommendedRecommended 213. System supports replacement of power supplies Required 214. System supports replacement of fans Required 215. System includes local hot-swap power supply replacement indicators Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended IA-32 Fault-Tolerant Hardware 216. System supports multiple hard drives Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 217. System includes intelligent RAID controller with adequate storage capacity Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering 218. System supports at least one of RAID 1, 5, or 1/0 Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering 219. RAID support includes notification of failed drive Required 220. RAID subsystem supports automatic replacement of failed drive Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering 221. RAID subsystem supports manual replacement of failed drive Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering IA-32 Serviceability Requirements 222. IA-32 system includes protected forced dump switch or other mechanism for system diagnosis Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RequiredRequiredRequiredSOHO:RecommendedRequiredRecommended IA-32 High Availability Requirements 223. System includes alert indicators for occurrence of failure Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 224. Hot-swappable drive includes a local disk drive replacement indicator Required 225. System includes alert indicators for imminence of failure Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended IA-32 General Manageability Baseline Requirements 227. Remote new system setup and service boot support use DHCP and TFTP Recommended 228. Expansion devices can be remotely managed Recommended IA-32 Manageability Component Instrumentation Requirements 229. System supports Windows Hardware Instrumentation Implementation Guidelines Required IA-64 Server Requirements Checklist IA-64 General Component Requirements 1. System and components properly support all dates Required System Microprocessor Requirements 2. Multiprocessor-capable system meets Windows requirements and minimum expansion requirements Required IA-64 Memory Requirements 4. For IA-64 system installed memory meets minimum requirements Required 6. For IA-64 system, memory capacity meets minimum requirements Systems that provide support for <4 processors: 16 GB required Systems that provide support for 4 or more processors: 32 GB required 7. System memory includes ECC memory protection Required 8. NUMA and NUMA-lite system design maintains near:far memory access time ratios of 1:3 or less Recommended IA-64 ACPI and Power Management Requirements 9. System design meets ACPI and related requirements Required for all server types, with additional requirements for SOHO servers 10. Hardware design supports OnNow initiative Required for all server types, with additional requirements for SOHO servers 11. System startup meets requirements for OnNow support Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:OptionalOptionalOptionalEnterprise:OptionalOptionalOptionalSOHO:RequiredRequiredRequired IA-64 Startup Support Requirements 12. System firmware meets general boot support requirements Required 14. IA-64 system complies with EFI 1.0 or later, with support for USB boot devices, firmware update, and PXE_BC, SERIAL_IO, and SIMPLE_NETWORK protocols Required 15. System provides a debug port solution Required IA-64 Plug and Play Requirements 16. System and device configuration meet Plug and Play requirements Required 17. Unique Plug and Play ID is provided for each system device and addon device Required 18. PNP vendor code is used only to define a legacy devices Compatible ID Required IA-64 Other Requirements 25. IA-64 system includes SAPIC support Required 26. IA-64 system supports message-signaled interrupts Recommended 27. System with no 8042 or other port 60h and port 64h based keyboard controller meets Hardware Design Guide requirements Required IA-64 I/O Bus Requirements 29. System provides an I/O bus based on industry standard specification Required 30. All PCI adapters function properly on system supporting more than 4GB memory Required 31. All PCI bridges in an IA-64 system support DAC Required 32. System supports a 64bit PCI bus architecture Required for all IA-64 systems Required for all IA-32 systems that support more than 4 GB of system memory 33. PCI bus and devices comply with PCI 2.2 and other requirements Required 34. PCI devices in an IA-64 system support message-signaled interrupts Recommended 35. System makes a best effort to provide each PCI slot and device type access to a non-shared interrupt line Required 36. System does not contain ghost devices Required 37. PCI-to-PCI bridges comply with PCI to PCI Bridge Specification 1.1 Required 38. System uses standard method to close BAR windows on nonsubtractive decode PCI bridges Required 39. PCI devices do not use the <1 MB BAR type Required 40. PCI devices decode only their own cycles Required 41. VGA-compatible devices do not use non-video I/O ports Required 42. PCI chipsets support Ultra DMA (ATA/33, minimum) Required 43. Functions in a multifunction PCI device do not share writable PCI configuration space bits Required 44. Devices use the PCI configuration space for their Plug and Play IDs Required 45. Device IDs include PCI Subsystem IDs Required 46. Interrupt routing is supported using ACPI Required 47. System that supports hot swapping or hot plugging for any PCI device uses ACPI-based methods Required 48. All 66MHz and 64bit PCI buses in a server system comply with PCI 2.2 and other requirements Required 49. All PCI devices complete memory write transaction (as a target) within specified times Required 50. All PCI components comply with PCI Bus Power Management Interface specification Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedEnterprise:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedSOHO:RequiredRequiredRequired 51. System that supports S3 or S4 state provides support for 3.3Vaux Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRecommendedRecommendedEnterprise:RecommendedRecommendedRecommendedSOHO:RequiredRequiredRequired 52. PCI bus power states are correctly implemented Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedEnterprise:Required if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedRequired if S1, S2, or S3 supportedSOHO:RequiredRequiredRequired 53. Software PCI configuration space accesses on an IA-64 system use SAL procedures Required 54. PCI-X buses and devices, if present, meet requirements for device and driver support Required 55. InfiniBand fabric connections, fabrics, and devices, if present, meet requirements for device and driver support Required IA-64 USB Requirements 56. System includes USB controller with at least one USB port Required 57. All USB hardware complies with USB 1.1 Required 58. USB devices and drivers support maximum flexibility of hardware interface options Required 59. System and devices comply with USB power management requirements Required 60. USB devices comply with their related USB device class specifications Required 61. USB hubs are self-powered Required 62. USB devices install without pre-loading software Required IA-64 Other Bus Requirements 63. Any subsystems implementing I2O comply with standards and other requirements Required 64. System does not include ISA or LPC expansion slots Required 65. System does not include embedded ISA or LPC network adapters, storage controllers, or graphics adapters Required 66. System does not include ISA or LPC expansion devices Required 67. System that supports Winsock Direct connectivity meets requirements for device and driver support Required IA-64 Device Requirements 68. Device driver and installation meet Hardware Design Guide requirements Required 69. Keyboard and mouse connections meet requirements for bus and device classes Required 70. Serial port adapter meets device class specifications for its bus Required 71. IA-64 system does not include parallel port Required 73. USB-to-printer port adapters comply with USB specifications Required 74. System includes emergency repair support Required 75. Primary graphics adapter on IA-64 system meets minimum requirements Required IA-64 Network Adapter Requirements 77. System includes non-ISA/non-LPC NDIS 5.0 network adapter Required 78. Network adapter uses NDIS 5.0 miniport driver Required 79. NDIS 5.0 miniport driver supports high-performance send and receive calls Required 80. Full-duplex adapter automatically detects and switches to full-duplex mode Required 81. Network adapter automatically senses presence of functional network connection Required 82. Network adapter automatically senses transceiver type Required 83. Network adapter can transmit packets from buffers aligned on any boundary Required 84. Network adapter communicates with driver across any bridge Required 85. Network adapter supports configuration capabilities and registry settings for performance tuning Required 86. PCI network adapter properly supports higher-level PCI commands Required 87. PCI network adapters are bus masters Required 88. USB or IEEE 1394 network device complies with related device class specifications Required 89. Network device and driver meet Plug and Play and power management requirements. Required 90. Network communications device supports wake-up events Recommended IA-64 Connectionless Networking Requirements 91. Network adapter offloads TCP/IP checksum, IP Security encryption, and TCP message segmentation Recommended 92. Network adapter supports filtering for at least 32multicast addresses Required 93. Server network adapter supports Load Balancing and Failover capabilities Recommended 94. Server network adapter supports remote system setup capabilities Recommended 95. Network connections used for remote boot meet PXE requirements Required 96. Network adapter and driver support promiscuous mode Required 97. Network adapter and driver support multicast promiscuous mode Required 98. Network adapter and driver support priority for IEEE 802-style networks Required IA-64 Modem Requirements 99. System includes WAN communications device Recommended IA-64 Unimodem-supported Modem Requirements 100. Modem controller meets minimum requirements Required 101. PSTN modem supports ITU-T V.250 command set Required 102. Device complies with device class power management Required 103. Device supports wake-up events Required 104. Data modem supports v.90 and v.34 modulation and other requirements Required 105. Data modem supports digital connection to support host-side V.90 operation Windows2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RequiredRequiredRequiredSOHO:RecommendedRequiredRecommended 106. Fax modem supports 14.4 Kbps (V.17) with Class 1 (T.31) command set Required for PSTN connected modems, recommended for ISDN connected modems 107. Modem supports call control signaling, controlled using V.251 modem commands Required 108. Modem supports blacklisted and delayed number clearing Required where applicable 109. Voice modem support is provided Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:OptionalOptionalOptionalEnterprise:OptionalOptionalOptionalSOHO:RecommendedRecommendedRecommended 110. Voice modem supports ITU V.253 (AT+V) Required for PSTN connected modems; recommended for ISDN or T1 connected modems IA-64 ATM Adapter Requirements 111. ATM adapter meets network adapter requirements Required 112. ATM adapter supports a minimum number of simultaneous connections Required 113. ATM adapter supports all service types defined by the ATM Forum Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 114. ATM adapter supports UBR service type Required 115. ATM adapter supports a minimum number of simultaneously active VBR or CBR connections Required 116. ATM adapter supports traffic shaping Required 117. ATM adapter enforces PCR on UBR virtual circuits Required 118. ATM adapter and driver support dynamic link speed configuration Required 119. ATM adapter supports OAM Required 120. ATM adapter supports buffer chaining (Tx + Rx) Required IA-64 ADSL Device Requirements 121. ADSL device is implemented as an integrated ADSL modem Recommended 122. Integrated ADSL modem meets network adapter requirements Required 123. ATM/ADSL solution is implemented for integrated ADSL modems Recommended 124. ADSL modem supports DMT line encoding Recommended 125. ADSL modem supports rate adaptation Recommended IA-64 Cable Modem Requirements 126. Device is implemented as an integrated cable modem Recommended 127. Integrated cable modem meets network adapter requirements Required 128. Integrated cable modem exposes an ATM or Ethernet interface Required IA-64 Serial ISDN Modem Requirements 129. ISDN modem supports required command set Required 130. ISDN modem exposes both B channels Recommended 131. ISDN modem supports asynchronous-to-synchronous conversion Required 132. ISDN modem uses high-speed port Recommended 133. ISDN modem driver supports unattended installation, with limitations Required IA-64 Parallel ISDN Device Requirements 134. Internal ISDN device meets network adapter requirements Required 135. Internal ISDN device supports synchronous HDLC framing Required 136. Internal ISDN device and driver support raw unframed synchronous B channel I/O Required 137. Driver for ISDN internal device supports unattended installation, with limitations Required 138. ISDN device with U-interface includes built-in NT1 capability Recommended 139. Internal ISDN device has software-selectable terminating resistors Required IA-64 IrDA Communications Requirements 140. Infrared network adapter meets network adapter requirements Required 141. Infrared device supports both FIR and SIR Required 142. IrDA hardware reports a unique Plug and Play ID sufficient to support unattended driver installation Required IA-64 Wireless Networking Requirements 143. Wireless networking media adapters meets network adapter requirements Required 144. Wireless networking media adapters support wireless extensions to NDIS Required 145. Wireless networking adapters support industry specifications Required IA-64 Storage Device General Requirements 146. Host controllers and devices support bus mastering Required 148. Block rewritable optical ATAPI device complies with SFF 8070i Required 149. Controller and peripherals support media status notification Required 150. Operating system recognizes the boot drive in a multiple-drive system Required 151. IA-64 system provides GPT-partitioned hard drive for boot Required 152. IA-64 system with GPT-partitioned bootable hard disks provide one ESP of correct size Required 153. IA-64 system with ESP contains only components needed for system boot, installation, or recovery Required 154. EFI IA-64 system provides restoration tool for recovery of critical ESP and OEM special partition contents Required 155. For EFI IA-64 system, MSR partition of correct size is present on every physical or virtual hard disk manifested to the operating system when such disks are otherwise being partitioned by the provider of the system Required 156. For IA-64 system, non-ESP partitions do not contain software required for boot Required 157. For IA-64 system, ESP resides only on a device that can be reached through firmware-resident EFI drivers Required 158. USB-based mass storage device complies with USB specifications Required 159. IEEE 1394-based mass storage complies with 1394 OpenHCI 1.1 Required 160. Drivers for devices that use SBP-2 command protocols follow Windows 2000 guidelines Required IA-64 SCSI Controllers and Peripherals 161. System includes SCSI host controller and SCSI peripherals Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 162. SCSI controllers with external connectors that can function as cluster nodes provide multi-initiator support Required 163. Bus type is clearly indicated on connectors for all adapters, peripherals, cables, and terminators Required 164. Differential devices support DIFFSENS as defined in SPI-3 standard Required 165. Automatic termination circuit and SCSI terminators comply with SCSI3 Required 166. Terminator power is supplied to the SCSI bus, with over-current protection Required 167. External connector complies with SCSI2 or later Required 168. Controller and peripherals implement SCSI data protection signal Required 169. SCSI connections use keyed and shrouded connectors Required 170. External devices provide SCSI-3-compliant termination Required 171. SCAM support is not present Required 172. Hardware supports the STOP/START UNIT command as defined in SBC specification Required 173. STOP/START UNIT command can be used to decrease power consumption Recommended 174. SCSI devices that support hot-plugging comply with Annex D of SPI-3 Required IA-64 ATA Controllers and Peripherals 175. System does not use ATA host controller or peripherals Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 176. Dual ATA adapters use single FIFO with asynchronous access or dual FIFOs and channels Required 177. ATA controller and peripherals comply with ATA/ATAPI-5 standard commands for features implemented and support Ultra-DMA (ATA/33, minimum) Required 178. ATA controller and peripheral connections include Pin1 cable designation with keyed and shrouded connectors Required 179. ATAPI peripherals comply with ATA/ATAPI-5 standard commands for features implemented Required 180. ATAPI devices support DEVICE RESET command Required 181. ATA/ATAPI device supports ATA STANDBY command Required IA-64 Fibre Channel Controllers and Peripherals 182. System includes Fibre Channel controller and peripherals Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRecommendedRecommendedEnterprise:RecommendedRecommendedRecommendedSOHO:OptionalOptionalOptional IA-64 Erasable Disk Drives 183. SCSI erasable drives support SCSI commands Required IA-64 CD and DVD Drives 184. System includes CD or DVD drive or other method for installing the operating system Required IA-64 CD Drive Requirements 185. CD drive provides 8x or higher performance Required 186. CD drive is CD-Enhanced compatible Required 187. CD drive supports specified logical and physical CD formats Required 188. ATA/ATAPI CD drive complies with MMC-2 Required 189. CD drive supports multisession and compatibility forms of the READ_TOC command Required 190. ATA/ATAPI CD changer meets MMC-2 standard Required IA-64 DVD Drive Requirements 191. DVD device provides 2 MB minimum transfer rate or better performance anywhere on the disk Required 192. DVD drive meets minimum compatibility requirements Required 193. DVD drive supports defect management Required 194. DVD-Video playback, if present, meets DVD-Video playback requirements Required IA-64 Backup Devices 195. System includes device for local backup Recommended 196. Single-backup device meets minimum capacity requirements Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:10 GB required10 GB required10 GB requiredEnterprise:20 GB required20 GB required20 GB requiredSOHO:10 GB required10 GB required10 GB required 197. Backup device meets industry standards Required 198. Driver integrated with Removable Storage Manager Required IA-64 CD Changers 199. If present, CD changer for seven or fewer discs meets MMC-2 standard Required IA-64 Tape and Optical Disk Changers 200. SCSI changer and drive support auto-configuration Required 201. SCSI tape and optical disk changers support SCSI commands Required IA-64 Physical Design Requirements 202. Icons are provided for all external connectors Required 203. All expansion slots in the system are accessible for users to insert cards Required 204. System and device design include protected switches Recommended 205. System design includes locking case Recommended 206. System and device design include positive retention connectors Recommended IA-64 Hardware Security Requirements 208. C2 evaluation for hardware Recommended 209. Peripherals follow hardware security recommendations Recommended IA-64 Backup Hardware 210. System includes integrated backup solution Recommended IA-64 Power Supply 211. System includes UPS provided with system Recommended 212. System includes power supply protection using N+1 (extra unit) Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRecommendedRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRecommendedRecommended 213. System supports replacement of power supplies Required 214. System supports replacement of fans Required 215. System includes local hot-swap power supply replacement indicators Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended IA-64 Fault-Tolerant Hardware 216. System supports multiple hard drives Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 217. System includes intelligent RAID controller with adequate storage capacity Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering 218. System supports at least one of RAID 1, 5, or 1/0 Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering 219. RAID support includes notification of failed drive Required 220. RAID subsystem supports automatic replacement of failed drive Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering 221. RAID subsystem supports manual replacement of failed drive Required for all Enterprise class systems Required for Basic and SOHO class systems deploying MSCS clustering IA-64 High Availability Requirements 223. System includes alert indicators for occurrence of failure Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 224. Hot-swappable drive includes a local disk drive replacement indicator Required 225. System includes alert indicators for imminence of failure Windows 2000 ServerAdvanced Server, Datacenter ServerSmall Business ServerBasic Server:RecommendedRequiredRecommendedEnterprise:RecommendedRequiredRecommendedSOHO:RecommendedRequiredRecommended 226. IA-64 system supports monitoring for power and down conditions Required IA-64 General Manageability Baseline Requirements 227. Remote new system setup and service boot support use DHCP and TFTP Recommended 228. Expansion devices can be remotely managed Recommended IA-64 Manageability Component Instrumentation Requirements 229. System supports Windows Hardware Instrumentation Implementation Guidelines Required 230. IA-64 hardware and firmware support IA-64 Machine Check Architecture Required 231. IA-64 system supports event logging for critical events Required Glossary See also the Hardware Glossary available on http://www.microsoft.com/hwdev/glossary.htm. Acronyms and Abbreviations ABR available bit rate ACPIAdvanced Configuration and PowerInterface ADSLAsymmetric Digital Subscriber Line AMLACPI Machine Language ANSIAmerican National Standards Institute ARMDATAPI Removable Media BIOS Specification APIapplication programming interface APICAdvanced Programmable Interrupt Controller ASCIIAmerican Standard Code forInformationInterchange ASICapplication-specific integrated circuit ASLACPI Source Language ATIBM registered trademark for PC/AT ATAAT Attachment ATAPIATA Packet Interface ATMasynchronous transfer mode BARbase address register BIOSbasic I/O system BISBoot Integrity Services bpsbits per second Bxbus state CAPICommunications API CBRconstant bit rate CD-Rcompact disc, read only CD-RWcompact disc, rewritable CDCUSB Class Definition for Communications Devices CICalling Indicator CIDCompatible ID CIMCommon Information Model CIPCompaq, Intel, Phoenix CMOScomplementary metal-oxide semiconductor CMTScable modem termination system COM1. Component Object Model; 2.legacy serial port. CPECustomer Premises Equipment DACdigital-to-analog converter DCEData Communications Equipment DDKdriver development kit DHCPDynamic Host Configuration Protocol DIFFDifferential DLLdynamic link library DMAdirect memory access DMIDesktop Management Interface DMTdiscrete multi-tone DMTFDistributed Management Task Force DOCSIS Data-Over-Cable Service Interface Specification DRAMDynamic RAM DSSSDirect Sequence Spread Spectrum DVB/DAVICDigital Video Broadcasting/Digital Audio-Visual Council Dxdevice state ECCerror correction code ECPextended capabilities port EFIExtensible Firmware Interface EPPenhanced parallel port ESCDExtended System Configuration Data ESPEFI System Partition ETSIEuropean Telecommunications StandardsInstitute FCDfloppy disk controller FC-PHFibre Channel Physical, Revision 4.3 FDDIFiber Distributed Data Interface FIFOfirst in/first out FIRfast IR GBgigabyte GPTGUID Partition Table GSMglobal system for mobile communications GUIDglobally unique identifier HCLHardware Compatibility List HCTHardware Compatibility Tests HDLChigh-level data link control HIDHuman Interface Device HSMhierarchical storage management HVDHigh-Voltage Differential HzHertz IEEEInstitute of Electrical and Electronics Engineers IETFInternet Engineering Task Force ILMIInterim Local Management Interface I/Oinput/output IAIntel Architecture IPInternet Protocol IPLInitial Program Load IPX/SPXInternetwork Packet Exchange/Sequenced Packet Exchange protocol IrDAInfrared Data Association IRPI/O request packet IRQinterrupt request ISAIndustry Standard Architecture ISDNIntegrated Service Digital Network I2OIntelligent I/O ITUInternational Telecommunications Union IVRinteractive voice response LANlocal area network LEDlight-emitting diode LPClow pin count LPTline printer LUNlogical unit number LVDLow voltage differential MBmegabyte Mb/smegabits per second MCNSMultimedia Cable Network System MDKModem Developers Kit MEIMatsushita Electronics Incorporated MPSMultiProcessor Specification MRL Memory Read Line MRMMemory Read Multiple msmillisecond MSCSMicrosoft Cluster Server MSImessage-signaled interrupts MWI Memory Write and Invalidate MSDNMicrosoft Developer Network NDISNetwork Driver Interface Specification NetBEUINetBIOS Extended User Interface NMINonmaskable Interrupt NUMANon-Uniform Memory Access OAMoperation and maintenance OEMoriginal equipment manufacturer OpenHCIOpen Host Controller Interface OSIOpen System Interface PANPersonal Area Network PCIPeripheral Component Interconnect PCMpulse coded modulation PCRPeak Cell Rates PIOprogrammed I/O PLDAPrivate Loop Direct Attach PMIPlatform Management Interrupt POSTpower-on self-test PPPPoint-to-Point Protocol PS/2Personal System/2 PSTNPublic Switched Telephone Network PTTPost, Telephone, and Telegraph PXEPreboot Execution Environment QoSQuality of Service RA-ADSLrate adaptive digital subscriber line RAIDRedundant Array of Independent Disks RAMrandom access memory RFradio frequency RFCRequest for Comments ROMread-only memory RSMRemovable Storage Manager RSVPResource Reservation Setup Protocol SALSystem Abstraction Layer SAPICStreamlined APIC SCAMSCSI Configured AutoMatically SCSIsmall computer system interface SDKsoftware development kit SFFSmall Form Factor SGLsingle-ended SIDSubsystem ID SIGSpecial Interest Group SIRserial IR SMPsymmetric multiprocessing SOHOsmall office/home office SPIservice profileID SPIDservice profile identifier SSIServer System Infrastructure STS/ENStatus and Enable bits (ACPI) SVIDSubsystem Vendor ID Sxsystem state TATrade Association TAPITelephony Application Program Interface TCOtotal cost of ownership TCP/IPTransmission Control Protocol/ InternetProtocol TFTPTrivial File Transfer Protocol UADSLUniversal ADSL UARTUniversal Asynchronous Receiver/Transmitter UAWGUniversal ADSL Working Group UBRunspecified bit rate UHCIUniversal Host Controller Interface UnimodemUniversal Modem Driver UPSuninterruptible power supply USBUniversal Serial Bus UUIDUniversally Unique Identifier VARvalue-added retailer VBRvariable bit rate VCIvirtual channel identifier VPIvirtual path identifier WANwide area network WBEMWeb-Based Enterprise Management WDMWindows Driver Model WEP Wired Equivalent Privacy WfMWired for Management WHIIGWindows Hardware Instrumentation Implementation Guidelines WHQLWindows Hardware Quality Laboratory WinsockWindows Sockets WMIWindows Management Instrumentation WSDWinsock Direct Hardware Glossary A ACPIAdvanced Configuration and Power Interface. A specification that defines an interface to the system board that enables the operating system to implement operating systemdirected power management and system configuration. Following the ACPI allows system manufacturers to build systems consistent with the OnNow design initiative for instantly available PCs. ACPI hardwareComputer hardware with the features necessary to support operating system power management and with the interfaces to those features described using the Description Tables as specified in Advanced Configuration and Power Interface Specification. add-on devicesDevices that are traditionally addedto the base system to increase functionality, such as audio, networking, graphics, SCSI controller, and so on. Add-on devices fall into two categories: devices built onto the system board and devices on expansion cards added to the system through a system board connector such as PCI. ADSLAsymmetric Digital Subscriber Line. A method for moving data over regular phone lines. An ADSL circuit is much faster than a regular phone connection, and the wires coming into the subscribers premises are the same (copper) wires used for regular phone service. APIApplication programming interface. A set of routines that an applications program uses to request and carry out lower-level services performed by a computer operating system. architectureA general term referring to the structure of all or part of a computer system. Also covers the design of system software, such as theoperating system, as well as referring to the combination of hardware and basic software that links machines on a computer network. ATAAT Attachment. An integrated bus usually used between host processors and disk drives. ATAPIATA Packet Interface. A hardware and software specification that documents the interface between a host computer and CDROM drives using the ATA bus. ATMAsynchronous transfer mode. A transmission protocol that segments user traffic into small, fixed-size units called cells, which are transmitted to their destination, where they are reassembled into the original traffic. During transmission, cells from different users may be intermixed asynchronously tomaximize utilization of network resources. B bandwidthUsually used in reference to the amount of data per unit of time that must move from one point to another, such as from CDROM to processor. BIOSBasic I/O system. A set of routines that works closely with the hardware to support the transfer of information between elements of the system, such as memory, disks, and the monitor. Although critical to performance, the BIOS is usually invisible to the end user; however, programmers can access it. bpsBits per second. The number of bits transferred per second in a data communications system. A measure of speed. bus enumeratorIn a Plug and Play system, a bus device driver that detects devices located on a specific bus and loads information about devices into the hardware tree. C cacheA special memory subsystem in which frequently used data values are duplicated for quick access. CD-ROMCompact disc read-only memory. A 4.75inch laser-encoded optical memory storage medium (developed by NV Philips and Sony Corporation) with the same constant linear velocity (CLV) spiral format as compact audio discs and some video discs. CDROM discs can hold about 550MB of data. CIComponent Instrumentation. A specification for DMI related to the service layer. classFor hardware, the manner in which devices and buses are grouped for purposes of installing and managing device drivers and allocating resources. class driverA driver that provides system-required, hardware-independent support for a given class of physical devices. Such a driver communicates with acorresponding hardware-dependent port driver, using a set of system-defined device control requests, possibly with additional driver-defined device control requests. Under WDM, the class driver is responsible for multiprocessor and interrupt synchronization. COM1. Component Object Model; the core of OLE. Defines how OLE objects and their clients interact within processes or across process boundaries. 2. Legacy serial port. connectionless networking Networking based on media such as IEEE 802 LAN adapters and Fiber Distributed Data Interface (FDDI) adapters. CPUCentral processing unit. A computational and control unit of a computer; the device that interprets and executes instructions. By definition, the CPU isthe chip that functions as the brain of the computer. D data rateThe speed of a data transfer process, normally expressed in bits per second or bytes per second. DDCDisplay data channel. The Plug and Play baseline for monitors. The communications channel between a monitor and the display adapter to which it is connected. This channel provides a method for the monitor to convey its identity to the display adapter. deviceAny circuit that performs a specific function, such as a parallel port. device IDA unique ASCII string for a device created by enumerators to identify a hardware device and used to cross-reference data about the device stored in the registry. Distinguishes each logical device and bus from all others on the system. disk I/O controllerAlso HDC. A special-purpose chip and circuitry that directs and controls reading from and writing to a computers disk drive. DLLDynamic link library. API routines that Usermode applications access through ordinary procedure calls. The code for the API routine is not included in the users executable image. Instead, the operating system automatically points the executable image to the DLL procedures at run time. DMADirect memory access. A method of moving data from a device to memory (or vice versa) without the help of the microprocessor. The system board uses a DMA controller to handle a fixed number of channels, each of which can be used by only one device at a time. DMIDesktop Management Interface. A framework created by the DMTF. DMTF specifications define industry-standard interfaces for instrumentation providers and management applications. driverKernel-mode code used either to control or emulate a hardware device. driver stackDevice objects that forward IRPs to other device objects. Stacking always occurs from the bottom up and is torn down from the top. DVDOptical disk storage that encompasses audio, video, and computer data. E ECPExtended capabilities port. An asynchronous, 8bitwide parallel channel defined by IEEE 12841944 that provides PC-to-peripheral and peripheral-to-PC data transfers. enumeratorA Plug and Play device driver that detects devices below its own device node, creates unique device IDs, and reports to Configuration Manager during startup. For example, a SCSI adapter provides a SCSI enumerator that detects devices on the SCSI bus. expansion busA group of control lines that provide a buffered interface to devices located either on the system board or on cards that are plugged into expansion connectors. Common expansion buses included on the system board are USB, PCCard, and PCI. expansion cardA card that connects to an expansion bus and contains one or more devices. expansion ROM See option ROM. F FDCFloppy disk controller. A chip and associated circuitry that directs and controls reading from and writing to a computers disk drive. FIFOFirst in/first out. A method for processing a queue in which items are removed in the same order they were added. full duplexIn terms of data flow, indicates bi-directional data flow. H HCIHost controller interface, such as the system-level interface supporting USB. I INF fileInformation file. A file created for a particular adapter that provides the operating system with information required to set up a device, such as a list of valid logical configurations for the device, the names of driver files associated with the device, and so on. An INF file is typically provided by the device manufacturer on a disk with an adapter. INI fileInitialization file. Commonly used under Windows 3.x and earlier, INI files have been used by both the operating system and individual applications to store persistent settings related to an application, driver, or piece of hardware. In Windows2000 and Windows95/98, INI files are supported for backward compatibility, but the registry is the preferred location for storing such settings. input classThe class of filters that provides an interface for HID hardware, including USB and legacy devices, plus proprietary and other HID hardware, under the WDM HID architecture. instrumentationA mechanism for reporting information about the state of hardware and software to enable management applications to ascertain and change the state of a system and to be notified of state changes. integrated deviceAny devicesuch as a parallel port or graphics adapterthat is designed on the system board rather than on an expansion card. I/OInput/output. Two of the three activities that characterize a computer (input, processing, and output). Refers to the complementary tasks of gathering data for the microprocessor to work with and make the results available to the user through a device such as the display, disk drive, or printer. IPLInitial program load. A device used by the system during the boot process to load an operating system into memory. IRPI/O request packet. Data structures that drivers use to communicate with each other. The basic method of communication between kernel-mode devices. An IRP is a key data structure for WDM, which features multiple layered drivers. In WDM, every I/O request is represented by an IRP that is passed from one driver layer to another until the request is complete. When a driver receives an IRP, it performs the operation the IRP specifies, and then either passes the IRP back to the I/O Manager for disposal or onto an adjacent driver layer. An IRP packet consists of two parts: a header and the I/O stack locations. IRQInterrupt request. A method by which a device can request to be serviced by the devices software driver. The system board uses a PIC to monitor the priority of the requests from all devices. When a request occurs, a microprocessor suspends the current operation and gives control to the device driver associated with the interrupt number issued. The lower the numberfor example, IRQ3the higher the priority of the interrupt. Many devices only support raising requests of specific numbers. ISAIndustry Standard Architecture. An 8bit (andlater, a 16bit) expansion bus that provides a buffered interface from devices on expansion cards to the internal bus. isochronousRefers to a communication protocol based on time slices rather than handshaking. For example, a process might have 20 percent of total bus bandwidth. During its time slice, the process canstream data. K kernelThe core of the layered architecture that manages the most basic operations of the operating system, such as sharing the processor between different blocks of executing code, handling hardware exceptions, and other hardware-dependent functions. kernel modeThe processor mode that allows full, unprotected access to the system. A driver or thread running in kernel mode has access to system memory and hardware. L legacyAny feature in the system based on older technology for which compatibility continues to be maintained in other system components. M minidriverA hardware-specific DLL that uses a Microsoft-provided class driver to accomplish most actions through functions call and provides only device-specific controls. Under WDM, the minidriver uses the class drivers device object to make system calls. miniport driverA device-specific kernel-mode driver linked to a Windows2000 or WDM port driver, usually implemented as a DLL that provides an interface between the port driver and the system. motherboardSee system board. multifunction deviceA piece of hardware that supports multiple, discrete functions, such as audio, mixer, and music, on a single adapter. N NDISNetwork Driver Interface Specification. The interface for network drivers used in Windows2000 and Windows. NDIS provides transport independence for network vendors because all transport drivers call the NDIS interface to access the network. nibble modeAn asynchronous, peripheral-to-host channel defined in the IEEE 12841944 standard. Provides a channel for the peripheral to send data to the host, which is commonly used as a means of identifying the peripheral. NMINonmaskable Interrupt. An interrupt that cannot be overruled by another service request. A hardware interrupt is called nonmaskable if it cannot be masked by the processors interrupt enable flag. NTFSWindowsNT file system. An advanced filesystem designed for use specifically with the WindowsNT/Windows 2000 operating system. NTFS supports file system recovery and extremely large storage media, in addition to other advantages. O OnNowA design initiative that seeks to create allthe components required for a comprehensive, system-wide approach to system and device power control. OnNow is a term for a system that is always on but appears off and that responds immediately to user or other requests. option ROMOptional read-only memory found onan expansion card. Option ROMs usually contain additional firmware required to properly boot the peripheral connected to the expansion card, for example, a hard drive. P PCIPeripheral Component Interconnect. A 32bit or 64bit bus designed to be used with devices that have high bandwidth requirements, such as the display subsystem. planarSee system board. Plug and PlayA design philosophy and set of specifications that describe hardware and software changes to the system and its peripherals that automatically identify and arbitrate resource requirements among all devices and buses on the system. Plug and Play specifies a set of device driver interface elements that are used in addition to,not in place of, existing driver architectures. portA connection or socket used to connect a devicesuch as a printer, monitor, or modem to the computer. Information is sent from the computer to the device through a cable. port driverA low-level driver that responds to a set of system-defined device control requests and possibly to an additional set of driver-defined (private) device control requests sent down by a corresponding class driver. A port driver insulates class drivers from the specifics of host bus adapters and synchronizes operations for all its class drivers. POSTPower-on self-test. A procedure of the system BIOS that identifies, tests, and configures thesystem in preparation for loading the operating system. power managementMechanisms in software and hardware to minimize system power consumption, manage system thermal limits, and maximize system battery life. Power management involves trade-offs among system speed, noise, battery life, processing speed, and power consumption. Q QICQuarter-Inch Cartridge Drive Standards, Inc. An international trade association dedicated to promoting use of quarter-inch tape technology and products. R RAMRandom access memory. Semiconductor-based memory that can be read and written by the microprocessor or other hardware devices. Refers to volatile memory, which can be written as well as read. registryIn Windows2000 and Windows, the tree-structured hierarchical database where general system hardware and software settings are stored. The registry supersedes the use of separate INI files for all system components and applications that know how to store values in the registry. resource1. A set from which a subset can be allocated for use by a client, such as memory or bus bandwidth. This is not the same as resources that are allocated by Plug and Play. 2. A general term that refers to IRQ signals, DMA channels, I/O port addresses, and memory addresses for Plug and Play. S scalability1. Ability of a system to take advantage of multiple processors. 2. The ability to vary the information content of a program by changing the amount of data that is stored, transmitted, or displayed. 3. In a video image, this translates to creating larger or smaller windows of video on screen (shrinking effect). SCSISmall computer system interface. Pronounced scuzzy. An I/O bus designed as a method for connecting several classes of peripherals to a host system without requiring modifications to generic hardware and software. smart cardA small electronic device about the size of a credit card that contains an embedded integrated circuit. Smart cards are used for a variety of purposes, including storing medical records, storing digital cash, and generating network IDs. software deviceA filter in kernel streaming and ActiveMovie that has no underlying hardware associated with it. static resourcesDevice resources, such as IRQ signals, DMA channels, I/O port addresses, and memory addresses, that cannot be configured or relocated. system boardAlso motherboard or planar. The primary circuit board in a system that contains mostof the basic components of the system. system devicesDevices on the system board, such as interrupt controllers, keyboard controller, real-time clock, DMA page registers, DMA controllers, memory controllers, FDC, ATA ports, serial and parallel ports, PCI bridges, and so on. In todays systems, these devices are typically integrated in thesupporting chipset. T TAPITelephony Application Program Interface. Aset of Win32-based calls that applications use tocontrol modems and telephones by routing application function calls to the appropriate service provider DLL for a modem. TCP/IPTransport control protocol/interface program. A software protocol developed by the Department of Defense for communications betweencomputers. telephonyTelephone technology. U UARTUniversal Asynchronous Receiver/ Transmitter. A module composed of a circuit thatcontains both the receiving and transmitting circuits required for asynchronous serial communication. UnimodemUniversal modem driver. A driver-level component that uses modem description files to control its interaction with the communications driver, VCOMM. UPSUninterruptible power supply. A device connected between a computer and a power source that ensures that electrical flow to the computer is not interrupted because of a blackout and, in most cases, protects the computer against potentially damaging events such as power surges and brownouts. USBUniversal Serial Bus. A bi-directional, isochronous, dynamically attachable serial interface for adding peripheral devices such as game controllers, serial and parallel ports, and input devices on a single bus. user modeThe nonprivileged processor mode in which application code executes, including protected subsystem code in Windows2000. V VESAVideo Electronics Standards Association. Agoverning body that establishes standards for the video and graphics portions of the electronics industry. W WBEMWeb-based Enterprise Management. A DMTF initiative to provide a standards-based mechanism to specify information exchange between management applications and managed components. This work was recently transferred to the DMTF by BMC Software, Inc., Cisco Systems, Inc., Compaq Computer Corporation, Intel Corporation, and Microsoft Corporation. WDMWindows Driver Model. A driver model based on the Windows2000 driver model that is designed to provide a common architecture of I/O services and binary-compatible device drivers for both Windows2ooo and Windows operating systems for specific classes of drivers. These driver classes include USB and IEEE 1394 buses, audio, still-image capture, video capture, and HID-compliant devices such as USB mice, keyboards, and joysticks. Provides a model for writing kernel-mode drivers and minidrivers, and provides extensions for Plug and Play and power management. WHQLWindows Hardware Quality Labs. Provides testing services for hardware and drivers for Windows and Windows2000. Administers testing for the Designed for Microsoft Windows logo programs. See http://www.microsoft.com/hwtest/. Win32 APIA 32bit application programming interface for both Windows and Windows2000 that includes sophisticated operating system capabilities, security, and API routines for Windows-based applications. Windows Management Instrumentation Extensions to WDM developed for Windows2000 and Windows to provide an operating system interface through which instrumented components can provide information and notifications. Windows 2000The Microsoft Windows 2000 operating system, including any add-on capabilities and later versions of the operating system. Index Note: Technical references appear in italics ; (semicolon) dial string modifier, 66 2-way modems, 74 3.3Vaux support, 41 3-way DATA/FAX/Voice call classification modems, 68 4-bit planar VGA mode, 54 10/100 Ethernet adapters, 34 16-bit protected mode components, 48 32-bit drivers, 47 32-bit Intel microprocessors. See IA-32 systems 32-bit Microsoft clients, 57 32-bit PCI bus architecture, 34 32-bit protected mode components, 48 64-bit BAR addresses, 38 64-bit drivers, 47 64-bit Intel microprocessors. See IA-64 systems 64-bit PCI buses, 3435, 40 66-MHz buses, 40 100Base-TX adapters, 61 802.1p/q-capable Ethernet drivers, 63 802.1p/q MAC headers, 64 802.3/DIX Ethernet adapters, 74 802.3/DIX Ethernet framed packets, 61 1000Base-LX adapters, 61 1000Base-SX adapters, 61 1000Base-TX adapters, 61 1394 Open Host Controller Interface Specification, xv 1999 Version of National ISDN Basic Rate Interface Terminal Generic Guidelines (SR-4620), xv 8042-compatible interface, 49 8042 controllers, 32 8259 configuration, 36 16550 UART hardware, 29 16550A UART hardware, 50 A abbreviations list, 14856 ABR (available bit rate), 70, 148 access, protecting. See security accessibility of expansion slots, 103 ACPI (Advanced Configuration and Power Interface) ACPI 1.0b and 2.0, vi, 6, 911 ACPI-compliant servers, 4 ATA devices and, 91 availability requirements, 11011 CPU-to-PCI bridges, 42 defined, 148, 151 general requirements, 1319 hot swapping or hot plugging, 3940 IA-32 or IA-64 systems, 11, 13 implementation guidelines, xvii interrupt routing, 39 parallel port devices, 52 PCI IRQ routing web site, 10 Plug and Play, 26 power switches, 1617 specification web site, xv, 6 Windows 2000 Server support, 56 ACPI Machine Language (AML), 6, 148 ACPI Source Language (ASL), 6, 148 acronyms list, 14856 action messages at startup, 19 active SCSI terminators, 8788 adaptive carrier detection, 67 add-in network adapter cards, 56 add-on devices, xxi, 151 Administrator level protection, 19 ADSL (Asymmetric Digital Subscriber Line) adapter requirements, 56, 65 ATM/ADSL modems, 73 defined, 148, 151 DMT line encoding, 73 modems, 64, 7273 rate adaptation, 7374 requirements, 7274 UBR virtual circuits, 71 upstream bandwidth, 71 Advanced Configuration and Power Interface Specification, xv. See also ACPI (Advanced Configuration and Power Interface) Advanced Programmable Interrupt Controller. See APIC (Advanced Programmable Interrupt Controller) AGP bus mastering, 97 A-law format, 69 alerts. See also indicators chassis-open intrusion, 104 hard failure alert indicators, 110 imminence of failure alerts, 111 alpha blending, 96 American National Standards Institute, 92, 148 American Standard Code for Information Interchange (ASCII), 48 AML (ACPI Machine Language), 6, 148 analog modems, 74 analog phones, 79 analog VGA connectors, 102 ANSI (American National Standards Institute), 92, 148 ANSI NCITS T10 Multi-Media Command Set-2, xv, 83 ANSI T1.413 Issue 2 specification, 73 answering features in modems, 65 APIC (Advanced Programmable Interrupt Controller) defined, 148 IA-32 and IA-64 systems, 7, 31 Multiple APIC Description Table, 9, 31 APIs (application programming interfaces), 148, 151 application-specific integrated circuits (ASIC), 45, 148 architecture, defined, 151 ARMD (ATAPI Removable Media BIOS Specification) ARMD-compliant boot system, 22 ATAPI Removable Media BIOS Specification (ARMD), xv, 22 defined, 148 specification web site, xv ASCII (American Standard Code for Information Interchange), 148 ASIC (application-specific integrated circuits), 45, 148 ASL (ACPI Source Language), 6, 148 Asymmetric Digital Subscriber Line. See ADSL (Asymmetric Digital Subscriber Line) asynchronous access (dual ATA adapters), 90 asynchronous PPP (ISDN modems), 77 asynchronous-to-synchronous conversion (ISDN modems), 77 asynchronous transfer mode. See ATM (asynchronous transfer mode) AT (IBM PC/AT), 148 ATA (AT Attachment) ATA ACTIVE command, 92 ATA/ATAPI-5, 90 ATAPI peripherals, 91, 92 ATA STANDBY command, 92 backup devices, 98 controller and device requirements, 8992 defined, 148, 151 DEVICE RESET command, 92 DMA, 90 dual ATA adapters, 90 floppy disk emergency repair support, 54 media status notification, 83 Pin 1 cable designation, 91 ATA/33 (Ultra-DMA), 38, 90 ATA/ATAPI-5 Standard, xv, 38, 90, 92 ATA/ATAPI devices ATA Bus Master DMA, 91 ATA STANDBY command, 92 CD drives, 95 ATA Packet Interface. See ATAPI (ATA Packet Interface) ATA Packet Interface for CD-ROM (SFF 8020i), xv ATAPI (ATA Packet Interface) ATA/ATAPI-5 standards, 91 bootable floppy disk drives, 22 CD drives, 94 defined, 148, 151 direct access drives, 83 floppy drives, 83 media status notification, 83 optical ATAPI devices, 83 optical drives, 83 ATAPI Removable Media BIOS Specification (ARMD), xv, 22. See also ARMD (ATAPI Removable Media BIOS Specification) AT Attachment. See ATA (AT Attachment) AT command, 66 AT command set ISDN extensions, 76 ISDN modems, 76 serial modems, 76 ATM (asynchronous transfer mode) ATM interface for ADSL modem, 73 ATM User-Network Interface Specification, xv, 69 buffer chaining, 72 cable modems, 75 Call Manager, 72 defined, 148, 151 dynamic link speed configuration, 7172 Interim Local Management Interface, 71 miniport drivers, 57 operation and maintenance support, 72 PCR on UBR virtual circuits, 71 requirements, 65, 6972 service types, 70 simultaneous connections, 6970 traffic shaping, 71 UBR service type, 70 VBR and CBR connections, 70 virtual circuits, 71 wake-up events, 61 ATM/ADSL adapters, 70, 71 ATM/ADSL modems, 73 ATM/cable modem adapters, 71, 75 ATM Call Manager, 72 ATM Forum service types, 70 ATM User-Network Interface Specification, xv, 69 audio devices, 102 audio line in or out, 102 audio synchronization, 97 authentication services, 19 automatic device configuration ACPI control methods, 13 Plug and Play requirements, 26 tape or optical disk changers, 99100 automatic replacement of failed drives, 109 automatic SCSI termination circuits, 8788 availability alert indicators, 110 Enterprise Server class requirements, 4 fault-tolerant hardware, 1089 high-availability goal, 1 imminence of failure alerts, 111 manageability requirements, 11214 monitoring systems, 111 power supplies, 1068 replacement indicators, 11011 requirements, 11011 serviceability, 109 available bit rate (ABR), 70, 148 B B0 state, 41 B1-B3 states, 4142 BackOffice Small Business Server. See Microsoft Small Business Server backup devices capacity, 98 hardware initiatives, 5 industry standards, 98 integrated backup, 106 offline backup, 98 Removable Storage Manager, 9899 requirements, 9899 Backup tool, 98 backward compatibility, modems, 68 bad cyclic redundancy checks, 79 bandwidth, 77, 151 BAR (base address register) <1 MB BAR type, 38 BAR windows, 37 defined, 148 bar code readers, 100 base address register. See BAR (base address register) basic I/O system. See BIOS Basic Rate interface, 76 Basic Server class 3.3Vaux support, 41 alerts and indicators, 1078, 110, 111 ATA requirements, 89, 90 ATM adapter service types, 70 backup device capacity, 98 bus power states, 4142 defined, 3 failed drive automatic replacement, 109 Fibre Channel requirements, 92 headless server support, 27 intelligent RAID controllers, 108 manual replacement of failed drives, 109 modem issues, 65 multiple hard drives, 108 operating system products and, xiixiii parallel port devices, 52 power management specifications, 40 power supply protection, 107 RAID 0, 1, 5, or 1/0, 108 S3 state support, 17 SCSI storage components, 86 startup requirements, 17 system diagnosis, 109 V.90 support, 67 voice modems, 68 B channel (I/O), 78 B channel (modems), 77 benchmark performance goals, 1 bilinear interpolation, 97 BIOS BIOS-based booting, 7 booting from USB devices, 2122 CIP BIOS Boot method, 21, 84 console redirection, 28, 29 defined, 148, 151 IA-32 systems, 20 IA-64 systems, 23 SMBIOS, 19 specification web site, xviii BIS (Boot Integrity Services) Boot Integrity Services (BIS) API, xv, 20 defined, 148 firmware support for, 19 specification web site, xv bit-level PPP, 77 bits per second (bps), 148, 151 blacklisted numbers, 68 blank hard drives, 85 block rewritable ATAPI devices, 83 Blue Book standards, 94 Bluetooth devices, 55, 80 boot devices ATA devices, 90 CD and DVD drive support, 20 I2O-capable systems, 45 IEEE 1394 storage devices, 86 network adapter link sensing, 58 order of precedence, 21 serial port requirements, 50 specification web sites, xv USB keyboards, 49 Boot Integrity Services (BIS) API, xv, 20. See also BIS (Boot Integrity Services) boot process BIOS-based boot, 7 boot drive recognition, 84 boot flag specification, xviii boot list variable storage, 24 DHCP and TFTP, 11213 ESP partitions, 84 firmware support, 19, 24 IA-32 and IA-64 systems, 7 non-ESP partitions, 85 preboot passwords, 19 remote network boot, 2022, 63 SOHO Server class recommendations, 19 speeding boot times, 18 startup requirements, 1925 Boulay terminators, 8788 boundaries, buffer alignment and, 59 bps (bits per second), 148, 151 broadcast interrupts, 31 buffers ATM adapters and buffer chaining, 72 DVD drives, 97 network adapters and buffer alignment, 59 overlapped I/O buffers, 78 PIO read pre-fetch buffers, 90 bundling network links, 62 buses bus class hardware initiatives, 4 enumerators, 151 error reporting and logging, 114 I2O implementations, 45 indicating type on connections, 87 I/O bus requirements, 3342 ISA or LPC adapters or controllers, 46 ISA or LPC expansion slots, 45 PCI buses, 3342 Plug and Play, 2526 power management, 5, 15 requirements, 4547 tips for high performance, 33 USB requirements, 4344 Winsock Direct connectivity, 4647 bus mastering ATA Bus Master DMA, 9091 DVD drives, 97 multiple hard drives, 108 PCI expansion cards, 35 PCI network adapters, 60 SCSI controllers, 86 storage components, 8283 tips for high performance, 33 bus power states 3.3Vaux support, 41 correct implementation, 4142 PCI bus power states, 4142 Bx (bus state), 4142, 148 byte-level PPP, 77 C C1, C2, or C3 power states, 14 C2 evaluation, 104 cable modems defined, 64 Ethernet or ATM, 75 integrated cable modems, 75 MCNS web site, xvii modem requirements, 65, 7475 network adapter requirements, 56, 75 UBR virtual circuits, 71 upstream bandwidth, 71 cable modem termination system (CMTS), 74, 148 cables Fibre Channel, 92 headless servers, 29 cable sense, 58 caches cacheable memory, 11, 12 defined, 151 snooping cache coherency mechanism, 38 supporting largest possible, 8 call control signaling, 68 Caller ID, 66 Caller ID Detection and Reporting, 69 Calling Indicator (CI), 68, 148 call manager driver requirements, 57 capacity of servers, 2 CAPI (Communications API), 60, 148 Carrier Detect signal, 28 cases, locking, 103, 104 CBR (constant bit rate), 70, 148 CD-Audio format, 94 CDC (USB Class Definition for Communications Devices), 60, 148 CD changers, 95, 99 CD devices ATA Bus Master DMA, 91 boot support, 20, 24 CD changers, 95, 99 CD-Enhanced compatibility, 94 installation and, 93 logical and physical formats, 94 media status notification, 83 multisession disks, 94 read speed, 94 READ-TOC command, 95 requirements, 9495 USB drives, 8586 CD-Enhanced compatibility, 94 CD-I content, 94 CD Red Book format, 94 CD-R format, 94, 95, 148 CD-ROM format ATA specification web site, xv boot specification web site, xvi defined, 151 multiread specification web site, xvii Yellow Book, 94 CD-RW format, 95, 148 channels (multicast address filtering), 62 chassis cover-open alerts and controls, 104, 110 imminence of failure alerts, 111 monitoring for intrusion, viii checklists IA-32 systems, 11632 IA-64 systems, 13247 CI (Calling Indicator), 68, 148 CI (Component Instrumentation), 151 CIDs (Compatible IDs), 27, 148 CIM (Common Information Model) defined, 148 manageability and, 112 web site, xiv CIP (Compaq, Intel, Phoenix), 148 CIP BIOS Boot method ATA DMA, 90 CIP BIOS Boot, 21 multiple-drive systems, 84 Class 1 command set, 67 Class 2 command set, 68 class drivers, 152 classes hardware and devices, 151 servers, 34 CLASS key, 53 cleaning drives with media changers, 100 clients, network, 57 client types (ATM), 70 clock date support, 9 closed captioning, 96 CLS key, 53 cluster nodes, 87 CMOS clean startup screen option, 19 defined, 148 disabling ACPI support, 14 CMTS (cable modem termination system) defined, 148 in two-way service, 74 code resources (recovery codes), 114 codes for pointing devices, 49 color coding connectors and ports, 101 COM (Component Object Model), 148, 152 Common Information Model (CIM), xiv. See also CIM (Common Information Model) Communications API (CAPI), 60, 148 Communications Device Class Power Management Reference Specification, 66, 67 compact discs. See CD-ROM format Compaq, Intel, Phoenix BIOS Boot Specification, xv compatibility form (READ_TOC command), 95 compatibility protocols (parallel ports), 52 Compatible IDs (CIDs), 27, 148 compliance dates, xiv compliance testing, xii, xiiixiv component instrumentation, 11314 Component Object Model (COM), 148, 152 COM ports, 77, 148, 152 configuration ACPI control methods, 13 device configuration settings, 48 network adapter configuration files, 59 network adapters, 59 S/T-interface, 79 configuration space multifunction PCI devices, 38 Plug and Play IDs in, 3839 SAL procedures, 42 Configuring PCI-to-PCI Bridges with VGA Cards, 35 conflicting serial ports, 50 connectionless networking, 6264, 152 connection-oriented media, 57. See also ATM (asynchronous transfer mode); Frame Relay; ISDN (Integrated Service Digital Network); X.25 connectors color coding, 101 icons on, 1012 keyboard and mouse connectors, 4950 parallel port devices, 52 positive retention connectors, 103 SCSI connectors, 88 console redirection IA-32 systems, 22, 28, 29 IA-64 systems, 24 management service processors, 30 constant bit rate (CBR), 70, 148 contacts for design guide, x contiguous buffers, double word boundary and, 59 Control Panel, 48 controls for chassis-open intrusion, 104 conventions and terminology, xxi cooling fans and systems. See fans; temperature costs balancing against performance, 2 SOHO servers, 3 TCO (total cost of ownership), 106, 150 CPE (Customer Premises Equipment), 74, 148 CPUs (central processing units) CPU-to-PCI bridges, 42 defined, 152 crash dump capture capability, vii Customer Premises Equipment (CPE), 74, 148 D D0 state modems, 66 network adapter link sensing, 58 support for, 1516 D1 state, 66 D2 state, 66, 67 D3 state modems, 66, 67 PCI bus power states, 4142 PCI network adapters, 61 support for, 1516 DAC (digital-to-analog converter) bus performance and, 34 defined, 148 PCI bridges and DAC support, 34 PCI DAC command, 35 data calling tones, 68 Data Communications Equipment (DCE), 68, 148 data compression modem commands, 66 data modems, 76 Data-Over-Cable Service Interface Specification (DOCSIS). See DOCSIS (Data-Over-Cable Service Interface Specification) data protection signals, 88 data rates, 152 dates compliance dates, xiv system and component support for, 9 DB25 connectors, 52 DCE (Data Communications Equipment), 68, 148 DDC (display data channel), 152 DDKs (driver development kits), xvii, 148 debugging hung systems future server developments, vii serial port-based debug alternatives, ix debug ports IA-64 systems, 7 requirements, 25 serial ports, 50 specification web site, xv Debug Port Specification, xv, 25 decode-rate adjustment, 96 decoding cycles (PCI devices), 38 Default Device Class Power Management Specification, 15 defect management (DVD drives), 95 delayed number clearing, 68 DESCRIPTION key, 53 description tables (ACPI), 13 deserialized miniports, 57 designing servers. See server design DES key, 53 Desktop Management Interface Specification, xv. See also DMI (Desktop Management Interface) detection boot drive recognition, 84 fax/data media detection, 67 full-duplex mode, 58 developer information web sites, xivxv Device Bay "eject" signal, 11011 device classes hardware initiatives, 4 Plug and Play requirements, 2526 USB requirements, 44 Device Class Power Management Specifications, xvi device-dependent region (PCI configuration space), 39 device drivers defined, 152 files, 48 Help files, 4849 installation and removal, 48 ISDN modem drivers, 77 requirements, 4748 unattended installation, 48 device IDs defined, 152 parallel port devices, 52, 53 PCI Subsystem IDs, 39 Device Manager Advanced Page, 59 network adapter resource settings, 60 device registers (PCI configuration space), 39 DEVICE RESET command, 92 devices. See also specific types of devices defined, 152 device driver requirements, 4748 ghost devices, 37 IA-32 and IA-64 systems, 7 Plug and Play IDs, 2627 power management and, 5 registry settings, 48 requirements, 4754 serial port adapters, 50 device states (Dx), 40, 148 device write protection, 83 DHCP (Dynamic Host Configuration Protocol) defined, 148 manageability, 11213 remote boot capabilities, 20 diagnostics debug ports, 50 diagnosing systems, 109 WMI and, viii Dial-Up Networking UI, 71 DIFF (differential), 87, 148 differential devices, 87 DIFFSENS, 82, 87 digital camera key, 53 digital modem V.90 support, 67 digital monitor connectors, 102 digital-to-analog converter. See DAC (digital-to-analog converter) Digital Video Broadcasting/Digital Audio-Visual Council, 7475, 148 direct memory access. See DMA (direct memory access) directory numbers (serial modem command set), 76 Direct Sequence Spread Spectrum, 81, 148 DirectShow, 69 disabling ACPI support, 14 discrete multi-tone. See DMT line encoding disk drive error alerts, 110 disk I/O controllers, 152 display device connectors, 102 Distributed Management Task Force (DMTF), xiv, 148 DLLs, 148, 152 DMA (direct memory access) ATA DMA, 90 defined, 148, 152 DMA controllers, 26 DMA page registers, 26 parallel port devices, 51, 52 Plug and Play, 26 DMI (Desktop Management Interface) defined, 148, 152 Desktop Management Interface Specification, xv DMI Compliance Guidelines, xv DMTF (Distributed Management Task Force), xiv, 148 DMT line encoding ADSL devices, 73 DMT defined, 148 DOCSIS (Data-Over-Cable Service Interface Specification) cable modem wake-up events, 61 as current modem specification, 7475 Data-Over-Cable Service Interface Specification (DOCSIS), xv defined, 148 documentation interrupt resources, 36 tape or optical disk changers, 100 double buffering, 97 double word boundary, 59 DRAM, 18, 148 drive cleaning, media changers and, 100 driver development kits (DDKs), xvii, 148 driver extensions (USB), 44 drivers. See device drivers driver stacks, 152 DRV bit, 92 DSL Architecture: An Interoperable End-to-End Broadband Service Architecture over ADSL System, xvi DSSS (Direct Sequence Spread Spectrum), 81, 148 DTE notification, 68 DTMF generation and detection, 69 dual 8259 configuration, 36 dual asynchronous adapters, 90 dual ATA adapters, 90 dual FIFOs, 90 dual processor systems, 10 DVB/DAVIC (Digital Video Broadcasting/Digital Audio-Visual Council), 7475, 148 DVD devices ATA Bus Master DMA, 91 boot support, 20, 24 compatibility requirements, 9596 defect management, 96 DVD decoder drivers, 96 DVD Specifications for Rewritable Disc, xvi, 96 DVD-Video Playback, 9697 graphics adapters, 97 installation and, 93 media status notification, 83 MPEG-2 playback, 97 multiread specification, xvii requirements, 9597 transfer rates, 95 DVD format, 152 DVD-RAM format, 96 DVD+RW format, 96 DVD Specifications for Rewritable Disc, xvi, 96 DVD-Video Playback, 9697 Dx (device states), 40, 148 dynamic disable capabilities ACPI control methods, 13 Plug and Play requirements, 26 serial port requirements, 50 dynamic enumeration, 39 Dynamic Host Configuration Protocol. See DHCP (Dynamic Host Configuration Protocol) Dynamic Interrupt Moderation, 59 dynamic link libraries (DLLs), 148, 152 dynamic link speed configuration, 71 Dynamic RAM (DRAM), 18, 148 dynamic sensing network adapter connections, 58 transceiver types, 5859 E E820 interface, 22 ease of use, 2 EAZ serial modem command set, 76 ECC (error correction code), 12, 149 ECMA-267 format, 95 ECMA-268 format, 95 ECMA-274 format, 96 ECP (extended capabilities ports) defined, 149, 152 parallel port devices, 52 parallel ports, 51 EFI (Extensible Firmware Interface) ATA devices, 91 boot drive recognition, 84 boot list variable storage, 24 boot manager, 23 CD and DVD drive boot support, 24 console redirection, 24 defined, 149 driver set, 24 dual asynchronous adapters, 90 ESP partitions (See ESP (EFI System Partitions)) GPT-partitioned hard drives, 84 IA-32 systems, ix IA-64 systems, 7, 23 MSR partitions, 85 remote network boot, 63 restoration tools, 8485 SAL implementation, 24 specifications web sites, xvi, xvii, 7 EFI System Partitions. See ESP (EFI System Partitions) eject signal, 11011 El Torito--Bootable CD-ROM Format Specification boot support, 24 No Emulation mode, 20 web site, xvi e-mail addresses for design guide, x e-mailed failure alerts, 111 embedded 10/100 Ethernet adapters, 34 embedded ISA or LPC adapters, 46 embedded single-FIFO ATA controllers, 90 emergency repair boot/recovery systems in flash memory, vii emergency repair support, 54 encryption (IP Security), 62 end-to-end service ADSL interoperability, 72 enhanced parallel ports (EPP), 52, 149 Enterprise Server class 3.3Vaux support, 41 64-bit BAR addresses, 38 alert controls and indicators, 1078, 110, 111 ATA requirements, 70, 89 backup device capacity, 98 bus power states, 4142 defined, 34 expansion requirements, 9 Fibre Channel requirements, 92 headless server support, 7, 27 high-volume-server future developments, vi intelligent RAID controllers, 108 modem issues, 65 modem servers, 64 Enterprise Server class, continued multiple hard drives, 108 multiple processors, vi operating system products and, xiixiii parallel port devices, 52 power management specifications, 40 power supply protection, 107 RAID 0, 1, 5, or 1/0, 108 replacement of failed drives, 109 S3 state support, 17 SCSI storage components, 86 startup requirements, 17 system diagnosis, 109 V.90 support, 67 voice modems, 68 enumeration ACPI control methods, 13 enumerators defined, 152 parallel port devices, 52 Plug and Play IDs, 26 EPP (enhanced parallel ports), 52, 149 EPS Power Supply: A Server System Infrastructure (SSI) Specification for Entry Chassis Power Supplies, xvi, 17 erasable disk drives, 93 error checking (Ultra DMA), 90 error control modem commands, 66 error correcting DVD drives, 95 error correction code (ECC), 12, 149 error detection alerts, 110 error reporting and logging, 114 IrDA miniport drivers, 79 ESCD (Extended System Configuration Data), 19, 149 ESP (EFI System Partitions) defined, 149 EFI drivers and, 85 ESP partitions, 84 non-ESP partitions, 85 restoration tools, 8485 Ethernet 802.1p/q-capable Ethernet drivers, 63 802.3/DIX Ethernet framed packets, 61 ADSL modem requirements, 73 cable modems, 75 DAC support and, 34 filtering multicast addresses, 62 multicast promiscuous mode, 63 network adapters and Ethernet connection model, 60 wake-up events and, 61 ETSI (European Telecommunications Standards Institute), xvi, 74, 149 European hardware evaluation practices, 104 European Telecommunications Standards Institute, xvi, 74, 149 event logging, 114 examples of icons, 101 expansion buses and cards error reporting and logging, 114 expansion buses defined, 152 expansion cards defined, 152 ISA or LPC, 46 multiprocessor-capable systems, 9 network adapter link sensing, 58 remote management, 113 sharing interrupts, 37 expansion ROMs. See option ROMs expansion slots accessibility, 103 Enterprise Server class requirements, 9 expensive data, viii extended capabilities ports. See ECP (extended capabilities ports) Extended System Configuration Data (ESCD), 19, 149 Extensible Firmware Interface Specifications, xvi, 7. See also EFI (Extensible Firmware Interface) Extensions to the VT100 Terminal Definition console redirection, 22 IA-64 systems, 24 pass-through legacy serial ports on UPS, 30 service processors, 29 web site, xvi external ADSL modems, 73 external drives, 104 external network interfaces, 56 external serial headless capacity, 29 external serial ports, 30 F F4 and F5 loopback OAM cells, 72 F12 key, 21 failed systems or components alert indicators, 110 automatic replacement, 109 emergency repair support, 54 fault domains, vi imminence of failure alerts, 111 manual replacement, 109 monitoring platform health, viii failed systems or components, continued RAID notification, 109 reliability goals, 1 system diagnosis, 109 Failover capabilities, 62 fail-safe functions, 17 fans ACPI requirements for controls, 13 alert indicators, 110 monitoring fan status, viii replacement, 107 far memory, 12 FAR support, 67 fast IR (FIR), 80, 149 fast POST, 18 fault domains, vi fault monitoring, 111 fault-tolerant hardware fault-tolerance capabilities, 1 requirements, 1089 fax services fax calling tones in modems, 68 fax/data media detection, 67 faxing imminence of failure alerts, 111 fax modems, 6768 modem issues, 65 serial ISDN modems, 76 F-C2/E3 hardware ratings, 104 FCDs (floppy disk controllers), 149 FC-PH (Fibre Channel Physical), xvi, 92, 149 FDCs (floppy disk controllers) bootable floppy disk drives, 22 defined, 152 emergency repair support, 54 FDC key, 53 omitting tests for, 18 storage components and, 83 FDDI (Fiber Distributed Data Interface), 6264, 149 Fibre Channel bus type connection labels, 87 future server developments, vii requirements, 92 storage components, 82 storage devices, 86 Fibre Channel Physical (FC-PH), xvi, 92, 149 field-replaceable units, ix FIFO (first in/first out) defined, 149, 152 dual ATA adapters, 90 files device driver files, 48 file name requirements, 48 Help files, 4849 filtering multicast addresses, 62 FIR (fast IR), 80, 149 firmware boot support requirements, 1920 date support, 9 EFI drivers, 85 event logging, 114 IA-32 and IA-64 system firmware boot support, 7 Machine Check Architecture, 7, 114 monitoring systems, 111 redirecting firmware displays, viii updating, 20, 23 first in/first out (FIFO), 90, 149, 152 Fixed ACPI Description Table Boot Architecture Flags, 32 fixed connection dual 8259 configuration, 36 flash memory, vii flat panel monitor connectors, 102 flexibility, USB device and driver support for, 4344 floppy disk controllers (FCDs), 149 forced dump switches, 109 format block fields, 96 Format command, 93 form factors, ix frame delivery, 97 Frame Relay, 57 framers defined, 79 framing responsibility, 79 full-duplex, defined, 153 full-duplex network adapters, 58 full-duplex voice modem features, 65 full MAC drivers, 56 future technology directions, viix G G.711 PCM format, 69 game ports, 102 GBs (gigabytes), 149 general requirements for system components, 9 ghost devices, 37 gigabytes (GB), 149 Global Engineering Documents web site, xv globally unique identifiers. See GUIDs (globally unique identifiers) global system for mobile communications (GSM), xvi, 149 Global System for Mobile (GSM) Standards, xvi GPT (GUID Partition Tables) defined, 149 GPT-partitioned hard drives, 84 IA-64 systems, 7 graphics adapters DVD drives, 97 IA-32 systems, 54 IA-64 systems, 54 ISA or LPC, 46 GSM (global system for mobile communications), xvi, 149 GUIDs (globally unique identifiers) defined, 149 GUID Partition Tables, 7, 84, 149 MSR partitions, 85 H H.221 frames, 78 H.320 standard, 78 half-duplex network adapters, 58 half-height cards, 103 hard drives. See also storage components erasable disk drives, 93 imminence of failure alerts, 111 multiple hard drives, 108 omitting tests for controllers, 18 replacing, 11011 hard failure alert indicators, 110 hardware event logging, 114 hardware initiatives, 45 insert/removal notification, 40 monitoring systems, 111 Windows 2000 Server hardware requirements, v Hardware Compatibility List. See HCL (Hardware Compatibility List) Hardware Compatibility Tests (HCTs), xiii, 149 hardware design guide compliance, xiiixiv HCI (host controller interface), 153 HCL (Hardware Compatibility List) defined, xiv, 149 web site, xiv, xvii HCTs (Hardware Compatibility Tests), xiii, 149 HDC key, 53 HDLC (high-level data link control) defined, 149 HDLC framing, 78 header region (PCI configuration space), 39 headless servers console redirection, 22 device requirements, 47 future server developments, viii graphics adapters, 54 IA-32 and IA-64 systems, 7, 2728 pass-through legacy serial ports on UPS, 30 requirements, 2730 specification web site, xvi heat controls. See fans; temperature Help files, 4849 Hertz (Hz), 149 HID (Human Interface Device), 149 hierarchical storage management (HSM), 5, 149 high availability. See availability higher-level PCI commands, 59 high-level data link control (HDLC), 78, 149 high-performance send and receive, 58 high-speed ports, 77 High-Voltage Differential. See HVD (High-Voltage Differential high volume server class, vi host bridges, 34 hot plugging I/O subsystems, vi memory, vi PCI devices and ACPI methods, 3940 processors, vi SCSI devices, 89 USB devices, 44 hot swapping fans, 107 hard drives, 108, 11011 PCI devices and ACPI methods, 3940 power supplies, 1078 HSM (hierarchical storage management), 5, 149 hubs, 21, 23, 44 Human Interface Device (HID), 149 hung-system debugging, vii HVD (High-Voltage Differential) defined, 149 HVD signal type, 87 storage components, 82 Hz (Hertz), 149 I I2O (Intelligent I/O) defined, 149 I2O architecture hardware initiatives, 5 I2O (Intelligent I/O) Architecture Specification, xvi, 45 I2O implementations defined, 45 I2O system devices, 27 Plug and Play exclusions for hidden devices, 26 Plug and Play IDs, 27 IA (Intel Architecture), 149 IA-32 systems 64-bit PCI bus architecture, 3435 ACPI requirements, 6, 911, 13, 39 APIC support, 7, 31 ARMD compliance, 22 ATA device recommendations, 91 boot and firmware support, 7 bus performance on large-memory systems, 34 checklists, 11632 compared to IA-64 systems, 67 console redirection, 22 debug ports, ix, 25 defined, xi device driver requirements, 47 E820 interface, 22 EFI, ix graphics adapters, 54 headless server support, 7, 2728 Int 13h extensions, 83 ISR support, 32 manageability, 7 management service processors, 29 memory requirements, 7, 11, 12 null modem cables, 28 parallel port requirements, 5153, 104 power management, 15 remote network boot, 2022, 63 serial ports, ix, 28 storage components, 82 system diagnosis, 109 tuning drivers for performance, 33 IA-64 Machine Check Architecture, 7, 114 IA-64 systems 64-bit PCI bus architecture, 3435 ACPI requirements, 6, 13, 39 boot and firmware support, 7 boot drive recognition, 84 boot list variable storage, 24 bus performance on large-memory systems, 34 CD and DVD drive boot support, 24 checklists, 13247 code resources, 114 compared to IA-32 systems, 67 console redirection, 24 debug ports, 25 defined, xi device driver requirements, 47 driver set, 24 EFI, ix, 85 error reporting and logging, 114 ESP partitions, 84 event logging, 114 firmware and Machine Check Architecture, 114 GPT-partitioned hard drives, 84 graphics adapters, 54 hardware initiatives, 5 headless systems, 7, 27 Machine Check Architecture, 7, 114 memory requirements, 7, 12 message-signaled interrupts, 31, 35 monitoring systems, 111 MSR partitions, 85 Multiple SAPIC Description Table, 11 multiprocessor requirements, 11 non-ESP partitions, 85 parallel ports, 7, 51, 104 PCI bridges and DAC support, 34 power management, 15 remote network boot, 63 restoration tools, 8485 SAL implementation, 24, 42 SAPIC support, 7, 31 startup requirements, 2324 storage components, 82 tuning drivers for performance, 33 IBM Personal System/2 Common Interfaces (S84F-9809), xvi, 49 IBM Personal System/2 Mouse Technical Reference (S68X-2229), xvi ICCs, xvi, 104 icons, connector, 1012 identification modem commands, 66 IDs CIDs (Compatible IDs), 27, 148 device IDs, 152 GUIDs (globally unique identifiers), 85, 149 IrDA hardware IDs, 80 parallel port device IDs, 52, 53 PCI Subsystem IDs, 39 Plug and Play IDs, 2627, 3839 SIDs (Subsystem IDs), 39, 150 IDs, continued SPIDs (service profile IDs), 76, 77, 78 SVIDs (Subsystem Vendor IDs), 39, 150 switch-type IDs, 77, 78 unique IDs, 2627 UUIDs (Universally Unique Identifiers), 19, 150 IEEE (Institute of Electrical and Electronics Engineers), 149 IEEE 802 802.1d bridging, 74 802.1p/q-capable Ethernet drivers, 63 802.1p/q MAC headers, 64 802.3/DIX Ethernet adapters, 74 802.3/DIX Ethernet framed packets, 61 802.11 adapters, 81 802.14 modem specifications, 7475 LAN adapters, 6264 networks, 6364 IEEE 1284 IEEE 1284-1994 (parallel ports), 51, 52 IEEE 1284-A connectors, 52 IEEE 1284-C connectors, 52, 104 IEEE 1284-I (parallel ports), 52 IEEE 1284-II (parallel ports), 52 IEEE 1284 specification, 104 IEEE 1394 color coding connectors, 102 IEEE 1394 Standards, xvi ISDN modems, 77 media status notification, 83 network adapters, 57, 60 OpenHCI, 86 storage components, 86 IETF (Internet Engineering Task Force) defined, 149 IETF intserv service types, 63 ILMI (Interim Local Management Interface) ATM Call Manager and, 72 defined, 149 Windows use of, 71 immanence of failure indicators, 111 indicators alert indicators, 110 hard drives, 11011 imminence of failure alerts, 111 power state indicators, 17 power supply replacement indicators, 1078 Type 1/Type 0 indicators, 37 Industry Standard Architecture. See ISA (Industry Standard Architecture) INF files defined, 153 fax modems, 67 IrDA hardware, 80 ISDN modems, 76 network adapters, 57 requirements, 48 Unimodem, 64 InfiniBand fabric connections InfiniBand Trade Association web site, xvi requirements, 42 informative failure, 111 Infrared Data Association. See IrDA (Infrared Data Association) INI files defined, 153 device configuration settings, 48 network adapters, 59 initialisms, 14856 Initialize Element Status command, 100 Initial Program Load (IPL), 21, 149, 153 input classes, 153 input/output (I/O), 149, 153 Inquiry command, 93, 100 installation ATA devices, 90 CD and DVD drives, 93 device drivers, 4748 dynamic PCI device installation, 39 ESP partitions, 84 firmware driver set, 24 IrDA hardware, 80 ISDN devices, 78 unattended device driver installation, 48 USB devices, 44 instances of devices, 37 Institute of Electrical and Electronics Engineers, 149. See also IEEE (Institute of Electrical and Electronics Engineers) instrumentation defined, 153 manageability and, 11314 Int 13h extensions ATA devices, 91 bootable floppy disk drives, 22 IA-32 systems, 7 option ROMs, 83 Int 40h support, 22 integrated ATM/ADSL adapters, 70, 71 integrated backup solutions, 106 integrated cable modems, 75 integrated devices, 153 Integrated Service Digital Network. See ISDN (Integrated Service Digital Network) integrity services, 19 Intel Architecture (IA), 149 Intel Architecture-32 systems. See IA-32 systems Intel Architecture-64 systems. See IA-64 systems Intel Corporation developer information web site, xiv industry relationships, 2 multiprocessor wake-up, 11 server design information, xiv Intelligent I/O. See I2O (Intelligent I/O) intelligent RAID controllers, 108 interactive voice response. See IVR (interactive voice response) Interface Power Management feature, 44 Interim Local Management Interface. See ILMI (Interim Local Management Interface) internal ISDN devices, 76 international certification or standards hardware evaluation, 104 modems, 68 International Telecommunications Union (ITU), 74, 149. See also ITU (International Telecommunications Union) Internet Engineering Task Force (IETF), 63, 149 Internet Protocol. See IP protocol Internet sites for references and resources, xiiixviii Internetwork Packet Exchange/Sequenced Packet Exchange protocol. See IPX/SPX protocol Interoperability Specification for ICCs and Personal Computer Systems, xvi, 104 Interoperable End-to-End Broadband Service Architecture over ADSL Systems, 72 Interrupt Line register, 36 interrupt requests. See IRQs (interrupt requests) interrupts broadcast interrupts, 31 IA-64 system interrupt controllers, 31 interrupt delivery mechanisms, 31 interrupt routing and ACPI, 39 message-signaled interrupts, 31, 35 non-shared interrupt lines, 3637 prior-owner interrupts, 31 sharing interrupts, 37 targeted interrupts, 31 interrupt service routing (ISR), 32 intrusion alerts, 104, 110 invisible devices, 27 I/O (input/output), 149, 153 I/O addresses, 50 IOAPIC, 31 I/O ports and devices future server developments, vivii hot plugging, vi industry standards for I/O buses, 33 I/O bus requirements, 3342 keyboard port addresses, 49 parallel port device addresses, 51 I/O request packets. See IRPs (I/O request packets) IPL (Initial Program Load) CIP BIOS Boot, 21 defined, 149, 153 IP protocol defined, 149 IP over ATM, 70 IP Security encryption, 62 IPX/SPX protocol defined, 149 network adapter drivers, 57 IrDA (Infrared Data Association) defined, 149 FIR and SIR support, 80 network adapter requirements, 79 Plug and Play support, 80 requirements, 7980 IRPs (I/O request packets) defined, 149, 153 device driver requirements, 47 IRQs (interrupt requests) defined, 149, 153 keyboard interrupts, 49 non-PCI devices, 50 parallel port devices, 51, 52 PCI IRQs, 10, 36 PIC-based IRQs, 51 pointing devices, 49 serial port assignments, 51 serial port requirements, 50 ISA (Industry Standard Architecture) adapters or controllers, 46 defined, 149, 153 expansion devices, 46 expansion slots, 45 ISA bus interrupts, 36 ISA Enable bits, 35 legacy reduction, 33 network adapters, 56 parallel port devices, 51 Plug and Play ID exemption, 26 storage components, 82 VGA ports, 38 ISDN (Integrated Service Digital Network) adapter requirements, 65 asynchronous-to-synchronous modem conversion, 77 Basic Rate interface (BRI), 65, 76 B channels, 77 defined, 149 fax modems, 67 high-speed ports, 77 ISDN Configuration Wizard, 77, 78 ISDN TA over USB, 77 miniport drivers, 57 modems, 60, 65, 76 narrow band networks, 74 network adapter requirements, 56 non-HDLC synchronous B channel I/O, 78 parallel ISDN devices, 7879 requirements, 7579 serial modems, 7677 specification web site, xv S/T-interface, 79 synchronous HDLC framing, 78 terminal adapters, 76 U-interface, 79 unattended installation, 77, 78 wake-up events, 61 isochronous, defined, 153 isochronous bandwidth, 4344 ISR (interrupt service routine), 32 Itanium processors. See IA-64 systems ITU (International Telecommunications Union) adoption of DVB/DAVIC, 74 defined, 149 ITU communications standards ITU Communications Standards, xvi ITU T.31, 67 ITU T.32, 68 ITU-T V.250, 66 ITU V.8, 65, 68 ITU V.8bis, 65 ITU V.17, 67 ITU V.25, 68 ITU V.25 ter (See ITU V.250 command set) ITU V.32, 68 ITU V.32bis, 68 ITU V.34, 67 ITU V.42, 67, 76 ITU V.42bis, 67, 76 ITU V.80, 67 ITU V.90, 65, 67 ITU V.110, 76 ITU V.120, 76 ITU V.250, 66, 76 ITU V.251, 65, 68 ITU V.253, 65, 69 IVR (interactive voice response) defined, 149 full-duplex voice, 65 voice modems, 68 J Joe Kane Productions Video Essentials disc, 97 jumpers, 59 K kernel, 153 kernel mode, 153 Keyboard Boot Protocol, 21 keyboard ports and peripherals booting from USB devices, 21, 22, 23 color coding connectors, 102 headless servers, 47 legacy reduction, 32 Plug and Play exclusions, 26 power switches, 17 requirements, 4950 keyed connectors, 88, 91, 101 key locks, 103 L labeling connectors, 87, 1012 LAN Emulation, 70 LANs (local area networks) defined, 149 network adapter drivers, 57 promiscuous mode, 63 wireless networking requirements, 8081 Layer 3 protocols, 74 LEDs defined, 149 replacement indicators, 111 state indicators, 17 legacy components 8042 controllers, 32 color coding connectors, 102 connectors, 103 IA-32 systems, 28, 32 ISA or LPC adapters or controllers, 46 ISA or LPC expansion devices, 46 ISA or LPC expansion slots, 45 ISA VGA ports, 38 legacy components, continued ISR support, 32 legacy defined, 153 legacy removal and reduction, ix parallel ports, 7, 5153 Plug and Play requirements, 26 serial debug ports, 7 serial port adapters, 50 storage components, 8283 USB and legacy reduction, 43 vendor codes, 27 Legacy Plug and Play Guidelines, xvii, 26 light-emitting diodes. See LEDs lights (indicators). See indicators line printers (LPT), 52, 149 line rates, ATM Call Manager and, 72 link aggregation techniques in network adapters, 62 Load Balancing capability, 62 local area networks. See LANs (local area networks) local backup, 98 local indicators, 108 locking cable connections, 103 cases, 103, 104 external drives, 104 switches, 104 logging error reporting and logging, 114 event logging, 114 logical CD formats, 94 logical network links, 62 logical unit numbers. See LUNs (logical unit numbers) low pin count. See LPC (low pin count) low-power states (D1, D2), 66, 67 low voltage differential (LVD), 87, 149 LPC (low pin count) adapters or controllers, 46 defined, 149 expansion devices, 46 expansion slots, 45 legacy reduction, 33 network adapter requirements, 56 storage components, 82 LPT (line printers), 52, 149 LUNs (logical unit numbers) defined, 149 media changers and, 100 optical storage devices, 83 LVD (low voltage differential) defined, 149 LVD signal type, 87 M MAC addresses, 113 MAC drivers, 56 MAC headers, 64 Machine Check Architecture, 7, 114 Machine Check recovery code, 114 MAC layer, 74 Magic Packet events, 61 magnetic tape drives, 99100 magneto-optical disk changers, 99100 magneto-optical drives, 93 maintenance. See serviceability manageability code resources, 114 component instrumentation, 11314 DHCP and TFTP, 11213 ease of server management, 3 event logging, 114 expansion devices, 113 IA-32 and IA-64 systems, 7 Machine Check Architecture, 7, 114 requirements, 11214 tips for implementing, 112 management information providers, 11314 management service processors headless server support, 28 IA-32 systems, 29 sharing ports, 29 without external serial connections, 30 manual replacement of failed drives, 109 MANUFACTURER key, 53 Matsushita Electronics Incorporated defined, 149 test disc, 97 Maximum Completion Time, 40 Mb/s (megabits per second), 149 MBs (megabytes), 149 MCNS (Multimedia Cable Network System), 74, 149 MCNS Documents, xvii MDKs (Modem Developers Kit), 64, 149 MDL key, 53 media changers, 99100 media checks, omitting tests for, 18 media key, 53 media sense, 79 media status notification, 83 Media Status Notification Support, xvii, 83 media types, 96 megabits per second (Mb/s), 149 megabytes (MBs), 149 MEI (Matsushita Electronics Incorporated) defined, 149 test disc, 97 Memory Read Line (MRL), 59, 149 Memory Read Multiple (MRM), 59, 149 memory requirements bus performance on large memory systems, 34 E820 interface, 22 error reporting and logging, 114 fast, large, expandable memory, 8 flash memory, vii hot plugging, vi IA-32 systems, 7, 11, 12 IA-64 systems, 7, 12 large physical memory support, 5 memory dumps, 109 memory write transactions, 40 minimum system requirements, 1112 Memory Write and Invalidate (MWI), 59, 149 message-signaled interrupts. See MSI (message-signaled interrupts) MFG key, 53 microphone connectors, 102 microprocessors. See IA-32 systems; IA-64 systems; multiprocessor systems; processors Microsoft BackOffice Small Business Server. See Microsoft Small Business Server Microsoft Cluster Server (MSCS), 4, 149 Microsoft Corporation developer information web site, xv industry relationships, 2 server design information, xiv Microsoft Developer Network (MSDN), xv, 149 Microsoft DirectShow, 69 Microsoft DirectX SDK, 97 Microsoft Extensible Firmware Interface FAT32 File System Specification, xvii Microsoft Extensible Firmware Interface Long File Name Specification, xvii Microsoft Network Monitor Agent, 63 Microsoft Platform SDK, xvii Microsoft Portable Executable and Common Object File Format Specification, xvii Microsoft Reserved partitions (MSRs), 85 Microsoft Small Business Server 3.3Vaux support, 41 alerts and indicators, 1078, 110, 111 ATA requirements, 89 ATM adapter service types, 70 backup device capacity, 98 bus power states, 4142 defined, 4 Fibre Channel requirements, 92 memory requirements, 11 multiple hard drives, 108 operating system product overview, xii power management specifications, 40 power supply protection, 107 SCSI storage components, 86 startup requirements, 17 system diagnosis, 109 V.90 support, 67 voice modems, 68 Microsoft Smart Card SDK, 105 Microsoft test disk, 97 Microsoft Windows 2000 defined, 156 NDIS support, 56 product name changes, xi Windows 2000 DDK, 46, 48 Microsoft Windows 2000 Advanced Server 3.3Vaux support, 41 alerts and indicators, 1078, 110, 111 ATA requirements, 89, 90 ATM adapter service types, 70 backup device capacity, 98 bus power states, 4142 DAC support, 34 defined, 4 DVD drives, 95 Fibre Channel requirements, 86, 92 memory requirements, 11 multiple hard drives, 108 operating system product overview, xii power management specifications, 40 power supply protection, 107 product name changes, xi SCSI storage components, 86 smart card readers and cards, 1045 startup requirements, 17 system diagnosis, 109 V.90 support, 67 voice modems, 68 Microsoft Windows 2000 Datacenter Server 3.3Vaux support, 41 alerts and indicators, 1078, 110, 111 ATA requirements, 89, 90 ATM adapter service types, 70 backup device capacity, 98 bus power states, 4142 DAC support, 34 defined, 4 DVD drives, 95 Microsoft Windows 2000 Datacenter Server, continued Fibre Channel requirements, 92 hardware initiatives, 4 memory requirements, 11 multiple hard drives, 108 operating system product overview, xii power management specifications, 40 power supply protection, 107 product name changes, xi S4 hibernation state, 16 SCSI storage components, 86 smart card readers and cards, 1045 startup requirements, 17 system diagnosis, 109 V.90 support, 67 voice modems, 68 Microsoft Windows 2000 Driver Development Kit, xvii Microsoft Windows 2000 Recovery Console, vii Microsoft Windows 2000 Server 3.3Vaux support, 41 alerts and indicators, 1078, 110, 111 ATA requirements, 89 ATM adapter service types, 70 backup device capacity, 98 Backup tool, 98 bus power states, 4142 defined, 4 features and capabilities web site, 5 Fibre Channel requirements, 92 hardware initiatives, 45 memory requirements, 11 minimum system requirements, v multiple hard drives, 108 operating system product overview, xii Plug and Play requirements, 2526 power management specifications, 40 power supply protection, 107 product name changes, xi S4 hibernation state, 16 SCSI storage components, 86 smart card readers and cards, 1045 startup requirements, 17 system diagnosis, 109 V.90 support, 67 voice modems, 68 Microsoft Windows ATM Call Manager, 72 Microsoft Windows Control Panel, 48 Microsoft Windows Hardware Compatibility List, xiv, xvii, 149 Microsoft Windows Hardware Quality Labs address, xiv defined, 150, 156 web site, xiii, xv Microsoft Windows IrDA stack, 79 Microsoft Windows NT. See also Microsoft Windows 2000 Media Services, 98 Windows NT Removable Storage Manager Programming Documentation, xviii, 100 Microsoft Windows NT Server. See Microsoft Windows 2000 Server Microsoft Windows NT Server, Enterprise Edition. See Microsoft Windows 2000 Advanced Server Microsoft Windows Whistler defined, v headless server support, 27 PCI devices and hot swapping, 3940 MIDI port connectors, 102 milliseconds (ms), 149 minidrivers defined, 154 device driver requirements, 47 DVD-Video Playback, 96 minimum system requirements (Windows 2000 server), v miniport drivers connection-oriented miniport drivers, 57 defined, 154 deserialized miniports, 57 high-performance send and receive, 58 intermediate miniport drivers, 57 IrDA miniport drivers, 79 modem issues, 65 NDIS miniport drivers, 5657 wake-up events, 61 MMC-2 Multi-Media Command Set-2 standard ATA/ATAPI CD drives, 95 CD audio standards, 94 CD changers, 99 specification web site, xv, xvii storage devices, 83 MODEL key, 53 Modem Developers Kits (MDKs), 64, 149 modems ADSL modems, 7273 blacklisted and delayed number clearing, 68 call control signaling, 68 color coding connectors, 102 fax modems, 6768 ISDN modems, 76 Modems, continued modem controllers, 66 modem key, 53 modem signaling functions, 65 power management, 66 serial ISDN modems, 7677 types of modems, 6465 Unimodem requirements, 6569 V.90 and V.34 modulation, 67 voice modems, 6869 wake-up events, 67 WAN communications devices, 65 modem servers, 64 Mode Select command, 93 Mode Sense command, 93, 100 modulation modem commands, 66 monitoring systems, viii, 111 monitors color coding connectors, 102 headless servers, 47 motherboards, 56, 155 mouse devices. See pointing devices Move Medium command, 100 MPEG-2 decoding, 95 MPEG-2 playback, 97 MPS (Multiprocessor Specification), xvii, 9, 11, 149 MRL (Memory Read Line), 59, 149 MRM (Memory Read Multiple), 59, 149 ms (milliseconds), 149 MSCS (Microsoft Cluster Server) defined, 149 hardware initiatives, 4 MSCS clustering automatic replacement of failed drives, 109 intelligent RAID controllers, 108 manual replacement of failed drives, 109 RAID 0, 1, 5, or 1/0, 108 MSDN (Microsoft Developer Network), xv, 149 MSI (message-signaled interrupts) defined, 149 IA-64 systems, 31 PCI devices in IA-64 systems, 35 MSR partitions, 85 multicast addresses, 62 multicast packets, 61 multicast promiscuous mode, 63 multifunction devices defined, 154 I2O-capable systems, 45 PCI devices, 38 Plug and Play IDs, 26 sharing interrupts, 37 multi-homed systems, 61 multi-initiator support, 87 multilink PPP, 77 Multimedia Cable Network System (MCNS), xvii, 74, 149 multi-pathing connections, vii Multiple APIC Description Table, 9, 31 multiple-aspect ratios (DVD), 97 multiple hard drives, 84, 108 multiple instances of devices, 37 multiple network adapters, 60 Multiple SAPIC Description Table, 11, 31 MultiProcessor Specification (MPS), xvii, 9, 11, 149 multiprocessor systems IA-64 systems, 11 requirements, 9 wake-up, 1011 multisession CDs, 94, 95 "must" features, xii MWI (Memory Write and Invalidate), 59, 149 N N+1 (extra unit) power supplies alerts, 110 power supply protection, 107 name changes in product line, xi narrow-band networks, 74. See also analog modems; ISDN (Integrated Service Digital Network) narrow SCSI devices, 37 navigation (DVD), 97 NCITS MMC-2 specification web site, xv NCITS Reduced Block Commands Standard, xvii, 83 NDIS (Network Driver Interface Specification) ATM adapter requirements, 69 call manager drivers, 57 defined, 149, 154 IrDA miniport drivers, 79 ISDN modems, 77 library calls, 57 miniport drivers, 5657 modem issues, 65 NDIS WAN drivers, 75 network adapter requirements, 55, 56 networking modems and, 64 Remote NDIS over CDC, 60 Remote NDIS over SBP-2, 60 web site, 55 wireless extensions, 81 WSD and NDIS miniports, 46 NdisMIndicateReceivePacket calls, 58 NDIS_PER_PACKET_INFO, 63 NdisSendPackets calls, 58 near memory, 12 NetBEUI (NetBIOS Extended User Interface), 57, 149 NetWare-compatible clients, 57 network adapters ADSL modem requirements, 73 ATM adapters, 6972 Bluetooth devices, 55 bridges and, 59 buffer alignment, 59 bus mastering, 60 cable modem requirements, 75 color coding connectors, 102 configuration and registry settings, 59 connectionless networking, 6264 full- and half-duplex adapters, 58 IEEE 802-style networks, 6364 IEEE 1394 adapters, 60 INF files, 57 IrDA devices, 79 ISA or LPC, 46 Load Balancing and Failover capabilities, 62 multicast promiscuous mode, 63 multiple adapters, 60 NDIS and, 55, 56 parallel ISDN devices, 78 PCI network adapters, 59 Plug and Play, 60 power management, 60 promiscuous mode, 63 remote boot, 63 remote system setup, 62 requirements, 55 sensing connection, 58 sensing transceiver types, 5859 USB adapters, 60 wake-up events, 61 wireless networking requirements, 8081 network boot IA-32 systems, 2022 IA-64 systems, 23 network clients, 57 Network Device Class Power Management Reference Specification, 61 Network Driver Interface Specification. See NDIS (Network Driver Interface Specification) networking modems, 64. See also ADSL (Asymmetric Digital Subscriber Line); cable modems; PSTN (Public Switched Telephone Network) network key, 53 network terminators (NT-1), 79 new system remote setup, 11213 nibble mode, 52, 154 NMI (nonmaskable interrupts) alerts, 110 defined, 149, 154 discontinuing, 114 forcing, 109 future server developments, vii NMI crash dump capture capability, vii Plug and Play exclusions, 26 No Emulation mode, 20, 24 nonmaskable interrupts. See NMI (nonmaskable interrupts) non-shared interrupt lines, 3637 nonsubtractive decode PCI bridges, 37 Non-Uniform Memory Access (NUMA), 12, 149 non-volatile storage, 24 notification of failed drives, 109 Novell Netware-compatible clients, 57 NT-1 (network terminators), 79 NTFS (Windows NT file system), 154 null modem cables, 28 NUMA (Non-Uniform Memory Access) defined, 149 NUMA and NUMA-"lite" system design, 12 O OAM (operation and maintenance). See also manageability; serviceability ATM support, 72 defined, 149 odd-byte boundary, 59 OEMs (original equipment manufacturers) customized system design and requirements, xii modem exceptions, 65 network adapter exemptions, 56 OEM splash screens, 18 offline backup, 98 offloading task mechanisms, 62 offscreen surface support, 96 on-board devices. See system devices online volume management, 5 OnNow initiative availability requirements, 11011 defined, 154 design support for, 1519 implementation guidelines, xvii modems, 66 startup requirements, 1719 web site, 6 Windows 2000 Server support, 56 OpenHCI (Open Host Controller Interface) 1394 OpenHCI, 86 defined, 149 Open Host Controller Interface (OpenHCI) Specification for USB, xvii specification web site, xv, xvii USB host controllers, 43 Open Host Controller Interface (OpenHCI) Specification for USB, xvii. See also OpenHCI (Open Host Controller Interface) Open System Interface (OSI), 92, 149 operating systems. See also names of specific operating systems defined, 4 installation and, 93 memory requirements, 11 operating system products, xiixiii Windows Whistler, v operation and maintenance (OAM), 72, 149 optical disk changers, 99100 optical storage devices, 83, 93 Optical Storage Technology Association (OSTA) MultiRead Specification for CD-ROM, CD-R, CD-R/RW, and DVD-ROM Devices, xvii, 94, 96 optional features defined, xii option ROMs defined, 154 Int 13h extensions, 83 No Emulation mode, 20 updatability, 20 Orange Book formats, 94, 95, 104 order of precedence for boot devices, 21 original equipment manufacturers. See OEMs (original equipment manufacturers) OSI (Open System Interface), 92, 149 OSTA MultiRead Specification for CD-ROM, CD-R, CD-R/RW, and DVD-ROM Devices, xvii, 94, 96 out-of-band cooling methods, 13 out-of-band management out-of-band management capabilities, 30 out-of-band remote management, 28 out-of-band systems management devices, 26 over-current SCSI terminator protection, 88 overlapped I/O buffers, 78 override power switch mechanism, 16 overriding startup screens, 18 over-temperature alert indicators, 110 overvoltage protection, 107 P PACKET command, 92 PAE mode, 15 page size, 47 page table hardware, 47 page tables, 46 paging alerts for imminent failure, 111 PANs (Personal Area Networks), 8081, 149 parallel ports color coding connectors, 102 IA-32 system requirements, 5153, 104 IA-64 system requirements, 7, 51 ISDN devices, 75 omitting tests for, 18 parallel ISDN devices, 7879 Plug and Play ID exemption, 26 partitioned hard drives ACPI 2.0, vi GPT-partitioned hard drives, 84 IA-64 systems, 7 MSR partitions, 85 restoration tools, 8485 passive back planes, 103 passwords, 19 PCCA (Portable Computer and Communications Association), 81 PC-controlled call control, 68 PCI (Peripheral Component Interconnect). See also PCI bridges; PCI configuration space; PCI documents and specifications <1 MB BAR type, 38 3.3Vaux support, 41 ATA bus master DMA, 90 bridges (See PCI bridges) burst mode, 82 bus mastering, 60, 97 bus power states, 4142 configuration space (See PCI configuration space) DAC (Dual Address Cycle), 34 decoding cycles, 38 defined, 149, 154 device IDs, 39 DMA implementation, 90 dual ATA adapters, 90 higher-level PCI commands, 33 hot swapping or hot plugging, 3940 improving I/O bandwidth with controllers, 8 I/O bus requirements, 3342 IRQ routing, 10 large memory systems, 34 PCI, continued memory write transactions, 40 message-signaled interrupts, 35 modem wake-up events, 66, 67 multifunction PCI devices, 27, 38 network adapters, 59, 61 non-shared interrupt lines, 3637 PCI 2.2 support, 35, 40 PCI-PM, 42 PCI-X buses, 42 power management specifications, 4041 Ultra DMA support, 38 PCI bridges BAR and, 37 card support, 35 CPU-to-PCI bridges, 42 DAC and, 34 in description tables, 13 network adapters, 59 PCI-to-PCI bridges, 34, 35, 37, 4041, 42 peer bridges, 35 PCI configuration space PCI network adapters, 60 Plug and Play IDs, 3839 SAL and configuration space accesses, 42 PCI documents and specifications PCI Bus Power Management Interface specification, xviii, 4041 PCI Device Subsystem IDs and Windows, 39 PCI Hot-Plug Specification, xviii, 40 PCI Local Bus Specification (PCI 2.2), xviii, 26 PCI Power Management Interface Specification, 42 PCI to PCI Bridge Specification, xviii, 37 PCI-X Addendum to the PCI Local Bus Specification, xviii, 42 PCI-PM, 42 PCI-X Addendum to the PCI Local Bus Specification, xviii, 42 PCI-X buses, 42 PCM (pulse coded modulation), 69, 150 PCMCIA key, 53 PCR (Peak Cell Rates) defined, 150 UBR virtual circuits, 71 peer bridges, 35 peer servers, 57 Pentium processors. See IA-32 systems; IA-64 systems; processors performance CD drives, 94 costs and, 2 goals for server systems, 1 tuning network adapters, 59 Peripheral Component Interconnect. See PCI (Peripheral Component Interconnect) peripherals. See names of specific types of peripherals permissions in remote management, 113 Personal Area Network (PANs), 8081, 149 Personal System/2. See PS/2 (Personal System/2) phase-change drives erasable disk drives, 93 requirements, 99100 physical ACPI power buttons, 14 physical addresses, 46 physical CD formats, 94 physical design connector icons, 1012 expansion slot accessibility, 103 issues, ix locking cases, 103 parallel ports, 104 positive retention connectors, 103 protected switches, 103 requirements, 1014 software management of physical components, 103 physical network links, 62 PICs (programmable interrupt controllers) PIC-based IRQs, 51 Plug and Play exclusions, 26 Pin 1 cable designation, 91 orientation, 88 PIO (programmed I/O) ATA devices and, 91 defined, 150 PIO read pre-fetch buffers, 90 planars (system boards), 56, 155 platform health monitoring error reporting and logging, 114 future server developments, viii platform-down monitoring, 111 watchdog timers, vii Platform Management Interrupt (PMI), 114, 150 platform remote access management, viii PLDA (Private Loop Direct Attach), 92, 150 Plug and Play. See also Plug and Play specifications ACPI-support in Windows 2000 Server, 5 defined, 154 device driver requirements, 47 Plug and Play, continued hardware initiatives, 4 IDs in PCI configuration space, 3839 IrDA hardware IDs, 80 legacy guidelines web site, xvii network adapters, 60 parallel port devices, 52 PNP vendor codes, 27 requirements, 2527 smart card readers and cards, 105 unique IDs, 2627 Plug and Play specifications Legacy Plug and Play Guidelines, xvii, 26 Plug and Play External COM Device Specification, 50 Plug and Play ISA Specification, 26 Plug and Play Parallel Port Device Specification, 51, 53 web site, xviii plus sign prefix in modem commands, 66 PMI (Platform Management Interrupt), 114, 150 PNP vendor codes, 27 pointing devices booting from USB devices, 21, 22, 23 color coding connectors, 102 connections or ports, 4950 headless servers, 47 mouse input device specification web site, xvi Point-to-Point Protocol. See PPP (Point-to-Point Protocol) policies in remote management, 113 port 60h-based controllers, 32 port 64h-based controllers, 32 Portable Computer and Communications Association, 81 port key, 53 ports. See also names of specific port types color coding and icons, 101 defined, 154 high-speed ports, 77 port drivers, 154 redirection web site, xviii positive retention connectors, 103 POST (power-on self-test) defined, 150, 154 disabling fast POST, 18 startup requirements, 18 Post, Telephone, and Telegraph (PTT), 68, 150 POTS port, 79 power buttons, 14, 1617 power failures, 110, 111 power management ACPI power management timer requirements, 13 ACPI support in Windows 2000 Server, 5 bus power management support, 15 bus power states, 4142 defined, 154 device driver requirements, 47 general requirements, 1319 hardware initiatives, 4 modems, 66 network adapters, 60 PCI adapters, 61 remote power-on capabilities, viii SCSI devices, 89 self-powered USB hubs, 44 specification web sites, xvi state indicators, 17 system-board power management, 15 USB requirements, 44 power-on self-test. See POST (power-on self-test) power states. See also names of specific power states modems, 66 network adapters, 61 support for, 14 power supplies fans, 107, 110 guaranteed power, 1068 monitoring systems, 111 over-temperature, 110 protection, 107 replacement, 107 replacement indicators, 1078 SCSI terminator power, 88 UPSs, 107 PPP (Point-to-Point Protocol) asynchronous PPP, 77 defined, 150 multilink PPP, 77 PPP-over-ATM over ADSL, 72, 73 PPP-over-ATM virtual circuits, 70, 71 synchronous PPP, 77 PPP-over-ATM virtual circuits, 71 Preboot Execution Environment. See PXE (Preboot Execution Environment) Preboot Execution Environment (PXE) Specification, xviii preboot passwords, 19 predictive failure analysis, viii + prefix, 66 preinstalled software on MSR partitions, 85 Prevent/Allow Media Removal command, 93, 100 printer key, 53 printer ports, 53 prior-owner interrupts, 31 Private Loop Direct Attach (PLDA), 92, 150 processors error reporting and logging, 114 hot plugging, vi IA-32 and IA-64 systems, 67 imminence of failure alerts, 111 internal error alerts, 110 microprocessor requirements, 911 number of, vi power failure alerts, 110 product name changes, xi programmable gain control, 69 programmed I/O. See PIO (programmed I/O) promiscuous mode, 63 protected forced dump switches, 109 protected mode components, 48 protecting servers. See security PS/2 (Personal System/2) defined, 150 keyboard and mouse connections, 49 PS/2-compatible keyboards, 102 PS/2-compatible pointing devices, 102 PS/2 compatible ports, 26 PSTN (Public Switched Telephone Network) defined, 150 design issues, 65 fax modems, 67 modems, 64 V.250 commands, 66 PTT (Post, Telephone, and Telegraph) defined, 150 modem certification, 68 Public Switched Telephone Network. See PSTN (Public Switched Telephone Network) pulse coded modulation (PCM), 69, 150 push technology, 62 PXE (Preboot Execution Environment) defined, 150 firmware update mechanisms, 20 IA-32 systems, 20 network adapter support, 62 remote boot capabilities, 21, 63 remote new system setup, 112 specification web site, xviii, 20 PXE_BC (remote/network boot) protocol, 7, 23 Q QIC (Quarter-Inch Cartridge Drive Standards), 154 QoS (Quality of Service) CMTS and, 74 defined, 150 link layer priority, 63 simultaneously active connections, 70 QoS: Assigning Priority in IEEE 802-style Networks, 64 Quality of Service. See QoS (Quality of Service) Quarter-Inch Cartridge Drive Standards, 154 querying for time discontinuities, 96 R RA-ADSL (rate adaptive digital subscriber line), 7374, 150 radio frequency (RF), 74, 150 RAID (Redundant Array of Independent Disks) defined, 150 notification of failed drives, 109 RAID 0, 1, 5, or 1/0, 108 RAID controllers, 108 replacement of failed drives, 109 RAM (random access memory) defined, 150, 155 IA-32 systems, 12 IA-64 systems, 12 random access memory. See RAM (random access memory) rate adaptation ADSL devices, 7374 ATM adapters, 71 rate adaptive digital subscriber line (RA-ADSL), 7374, 150 raw unframed synchronous B channel I/O, 78 RBC (Reduced Block Commands standard), xvii, 83 RDMA operators, 47 Read Capacity command, 93 Read command, 93 Read Defect Data command, 93 Read Element Status command, 100 Read Format Capacities command, 83 read-only memory (ROM), 150 read speed (CD drives), 94 READ_TOC command, 94, 95 real-mode components, 48 real-time clocks date support, 9 Plug and Play exclusions, 26 SOHO Server class, 14 Reassign Blocks command, 93 rebooting, viii recommended features, xixii recovery support ESP partitions, 84 hardware initiatives, 5 recovery code, 114 Recovery Console, vii recovery firmware driver set, 24 restoration tools, 8485 Red Book audio, 94 redirecting firmware displays, viii redirecting ports, xviii reduced latency in storage components, 82 Redundant Array of Independent Disks. See RAID (Redundant Array of Independent Disks) references, xiiixviii registry defined, 155 device configuration settings, 48 network adapters, 59, 60 regulated SCSI terminators, 8788 Release command, 93, 100 reliability fault-tolerant hardware, 1089 goals of server design, 1 manageability baseline requirements, 11214 power supplies, 1068 serviceability, 109 remote management expansion devices, 113 future server developments, viii headless server support, 2730 IA-32 system boot, 2022 IA-64 system boot, 23 network adapter support, 62 new system setup, 11213 remote network boot, 63 remote software management, 104 remote system reset, 29, 30 security, 104 Remote NDIS over CDC, 60 Remote NDIS over SBP-2, 60 removable media drives, 91 Removable Storage Manager. See RSM (Removable Storage Manager) removing device drivers, 48 removing devices (PCI dynamic removal), 39 repair support. See serviceability replacing failed drives automatically, 109 failed drives manually, 109 fans, 107 hard drives, 11011 power supplies, 1078 Request for Comments (RFC), 150 Request Sense command, 93, 100 Request Volume Element Address command, 100 required features customized OEM system design and, xii defined, xi operating system products and, xiixiii Reserve command, 93, 100 reserved registers, 39 reserved values in Interrupt Line register, 36 residential broadband networks, 71 resource allocation, 13, 26 resource configuration, 50 Resource Reservation Setup Protocol (RSVP), 74, 150 resources, defined, xiiixviii, 155 resource settings Device Manager, 60 non-PCI devices, 5051 restoration tools, 8485 rewritable compact discs (CD-RW), 95, 148 RF (radio frequency), 74, 150 RFCs (Requests for Comments) defined, 150 RFC 1717, 77 RF-return modems, 74 right-to-left speakers, 102 robustness, 2 ROM (read-only memory), 150 ROM (stamped) format, 94, 95 rotational speed of storage components, 82 routing, CMTS and, 74 RS-IA-64 System Abstraction Layer (SAL) Specification, xviii, 24 RSM (Removable Storage Manager) defined, 150 driver integration, 9899 hardware initiatives, 5 programming web site, xviii tape or optical disk changers, 99 RSVP (Resource Reservation Setup Protocol), 74, 150 run-time diagnostics, viii S S1 state bus support, 15 indicators, 17 OnNow support, 15 PCI bus power states, 4142 resuming from, 18 SOHO Server class, 14 S2 state bus support, 15 indicators, 17 OnNow support, 15 PCI bus power states, 4142 resuming from, 18 SOHO Server class, 14 wake-up, 15 S3 state 3.3Vaux support, 41 bus support, 15 indicators, 17 OnNow support, 15 PCI bus power states, 4142 resuming from, 18 SOHO Server class, 14 standby power, 17 wake-up, 15 S4 state 3.3Vaux support, 41 lack of support for, 16 OnNow support, 15 PCI bus power states, 4142 state indicators, 17 S5 state PCI bus power states, 4142 SOHO Server class, 14 state indicators, 17 SAL (System Abstraction Layer) defined, 150 event logging, 114 IA-64 system implementation, 24 monitoring systems, 111 RS-IA-64 System Abstraction Layer (SAL) Specification, xviii, 24 SAL System Table, 24 SAPIC (Streamlined APIC), 7, 31, 150 SBP-2 protocol, 60, 86 SBP-2 Support and Windows 2000, 86 scalability of servers, 2, 155 scaling (DVD), 97 SCAM (SCSI Configured AutoMatically), 89, 150 scan codes, 17, 49 scanner key, 53 screen displays, viii SCSI (small computer system interface) backup devices, 98 bus addresses, 100 bus mastering, 86 color coding connectors, 102 command sets, 93 connection labels, 87 data protection signal, 88 defined, 150, 155 differential devices, 87 erasable drives, 93 external connectors, 88 external device termination, 88 host adapters, 86 hot-plugging, 89 HVD differential devices, 82 keyed and shrouded connectors, 88 media changer command sets, 100 media status notification, 83 multi-initiator support, 87 SCSI-2, 88 SCSI-3, 8788 SCSI-3 Parallel Interface (SPI) specification, Annex F, 87, 88 SCSI Block Commands specification, 89 SCSI Configured AutoMatically (SCAM), 89, 150 sharing interrupts, 37 START/STOP UNIT command, 89 storage components, 82, 8689 tape or optical disk changers, 99100 termination, 8788 terminator power, 88 SCSI Configured AutoMatically (SCAM), 89, 150 SDKs (software development kits), xvii, 150 security C2 evaluation, 104 goals of server design, 2 peripherals, 1045 preboot passwords, 19 requirements, 1045 Winsock Direct, 47 Seek command, 93 self-powered USB hubs, 44 semicolon dial string modifier, 66 Send Volume Tag command, 100 sensing connections, 58 sensing transceiver types, 5859 Serial AT command set, 76 SERIAL_IO protocol, 7, 23 serial IR (SIR), 80, 150 serializing access, 90 serial numbers media changer command sets, 100 SCSI erasable drives, 93 Serial Port Console Redirection Table, xviii, 22, 29 serial ports and peripherals alternatives to debug ports, ix color coding connectors, 102 console redirection, 22, 24 debug ports, 7, 25, 50 external serial ports, 29 headless server support, 28, 29 IA-32 systems, 28 IA-64 systems, 7 ISDN devices, 75 management service processors lacking external ports, 30 omitting tests for, 18 pass-through legacy serial ports on UPS, 30 Plug and Play ID exemption, 26 serial ISDN modems, 7677 serial modems, 64, 65 serial port adapters, 50 SOHO Server class serial modems, 64 Unimodem requirements, 6569 server classes, 34 server design e-mail contacts for design requirements, x future directions, viix goals, 23 hardware initiatives, 45 high-performance system components, 8 issues, 1 legacy removal and reductions, ix new server segments, ix overview, 13 physical design, 1014 references and resources, xiiixviii required and recommended features, xixii server classes and operating systems, xii, 34 Server System Infrastructure (SSI), xvi, 150 serviceability ease of maintenance, 2 emergency repair support, 54 manageability baseline requirements, 11214 requirements, 109 system diagnosis, 109 service profile IDs (SPIDs). See SPIDs (service profile IDs) setup ease of, 3 redirecting setup screens, viii remote new system setup, 63 SFF (Small Form Factor) documents SFF 8020i, xv SFF 8038i, 90 SFF 8070i, 83 SFF defined, 150 SFF publications web site, xv SGL (single-ended) defined, 150 SGL signal type, 87 sharing configuration space bits, 38 interrupts, 37 SCSI, 87 serial ports, 29, 30 "should" features, xii shrouded connectors, 88, 91, 101 SIDs (Subsystem IDs), 39, 150 SIGs (Special Interest Groups), 150 Simple Boot Flag Specification, xviii, 19 SIMPLE_NETWORK protocol, 7, 23 simultaneous network connections, 6970 single-ended (SGL), 87, 150 SIR (serial IR), 80, 150 sleep buttons, 16 sleep states. See also S1-S5 states multiprocessor wake-up, 10 PCI bus power states, 4142 resuming from, 18 Small Business Server. See Microsoft Small Business Server small computer system interface. See SCSI (small computer system interface) Small Form Factor. See SFF (Small Form Factor) documents small office/home office (SOHO), 150 small office/home office servers. See SOHO server class smart card readers and cards, 1045, 155 SMBIOS, 19, 20 SMP (symmetric multiprocessing), 150 snooping cache coherency mechanism, 38 software development kits (SDKs), xvii, 150 software devices, 155 software-initiated spin down, 89 software management of physical components, 103 software-selectable terminating resistors, 79 SOHO (small office/home office), 150 SOHO Server class 3.3Vaux support, 41 ACPI and power management, 1415 alert indicators, 110 ATA requirements, 89, 90 ATM adapter service types, 70 backup device capacity, 98 boot recommendations, 19 bus power states, 4142 defined, 3 Fibre Channel requirements, 92 headless server support, 27 imminence of failure alerts, 111 intelligent RAID controllers, 108 ISDN devices, 79 modem issues, 64, 65 multiple hard drives, 108 operating system products, xiixiii parallel ports, 51 power management specifications, 40 power supply protection, 107 power supply replacement indicators, 1078 power switches, 16 RAID 0, 1, 5, or 1/0, 108 replacement of failed drives, 109 S3 state support, 17 SCSI storage components, 86 startup requirements, 17, 1819 system diagnosis, 109 V.90 support, 67 voice modems, 68 Sony ReadTOC method, 94 speaker out ports, 102 Special Interest Groups (SIGs), 150 specification web site list, xiiixviii speed boot times, 18 CD drives, 94 DVD drives, 95 dynamic link speed configuration, 7172 high-speed ports, 77 IrDA speed change commands, 79 rotational speed of storage components, 82 SPI (service profile ID). See SPIDs (service profile IDs) SPI-3 standard data protection signal, 88 hot-plugging SCSI devices, 89 HVD differential devices, 82 SCSI devices, 87 SPIDs (service profile IDs) defined, 150 ISDN devices, 78 ISDN modem drivers, 77 ISDN modems, 76 serial modem command set, 76 spin down, 89 splash screens, 18 SR-4620 (ISDN Basic Rate Interface), xv SSI (Server System Infrastructure), xvi, 150 standard high-volume server class, vi standby power, 17 START/STOP UNIT command, 89, 93 startup minimizing displays, 18 OnNow requirements, 1719 requirements, 1925 static resources, 155 Status and Enable bits. See STS/EN (Status and Enable bits (ACPI)) S/T-interface, 79 Stop Grant Bus cycle, 10 storage components ATA controllers and devices, 8992 backup devices, 9899 boot drives, 84 bus mastering, 8283 CD and DVD drives, 9397 erasable disk drives, 93 ESP partitions, 84, 85 Fibre Channel, 92 general requirements, 8286 GPT-partitioned hard drives, 84 IEEE 1394 components, 86 Int 13h extensions, 83 ISA or LPC components, 46 locking cases, 104 media changers, 99100 media status notification, 83 MSR partitions, 85 multiple-drive systems, 84 non-ESP partitions, 85 optical ATAPI devices, 83 restoration tools, 8485 SBP-2 protocol, 86 SCSI components, 8689 USB mass storage, 8586 Storage Device Class Power Management Reference Specification, 92 STPCLK state, 10 STPGNT state, 10 Streamlined APIC (SAPIC), 7, 31, 150 STS/EN (Status and Enable bits (ACPI)) ACPI requirements, 13 defined, 150 wake-up and, 14 subpicture compositing, 96 subpicture decoders, 9697 subscriber numbers, 76 Subsystem IDs (SIDs), 39, 150 Subsystem Vendor IDs (SVIDs), 39, 150 subwoofer port connectors, 102 Super I/O devices, 27 SVIDs (Subsystem Vendor IDs), 39, 150 switches locking, 104 protected switches, 103 switching to full-duplex mode, 58 switch type IDs ISDN devices, 78 ISDN modems, 77 switch types ISDN modems, 76 serial modems, 76 Sx (system state), 150 symmetrical processors, 9, 11 symmetric multiprocessing (SMP), 150 synchronous B channel I/O, 78 synchronous HDLC framing, 78 synchronous PPP, 76, 77 System Abstraction Layer. See SAL (System Abstraction Layer) System Area Networking, 5 System Area Network Management Driver, 46 System Area Network Windows Sockets provider, 46 system-board power management, 15 system boards, 56, 155 system clocks, 9 system component requirements, 9, 3132 system devices, xi, 155. See also ATA (AT Attachment); DMA (direct memory access); FDCs (floppy disk controllers); keyboard ports and peripherals; parallel ports; PCI bridges; real-time clocks; serial ports and peripherals system diagnosis, 109 system errors, 114 system fans, 110 System Management BIOS Reference Specification, xviii, 19 system requirements, v system state (Sx), 150 system types ATM adapters, 70 simultaneously active connections, 70 system utilities, 85 T T1.413 Issue 2 specification, 73 T10/97-260r0 standard, 83 T.31 command set, 67 T.32 command set, 68 TA (Trade Association), 150 tape changers, 99100 tape drives ATA Bus Master DMA, 91 backup solutions, 106 media status notification, 83 USB drives, 8586 TAPI (Telephony Application Program Interface) ATM adapter requirements, 69 defined, 150, 155 numbers of modems supported, 64 Unimodem requirements, 6569 targeted interrupts, 31 task-offloading mechanisms, 62 TCO (total cost of ownership). See costs TCP/IP defined, 150, 155 error reporting and logging, 114 network adapter drivers, 57 offloading mechanisms, 62 TCP message segmentation, 62 tearing (DVD), 97 technical references, xiiixviii technology and future directions, viix telephone jacks, 102 telephony, 155 Telephony Application Program Interface. See TAPI (Telephony Application Program Interface) temperature ACPI and thermal controls, 6, 13 alert indicators, 110 imminence of failure alerts, 111 monitoring, viii termination, 8788 terminology conventions, xxi TERMPWR, 88 testing DVD-Video Playback, 97 manageability, 112 recommended features and, xii references and resources, xiiixiv Test Unit Ready command, 93, 100 TFTP (Trivial File Transfer Protocol) defined, 150 manageability, 11213 remote boot capabilities, 20 thermal management. See temperature TIA-592 specification, 68 TIA-602 specification, 66, 76 time discontinuity, 96 time-out alerts, 110 timers ACPI power management timer requirements, 13 Plug and Play exclusions, 26 watchdog timers, vii, 110, 111 tips bus components, 33 manageability capabilities, 112 storage components, 82 system components, 8 Token Ring adapters, 61 total cost of ownership. See costs Trade Association, 150 traffic shaping, 71 transceiver types, 5859 transfer rates (DVD), 95 translating user addresses to physical addresses, 46 Transmission Control Protocol/Internet Protocol. See TCP/IP transparency, 79 Trivial File Transfer Protocol. See TFTP (Trivial File Transfer Protocol) troubleshooting. See availability; recovery support; reliability; serviceability tuning parameters for network adapters, 59 two-way modems, 74 Tx + Rx (buffer chaining), 72 Type 1/Type 0 indicators, 37 Type 31 (BIS Entry Point), 20 U UADSL (Universal ADSL Working Group), 73, 150 UART (Universal Asynchronous Receiver/Transmitter) defined, 155 headless server support, 29 port requirements, 50 UBR (unspecified bit rate) ATM adapters, 70 defined, 150 UBR virtual circuits, 71 UHCI (Universal HCI) defined, 150 specification web site, xviii USB host controllers, 43 UHD floppy drives, 8586 U-interface, 79 u-law format, 69 Ultra-DMA (Ultra-ATA), 38, 90 unattended installation device driver installation, 48 IrDA hardware, 80 ISDN devices, 78 ISDN modem drivers, 77 undervoltage protection, 107 unframed synchronous B channel I/O, 78 Unimodem (Universal Modem Driver) defined, 64, 150, 155 ISDN devices, 75 modem controllers, 66 numbers of modems supported, 64 requirements, 6569 Unimodem Diagnostics Command Reference Specification, xviii unimplemented registers, 39 uninterruptible power supplies. See UPSs (uninterruptible power supplies) unique IDs, 2627 Universal ADSL implementation, 73 Universal ADSL Working Group (UADSL), 73, 150 Universal Asynchronous Receiver/Transmitter. See UART (Universal Asynchronous Receiver/Transmitter) Universal Disk Format Specification, xviii, 94 Universal HCI (UHCI) Specification, xviii. See also UHCI (Universal HCI) Universally Unique Identifiers (UUIDs), 19, 150 Universal Modem Driver. See Unimodem (Universal Modem Driver) Universal Serial Bus. See USB (Universal Serial Bus) Universal Serial Bus Class Definition for Printing Devices, 53 Universal Serial Bus Mass Storage Class Specification Overview, 86 Universal Serial Bus PC Legacy Compatibility Specification, 49 unsigned linear PCM format, 69 unspecified bit rate. See UBR (unspecified bit rate) updating firmware, 20 upgrading modem controllers, 66 UPSs (uninterruptible power supplies) defined, 150, 155 including in systems, 107 pass-through legacy serial ports, 30 upstream bandwidth, 71 USB (Universal Serial Bus). See also USB (Universal Serial Bus) documents and specifications booting from USB devices, 20, 2122, 23 bus requirements, 4344 color coding connectors, 102 controllers and ports, 43 defined, 150, 155 device class requirements, 44 flexibility, 4344 host controller wake-up capabilities, 14 installation, 44 ISDN modems, 77 keyboard and mouse connections, 4950 legacy removal and reductions, ix minidriver support, 49 modem wake-up events, 67 network adapters, 57, 60 power management requirements, 44 self-power, 44 storage components, 8586 USB 1.1 requirements, 43 USB CDC, 60 USB-to-printer port adapters, 53 USB (Universal Serial Bus) documents and specifications OpenHCI web site, xvii Universal Serial Bus (1.1), xviii Universal Serial Bus Class Definition for Printing Devices, 53 Universal Serial Bus Mass Storage Class Specification Overview, 86 Universal Serial Bus PC Legacy Compatibility Specification, xviii, 49 USB Class Definition for Communications Devices, 148 USB Common Class Specification, 44 USB Device Class Definition for Mass Storage Devices, xviii USB Device Class Definitions for Human Interface Devices, 21, 49 user addresses, 46 user experience, v User level protection, 19 user mode, 155 user priority objects, 63 user-tunable network adapter parameters, 59 utilities, 48 UUIDs (Universally Unique Identifiers), 19, 150 V V.110, V.250, etc. See ITU communications standards value-added retailers (VARs), 150 variable bit rate (VBR), 70, 150 VARs (value-added retailers), 150 VBR (variable bit rate), 70, 150 VCID (caller ID detection), 69 VCIs (Virtual Channel Identifiers), 6970 vendor-specific fields in SIDs, 39 Verify command, 93 VESA (Video Electronics Standards Association) defined, 156 VESA monitor timing standards, 54 VGA connectors, 102 VGA destination color keying, 97 VGA devices, 35, 38 VGA Enable bits, 35 VGA mode, 54 Video Electronics Standards Association (VESA), 54, 156 video memory tests, 18 video out ports, 102 video synchronization, 97 virtual ACPI power buttons, 14 Virtual Channel Identifiers (VCIs), 6970 virtual circuits, 71 Virtual Path Identifiers (VPIs), 6970 visual display startup requirements, 18 voice capabilities modem features, 65 voice calls, 78 voice modems, 69 voice recording and playback, 69 Voice I/O support, 69 VPIs (Virtual Path Identifiers), 6970 VT100 terminal definition, xvi W Wake-On-LAN capability, 61 wake-up events modems, 66, 67 multiprocessor wake-up, 1011 network adapters, 61 SOHO Server class, 14 standby power, 17 Waking Vector, 18 WANs (wide-area networks) defined, 150 network adapter drivers, 57 WAN communications devices, 65 wireless networking requirements, 8081 warnings. See also indicators chassis-open intrusion, 104 hard failure alert indicators, 110 imminence of failure alerts, 111 watchdog timers alerts, 110 future server developments, vii monitoring systems, 111 WBEM (Web-based Enterprise Management) defined, 150, 156 hardware initiatives, 5 information web site, xviii manageability, 112 WDM (Windows Driver Model) class requirements, 44 defined, 150, 156 power management, 5 system calls, 57 WDM HID class support, 49 WDM minidriver, 48 Web-Based Enterprise Management (WBEM) information, xviii. See also WBEM (Web-Based Enterprise Management) web sites for references and resources, xiiixviii WEP (Wired Equivalent Privacy), 81, 150 WfM (Wired for Management) defined, 150 manageability baseline requirements, 11214 Wired for Management Baseline Specification, xviii, 103 WHIIG (Windows Hardware Instrumentation Implementation Guidelines) defined, 150 manageability and, 112, 113 software management of physical components, 103 Windows Hardware Instrumentation Implementation Guidelines, xviii, 7 Whistler. See Microsoft Windows Whistler White Book format, 94 WHQL (Windows Hardware Quality Laboratory). See Microsoft Windows Hardware Quality Labs wide-area networks. See WANs (wide-area networks) wide SCSI devices, 37 Win32 API, xvii, 156 Win32 Extensions schema, xviii Win64 API, xvii Windows 2000 DDK, 46, 48 Windows 2000 Server. See Microsoft Windows 2000 Server Windows Driver Model. See WDM (Windows Driver Model) Windows Hardware Instrumentation Implementation Guidelines defined, 150 manageability and, 112, 113 software management of physical components, 103 standard, xviii, 7 Windows Hardware Quality Labs. See Microsoft Windows Hardware Quality Labs Windows Management Instrumentation (WMI) and Win32 Extensions schema, xviii. See also WMI (Windows Management Instrumentation) Windows NT. See Microsoft Windows 2000 Windows NT Removable Storage Manager Programming Documentation, xviii, 100 Windows NT Server. See Microsoft Windows 2000 Server Windows NT Server, Enterprise Edition. See Microsoft Windows 2000 Advanced Server Windows Whistler. See Microsoft Windows Whistler Winsock (Windows Sockets) ATM adapter requirements, 69 defined, 150 Winsock Direct Specification, 46. See also WSD (Winsock Direct) Wired Equivalent Privacy (WEP), 81, 150 Wired for Management Baseline Specification, xviii, 103. See also WfM (Wired for Management) wireless networking, 8081 wire-OR techniques, 36 WMI (Windows Management Instrumentation) defined, 150, 156 hardware initiatives, 5 manageability, 112 platform monitoring and, viii schema web site, xviii Windows Management Instrumentation (WMI) and Win32 Extensions schema, xviii word boundary, 59 writable configuration space bits, 38 Write and Verify command, 93 Write command, 93 WSD (Winsock Direct) connectivity, 4647 defined, 150 physically secure computer environments, 47 requirements, 4647 Winsock Direct Specification, 46 X X3T11 Private Loop Direct Attach Profile, 92 X.25, 57 Y Yellow Book format, 94 YUV offscreen surface, 96, 97 Z Zero Administration initiative, 5, 11214     page ii Hardware Design Guide  REF version Version3.0 for Microsoft Windows 2000 Server 1997-2000 Intel Corporation and Microsoft Corporation. All rights reserved. Welcome page viii page v Hardware Design Guide  REF version Version3.0 for Microsoft Windows 2000 Server 1997-2000 Intel Corporation and Microsoft Corporation. All rights reserved. Chapter 1 Overview of Server Design Issues page 7 Chapter 2 System Component Requirements page 32 Chapter 3 Bus and Device Requirements page 53 Chapter 4 Networking and Communications Requirements page 81 Hardware Design Guide  REF version Version3.0 for Microsoft Windows 2000 Server 1997-2000 Intel Corporation and Microsoft Corporation. All rights reserved. Chapter 5 Storage Device Requirements page 100 Chapter 6 Physical Design and Hardware Security Requirements page 105 Chapter 7 Reliability, Availability, and Serviceability Requirements page 115 page 116 Appendix A Server Requirements Checklist page 147 Glossary page 156 Hardware Design Guide  REF version Version3.0 for Microsoft Windows 2000 Server 1997-2000 Intel Corporation and Microsoft Corporation. All rights reserved. page 157 Hardware Design Guide  REF version Version3.0 for Microsoft Windows 2000 Server 1997-2000 Intel Corporation and Microsoft Corporation. All rights reserved. Index page 172 D  ')*RUVruvPTǾsssssesesesh%Zh%ZaJmHnHuh%Zh%ZmHnHuh%Zh%ZaJ$mHnHuh%Zh%ZCJaJmHnHuh%Zh%Z5mHnHuh%Zh%Z5aJ,mHnHuh%Zh%ZCJ,h%Zh%ZCJh%Zh%ZmHnHuh%Zh%ZOJQJh%Zh%ZCJh%Zh%ZCJ$ h%Zh%Z'D % y v`0~ *Vv+* d^ #d1$#dx1$#dd1$21$&@#$11$01$Us#Cr@k0Rh*+TUmrs "#@BCoqr=?@Khjkﵥﵥ"h%Zh%Z5CJaJmHnHuh%Zh%Z5mHnHuh%Zh%Z5aJ,mHnHuh%Zh%Z5aJmHnHuh%Zh%ZaJmHnHuh%Zh%ZmHnHuh%Zh%ZaJ$mHnHuh%Zh%ZCJaJmHnHu4,/0NQRdghs$'(DGHnqrĴĴh%Zh%ZaJmHnHu"h%Zh%Z5CJaJmHnHuh%Zh%Z5mHnHuh%Zh%Z5aJ,mHnHuh%Zh%Z5aJmHnHuh%Zh%ZaJ$mHnHuh%Zh%ZCJaJmHnHuh%Zh%ZmHnHu4(Hr>b'?Tm?b+*:=>^abm#&';>?PSTilmӵ"h%Zh%Z5CJaJmHnHuh%Zh%Z5mHnHuh%Zh%Z5aJ,mHnHuh%Zh%Z5aJmHnHuh%Zh%ZaJ$mHnHuh%Zh%ZCJaJmHnHuh%Zh%ZmHnHuh%Zh%ZaJmHnHu4:>?]abm045SWX{:>?bóӄóӄӄóӄh%Zh%ZaJ$mHnHu"h%Zh%Z5CJaJmHnHuh%Zh%Z5mHnHuh%Zh%Z5aJ,mHnHuh%Zh%Z5aJmHnHuh%Zh%ZCJaJmHnHuh%Zh%ZmHnHuh%Zh%ZaJmHnHu45X?gt~`p o!!" ###%A & F & F1$1$#dx1$*+bfgosty}~+,45MN##&:&''**I-_-t-?...L1b1o11 3 3-3m34455$5J5i666D7.8ñ⪢h%Zh%Z5mHnHuh%Zh%Z5h%Zh%ZCJh%Zh%Z6 h%Zh%Z"h%Zh%Z5CJaJmHnHuh%Zh%Z5mHnHuh%Zh%Z5aJ,mHnHuh%Zh%ZCJaJmHnHuh%Zh%ZmHnHu3%%'r))+ -t-..o1-356M89];t<<J?@4BCC5$]  & Fh^h] & Fx & F$ & F  & F^.898<=J?l?$@:@@A}BBADKDDDEE9FNF1GFGGGGGIIjJJpLLLLNNOOV!VWWtXxXXXXXXXXXeZqZuZZ{[[[[[[\\^^^^^^^*_c_r__\afah%Zh%Z5\h%Zh%ZCJh%Zh%Z6>*h%Zh%Z6h%Zh%Z5 h%Zh%Zh%Zh%ZmHnHuKCADDEE9FGJJlLNNOOO$ & F$1$If^ %$ & F$1$If$$ & F  & F1$^ & F  & F^  & Fh^h5OOO"P#PLPrPd?kdn$$If0 8 da$$ & F$1$If^ # & F$1$If?kd$$If0 8 darPsPPPPQvQd?kd.$$If0 8 da$$ & F$1$If^ # & F$1$If?kd$$If0 8 davQwQQQQ=RRd?kd$$If0 8 da$$ & F$1$If^ # & F$1$If?kd$$If0 8 daRRSbScSSSd?kd$$If0 8 da$$ & F$1$If^ # & F$1$If?kdN$$If0 8 daSSS9T:T;TUEUFUe^YN^  & Fh1$^h & F & F1$?kd|$$If0 8 da$ & F$1$If^ # & F$1$If?kd$$If0 8 daFUeUUV!VWWXXeZZW[[[["\e\$$ & F 0^$$ & F 0&dP^ $$ & F^  & F1$^  & F^ & F1$  & F1$^$ & F  & F1$^e\\\\&]^r_}`\aabbbbbbbd9eefVf$$$$ & FA & F & F1$$ & F1$ $$ & Ft]t  & F1$^ & F & F & F 0^fabbbbbbfff gjkkllllllll m.m/m5mPmQm]mxmzm{mnnLpqprru(u x8x#y?y|\||.}a}}}&~[~~~=deM/H{h%Zh%Z6mH sH h%Zh%ZmH nH uh%Zh%Z56CJOJQJh%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZCJh%Zh%Z5 h%Zh%ZCVfff7hijk|llllbW # & F$1$If\kd$$Ifd4404 daf4 < & F$1$If' & F$d%d&d'dNOPQ & F & F1$ lllll mm"m.m^SSSS & F$1$Ifkdz$$Ifd4\0 (`,04 daf4 # & F$1$If.m/m5m>mGmPmiTIII & F$1$If.$ & F 0d$IfkdL$$Ifd4\0 (`,04 daf4PmQm]mfmomxmi^^^^ & F$1$Ifkd$$Ifd4\0 (`,04 daf4xmymzmi^  & F$1$Ifkd$$Ifd4\0 (`,04 daf4zm{mnnn;4 & F1$\kdR$$Ifd4404 daf4  & F$If\kd$$Ifd4404 daf4n*n.oeoLprsuwgwwwww{ & F1$Hkd$$Ifl40   4 laf4  & F$If$ & F & F  & F1$^$$ & F  & F1$^ wx xx#yyBzCzYzZzyzzzzz{8{X{{{  & F  1$ & F  1$^  & F1$^ & F1$ & F1$ & F  & F^ & F & F & F1${{||||\||G}a}}}&~;~}~~~=  & F1$^  & F^ & F & F1$ & F & F1$ & F  1$^ & F1$Ms/H{ځ+W,j-؄`ą & F  & F^O   & F1$^ & F1$فW,5678j؄`ąۅ KΆ7;Z 3B\LOTh%Zh%ZCJOJQJ^Jh%Zh%ZCJh%Zh%ZmHsHh%Zh%Z6mHsHh%Zh%Z6mHnHuh%Zh%ZmHnHuh%Zh%Z6H*h%Zh%ZmH sH h%Zh%Z6@ h%Zh%Zh%Zh%Z65 K%Zx3B\Њ^ & F $ & F1$^  & F1$^ & F1$  & F^^6T}֎9fՏPݐ WtZ & F  & F^ & F1$  & F1$^Tt֎9ܐ̑͑ J%Zǔϔ;deƖ"\]j%c͘Ý()4A%=8Bn| 4|WX$h%Zh%Z@h%Zh%Z5h%Zh%Z6mHnHuh%Zh%ZmHnHu h%Zh%Zh%Zh%Z6J%Zǔ5leƖږ "jӗ%d͘ژ & F  & F1$^  & F 1$  & F^ & F1$()3T̛4%8ϦS & F1$  & F1$^ & F & F1$  & F1$^$ & F  & F1$^ & FO(ޫ߫ n TE|67+  & Fh1$^h & F  & F1$^ & Fd & F1$1*f~5Y12~ & F  & F1$^ & F & F1$ & Fd & Fx & F<1$^$%CZabc |<r)/ +F)*<={}<@Zb𳥳h%Zh%ZmHnHuh%Zh%Z6CJOJQJh%Zh%Z6CJOJQJh%Zh%ZCJOJQJh%Zh%Z6mHnHuh%Zh%Z5h%Zh%Z\h%Zh%Z5\h%Zh%Z6 h%Zh%Zh%Zh%ZH*6gh!8c,HzJ|fg  & F1$^ & F & F1$ghr()o3< 6 & F1$$ & Fx & F<1$^ & F & F & F$$ & F  & F1$^A & F & F$1$1$1$6?i9K*c & Fh&dP^h  & F^  & FhP^h  & Fh^hA & Fh&dP^h $ & Fh^h  & Fh^h  & Fh^h  & Fh^h  & Fh^h & F*^gh|=|}rBkdG $$If408 80 af4 # & F$1$If  & Fd1$ & FA & F$$ & F  & F1$^ & F  & Fh^h  & Fh^h }'wxy qgbbb & F  & Fd1$Bkd! $$If408 80 af4Bkd $$If408 80 af4  & F$If '0 r678xn  & Fd1$4kd $$Ifl64 lal4kd $$Ifl64 lal$If & F & F & F & F & F 8WXAqz*}vql & F & F & F1$  & Fd1$4kdz $$Ifl64 lal4kd) $$Ifl64 lal$If & F & F ^S(~05[ ;   9 & F^5  & Fh^h  & Fh^h$ & Fx & F1$$ & F  & F1$^ & F & Fb~h0KL[U    \ q z }     Q  72Fo.45h)%*%../////////00<0A0'1(1114C5p6q6666;F;<h%Zh%ZmHnHuh%Zh%Z6CJOJQJh%Zh%Z5\h%Zh%ZB*phh%Zh%Z5B*phh%Zh%Z6h%Zh%Z5 h%Zh%ZD   Q F@-.(VA~  & Fh^h  & Fh^h & F & F & F1$A & F & F1$9A$dN^5~h  t!!'"7""##$+%%& ''((-))*$* & F 9 & F1$^5  & Fh1$^h  & Fh^h & F  & Fh^h$*%++7,-.b/c////// # & F$1$If & F1$ & F1$  & Fh^h  & Fh^h  & Fh1$^h ///0 00  & F$Ifhkd $$If4\T 8<af400 0)020;0  & F$Ifhkd] $$If4\T 8<af4;0<0B0K0T0]0  & F$Ifhkd $$If4\T 8<af4]0^0_0(11 3{333!4446*79{yyyy{{5  & Fh1$^h & F  & Fd1$hkde $$If4\T 8<af49G9`99:::::;<V<<< =R={=>?@A  & Fh^h  & Fh^h & F & F & F$ & Fx  & F1$^ & F & F1$5  & Fh1$^h<<z={= >E>??IBsBCC)E*EHHIIIIIIPPSSYYZZZZ[[R^^c`h`UcVccchhhOkzkll#p(p"q/qrs$t%tu4uuu^x_xyzz{F{L{{{|}}}h%Zh%ZH*h%Zh%Z5>*h%Zh%Z>*h%Zh%Z]h%Zh%ZmHnHuh%Zh%Z5 h%Zh%Zh%Zh%Z6IAABOCCCqDD*EEFF-FPFF:Dkn3 & F & F & F & F1$ & F  & F1$^38Hs8XB|T)pq  & F$ & F & FA & F & F & F & F1$ & F & F s-.Xa} z0^  & F]  & F] & F & F & F1$  & Fh^h & F & F^g 6?"+ ?HgpNX| & F1$ & F & F$ & F & Fg12t}_|f9B< & F  & F   & F & F1$ & F & F<=Qt  & F$Ifhkd $$If4\T 8<af4 # & F$1$If 6Z~  & F$Ifhkd{$$If4\T 8<af4~  & F$Ifhkd$$If4\T 8<af4vvvv # & F$1$If & F1$ & F  & Fd1$hkd$$If4\T 8<af4*P[+-GI  /0EGT;@    i s      "   vRZov^sth%Zh%Z5H*h%Zh%Z\h%Zh%Z6mHnHuh%Zh%ZmHnHuh%Zh%Z5h%Zh%Z6CJOJQJ h%Zh%Zh%Zh%Z6C+7CO  & F$Ifhkd$$If4\T 8<af4OP\ht  & F$Ifhkd$$If4\T 8<af4  & F$Ifhkd$$If4\T 8<af4 0Fvvvv # & F$1$If & F1$ & F  & Fd1$hkd$$If4\T 8<af4 FGUy  & F$Ifhkd%$$If4\T 8<af4:  & F$Ifhkd$$If4\T 8<af4:;AJS\  & F$Ifhkd;$$If4\T 8<af4\]^$/ / 8 ~ytot & F & F & F & F & F & F  & Fd1$hkd$$If4\T 8<af4 8 0 @  < E \ n    kf#?o]^ & F1$ & F1$$ & F  & F1$^ & F & F & F & F^ Rhu'!""P"Y" & F1$$ & F  & F1$^ & F & F & F1$9lmabyz  !!+!,!x!y!!!%%Q(Y(i+o+=,.^/d/1188AAZBoBXDDFHFNHHHHKBKwP|PTTT6Uc d eh%Zh%ZB*^Jphh%Zh%Z5h%Zh%ZmHnHuh%Zh%Z6H*h%Zh%Z6 h%Zh%Zh%Zh%ZH*HY"g###c$$$)%%%%&&'4))i+q+:,..^/$ & F  & F1$^A & FA$ & F  & Fh^h & F & F & F & F1$ & F^/r1112 3Q345666678809 :]:T;<<==w?5h^h & F & F & F1$A & Fw?x???@@%A]AAAA2BB=CCCC.DLDD4E5EG[GdGJVb  & F$Ifhkd$$If4\T 8<af4bcdq|ussssss$ & F & F & F1$ & F  & Fd1$hkd$$If4\T 8<af4 ]JS & F$1$If^ % & F$1$If & F1$ & F & F1$ & F  & F^ & F  2=aBkd $$If408x af4 & F$1$If^ # & F$1$IfBkd$$If408x af4=>FSTUaZUN & F1$ & F & F1$Bkd$$If408x af4 & F$1$If^ # & F$1$IfBkds$$If408x af42Uklz  & F$Ifhkd?$$If4\T 8<af4 # & F$1$If  & F$Ifhkd$$If4\T 8<af4  & F$IfhkdU$$If4\T 8<af4"}||q % & F$1$If & F & F1$ & F  & Fd1$hkd$$If4\T 8<af4 RBkd$$If408af4 & F$1$If^ # & F$1$IfBkd]$$If408af4 & F$1$If^#,DM'5zy4RA & F & F & F & F1$ & F1$Bkd7$$If408af4R[H|W LR[T      A & F  & F^ & F1$ & F & F  v Mf ?JG^  & F & F1$ & F1$ & F$ & F  & F^ & F & F ww  !W"####K$u$$$$ % & F & F1$$$ & F  & F^ & F & F1$ & F %n%%%%%&&4(\(h((X)*9++2,;,-p...///00+1$1$1$+1h1q112#22E3N3I426b777d8888:q<<</>Q>>@>AGAA$1$A1$889 9uEE=GHGGGMJiJ@LALLLPPfRlRT)TVVVVVWWWWWWXKXXXXX.Y3Y4YJYX[m[u^^``aajahcqcgghhlipikkoopp2p3pHpJpWpzpǿ𿱿h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%Z6]h%Zh%Z;h%Zh%ZB*phh%Zh%ZmHnHu h%Zh%Zh%Zh%Z5FAAABBBD?EFFG IkItIIDJMJ4KvKKKL>L?L@LJLfL1$1$  & F hA1$fLLMM&N`NvOOOAPBPfPPQQQfRR)S2STWT`T & FA & F & F & F1$ A & F$dN & F  & F^ & F1$`TUUUeVrVVVVW # & F$IfEkd$$Ifl0| | 4 lal % & F$If & F & F1$ & F WWEWWWWWiEkd $$Ifl0| | 4 lal # & F$IfEkd $$Ifl0| | 4 lalWWXMXNX}XXiEkdI!$$Ifl0| | 4 lal # & F$IfEkd $$Ifl0| | 4 lalXX YUYVYWYYYZib[VI  & Fh(^h & F & F1$ & F1$Ekd"$$Ifl0| | 4 lal # & F$IfEkd!$$Ifl0| | 4 lalZZ{[,\-\l\u\]^^_```aajabhcqcd&fgf & FP  & Fx] & Fx  & Fx] & F & F & F  & Fh^h  & Fh(^hgffffffffTgUgggPhhhjjjlIlRll=mm & F & F & F1$ & Fx & F & F & F & FP & Fd.mmGnhnooop3pIpJpXppf  & F$Ifhkdu"$$If4\T 8<af4 # & F$1$If & F1$  & F1$^ & F & F Xpdpmpypzppppphkd#$$If4\T 8<af4  & F$Ifzpppprrs~yzƋȋՋ&+"#˓ӓ͘y˝̝GHIQSDEXY{|ƥѥp-/:;iph%Zh%ZCJh%Zh%Z5CJh%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZmHnHu h%Zh%Zh%Zh%Z5Gpppppp  & F$Ifhkd#$$If4\T 8<af4pppq]i}"@f}gPb=MpS\W-8VZ  y}~϶ϣh%Zh%Z56h%Zh%ZCJh%Zh%Z5mHnHuh%Zh%ZB*phh%Zh%Z5h%Zh%ZmHnHu h%Zh%Zh%Zh%Z6h%Zh%Z6mHnHu@}QZlpW  & Fh1$^h5 & F1$ & F & F1$ & F$ & FWDf:ey a#/#Y  & Fd1$  & F^ & F  & Fh1$^h5/e\]2=lq()01679L]$4:rv#\"&D*1WXkl  > V h%Zh%Z6mHnHuh%Zh%ZmHnHuh%Zh%Z6CJOJQJh%Zh%Z6h%Zh%Z5 h%Zh%ZL4amilhkd($$If4\T 8<af4 # & F$1$If & F & F1$ & F & F<1$^ "12>M\khkda)$$If4\T 8<af4  & F$If klr  & F$Ifhkd)$$If4\T 8<af4/o]KT|w|w & F & F1$ & F & F  & Fd1$hkdi*$$If4\T 8<af4 !-a#mvAU9{  & Fh1$^h  & FH]H & F1$ & F & F1$  & F1$^ & F  & F^U"#3>}!-j~rs} & F1$  & F1$^ & F & F & F1$1$1$-kW\  % & F$1$If  & Fh^h & F & F & F1$ & F  & F1$^ #()7CEUkdw+$$If4F4! =8     a4f4# & F 0$1$IfUkd*$$If4F4! =8     a4f4CHIX^cdEUkdo,$$If4F4! =8     a4f4Ukd+$$If4F4! =8     a4f4# & F 0$1$IfEUkdg-$$If4F4! =8     a4f4Ukd,$$If4F4! =8     a4f4# & F 0$1$IfUkd-$$If4F4! =8     a4f4# & F 0$1$IfEUkd.$$If4F4! =8     a4f4# & F 0$1$IfUkd_.$$If4F4! =8     a4f4  !(./6EUkd/$$If4F4! =8     a4f4UkdW/$$If4F4! =8     a4f4# & F 0$1$If6INOemrsEUkd0$$If4F4! =8     a4f4UkdO0$$If4F4! =8     a4f4# & F 0$1$IfsUkdG1$$If4F4! =8     a4f4# & F 0$1$IfEUkd?2$$If4F4! =8     a4f4# & F 0$1$IfUkd1$$If4F4! =8     a4f4 $NW} & F & F1$A & F & F & FUkd2$$If4F4! =8     a4f4# & F 0$1$IfWj{|j6U  & F1$^A & F$ & F & F$$ & F & F & F1$ & F & F1$ & Fzr7>b  & F1$^ & F1$  & F1$^ & F1$ & F & F1$JVjTWXl # & F$1$If & F & F1$ & F  & F1$^  & F$Ifhkd73$$If4\T 8<af4   & F$Ifhkd3$$If4\T 8<af4    % 1   & F$IfhkdM4$$If4\T 8<af41 2 3  9 B i y     h|w|w & F & F & F1$ & F  & Fd1$hkd4$$If4\T 8<af4 h ".{{{{  & F$IfhkdU5$$If4\T 8<af4 # & F$1$If & F1$  /:]b 05 !45WXmo|R"S"f"g"""""""""#i(m()) * *.*/*D*F*S*v****D.o.p0011113355668h%Zh%ZmHnHu h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6Q./;GP\  & F$Ifhkd5$$If4\T 8<af4\]cox  & F$Ifhkdk6$$If4\T 8<af4Y{tiiii # & F$1$If & F1$  & F1$^ & F  & Fd1$hkd6$$If4\T 8<af4   & F$Ifhkds7$$If4\T 8<af4#/  & F$Ifhkd8$$If4\T 8<af4/06BKW  & F$Ifhkd8$$If4\T 8<af4WXY`p Q!5l|ww|ww & F & F1$ & F & F  & Fd1$hkd 9$$If4\T 8<af4 b>>Nj !5Xn # & F$1$If & F  & F1$^ & F & F1$ & Fno}  & F$Ifhkd9$$If4\T 8<af4  & F$Ifhkd#:$$If4\T 8<af4  & F$Ifhkd:$$If4\T 8<af4@   "R"S"g"""}vkkkk # & F$1$If & F1$  & F1$^ & F  & Fd1$hkd+;$$If4\T 8<af4 """"""  & F$Ifhkd;$$If4\T 8<af4""""""  & F$IfhkdA<$$If4\T 8<af4""###&#  & F$Ifhkd<$$If4\T 8<af4&#'#(##$%C%r%%%%% &?&}&| & F & F & F  & Fd1$hkdI=$$If4\T 8<af4}&&&&&'-)))) */*E*F*rhkd=$$If4\T 8<af4 # & F$1$If & F & F & F1$ & F1$ F*T*`*i*u*v*****hkd_>$$If4\T 8<af4  & F$If ******  & F$Ifhkd>$$If4\T 8<af4***B,(-\----D.p0&1'1K1}x1$1$ & F  & Fd1$hkdg?$$If4\T 8<af4 K12U33j44U555j6k667_7k77w899 :';;=M>> & F & F1$ & F  & F1$^ & F1$88>>>>CCJ K K?K@KHKIKqKrKKKKKKK4L5L_L`LLLMMMNN]N^NNNNNNNOO1Oξξξqq쵣h%Zh%Z6CJOJQJ*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHuh%Zh%Z5h%Zh%Z6 h%Zh%Zh%Zh%ZmHnHu,>0?|??X@Y@@@@'A0AAGBC5E~EFG]GrHHI IIIAh^hh^h1$1$ & F  & F1$^IIIIJJ K@KIKrKKKK5L`LLLL  & F$IfBkd?$$If408 80 af4 # & F$1$If? & .)1$1$LLLJMMMMM^NNNqge_e_? & .  & Fd1$Bkd@$$If408 80 af4Bkd_@$$If408 80 af4  & F$If NNO2OgOOO/PgPhP|PPPPhkd+A$$If4\T 8<af4 # & F$1$If)? & . 1O2OfOgOOOOO.P/PfPgPhP{P|PPPPPPPPQ Q+QMQNQQQQQQQQQ$R%R-R.RNRORRRRRRRRRBSưưԨ}ưưư}ưưh%Zh%ZaJ$mHnHu h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHu1PPPPPPPPPQhkdA$$If4\T 8<af4  & F$If QQQQ Q)Q  & F$IfhkdAB$$If4\T 8<af4)Q*Q+QNQQQQQ%R.RORRRRRCS? & .)  & Fd1$hkdB$$If4\T 8<af4BSCSKSLSpSqSSS%T&TTTTTUU?V@VVV%W&WWWWWWW X XXXXXXXXXXXXX3Y4YwhwiwϹϹ h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHu=r s)sasjsssss9t:tMtpttthkdI$$If4\T 8<af4 # & F$1$If? & .tttttttttthkd5J$$If4\T 8<af4  & F$If tttttu  & F$IfhkdJ$$If4\T 8<af4uuuQuuuu2vLvqvrvvvvzzzz # & F$1$If? & .  & Fd1$hkd=K$$If4\T 8<af4 vvvvvv  & F$IfhkdK$$If4\T 8<af4vvvvww  & F$IfhkdSL$$If4\T 8<af4www$w0wwiwww xx\xexxxxxxxx # & F$1$If)? & .  & Fd1$hkd[M$$If4\T 8<af4 iwwwwww x xxx[x\xdxexxxxxxxxxxy)y4yWy\yyyyyyzzzzAzBzJzKzzzzͿۦۦ~~~vovovoۦۦۦ h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu+xxxyyy(y  & F$IfhkdM$$If4\T 8<af4 # & F$1$If(y)y5yAyJyVy  & F$IfhkdqN$$If4\T 8<af4VyWy]yiyry~y  & F$IfhkdN$$If4\T 8<af4~yyyyyzzBzKzzzzzzz3{? & .  & Fd1$hkdyO$$If4\T 8<af4zzzzzzzzzz2{3{;{<{B{Z{[{{{{{{{{{*|+|6|7|a|b|m|n||||||||||}}D}E}M}N}}}}}}}곥곥곇h%Zh%ZaJmHnHuh%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHuh%Zh%ZaJ$mHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHu53{<{[{{{{{+|7|b|n|||||}E}N}}}}}}~(~h~q~~~.)? & }}}}}}~~'~(~g~h~p~q~~~~~~~~~~YZbc\]ef-.nowxưưưưưưưưưưưưưh%Zh%ZaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHu:~~~Zc]f.ox#J5)? & ."#IJ45=>ghEFNO12:;{|݅ޅ LMNh%Zh%Z6h%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ95>hFO2;|ޅMNb # & F$1$If.)? & Nab̆׆#VW_`  BCKL҉Ӊۉ܉ @AIJAѿѿѿѿѿѿѿѿѿѿѿѿ*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ h%Zh%Zh%Zh%Z5h%Zh%Z6h%Zh%Z6CJOJQJ=ˆ  & F$IfhkdO$$If4\T 8<af4ˆ̆؆  & F$IfhkdP$$If4\T 8<af4 !  & F$IfhkdQ$$If4\T 8<af4!"#W` CL? & .  & Fd1$hkdQ$$If4\T 8<af4Ӊ܉ AJBKq‹ # & F$1$If).? & ABJKpq‹ ,7Z_݌ތuv~ST\]ȎɎюҎ?@Aʼ~~~ʣʣʣʣʣʼ h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJ1 +  & F$IfhkdR$$If4\T 8<af4+,8DMY  & F$IfhkdR$$If4\T 8<af4YZ`lu  & F$Ifhkd1S$$If4\T 8<af4ތvT]ɎҎ)? & .  & Fd1$hkdS$$If4\T 8<af4@AUx  & F$Ifhkd9T$$If4\T 8<af4 # & F$1$If. ATUwx͏01`aijڐې/089`aijߑ̼}̼}o}}}}h%Zh%ZaJmHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu h%Zh%Zh%Zh%Z5h%Zh%Z6h%Zh%Z6CJOJQJ+Ώڏ  & F$IfhkdT$$If4\T 8<af4   & F$IfhkdOU$$If4\T 8<af41ajې09aj? & .)  & Fd1$hkdU$$If4\T 8<af4=Fu~;Dnw“˓ WXl # & F$1$If)? & .<=EFtu}~:;CDmnvw“ʓ˓ߓ  VWXklwp h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ,ÔҔ  & F$IfhkdWV$$If4\T 8<af4   & F$IfhkdV$$If4\T 8<af4!Q|}ĕŕ˕֕ו !)*0NO͖Ζ֖ז-.67ȗɗԗ՗  MNYZDZDZDZDZDZDZDZDZDZDZh%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ h%Zh%Zh%Zh%Z54"1@O  & F$IfhkdmW$$If4\T 8<af4OPQ}ŕו!*OΖז)? & .  & Fd1$hkdW$$If4\T 8<af4.7ɗ՗ NZĘ͘XdzəGH\ # & F$1$If)? & .ZØĘ̘͘WXcdjyzșəFGH[\~ɚԚ#Uwpwpwp h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZaJmHnHuh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ,Ț  & F$IfhkduX$$If4\T 8<af4 # & F$1$IfȚɚ՚  & F$IfhkdY$$If4\T 8<af4 !  & F$IfhkdY$$If4\T 8<af4!"#V_ٛڛ'zzzz # & F$1$If? & .  & Fd1$hkdZ$$If4\T 8<af4 UV^_؛ٛڛ&(5Xc̜͜  ./DFSv͝FGph%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHuh%Zh%ZaJ$mHnHu h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJ,'(6BKW  & F$IfhkdZ$$If4\T 8<af4WXdpy  & F$Ifhkd%[$$If4\T 8<af4  & F$Ifhkd[$$If4\T 8<af4͜ /E~~~~ # & F$1$If.)  & Fd1$hkd-\$$If4\T 8<af4EFT`iu  & F$Ifhkd\$$If4\T 8<af4uv  & F$IfhkdC]$$If4\T 8<af4˝  & F$Ifhkd]$$If4\T 8<af4˝̝͝Gž0hqޟ"b? & .  & Fd1$hkdK^$$If4\T 8<af4Gž/0ghpqݟޟ!"abϠР֠QRSfgѡܡ"F۲~~~vovovo h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHuh%Zh%ZaJ$mHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu+РRSgġСxxxx  & F$Ifhkd^$$If4\T 8<af4 # & F$1$If.)? & Сѡݡ  & F$Ifhkda_$$If4\T 8<af4    & F$Ifhkd_$$If4\T 8<af4 !"Gբ~~~~ # & F$1$If.)  & Fd1$hkdi`$$If4\T 8<af4FGԢ֢49]'(=?LozƤ̤?@KLz̶̾̾̾ԡ̶̾̾̾}oԡh%Zh%ZaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHu+բ֢  & F$Ifhkd`$$If4\T 8<af4'3  & F$Ifhkda$$If4\T 8<af434:FO[  & F$Ifhkdb$$If4\T 8<af4[\](>zzzz # & F$1$If? & .  & Fd1$hkdb$$If4\T 8<af4 >?MYbn  & F$Ifhkd c$$If4\T 8<af4no{  & F$Ifhkdc$$If4\T 8<af4Ĥ  & F$Ifhkd!d$$If4\T 8<af4ĤŤƤ@L{¥?d~)? & .)$  & Fd1$hkdd$$If4\T 8<af4z{¥EcdæĦ"#+,2EFΧϧU()]^ة٩%&]^ʼʎʼʎʕʕʎʕʕ h%Zh%Zh%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJ6Ħ#,FϧU)^٩&^_s # & F$1$If?? & .)^_rsת(DE"#+,UV^_eìĬ̬ͬ&'st|}ƭǭ̼}}}̼}}}̼}*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z61Ī֪ͪ  & F$Ifhkd)e$$If4\T 8<af4֪ת  & F$Ifhkde$$If4\T 8<af4   & F$Ifhkd?f$$If4\T 8<af4 !"E#,V_Ĭͬ't? & .)  & Fd1$hkdf$$If4\T 8<af4t}ǭ JS,ox˰9Bluű.)? & ǭ IJRS+,nowxʰ˰89ABkltuıű'(UV^_βϲh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu h%Zh%Z*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ=(V_ϲز u~Ƴϳ/8 hqŵƵڵ # & F$1$If.? & ϲײز  tu}~ųƳγϳ./78  ghpqĵŵƵٵڵ! +opq̷ h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu="Fj  & F$IfhkdGg$$If4\T 8<af4 # & F$1$If  & F$Ifhkdg$$If4\T 8<af4 )  & F$Ifhkd]h$$If4\T 8<af4)*+pq # & F$1$If.  & Fd1$hkdh$$If4\T 8<af4ͷٷ  & F$Ifhkdei$$If4\T 8<af4 "  & F$Ifhkdi$$If4\T 8<af4"#)2;D  & F$Ifhkd{j$$If4\T 8<af4#(FxyzƸȸոCN߹23;<"23pqyz  QRZ[ֲֲֲ~ֲֲֲֲh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHuh%Zh%Z6CJOJQJh%Zh%Z6"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%Z5 h%Zh%Z1DEFyzǸ # & F$1$If.  & Fd1$hkdj$$If4\T 8<af4ǸȸָB  & F$Ifhkdk$$If4\T 8<af4BCOs  & F$Ifhkdl$$If4\T 8<af4¹˹Թݹ  & F$Ifhkdl$$If4\T 8<af4ݹ޹߹3<3qz )? & .  & Fd1$hkdm$$If4\T 8<af4 R[̼ռ 0ʽ6?x U^6?)? & .[˼̼Լռ  /0QRɽʽ56>?wx  TU]^56>?~h%Zh%ZH*aJh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu h%Zh%Z*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ9?2ox YbOXR[)? & .~12nowx  XYabNOWX QRZ[ʺh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu h%Zh%Zh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJ=@I+v)luMVo).? & ?@HI*+uv~()kltuLMUV\no꺬꺬꺎h%Zh%ZaJmHnHuh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu h%Zh%Zh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHu8@I YZm # & F$1$If? & .?@HI XYZlm(pq  QRkl 27^ h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu=  & F$Ifhkdm$$If4\T 8<af4  & F$Ifhkd3n$$If4\T 8<af4&  & F$Ifhkdn$$If4\T 8<af4&'(q Rlzzzz # & F$1$If? & .  & Fd1$hkd;o$$If4\T 8<af4    & F$Ifhkdo$$If4\T 8<af4  (1  & F$IfhkdQp$$If4\T 8<af4128DP\  & F$Ifhkdp$$If4\T 8<af4\]^,5|xxx # & F$1$If)? & .  & Fd1$hkdYq$$If4\T 8<af4 +,45{|&ITw|./78abjkõʜʜ~~~Üʜʜʜʜh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHu h%Zh%Z*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJ1'3<H  & F$Ifhkdq$$If4\T 8<af4 # & F$1$IfHIUajv  & F$Ifhkdor$$If4\T 8<af4vw}  & F$Ifhkdr$$If4\T 8<af4/8bkS? & .  & Fd1$hkdws$$If4\T 8<af4RS[\bz{  JKVW%&demn  ;<Gh%Zh%ZaJmHnHuh%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHu h%Zh%Z*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ8S\{ KW&en <H.)? & GH  <=yz$%|}&'-MN9:BCI꺬꺎h%Zh%ZaJ$mHnHuh%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHu h%Zh%Zh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHu8 =z%}'N:Cj U)? & .Iij  TU]^d  VW_`VW_`>?GH#$,-ƸƸƸƸƸƸƸƸƸƸƸ؛ƸƸƸ h%Zh%Z*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu=U^ W`W`?H$-EN.)? & DEMN !_`atu 6!"ijrs꺬ϔ~~~h%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu h%Zh%Zh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHu1!`auxxxx  & F$Ifhkds$$If4\T 8<af4 # & F$1$If)? & .    & F$Ifhkdt$$If4\T 8<af4  (4  & F$Ifhkdu$$If4\T 8<af4456"js V_? & .  & Fd1$hkdu$$If4\T 8<af4 UV^_)*23ST\]  TU]^ ?Jm۲}} h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu1*3T] U^ # & F$1$If).? & )2>  & F$Ifhkdv$$If4\T 8<af4>?KW`l  & F$Ifhkdv$$If4\T 8<af4lms  & F$Ifhkd/w$$If4\T 8<af4mr  fgopSTUhi 0DEtu}DZDZDZDZDZDZՋ}}}h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ h%Zh%Zh%Zh%Z51 gp)? & .  & Fd1$hkdw$$If4\T 8<af4TUi  & F$Ifhkd7x$$If4\T 8<af4 # & F$1$If.   & F$Ifhkdx$$If4\T 8<af4 (  & F$IfhkdMy$$If4\T 8<af4()*Eu~DMu~? & .)  & Fd1$hkdy$$If4\T 8<af4}~CDLMtu}~PQYZ NOWXżż꼪꼪꼪꼪꼪ż꼪꼪꼪h%Zh%ZaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu h%Zh%Z*h%Zh%Z6CJOJQJaJmHnHu8QZOX!-kl # & F$1$If.P)? & . !,-jkl05e45=>DbcưԨưư}ư}ưưh%Zh%ZaJmHnHu h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHu/  & F$IfhkdUz$$If4\T 8<af4 /  & F$Ifhkdz$$If4\T 8<af4/06ETc  & F$Ifhkdk{$$If4\T 8<af4cde5>c.P)? & .  & Fd1$hkd{$$If4\T 8<af4 ABJKabmnt JKVW]ijƸƸƸƸƸƸƸƸƸƅh%Zh%Z6h%Zh%ZaJmHnHu h%Zh%Z*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu2BKbnKWj  # & F$1$If.? & .P) 57Dju()12yz{',Vmn"ѿѿѿڍ}ѿh%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJ h%Zh%Zh%Zh%Z5h%Zh%Z6h%Zh%Z6CJOJQJ1 67EQ]i  & F$Ifhkds|$$If4\T 8<af4 # & F$1$Ifijv  & F$Ifhkd}$$If4\T 8<af4  & F$Ifhkd}$$If4\T 8<af4)2z{zzzz # & F$1$If? & .  & Fd1$hkd ~$$If4\T 8<af4   & F$Ifhkd~$$If4\T 8<af4&  & F$Ifhkd#$$If4\T 8<af4&'-9BN  & F$Ifhkd$$If4\T 8<af4NOPn~~~~ # & F$1$If.)  & Fd1$hkd+$$If4\T 8<af4   & F$Ifhkd$$If4\T 8<af4#/8D  & F$IfhkdA$$If4\T 8<af4DEKW`l  & F$IfhkdŁ$$If4\T 8<af4"EJn+,bc TU~pqw #%2U`ȲȲȲȲȲȲȲȲ֌~~~h%Zh%Z6CJOJQJh%Zh%Z6h%Zh%ZCJaJmHnHuh%Zh%ZaJ$mHnHu*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu"h%Zh%Z56CJOJQJaJh%Zh%ZaJh%Zh%Z5 h%Zh%Z1lmn,c Uq)? & .  & Fd1$hkdI$$If4\T 8<af4$%3?HT  & F$Ifhkd͂$$If4\T 8<af4 # & F$1$If TUamv  & F$Ifhkd_$$If4\T 8<af4  & F$Ifhkd$$If4\T 8<af4?@Twzzzz # & F$1$If? & .  & Fd1$hkdg$$If4\T 8<af4 >?@STvwXYabh"#)]^  FGOPۛ}ۛ}ۛh%Zh%ZCJaJmHnHuh%Zh%ZaJmHnHu h%Zh%Zh%Zh%Z5h%Zh%Z6CJOJQJh%Zh%Z6"h%Zh%Z56CJOJQJaJh%Zh%ZaJ*h%Zh%Z6CJOJQJaJmHnHuh%Zh%ZaJmHnHu1  & F$Ifhkd$$If4\T 8<af4  & F$Ifhkd}$$If4\T 8<af4  & F$Ifhkd$$If4\T 8<af4Yb#^ G)? & .  & Fd1$hkd$$If4\T 8<af4GPQR[EaS3Ki71$K1$#1$Q&1$? & EK`e:;FGSW37KQhl5;MSad*+1NQps h%Zh%Z56h%Zh%Z]h%Zh%Z6h%Zh%Z5 h%Zh%ZU6Ma+Np &IcDV71$ &)IOcg DEIUYruEFPSmruAHbf/1:>sw   ( + h%Zh%Z6h%Zh%Z56 h%Zh%Zh%Zh%Z5UVrPmAc/:s 71$ ! k      " O p        - U p       C e  771$+ 7 j k r             " % O R p s               , - 1 4 U X p s            & B F e i                = @ c h%Zh%Z5\h%Zh%Z5H*h%Zh%Z5]h%Zh%Z5 h%Zh%Zh%Zh%ZmHnHuN     = c      4Vz=V471$c j           "38UYz~=@V`4;^e~ ,3?C]`mp 29LNR_dh%Zh%Z56h%Zh%Z5 h%Zh%Zh%Zh%Z5mHnHuV4_~-@]m 2M_v#:m71$duz#+9>mt7;\_wz (-GJaj=Av9>8A!!x!!$")"""h%Zh%Z6h%Zh%Z5mHnHuh%Zh%Z5 h%Zh%ZV7\w (Gb();=9K71$968!x!""$""#$$:&&m'C(E(()**+,-o..N//7K71$"##$$$$$$:&=&&&& 'm'p'E(N((())* ** + ++++,,--o.u...N/Q/////H0T0O1^1N2^222222U3[33344m4w45566n7{7(8988999::4;9;h%Zh%Z@h%Zh%Z6h%Zh%ZmHnHuh%Zh%ZOJQJh%Zh%Z5 h%Zh%ZO//H0O1N2222U3344k4m45n7(889:4;=?8@AABBBCC71$K9;===??8@C@E@AABBBBECQCIDZD EEE+EAEEEFFGGGHH^HdHNISI_J`JlJ9K>KKKKKL~MMMMMMM1N>NOO4PFPIQLQQQRRRRSSh%Zh%Z@h%Zh%ZCJh%Zh%ZmHnHuh%Zh%Z6h%Zh%Z5mHnHuh%Zh%Z5h%Zh%ZCJOJQJ h%Zh%ZECCECID E+EEEFG^HLINI`J7K9KKKM1NO4PGQIQQQRSTT771$KST UDVJVkVvV!W-WX+XXX%Y3Y7YDYFYYYZZ[[h\s\\\I]S]]]__>_I____`o`u` a a aambrbVdadddee[f}f1g=gggggiiiijkktkGlJlpppp$q'qqqh%Zh%Z6]h%Zh%Z5\h%Zh%ZmHnHuh%Zh%Z6h%Zh%Z5 h%Zh%ZOTDV!WXX%YYZZ[h\\\I]]__m`o` a ambde[f1ggggK71$ggggggh+h?hhhshhhhhi/iOitiiiiiij;jTjtj43 Q&+D1$tjjjjjkxkkkkkkkkl3lTlzlllllm2mDm`mmm44$3$81$^3mmmmn"n8nVnwnnnnno1oRoloooooop$p;pOphpppZq34Zqpqqqqqqr?r~rrrrrsHsnssssstHttttt#u0u43$3qs@sHsjstu vvvvxxyy2y^yOzzzzzz~{{}~ƂɂTU /8@ijߎ'\ݘ M$ݞˡA Q(+Fqv~Φ58mh%Zh%ZH*h%Zh%Z6] h%Zh%Z[0uKuuuu9vevvvww*wAwQwkwwwwwww x2xPxlxxxxxx34xx2ybyyyyyyyz"zUlā81$^347JZg}ς6OmӃ0YjƄ!6436Rk΅ #C`|ۆ#0Idvć34&6Skˆ߈ _l؉5Lbۊ43:S[ԋ6Gh+CWu؍432GaŽގ  .ANZn@GY81$^34Yn~Ґ @`ّ'fzŒ7N34N]rǓޓ$ERyʔҔ;F\rՕ34&H]i{Ɩٖ>Sjٗ'4Kp34ݘ*MEdz $FnǛ(Ek43D^Ý՝5fxÞ*R}43&GZgxŠؠ?SjˡB^nt¢3$4381$^¢9Ppǣأ/QȤܤ:Fǥ!C43CRjӦ %/A^uۧ8gۨ4$3$43!9Oc|ߩ+;Sa{ª٪[ԫ.=X34mp-ЮE\_Ѳ̳%TǾ-jm&Q/ Cl)1DG0:;Z[|)LO~h%Zh%Z6H*]h%Zh%ZH* h%Zh%Zh%Zh%Z6]WX٬ 6BThҭ1dvѮS`n43ׯ 7So!6Xtӱ#/F[}۲  43 >Rp̳2Oh1Y~ʵ81$^34)Nbvض:Yj߷0BWjٸ3$43ٸ%Uf|̹<Mxߺ2Kzƻӻ +V43Vxټ3WtŽ!2>WpǾ6On34Կ+^z 3O`tDp340M\~8M&Rj|A[\34\^)Ab'=Yjy4381$^"/Ol=\|&Eev43,2Jew =`x;Mp4$3$43 3CWr  #3Hv Cq481$^3W{E^ 'G_81$^34)Np?Ph5Zl|4$3$43;av 1@Qanx ,Ggt439Yp';On!@S[q4381$^ "I^} <Yv%D\lx34&F\t>^u&BY|34 !CGfv.>f$-Ag43!+Sn.>\u.;Ns~34,u9Jc,Uh4$3$34 6HY&6C]p7O734sv%(*-fnhk}KN:Wt    = _ 8;Y $Iv K  Q"y"%%&7&(h%Zh%ZH*h%Zh%Z6] h%Zh%Z[7ImOv $/'}7it43;Vm *M^-?Q]jz346Pd&7J_{,@Uj34 <_n{8_|5Hb34$3$4b:\iv#7DUcq4$43.:;=IZu0Dbqrt81$^43&<ANj1Pb,Fct34t$Xv#+L_v7Kgt43$1Ie - E b        81$^34 : M d       5 G Y        : O         34 = i y      7Kw ?Qo '}43 .Hg_9Mt6]43 )AXev #A\t>[t34.Bi2Qi5Qu34'EY'F`x;Tm34%I8K1 L W s      !!L!]!!4$3$34!!!!!"!">"Q"z""""""""#)#<#h########$,$F$34F$]$z$$$$$$%#%A%_%h%%%%%%&&J&j&&&&&&&&'H'34H'q''''''(,(D(Z(y((((((( )%)7)m)))))*2*[**34(([*}*++N,t,Z2222 3344667759t9999:d:l:m::h;;<<=i=AA7B:BBBkFFFFFFFG*GWG[G{GGGGHHHqItIIIII7J:JNNOOO!P%PEPIPzPQQRRRRVV:VBVCVaVEXHXh%Zh%Z6] h%Zh%Zh%Zh%ZH*[******+1+2+4+T+`+}+++,',-,N,~,,,,,--0-H-Y-81$^43Y-n------.!.F._.y.....//2/B/W/i/////0.0E0S034S0d0s0000011+1@1U1e1}1111112242F2Z222x33333433344*474W4~4444565`5y555566;6H6o6p6r666681$^43667D7Y7x777778 818S8`8z8888889(959z999,:Q::43:::::;*;H;h;; <<#<:<P<a<<<<=x=====$>P>k>>>34>>>>>??"?:?J?r?????@ @7@T@s@@@@@@@AAXA43$81$^3XAwAABB.BHBWBmBBBBBB C C6CTCxCCCCCCD7DTDvDDD43DDDD E!E-E9EJEaEmEEEEEEF!FJFkFFFF*G[GGGG HH34HAHPHfHsHHHHHH II2INIIII$JTJhJJJJJJJ K.K9K4$3$439KLK`KKKKKK$L7LTLZLpLLLLLLLM2MSMqMMMMNpCÍčې  padӖ ٘ܘh%Zh%Z6] h%Zh%Z^%[C[d[}[[[[[ \5\B\T\c\n\\\\\]A]U]y]]]]]]^3^`^43`^a^c^^^^^^_=_n______`I`V`y`````` aaQaaa43$81$^3aauaaaab0bJb[bxbbbbb c%c6cFcccycccccccd'dHdad34adtdddd1eHeQe^eeeeeeefEf[foffffffg#gnNn]nonnnnnnnnn o)o;oQocoooxoooo43oooo p"p7pVpcpvppppq)q@qcqqqqqqq"r5rHrZrwrrr34rrrrrs0sBsSspsssssstDtjtttttu"u7ueuuuuu34uuuvv(vBvevvvvvvww.wNwgwwwwwx)xCxcxuxxxx34xxy2yLyby{yyyyy z"z-zGzmzwzzzzzz%{T{{{{{{|34||U|[|f||||||||}0}=}Q}Y}v}}}}}}}~G~f~~~4$3$34~~~~0B}'_%FvɁہ&?]x4$3$43xӂ2CXr̓(Bdy˄܄@hn34n}…ׅ![jц "2O]pŇ%=4$3$34=WkĈֈ%;K`y׉'ATkΊ34+C̋ &A\s֌(@brٍ34ٍ:WoƎ!CZkr!2Xmnp81$^4$3$3Ց*@^pΒ #Bkrۓ +ShwӔ43Ӕߔ7H[yՕ?Lbۖ;Xw|43Ɨۗ-AZs?Ι '(*Xʚ81$^34ܘPSJFI}Ϟמߞ=@y|ӟןUC]e!-\b &)ѯ  #İ9Jgj;>V:=Ǵ1h%Zh%Z6] h%Zh%Z^1>\u͛'>[˜Qmɝ34$3$4}%cןYxà 5ZqΡ+EWu¢43¢Ң1Jcǣӣ,Ce-b(BQk34զ֦ئ .Oqۧ@Mǫ٨(=Wvܩ481$^3ܩ*:KlȪɪ˪"7M_qӫ5X4$3$81$^43Xyͬ:MhЭNĮѮ5xѯ34?U߰ )9R"Re/Vֳ(Ysݴb431>F/tXu!"$%()*/0234LMZ[gh)*67ڹ۹ܹGHINOQRST h%ZCJ h%ZCJh%ZmHnHuh%Z@CJh%Zjh%ZUh%Zh%Z6] h%Zh%ZNb}ϵ/{ж DXyz|̷81$^43 !#$&'456ݸ޸߸,1$,1$^1$-1$381$^[STUABwxy-1$1$-$$1$  & F1$^ -$$ & F1$^,1$^ 1$]^˺̺jklqruvwxûĻŻƻ$%()WXY^_bcdeopqvwz{|}&',-01JKXYefh%Z@CJ h%ZCJ h%ZCJh%ZmHnHuh%Zjh%ZUTyŻƻǻ*+,def|}~Լ%&234 1$]^ -$1$^a$,1$^1$^- 08"1$1$-1$  & F1$^ - & F1$^4۽ܽݽ޽1$^- 08"1$,1$^  h%Zh%Z h%ZCJ h%ZCJh%ZmHnHuh%Zjh%ZU D 0 000*P`/P`/PBP/ =! "# $D%h A 0002P`/P`/PBP/ =! "# $D%h ?xhxhxhxhxhxhxhxhx?o??o??o? 000P`/P`/P8$BP/ =! "# $D%h <hxhxhxhxhxhxhxhxhxooo   00P`/P`/P8$BP/ =! "# $D%h > 00P`/P`/PBP/ =! "# $D%h <hxhxhxhxhxhxhxhxhxooo   00P`/P`/P8$BP/ =! "# $D%h <xhxhxhxhxhxhxhxhx?o??o??o? 00P`/P`/P8$BP/ =! "# $D%h > 00P`/P`/PBP/ =! "# $D%h <hxhxhxhxhxhxhxhxhxooo   00P`/P`/P8$BP/ =! "# $D%h > 00P`/P`/PBP/ =! "# $D%h B 00:P`/P`/PBP/ =!"# $D%h P B 00:P`/P`/PBP/ =!"# $D%h P B 0 0P`/P`/PBP/ =!"# $D%h P l$$If!vh5 5d#v #vd:V 5 5d/ 4a^$$If!vh5 5d#v #vd:V 5 5d4a^$$If!vh5 5d#v #vd:V 5 5d4a^$$If!vh5 5d#v #vd:V 5 5d4a^$$If!vh5 5d#v #vd:V 5 5d4a^$$If!vh5 5d#v #vd:V 5 5d4a^$$If!vh5 5d#v #vd:V 5 5d4al$$If!vh5 5d#v #vd:V 5 5d/ 4a^$$If!vh5 5d#v #vd:V 5 5d4al$$If!vh5 5d#v #vd:V 5 5d/ 4a$$If!vh54#v4:V d405444 daf4$$If!vh5(55`5,#v(#v#v`#v,:V d405(55`5,44 daf4$$If!vh5(55`5,#v(#v#v`#v,:V d405(55`5,44 daf4$$If!vh5(55`5,#v(#v#v`#v,:V d405(55`5,44 daf4$$If!vh5(55`5,#v(#v#v`#v,:V d405(55`5,44 daf4$$If!vh54#v4:V d405444 daf4$$If!vh54#v4:V d405444 daf4c$$If!vh5 5 #v #v :V l45 5 4f4r$$If!vh50 5#v0 #v:V 450 5/ 4af4d$$If!vh50 5#v0 #v:V 450 54af4d$$If!vh50 5#v0 #v:V 450 54af4O$$Ifl!vh5#v:V l654alO$$Ifl!vh5#v:V l654alO$$Ifl!vh5#v:V l654alO$$Ifl!vh5#v:V l654al$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4r$$Ifp!vh5 5(#v #v(:V 45 5(/ 4apf4r$$Ifp!vh5 5(#v #v(:V 45 5(/ 4apf4d$$Ifp!vh5 5(#v #v(:V 45 5(4apf4d$$Ifp!vh5 5(#v #v(:V 45 5(4apf4d$$Ifp!vh5 5(#v #v(:V 45 5(4apf4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4r$$If!vh5x5 #vx#v :V 45x5 / 4af4d$$If!vh5x5 #vx#v :V 45x5 4af4d$$If!vh5x5 #vx#v :V 45x5 4af4d$$If!vh5x5 #vx#v :V 45x5 4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4r$$If!vh55#v#v:V 455/ 4af4d$$If!vh55#v#v:V 4554af4d$$If!vh55#v#v:V 4554af4p$$Ifl!vh5| 5#v| #v:V l5| 5/ 4alp$$Ifl!vh5| 5#v| #v:V l5| 5/ 4alb$$Ifl!vh5| 5#v| #v:V l5| 54alb$$Ifl!vh5| 5#v| #v:V l5| 54alb$$Ifl!vh5| 5#v| #v:V l5| 54alb$$Ifl!vh5| 5#v| #v:V l5| 54alb$$Ifl!vh5| 5#v| #v:V l5| 54al$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If4!vh55 5#v#v #v:V 455 5/ 4a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4z$$If4!vh55 5#v#v #v:V 455 54a4f4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4r$$If!vh50 5#v0 #v:V 450 5/ 4af4d$$If!vh50 5#v0 #v:V 450 54af4d$$If!vh50 5#v0 #v:V 450 54af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555</ 4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4$$If!vh5555<#v#v#v<:V 4555<4af4QL@L Normal1$5$7$8$9DH$_HmH sH tH h@h Heading 1,Head 1,H1,h1$dHP@&^CJ$b@b Heading 2,H2,chn,h2$d<@&^CJX@X Heading 3,H3,h3$ X(@&CJX@RX Heading 4,H4,h4,4$$x(@&5CJ\@R\ Heading 5,H5,h5$$ hx(@&5CJb@b Heading 6,H6,h6!$dx(1$@&^5CJR@R Heading 7,H7$$(@&6CJOJQJ8a8 Heading 8,H8@&@ @ Heading 9,H9,H91 @&DAD Default Paragraph FontVi@V  Table Normal :V 44 la (k@(No List O INormal1,n,P,N,normal1,body text,Blockquote,Nnorma,body page break,Nnormal$ hd5$7$8$9DH$CJ_HmH sH tH HOH Ln1,n1 P^`CJ\O"\ Tt&$d$<1$5$7$8$9DH$5CJ_HmH sH tH hOh Tr5$$d$d1$5$7$8$9DH$Na$CJ_HmH sH tH BO2B Th$d$<^5CJFOBF Tp# 0d$<^CJpOp Le,e,list end,le!$d`1$5$7$8$9DH$a$CJ _HmH sH tH FbF d&$$d-D 1$M CJfOf Ch4$d@&`#$+D 1$5$7$8$9DH$CJ,_HmH sH tH O Ex,code,CodeS 5 $ 0 <HT`d$1$5$7$8$9DH$CJOJQJ_HmH sH tH O LLb1,b1,lb1,list bullet,bullet,bulleted list 1,List Bullet 1,List Bullet 1lb1 & FP1$CJlOl Mp-$d$&/1$5$7$8$9DH$6CJOJQJ_HmH sH tH TOT Lp1,p1,normal indenth^h`dOrd Cn*$d1$5$7$8$9DH$^;@xCJ_HmH sH tH O header rule@d2$d1$5$7$8$9DH$N]^CJ _HmH sH tH vOv Term1,DT,Question&$ d1$5$7$8$9DH$CJ_HmH sH tH XOX Def1,VAR,DL,DFN,AnswerP^CJ>A> Tpi 0^`2AB2 Tpr!$ 0a$FA"F Tf#" 0td8(^`tCJ6OA26 Tpf#$$d^hh Art3$ 0P1$5$7$8$9DH$^CJ_HmH sH tH *O12* Thf %^6b6 Tpif& ^LL index'$dP<B*CJOJQJphbb Cap*( 0d$1$5$7$8$9DH$5CJ_HmH sH tH 4@4  TOC 3,toc3)CJ 8@8  TOC 1,toc1 * : 8@8  TOC 2,toc2 +^d @d Footer,f,Footer First,d^6CJOJQJR@R Header,h- 0d.^5CJOJQJl@l TOC 4,toc4 .$ h0d8x56CJOJQJmHnHuvv TOC 5,toc5)/ 0 (hd8P(1$^h56CJOJQJmHnHu\O\ Bt*0$d 1$5$7$8$9DH$^CJ8_HmH sH tH `O` Prod1$d1$5$7$8$9DH$5CJ0OJQJ_HmH sH tH DOD MS Corp 2&@#$5CJOJQJf @2f Index 1,i1,1,Main!3 $td$*$1$^`tCJKHV @1BV Index 2,i2,2,Sub 14 $h*$^h`2OR2 Lb2,lb2 5^lrl Gt-6$d& +D׀/1$5$7$8$9DH$5CJOJQJ_HmH sH tH (O1r( Gd 7$PnOn Ih,ahead$8$(1$5$7$8$9DH$^5CJOJQJ_HmH sH tH *O* Lp2 9^.. Term2 :^,, Def2 ;0^0bOb Head 4,head4<$1$5$7$8$9DH$5CJ_HmH sH tH 88 TOC 7=56CJOJQJZZTOC 6>$ :h(^h5CJOJQJmHnHuJ@J TOC 8?x6CJOJQJ_HmH sH tH .. TOC 9 @@^@VOV note'A$$d&dNP CJOJQJ>'!> Comment ReferenceCJ424  Comment TextCd aBd Index 3,i3,3,Sub 2"D$Xd8@& ^X`CJBRB edE-DM 5B*phjbja*F$-D 5$7$8$9DH$M #5B*_HmHnHphsH tH uPrP Tpib!G 1$^` CJOJQJBqB Tpi2H hXX^X`,X, Emphasis6 sh4fJ & F>TTf5fOf Ltr&K$dP(1$5$7$8$9DH$5CJOJQJ_HmH sH tH @V@ FollowedHyperlink>*B* ::8@CJOJQJkHmHnHu,, def N & F1$2O2 term O & F1$66U6 Hyperlink >*B*phOhfB?x]] F    H    B     Izzzz z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z !z "z #z $z %z &z 'z (z )z *z +z ,z -z .z /z 0z 1z 2z 3z 4z 5z6 (39>F O}Xajsyǀ)$OKN9& .8%-/U7p?J8U]^gqoNy-qáj`ƼV7Mf $!C+4<E2OiYaf1 v  2 )-' [#gI[ *!V"#$@%Z&'()I*3+q,-./0C1z2345w67a8G9:b;<=/>j?@ABCDbEFnG-HD%yv` 0 ~  `po r!!# %t%&&o)-+-.M01]3t44J784:;;A<<==9>?BBlDFFGGGGG"H#HLHrHsHHHHIvIwIIII=JJJKbKcKKKKK9L:L;LMEMFMeMMN!NOOPPeRRWSSSS"TeTTTT&UVrW}X\YaZbZZZZZ\9]]^V^^^7`abc|dddddddd ee"e.e/e5e>eGePeQe]efeoexeyeze{efff*f.gegLhjkmogooooop pp#qqBrCrYrZryrrrrrs8sXsssstttt\ttGuauuu&v;v}vvvw=wwwwMxsxx/yHy{yyy+zWzzz{,{j{{{-|||}`}}}} ~K~~%Zx3B\Ђ-Ճ(\z҄9_Յv3}͈ <K([3HKǎ$%5OYܓZK^yƟ:uN2@2zk\]7Q!,-W P=[÷ķAWXԺ۽&)G^;Rnp=*)NO$Yb3\e"_qPP78cM0 MV2B\]^>}~gP/?yNV[!aw,(l% 5 f S T  N |  g<M]C Q&/S: J K!!]"$$%%%%%%&&&'&0&9&:&F&O&X&a&b&h&q&z&&&&N''2))) *G**+,P--/m///00111 2(2|222/3x3345-6778u99:::P;;C<D<S<v<<b=c=F>>>>U@@7BCEBGhHHKLQMNNPVQQQQTRS7U8UUUVeWW5Y|YY[\1]H^`_q``ubbccdteIf^gggrhhiKjCk9l:l}lmm nNnnnoVpkqlq#ttt}twu,vZw[wwNy-z {K|L|}j}s}  k-o҃#p͈݈xߊJYE\ Ilqjxá֡o"+Oݦqj <FfбOdв!`8jƷĹ͹ YƼ^nܽ^~hz9BO3D6ST~4FV/\eHQ/en.t7~"+WX 8_h#%.bcw+,8\ ,BCQ]iuvC3Vlm{<`agpyJU U^Vfbk6@ I          '0$;xM>?vO" Z !!`"%%%'''(1)w)*C+:,,,--)..V/000z12234555566K777 8 8X88c99::T:r::Z;[;;===b>t>>??@??@ABCC/DDEFYFFFFFNGGHIJKYLVMfMMbNrNNOkPQQhRiRRS0U@UVW?XYZZZZ[ [ [[[[["[#[/[3[4[5[]^~___```a{aaaMZ\)+ӯ  CEy:d:t;:܎:܎:x:) :):):):):):):@t;0PS0PS0l0 0؎0)0܎00lA0PS0PS0lA0PS0PS0PS00l0l00 0 0 0 k0 k0 k0 k0L0j0 0 k0؎0l0l0l0 k0 k0 0l0lA0PS0PS0lA0PS #d#$ )d# )d# )d# )d# )d# )d#`A )d#`A )d# )d# 0܎0PS0 k0܎0lA0PS00PS0 k0PS0 k0PS0 k0PS0 k0 k0|;0#0#0#0#0܎0PS00PS0)0 0 k0 0܎0PS0؎0؎0܎000PS0؎0l0l0܎0PS0PS0PS0̂ 0PSl,e,ea)XXcX$eaXXXcXXaXXXcXXaXXXcXXl܎܎lPS|50܎0lA0PS00PS0PS0PS0PS0PS PS PS 0܎00#0XS0PS0 k0PS0 k0܎0#0XS0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0܎0#0XS0PS0 k0PS0 k0PS0 k0PS0PS0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0 k0PS0PS0 k0܎0lA0PS0PS@t;0lA0PS0PS0L0 0 0)0l0܎0PS0PS0l0)0)0܎0PS0l0؎0؎0l0)0܎0lA0PS0j0 k0,A0 k0 k0j0܎0PS0l0 0)0 0܎0lA0PS0PS0PS0l0l0)0؎0؎0؎0 0܎0PS0lA0PS0PS0PS0؎0)0 0؎0l0܎0PS0PS0PS0lA0PS0)0؎0܎0PS00PS0PS00PS0PS0PS0PS00PS0PS0PS0PS0PS:PS@t;:PS:؎:؎:؎:܎:4M :PS:,e:PS:PS:lA:PS: :,e:PS:,e:,e: k: k: k:H;:PS:PS:PS:PS::PS:,e: k: k: k:܎:lA:PS:4M :,e:)0 XX$e0 PSPS 0 PSPS :):PS:PS:PS:,e:PS:PS:PS#:PS:,e;PS;PS:):PS:,e;PS;PS:):PS:,e:PS:PS:,e:PS:PS:lA:PS:,e:PS:PS:PS:PS:,e: k:l: : : k:_: k:l:#: k:,e: k:):_:: :l: k: #: k: k:܎: : :,e:PS:PS:,e: k:,e: k: k : k: k#: k:,e: k#: k: k:): : k:)#: k: k: :܎: k:,e: k#: k: k:,e: k: k: k:܎:,e)XX=X$ePSPSPS=PSPSPSPS=PSPSPSPS=PS:):PS:PS: : k:؎:؎:؎:l: k:d:l: k: k:؎:l:):؎:؎:܎#:PS:lA:PS:,e:PS:PS:PS:,e: k: k:,e: k:,e: k: k:,e: k: k:,e: k:l:l:܎#:PS:؎:):܎:PS:,e:PS:,e: k:,e: k: k: k: k: k:,e : k: k: k: k:,e: k: k: k:܎#:PS:j: :܎:,e:PS:PS: :,e: k:,e: k: k: k: k: k: k: k:,e: k:,e: k:,e: k:,e: k:4M :,e:PS:PS:,e: k: : k: :܎:,e: k:܎:lA:PS:,e:PS:PS:l: :܎:A:,e:PS:PS:): :܎:PS:j:):): :܎:PS:,e:PS:PS#:PS:lA:PS: k:PS:PS:PS:PS: k: k: k:,e:PS:PS:,e: k#: k:,e: k::,e: k:,e:PS:PS :PS:,e: k:,e: k: k:,e: k:,e:PS:PS:PS:PS:PS#:PS:,e:PS:PS:PS:lA:,e:PS:PS:PS:,e:PS:PS:,e: k:,e: k:܎:,e:PS:PS:PS:PS:(_:PS:PS:,e:PS0PS@t;0PS0l0؎0l0 0l0lA0PS0,e0PS0PS0,e0PS0PS0PS0PS0PS0,e0PS0PS0PS0PS0,e0PS0PS0PS0PS#0PS0,e0PS0PS0PS0PS#0PS0t0,e0PS0PS0PS0,e0PS0PS0)0؎0܎ 0PS 0PS0PS0l0l0܎0PS0 0l0 k0 k0܎0,e0PS0PS0PS0,e0PS0PS0,e0PS0PS0,e0PS0PS#0PS0,e0PS0PS0,e0PS0PS#0PS0,e0PS0PS0,e0PS0PS0,e0PS0PS0PS0PS0PS0,e0PS0PS0PS0؎0 0܎0PS0,e0PS0PS0,e0PS0PS0PS0PS0PS0,e0PS0PS#0PS0,e0PS0PS0,e)XX=X$ePSPSPS=PS PSPSPS=PS PSPSPS=PS0)0PS0,e)XX=X$ePSPSPS=PSPSPSPS=PSPSPSPS=PS0)0PS0PS0PS0,e)XX=X$ePSPSPS=PS PSPSPS=PS PSPSPS=PS0)0PS0PS0)0l0܎0,e0PS0PS0,e0PS0PS#0PS0,e0PS0PS0PS0,e0PS0PS0,e0PS0PS0PS0PS0,e0PS0PS0l0l0܎0,e0PS0PS0,e0PS0PS0,e0PS0PS0,e0PS0PS0lA0PS0e0PS0PS0PS0j0l0 0܎0,e0PS0PS0,e0PS0PS0,e0PS0PS0PS0,e0PS0PS0l0 k0PS0 k0 k0 0PS0850lA0PS0$G0 k0PS0PS0PS0,e0 k0l0 0)0܎0,e0 k0,e0 k0 k0 k0,e0 k0 k0,e0 k0,e0 k0܎0,e0PS0PS0PS0؎0؎0؎0l0܎0PS0l0)0l0l0܎0PS0؎0l0)0܎0PS0,e0PS0PS0؎0l0 k0܎0PS0 0 0 0 #0 k0)0)0l0؎0؎0܎0,e0PS0PS0,e0PS0PS0PS0PS0PS0 #0 k0)#0 k0 0)0)0l0 k0܎0PS0 0 #0 k0 0 k0j0 k #'#$ )') )') )') )')DY0܎ 0 k0 k0 k0 k#0 k0܎0,e0PS0PS0؎0l0,e: :,:X:X:X0 0,0 0,0X0X0 0,: :,0 0,D%yv` 0 ~   * V v  U s #Cr@k0Rh(Hr>b'?Tm?b5X?gt~`po r!!# %t%&&o)-+-.M01]3t44J784:;;A<<==9>?BBlDFFGGGGG"H#HLHrHsHHHHIvIwIIII=JJJKbKcKKKKK9L:L;LMEMFMeMMN!NOOPPeRRWSSSS"TeTTTT&UVrW}X\YaZbZZZZZ\9]]^V^^^7`abc|dddddddd ee"e.e/e5e>eGePeQe]efeoexeyeze{efff*f.gegLhjkmogooooop pp#qqBrCrYrZryrrrrrs8sXsssstttt\ttGuauuu&v;v}vvvw=wwwwMxsxx/yHy{yyy+zWzzz{,{j{{{-|||}`}}}} ~K~~%Zx3B\Ђ-Ճ(\z҄9_Յv(3}͈ <K([3HKǎ$%5NOYzܓZK^yƟ:uN2@2zk\]7Q!,-W P=[÷ķAWXԺ۽&)G^;Rnp=*)NO$Yb3\e"_qPP78cM0 MV2B\]^>}~gP/?yNV[!aw,(l% 5 f S T  N |  g<M]C Q&/S: J K!!]"$$%%%%%%&&&'&0&9&:&F&O&X&a&b&h&q&z&&&&N''2))) *G**+,P--/m///00111 2(2|222/3x3345-6778u99:::P;;C<D<S<v<<b=c=F>>>>U@@7BCEBGhHHKLQMNNPVQQQQTRS7U8UUUVeWW5Y|YY[\1]]H^`_q``ubbccdteIf^gggrhhiKjCk9l:l}lmm nNnnnpooVpkqlq#ttt}twu,vZw[wwNy-z {K|L|}j}s}  k-o҃#p͈݈xߊJYE\ Ilqjxá֡o"+Oݦqj <EFfбOdв!`8jƷĹ͹ YƼ^nܽ^~hz9BO3D6ST~4FV/\eHQ/en.t7~"+WX 8_h#%.bcw+,8\ ,BCQ]iuvC3Vlm{<`agpyJU U^Vfbk6@ I e          '0$;xM>?vO" Z !!`"%%%'''(1)w)*C+:,,,--)..V/000z12234555566K777 8 8X88c99::T:r::Z;[;;===b>t>>??@??@ABCC/DDEFYFFFFFNGGHIJKYLVMfMMbNrNNOkPQQhRiRRS0U@UVW?XYZZZZ[ [ [[[[["[#[/[3[4[5[]^~___```a{aaa bikkk#mnnoSrrsttuuMmbkg7QRhLM|}  56]^23cdyzIR4jz.../1<<=F??hFFFGGGHHOILL@MAMMMNNsNtN O O{O|OofpfffffffbhrhhZiiKLst>? ]^ˬWX78NOno/0TUtu/J!\{,-WX$%TU'(UV}~$%LMk l       8m89[;;BB C!CCCFFGG-G.GOGPGUUjVkVVVWWWWWWWW X!XXXYYYYYYjjjjkk,k-kllmm7m8mbmcmooNoOo|o}ooo||||} }G}H}!"QR:;ˊ̊ABuvGHMN}~ӒԒklɓʓƗǗFG+,YZdešÚҠӠ$%FG9:-.OPHIjkhi$%LM/0WX>?no23Z[45de,-NOUV\]LMtu  <=jkJKz{9:AMZ[\)*+үӯ   CDEyzي0ي0ي0ي0ي0ي0ي0ي0ي0ي0ي0ي0ي0#00*0*0*0*0*0*0+0+0+0*0+0+0*0*0*0*0*0*0*0+0+0+0*0*0*0*0*0*0*0*0*0*0*0*0*0*0*0*0*0*0+0+0+0+0+0*0*0*0*0*0*0*0*0*0+0+0*0*0+0+0*0*0*0*0*0+0+0+0+0*0*0+0+0*0*0*0*0*0+0ي00000 0 0 0 0 0 A0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 50 50 50 50 0 0 0 0 0 0 0 0 0 %0 0 0 #0 0 0 #0 0 0 #0 0 0 #0 0 0 #0 0 0 #0 0 0 #0 0 0 #0 0 0 #0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 A0 0 0 0 0 0 0 0 0 0 0 0 <0 0 #0 #0 #0 #0 0 0 0 0 0 0 .0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 O00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0ي0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 000000000000000000ي00000 0 0 0 0 A0 0 08 0h 0 0 0 0 A08 0h 08 0H 0 0 0 0 0 A0 0 0 0 0 0 0 0X 0 0 0 0 0 0 0 A0H 0 0 #0 #0 0 0 0 0 0 0 0 0 0 0 0X 0h 0 0 0 0 0H 00 0 0 0 0 0X 00 0 0 0 0 08 0h 0 08 0h 0 0 0 08 0h 0 0 0 08 0 0 50 50 50 90 50 90 50 50 908 00 50A0 50 50 5090 5009090 0 A0 A08 0h 0 08 0 08 0 0 0 0 0 0 08 0 00 0 0 50 50 90 50 0 90 90 50 0 08 0 0 0 0 08 0 0 0 0 08 0 #0 #0 #0 #0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 50 50 50 50 0 0 0 0 0 50 50 50 50 50 00 0 0 08 0h 0 0 08 0 0 08 0 08 0 0 08 0 0 08 0 0 50 50 0 0 0 0 0 0 0H 0h 0H 0 0H 0 0 0 0 0 0H 0 0 0 0 0H 0 0 0 0 0 0 0 0 00X0h00A0X00X000000X000X00X00X00X00A080h00H00 5090 500X0000080h00 0 0 0 0 A08 0h 0 0 0 0 0 0 0 0 0 0 0 08 0h 0 0 0 0 0 0H 0h 0h0 0 0 0 0 0H 0h 0 0H 0 0 0 0H 0 0 A0H 0 0H 0h 0 0 0H 0 0H 0 0 0H 0 0H 0h 0 0 0 0 0 0 0H 0h 0 0 0 0H 0h 0 0 0X 0h 0 0X 0 0X 0 0 0X 0h 0 0 0 08 0h 0 0H 0h 0 0ي0 0 0 0 0 0 0 0 0 0 0 08 0h 0 08 0h 0 0 0 0 0X 0h 0 0 0 08 0h 0h0 0 0 0 08 0h 0 0 0 0 0 0 A0X 0h 0 0 08 0h 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 08 0h 0 0 08 0h 0 08 0h 0 08 0h 0 0 0 08 0h 0 08 0h 0 0 0 08 0h 0 08 0h 0 08 0h 0 0 0 0 08 0h 0 0 0 0 0 0 08 0h 0 08 0h 0 0 0 0 08 0h 0 0 0 08 0h 0 08 0 #0 #0 #0 #0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 08 0 #0 #0 #0 #0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 08 0 #0 #0 #0 #0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0X 0h 0 08 0h 0 0 0 08 0h 0 0 0 08 0h 0 08 0h 0 0 0 08 0h 0 0 0 0 0 08 0h 0 08 0h 0 08 0h 0 08 0h 0 0 0 08 0h 0 0 0 0 0 0 08 0h 0 08 0h 0 08 0h 0 0 08 0h 0 0 00 00 0 A0 A0 A0 0 0 A08 0h 0 00800 50 50 500800800008000800800 08 0h 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 08 0h 0 0 0 0000 0 0 0 0 0 0 50 50 50 50 50 0X 0h 0 0H 0h 0 0 0 0 0 0 0 0 0 0 0 0 0 50 50 0 0 0 0 0 0 0 0 0 0 0 %0 %0 0 #0 #0 0 #0 #0 0 #0 #0 0 #0 #0 0 0 0 0 0 0 0 0 08 0h 0 0 0 080ۊ0ي0ي0ي0@ي0@ي0@ي0ي0@ۊ0ي0ي0ي0@ۊ0ي0ي0ي0@ۊ0,ي0ي0ي0@ۊ0  ي0 ي0 ي0@ي0@AIۊ0BCIۊ0DEIۊ0FG0Jۊ0HIhJۊ0JKJۊ0LMJۊ0NOKۊ0PQHKۊ0RSKۊ0TUKۊ0VWKۊ0XY(Lۊ0Z[`Lۊ0\]Lۊ0^_Lۊ0`aMۊ0bc@Mۊ0dexMۊ045lي04ي04ي0fۊ09:ي09ي09ي0fي0>ي0>ي0fۊ0BCي0Bي0Bي0fۊ0GHي0Gي0Gي0fۊ0LM ي0Lي0Lي0fي0Qي0Qي0fي0fgMۊ0hiMۊ0jk Nۊ0lmXNۊ0noNۊ0pqNۊ0rsOۊ0tu8Oۊ0vwpOۊ0xyOۊ0z{Oۊ0k|lpي0k{ي0kyي0|ي0|}Pۊ0~PPۊ0Pۊ0Pۊ0Pۊ00Qۊ0hQۊ0Qۊ0lي0kي0iي0ي0Qۊ0Rۊ0HRۊ0Rۊ0Rۊ0Uۊ0Uۊ0Uۊ0,Vۊ0dVۊ0Vۊ0Vۊ0 Wۊ0DWۊ0|Wۊ0Wۊ0Wۊ0$Xۊ0\Xۊ0Xۊ0Xي0Aي0?ي0ۊ0BPي0Aي0?ي0ي0Yۊ0? kۊ0@AXkۊ0BCkۊ0DEkۊ0FGlۊ0HI8lۊ0JKplۊ0LMlۊ0NOlۊ0PQmۊ0RSPmۊ0TUmۊ0VWmۊ0XYmۊ0Z[0nۊ0\]hnۊ0^_nۊ0`anۊ0bcoۊ0deHoۊ0fgoۊ0hioۊ0jkoۊ0lm(pۊ0no`pۊ0pqpۊ0rspۊ0tuqۊ0vw@qۊ0xyxqۊ0z{qۊ0|}qۊ0~ rۊ0Xrۊ0rۊ0rۊ0sۊ08sۊ0psۊ0sۊ0sۊ0tۊ0Ptۊ0tۊ0tۊ0tۊ00uۊ0huۊ0uۊ0uۊ0vۊ0Hvۊ0vۊ0vۊ0vۊ0(wۊ0`wۊ0wۊ0wۊ0xۊ0@xۊ0xxۊ0xۊ0xۊ0 yۊ0Xyۊ0yۊ0yۊ0zۊ08zۊ0pzۊ0zۊ0zۊ0{ۊ0P{ۊ0{ۊ0{ۊ0{ۊ00|ۊ0h|ۊ0|ۊ0|ۊ0}ۊ0H}ۊ0}ۊ0}ۊ0}ۊ0(~ۊ0`~ۊ0~ۊ0~ي0ۊ0-00ۊ08,0,0ي0ي0ۊ0 ~-00ي0 -00ۊ0  j~,0,0ۊ08'~ -0 0ۊ0k~-00ۊ0Xk~ -0 0ي0hGG"H#HrHsHHHvIwIIIJJbKcKKK9L:Ldddd.e/ePeQexeyeze{effoo\]}~&&9&:&a&b&&&+,BCuvlm`aZZ [ [[["[#[3[4[LM|}  56]^23cdyzLL@MAMMMNNsNtN O O{O|OofpfffffffKLst>?WX78NOno/0TUtu,-WX$%TU'(UV}~$%LMk l       BB C!CCCFFGG-G.GOGPGUUjVkVVVWWWWWWWW X!XXXYYYYYYjjjjkk,k-kllmm7m8mbmcmooNoOo|o}ooo||||} }G}H}!"QR:;ˊ̊ABuvGHMN}~ӒԒklɓʓƗǗFG+,YZdešÚҠӠ$%FG9:-.OPHIjkhi$%LM/0WX>?no23Z[45de,-NOUV\]LMtu  <=jkJKz{9:Aۊ0~ي0ۊ0<~ي0ۊ0t~ي0ۊ0~ي0ۊ0 ~ي0ۊ0  ي0ۊ0  ي0ۊ0 ي0ۊ0Dي0ۊ0,ي0ۊ0dي0ۊ0ي0ۊ0Xdي0ۊ0dي0ۊ0dي0ۊ0<ي0ۊ0 !<ي0ۊ0"#=ي0ۊ0$%lي0ۊ0&'ي0ۊ0()ي0ۊ0*+ي0ۊ0,-Lي0ۊ0./$@ي0ۊ001\@ي0ۊ023@ي0ۊ045@ي0ۊ067Aي0ۊ089`'ي0ۊ0:;'ي0ۊ0<='ي0ۊ0>?(ي0ۊ0@A@(ي0ۊ0BCx(ي0ۊ0DE(ي0ۊ0FGAي0ۊ0HIBي0ۊ0JKHBي0ۊ0LMBي0ۊ0NOBي0ۊ0PQBي0ۊ0RS(Cي0ۊ0TU`Cي0ۊ0VWCي0ۊ0XYT:ي0ۊ0Z[:ي0ۊ0\]Ĉ:ي0ۊ0^_:ي0ۊ0`a4:ي0ۊ0bcl:ي0ۊ0de:ي0ۊ0fg܉:ي0ۊ0hi:ي0ۊ0jkL:ي0ۊ0lm:ي0ۊ0noP:ي0ۊ0pq:ي0ۊ0rs:ي0ۊ0tu:ي0ۊ0vw0:ي0ۊ0xyh:ي0ۊ0z{:ي0ۊ0|}ؚ:ي0ۊ0~:ي0ۊ0H:ي0ۊ0:ي0ۊ0:ي0ۊ0:ي0ۊ0(:ي0ۊ0PN:ي0ۊ0N:ي0ۊ0N:ي0ۊ0N:ي0ۊ00O:ي0ۊ0hO:ي0ۊ0O:ي0ۊ0O:ي0ۊ0P:ي0ۊ0HP:ي0ۊ0P:ي0ۊ0P:ي0ۊ0P:ي0ۊ0(Q:ي0ۊ0`Q:ي0ۊ0Q:ي0ۊ0Q:ي0ۊ0R:ي0ۊ0@:ي0ۊ0x:ي0ۊ0:ي0ۊ0:ي0ۊ0 :ي0ۊ0X:ي0ۊ0:ي0ۊ0ș:ي0ۊ0:ي0ۊ08:ي0ۊ0p:ي0ۊ0:ي0ۊ0:ي0ۊ0:ي0ۊ0P:ي0ۊ0:ي0ۊ0:ي0ۊ0:ي0ۊ00:ي0ۊ0h:ي0ۊ0:ي0ۊ0 }ي0ۊ0D}ي0ۊ0|}ي0ۊ0}ي0ۊ0}ي0ۊ0$}ي0ۊ0\}ي0ۊ0}ي0ۊ0}ي0ۊ0}ي0ۊ0<}ي0ۊ0t}ي0ۊ0}ي0ۊ0}ي0ۊ0}ي0ۊ0T}ي0ۊ0}ي0ۊ0}ي0ۊ0}ي0ۊ04 }ي0ۊ0l }ي0ۊ0 }ي0ۊ0 }ي0ۊ0!}ي0ۊ0 L!}ي0ۊ0  !}ي0ۊ0  !}ي0ۊ0#}ي0ۊ0<#}ي0ۊ0t#}ي0ۊ0#}ي0ۊ0#}ي0ۊ0$}ي0ۊ0T$}ي0ۊ0$}ي0ۊ0$}ي0ۊ0 !$}ي0ۊ0"#4%}ي0ۊ0$%l%}ي0ۊ0&'%}ي0ۊ0()%}ي0ۊ0*+&}ي0ۊ0,-L&}ي0ۊ0./&}ي0ۊ001&}ي0ۊ023&}ي0ۊ045,'}ي0ۊ067d'}ي0ۊ089'}ي0ۊ0:;'}ي0ۊ0<= (}ي0ۊ0>?D(}ي0ۊ0@A|(}ي0ۊ0BC(}ي0ۊ0DE(}ي0ۊ0FG$)}ي0ۊ0HI\)}ي0ۊ0JK)}ي0ۊ0LM)}ي0ۊ0NO*}ي0ۊ0PQ<*}ي0ۊ0RS+}ي0ۊ0TU,}ي0ۊ0VW8,}ي0ۊ0XYp,}ي0ۊ0Z[,}ي0ۊ0\],}ي0ۊ0^_-}ي0ۊ0`aP-}ي0ۊ0bc-}ي0ۊ0de-}ي0ۊ0fg-}ي0ۊ0hi0.}ي0ۊ0jkh.}ي0ۊ0lm.}ي0ۊ0no.}ي0ۊ0pq/}ي0ۊ0rsH/}ي0ۊ0tu/}ي0ۊ0vw/}ي0ۊ0xy/}ي0ۊ0z{(0}ي0ۊ0|}`0}ي0ۊ0~0}ي0ۊ00}ي0ۊ01}ي0ۊ0@1}ي0ۊ0x1}ي0ۊ01}ي0ۊ01}ي0ۊ0 2}ي0ۊ0X2}ي0ۊ02}ي0ۊ02}ي0ۊ03}ي0ۊ083}ي0ۊ0p3}ي0ۊ03}ي0ۊ03}ي0ۊ04}ي0ۊ0P4}ي0ۊ04}ي0ۊ04}ي0ۊ04}ي0ۊ06}ي0ۊ07}ي0ۊ0H7}ي0ۊ07}ي0ۊ07}ي0ۊ07}ي0ۊ0(8}ي0ۊ0`8}ي0ۊ08}ي0ۊ08}ي0ۊ09}ي0ۊ0@9}ي0ۊ0x9}ي0ۊ09}ي0ۊ09}ي0ۊ0 :}ي0ۊ0X:}ي0ۊ0:}ي0ۊ0:}ي0ۊ0;}ي0ۊ08;}ي0ۊ0p;}ي0ۊ0;}ي0ۊ0;}ي0ۊ0<}ي0ۊ0P<}ي0ۊ0<}ي0ۊ0<}ي0ۊ0<}ي0ۊ00=}ي0ۊ0h=}ي0ۊ0=}ي0ۊ0=}ي0ۊ0>}ي0ۊ0H>}ي0ۊ0>}ي0ۊ0>}ي0ۊ0>}ي0ۊ0(?}ي0ۊ0`?}ي0ۊ0?}ي0ۊ0?}ي0ۊ0@}ي0ۊ0@@}ي0ۊ0x@}ي0ۊ0@}ي0ۊ0@}ي0ۊ0 A}ي0ۊ0 XA}ي0ۊ0  A}ي0ۊ0  A}ي0ۊ0B}ي0ي0ي0p ::::::''^^^^^^KKKKKKcc Tb.8faT$b< e8zp81OBS*[_dVimnriwz}NAAZUGFz^ǭϲ[~GIm}" + c d"9;Sqm(HXܘ1_cdfgikt27;>ALNPR[`bdflrwz~  '>Rbx%COrPvQRSFUe\Vfl.mPmxmzmnw{^g6}8 ~$*/0;0]09ALc`r4pK˯3 ^<~OF:\8 ^Y"^/w?ILNPQ)QCSZ^D```taaaa}bbqcce[jnrttuvvwnĤ֪ t)"DǸBݹ ?& 1\HvSU 4>l(/c i&NDlTGV  49/CCTgtjmZq0uxF|c6YN¢CX ٸV\7bt  !F$H'*Y-S036:>XADH9KpN RUW%[`^aaadgjmorux|~xn=ٍӔ¢ܩXby4`behjlmnopqrsuvwxyz{|}~      !"#$%&'()*+,-./01345689:<=?@BCDEFGHIJKMOQSTUVWXYZ\]^_aceghijkmnopqstuvxy{|}    !"#$%&()*+,-./0123456789:;<=?@ABCDEFGHIJKLMNOPQSTUVWXYZ[\]^_`acdefghijklmnopqrstuvwyz{|}~a1?L-36rx{PVZ  =CGU[_y /=J!!!!!!!!!!!!!!!@  @ 0(  B S  ?H0(  titleversiondate _Toc390577607 _Toc391278930 _Toc373034398 _Toc383328893 _Toc386525759 _Toc399050513 _Toc400765930 _Toc401110595 _Toc401110925 _Toc417118855 _Toc419615427 _Toc419615669 _Toc419677916 _Toc419867929 _Toc472153878 _Toc472476266 _Toc474830875 _Toc474834860 _Toc474835712 _Toc480169272 _Toc482779516 _Toc486233149 _Toc454812784 _Toc472153880 _Toc474830508 _Toc474830876 _Toc474834861 _Toc474835713 _Toc480169273 _Toc482779517 _Toc485188628 _Toc485190074 _Toc485200432 _Toc486233150 _Toc454812785 _Toc472153881 _Toc474830509 _Toc474830877 _Toc474831552 _Toc474834862 _Toc474835714 _Toc480169274 _Toc482779518 _Toc485188629 _Toc485190075 _Toc485200433 _Toc486233151 _Toc454812786 _Toc472153882 _Toc474830510 _Toc474830878 _Toc474831553 _Toc474834863 _Toc474835715 _Toc480169275 _Toc482779519 _Toc485188630 _Toc485190076 _Toc485200434 _Toc486233152 _Toc399050516 _Toc400765933 _Toc401110497 _Toc401110598 _Toc401110928 _Toc417118859 _Toc419615428 _Toc419615670 _Toc472153883 _Toc474830511 _Toc474830879 _Toc474831554 _Toc474834864 _Toc474835716 _Toc480169276 _Toc371903855 _Toc373034401 _Toc383328896 _Toc386525762 _Toc371903854 _Toc373034400 _Toc383328895 _Toc386525761 _Toc482779520 _Toc485188631 _Toc485190077 _Toc485200435 _Toc486233153 _Toc371903856 _Toc373034402 _Toc383328897 _Toc386525763 _Toc399050517 _Toc400765934 _Toc401110498 _Toc401110599 _Toc401110929 _Toc417118860 _Toc419615429 _Toc419615671 _Toc472153884 _Toc474830512 _Toc474830880 _Toc474831555 _Toc474834865 _Toc474835717 _Toc480169277 _Toc482779521 _Toc485188632 _Toc485190078 _Toc485200436 _Toc486233154 _Toc399050518 _Toc400765935 _Toc401110499 _Toc401110600 _Toc401110930 _Toc415389999 _Toc417118861 _Toc419615430 _Toc419615672 _Toc472153885 _Toc474830513 _Toc474830881 _Toc474831556 _Toc474834866 _Toc474835718 _Toc480169278 _Toc482779522 _Toc485188633 _Toc485190079 _Toc485200437 _Toc486233155 _Toc399050519 _Toc400765936 _Toc401110500 _Toc401110601 _Toc401110931 _Toc415390000 _Toc417118862 _Toc419615431 _Toc419615673 _Toc472153886 _Toc474830514 _Toc474830882 _Toc474831557 _Toc474834867 _Toc474835719 _Toc480169279 _Toc482779523 _Toc485188634 _Toc485190080 _Toc485200438 _Toc486233156 _Toc419615432 _Toc419615674 _Toc472153887 _Toc474830515 _Toc474830883 _Toc474831558 _Toc474834868 _Toc474835720 _Toc480169280 _Toc371903857 _Toc373034403 _Toc383328898 _Toc386525764 _Toc399050520 _Toc400765937 _Toc401110501 _Toc401110602 _Toc401110932 _Toc417118863 _Toc482779524 _Toc485188635 _Toc485190081 _Toc485200439 _Toc486233157 _Toc419615433 _Toc419615675 _Toc472153888 _Toc474830516 _Toc474830884 _Toc474831559 _Toc474834869 _Toc474835721 _Toc480169281 _Toc482779525 _Toc485188636 _Toc485190082 _Toc485200440 _Toc486233158 _Toc417118858 _Toc419615435 _Toc419615677 _Toc472153889 _Toc474830517 _Toc474830885 _Toc474831560 _Toc474834870 _Toc474835722 _Toc480169282 _Toc399050515 _Toc400765932 _Toc401110496 _Toc401110597 _Toc401110927 _Toc482779526 _Toc485188637 _Toc485190083 _Toc485200441 _Toc486233159 _Toc419615436 _Toc419615678 _Toc472153890 _Toc474830518 _Toc474830886 _Toc474831561 _Toc474834871 _Toc474835723 _Toc480169283 _Toc482779527 _Toc485188638 _Toc485190084 _Toc485200442 _Toc486233160 _Toc380382292 _Toc381582270 _Toc382099015 _Toc380382293 _Toc381582271 _Toc382099016 _Toc371903858 _Toc373034404 _Toc383328899 _Toc386525765 _Toc399050521 _Toc400765938 _Toc401110502 _Toc401110603 _Toc401110933 _Toc417118864 _Toc419615437 _Toc419615679 _Toc472153891 _Toc474830519 _Toc474830887 _Toc474831562 _Toc474834872 _Toc474835724 _Toc480169284 _Toc482779528 _Toc485188639 _Toc485190085 _Toc485200443 _Toc486233161 _Toc399050522 _Toc400765939 _Toc401110604 _Toc401110934 _Toc415390003 _Toc416409184 _Toc417118865 _Toc419615438 _Toc419615680 _Toc419677927 _Toc419867940 _Toc422135653 _Toc425225732 _Toc431091210 _Toc472153892 _Toc474830888 _Toc480169285 _Toc482779529 _Toc485200602 _Toc486233162 _Toc351353212 _Toc351792711 _Toc369417233 _Toc369417457 _Toc371903859 _Toc373034407 _Toc383328901 _Toc384454479 _Toc386525767 _Toc399050523 _Toc400765940 _Toc401110605 _Toc401110935 _Toc417118866 _Toc419615439 _Toc419615681 _Toc419677928 _Toc419867941 _Toc472153893 _Toc472476267 _Toc474830889 _Toc474834873 _Toc474835725 _Toc480169286 _Toc482779530 _Toc486233163 _906539761 _Toc383328902 _Toc386525768 _Toc399050524 _Toc400765941 _Toc401110503 _Toc401110606 _Toc401110936 _Toc417118867 _Toc419615440 _Toc419615682 _Toc472153894 _Toc474830520 _Toc474830890 _Toc474831563 _Toc474834874 _Toc474835726 _Toc480169287 _Toc336413185 _Toc337619969 _Toc338735757 _Toc341255732 _Toc346600362 _Toc349963187 _Toc337619913 _Toc344790490 _Toc346855408 _Toc482779531 _Toc485188640 _Toc485190086 _Toc485200444 _Toc486233164 _Toc369417234 _Toc369417458 _Toc371903861 _Toc373034409 _Toc383328904 _Toc386525770 _Toc399050526 _Toc400765943 _Toc401110505 _Toc401110608 _Toc401110938 _Toc417118868 _Toc419615441 _Toc419615683 _Toc472153895 _Toc474830521 _Toc474830891 _Toc474831564 _Toc474834875 _Toc474835727 _Toc480169288 _Toc482779532 _Toc485188641 _Toc485190087 _Toc485200445 _Toc486233165 _Toc371903862 _Toc373034410 _Toc383328905 _Toc386525771 _Toc399050527 _Toc400765944 _Toc401110506 _Toc401110609 _Toc401110939 _Toc362754191 _Toc361574414 _Toc371903860 _Toc373034408 _Toc383328903 _Toc386525769 _Toc399050525 _Toc400765942 _Toc401110504 _Toc401110607 _Toc401110937 _Toc417118869 _Toc419615442 _Toc419615684 _Toc472153896 _Toc474830522 _Toc474830892 _Toc474831565 _Toc474834876 _Toc474835728 _Toc480169289 _Toc482779533 _Toc485188642 _Toc485190088 _Toc485200446 _Toc486233166 _Toc416409134 _Toc417118870 _Toc419615443 _Toc419615685 _Toc472153897 _Toc474830523 _Toc474830893 _Toc474831566 _Toc474834877 _Toc474835729 _Toc480169290 _Toc482779534 _Toc485188643 _Toc485190089 _Toc485200447 _Toc486233167 _Toc369417237 _Toc369417461 _Toc371903863 _Toc373034411 _Toc383328906 _Toc386525772 _Toc399050528 _Toc400765945 _Toc401110507 _Toc401110610 _Toc401110940 _Toc417118871 _Toc419615444 _Toc419615686 _Toc472153898 _Toc474830524 _Toc474830894 _Toc474831567 _Toc474834878 _Toc474835730 _Toc480169291 _Toc482779535 _Toc485188644 _Toc485190090 _Toc485200448 _Toc486233168 _Toc482779536 _Toc485188645 _Toc485190091 _Toc485200449 _Toc486233169 _Toc482779537 _Toc485188646 _Toc485190092 _Toc485200450 _Toc486233170 _Toc482779538 _Toc485188647 _Toc485190093 _Toc485200451 _Toc486233171 _Toc383328907 _Toc386426457 _Toc386525773 _Toc391278948 _Toc394920719 _Toc395079662 _Toc399050531 _Toc369417238 _Toc369417462 _Toc371903864 _Toc373034412 _Toc400765948 _Toc401110613 _Toc401110943 _Toc415390012 _Toc416409191 _Toc417118872 _Toc419615445 _Toc419615687 _Toc419677934 _Toc419867947 _Toc422135660 _Toc425225739 _Toc431091217 _Toc472153899 _Toc474830895 _Toc480169292 _Toc482779539 _Toc485200612 _Toc486233172 _Toc383328908 _Toc384454486 _Toc386525774 _Toc399050532 _Toc400765949 _Toc401110614 _Toc401110944 _Toc417118873 _Toc419615446 _Toc419615688 _Toc419677935 _Toc419867948 _Toc472153900 _Toc472476268 _Toc474830896 _Toc474834879 _Toc474835731 _Toc480169293 _Toc482779540 _Toc486233173 _Toc369417264 _Toc369417464 _Toc371903866 _Toc373034414 _Toc383328910 _Toc386525776 _Toc399050533 _Toc400765950 _Toc401110508 _Toc401110615 _Toc401110945 _Toc417118874 _Toc419615447 _Toc419615689 _Toc472153901 _Toc474830525 _Toc474830897 _Toc474831568 _Toc474834880 _Toc474835732 _Toc480169294 _Toc383328909 _Toc386525775 _Toc482779541 _Toc485188648 _Toc485190094 _Toc485200452 _Toc486233174 _Toc472476271 _Toc474834883 _Toc474835735 _Toc485188649 _Toc485190095 _Toc472476272 _Toc474834884 _Toc474835736 _Toc485188650 _Toc485190096 _Toc399050534 _Toc400765951 _Toc401110509 _Toc401110616 _Toc401110946 _Toc417118875 _Toc419615448 _Toc419615690 _Toc472153902 _Toc474830526 _Toc474830898 _Toc474834885 _Toc474835737 _Toc480169295 _Toc482779542 _Toc485188651 _Toc485190097 _Toc485200453 _Toc486233175 _Toc369417239 _Toc369417242 _Toc472476273 _Toc474834886 _Toc474835738 _Toc485188652 _Toc485190098 _Toc472476274 _Toc474834887 _Toc474835739 _Toc485188653 _Toc485190099 _Toc474834888 _Toc474835740 _Toc485188654 _Toc485190100 _Toc474834889 _Toc474835741 _Toc485188655 _Toc474834890 _Toc474835742 _Toc485190101 _Toc369417465 _Toc371903868 _Toc373034416 _Toc383328911 _Toc386525777 _Toc399050535 _Toc400765952 _Toc401110510 _Toc401110617 _Toc401110947 _Toc417118876 _Toc419615449 _Toc419615691 _Toc472153903 _Toc474830527 _Toc474830899 _Toc474834891 _Toc474835743 _Toc480169296 _Toc482779543 _Toc485188656 _Toc485190102 _Toc485200454 _Toc486233176 _Toc369417265 _Toc472476275 _Toc474834892 _Toc474835744 _Toc485188657 _Toc485188658 _Toc485190103 _Toc485188659 _Toc485190104 _Toc485188660 _Toc485190105 _Toc485188661 _Toc485190106 _Toc369417268 _Toc485190107 _Toc485188662 _Toc485190108 _Toc472476288 _Toc474834905 _Toc474835757 _Toc485188663 _Toc485188664 _Toc485190109 _Toc485188665 _Toc485190110 _Toc369417271 _Toc472476301 _Toc485190111 _Toc485188666 _Toc485190112 _Toc474834918 _Toc474835770 _Toc485188667 _Toc485190113 _Toc472476302 _Toc474834919 _Toc474835771 _Toc485188668 _Toc485190114 _Toc472476303 _Toc474834920 _Toc474835772 _Toc485188669 _Toc485190115 _Toc472476304 _Toc474834921 _Toc474835773 _Toc485188670 _Toc485190116 _Toc399050537 _Toc400765954 _Toc401110512 _Toc401110619 _Toc401110949 _Toc415390018 _Toc417118877 _Toc419615450 _Toc419615692 _Toc472153904 _Toc474830528 _Toc474830900 _Toc474834922 _Toc474835774 _Toc480169297 _Toc482779544 _Toc485188671 _Toc485190117 _Toc485200455 _Toc486233177 _Toc349963189 _Toc472476305 _Toc474834923 _Toc474835775 _Toc350125612 _Toc369417277 _Toc349963188 _Toc337513003 _Toc338230124 _Toc341258123 _Toc341671009 _Toc348745808 _Toc350155076 _Toc350923523 _Toc352122150 _Toc485188672 _Toc485190118 _Toc472476306 _Toc474834924 _Toc474835776 _Toc485188673 _Toc485190119 _Toc474834925 _Toc474835777 _Toc485188674 _Toc485190120 _Toc474834926 _Toc474835778 _Toc485188675 _Toc485190121 _Toc472476307 _Toc474834927 _Toc474835779 _Toc485188676 _Toc485190122 _Toc472476308 _Toc474834928 _Toc474835780 _Toc485188677 _Toc485190123 _Toc474834929 _Toc474835781 _Toc485188678 _Toc485190124 _Toc474834930 _Toc474835782 _Toc485188679 _Toc485190125 _Toc474834931 _Toc474835783 _Toc485188680 _Toc485190126 _Toc474834932 _Toc474835784 _Toc485188681 _Toc485190127 _Toc474834933 _Toc474835785 _Toc485188682 _Toc485190128 _Toc472476309 _Toc474834934 _Toc474835786 _Toc485188683 _Toc485190129 _Toc472476310 _Toc474834935 _Toc474835787 _Toc485188684 _Toc485190130 _Toc472476311 _Toc474834936 _Toc474835788 _Toc485188685 _Toc485190131 _Toc472476312 _Toc474834937 _Toc474835789 _Toc485188686 _Toc485190132 _Toc472476313 _Toc474834938 _Toc474835790 _Toc485188687 _Toc485190133 _Toc472476314 _Toc474834939 _Toc474835791 _Toc485188688 _Toc485190134 _Toc472476315 _Toc474834940 _Toc474835792 _Toc485188689 _Toc485190135 _Toc472476316 _Toc474834941 _Toc474835793 _Toc485188690 _Toc485190136 _Toc472476317 _Toc474834942 _Toc474835794 _Toc485188691 _Toc485190137 _Toc472476318 _Toc474834943 _Toc474835795 _Toc485188692 _Toc485190138 _Toc472476319 _Toc474834944 _Toc474835796 _Toc485188693 _Toc485190139 _Toc472476320 _Toc474834945 _Toc474835797 _Toc485188694 _Toc485190140 _Toc472476321 _Toc474834946 _Toc474835798 _Toc485188695 _Toc485190141 _Toc415390589 _Toc399050538 _Toc400765955 _Toc401110513 _Toc401110620 _Toc401110950 _Toc415390019 _Toc417118878 _Toc419615451 _Toc419615693 _Toc472153905 _Toc474830529 _Toc474830901 _Toc474834947 _Toc474835799 _Toc480169298 _Toc482779545 _Toc485188696 _Toc485190142 _Toc485200456 _Toc486233178 _Toc369417248 _Toc472476322 _Toc474834948 _Toc474835800 _Toc485188697 _Toc485190143 _Toc472476323 _Toc474834949 _Toc474835801 _Toc485188698 _Toc485190144 _Toc474834950 _Toc474835802 _Toc485188699 _Toc485190145 _Toc474834951 _Toc474835803 _Toc485188700 _Toc485190146 _Toc474834952 _Toc474835804 _Toc485188701 _Toc485190147 _Toc474834953 _Toc474835805 _Toc485188702 _Toc485190148 _Toc474834954 _Toc474835806 _Toc485188703 _Toc485190149 _Toc474834955 _Toc474835807 _Toc485188704 _Toc474834956 _Toc474835808 _Toc485188705 _Toc485190150 _Toc474834957 _Toc474835809 _Toc485188706 _Toc474834958 _Toc474835810 _Toc485188707 _Toc474834959 _Toc474835811 _Toc485188708 _Toc474834960 _Toc474835812 _Toc485188709 _Toc474834961 _Toc474835813 _Toc485190151 _Toc474834962 _Toc474835814 _Toc485188710 _Toc485190152 _Toc349963191 _Toc485190153 _Toc474834965 _Toc474835817 _Toc485190154 _Toc474834966 _Toc474835818 _Toc485190155 _Toc474834967 _Toc474835819 _Toc485190156 _Toc485190157 _Toc485190158 _Toc485190159 _Toc472476324 _Toc474834968 _Toc474835820 _Toc485188711 _Toc485190160 _Toc472476325 _Toc474834969 _Toc474835821 _Toc485188712 _Toc485190161 _Toc485188713 _Toc485190162 _Toc399050539 _Toc400765956 _Toc401110514 _Toc401110621 _Toc401110951 _Toc415390020 _Toc417118879 _Toc419615452 _Toc419615694 _Toc472153906 _Toc474830530 _Toc474830902 _Toc474834970 _Toc474835822 _Toc480169299 _Toc482779546 _Toc485188714 _Toc485190163 _Toc485200457 _Toc486233179 _Toc472476326 _Toc474834971 _Toc474835823 _Toc351353216 _Toc351792715 _Toc369417280 _Toc369417467 _Toc371903870 _Toc373034418 _Toc349446152 _Toc349446182 _Toc349963159 _Toc349963205 _Toc350125619 _Toc485188715 _Toc485190164 _Toc472476327 _Toc474834972 _Toc474835824 _Toc485188716 _Toc485190165 _Toc472476328 _Toc474834973 _Toc474835825 _Toc485188717 _Toc485190166 _Toc472476329 _Toc474834974 _Toc474835826 _Toc485188718 _Toc485190167 _Toc349963198 _Toc349963199 _Toc472476332 _Toc474834977 _Toc474835829 _Toc485188719 _Toc485190168 _Toc472476333 _Toc474834978 _Toc474835830 _Toc485188720 _Toc485190169 _Toc480169300 _Toc472153907 _Toc474830531 _Toc474830903 _Toc474834979 _Toc474835831 _Toc482779547 _Toc485188721 _Toc485190170 _Toc485200458 _Toc486233180 _Toc485188722 _Toc485188723 _Toc485190171 _Toc485188724 _Toc485190172 _Toc485188725 _Toc485188726 _Toc485190173 _Toc485188727 _Toc485188728 _Toc485188729 _Toc485188730 _Toc485188731 _Toc485190174 _Toc485188732 _Toc485188733 _Toc485188734 _Toc485188735 _Toc485188736 _Toc485190175 _Toc485188737 _Toc485188738 _Toc485190176 _Toc480169301 _Toc482779548 _Toc485188739 _Toc485190177 _Toc485200459 _Toc486233181 _Toc472476334 _Toc474834980 _Toc474835832 _Toc485188740 _Toc472476335 _Toc474834981 _Toc474835833 _Toc485188741 _Toc485190178 _Toc472476336 _Toc474834982 _Toc474835834 _Toc485190179 _Toc472476337 _Toc474834983 _Toc474835835 _Toc485188742 _Toc485190180 _Toc472476338 _Toc474834984 _Toc474835836 _Toc485190181 _Toc472476340 _Toc474834985 _Toc474835837 _Toc485190182 _Toc472476342 _Toc474834986 _Toc474835838 _Toc485190183 _Toc472476343 _Toc474834987 _Toc474835839 _Toc485188743 _Toc485190184 _Toc485188744 _Toc485190185 _Toc485188745 _Toc485190186 _Toc457380582 _Toc457380578 _Toc485188746 _Toc485188747 _Toc485190187 _Toc383328913 _Toc386525779 _Toc391278957 _Toc394920728 _Toc395079671 _Toc399050540 _Toc400765957 _Toc401110622 _Toc401110952 _Toc415390021 _Toc416409199 _Toc417118880 _Toc419615454 _Toc419615696 _Toc419677943 _Toc419867956 _Toc422135669 _Toc425225748 _Toc431091226 _Toc472153908 _Toc474830904 _Toc480169302 _Toc482779549 _Toc485200622 _Toc486233182 _Toc399050541 _Toc400765958 _Toc401110623 _Toc401110953 _Toc417118881 _Toc419615455 _Toc419615697 _Toc419677944 _Toc419867957 _Toc472153909 _Toc472476344 _Toc474830905 _Toc474834988 _Toc474835840 _Toc480169303 _Toc482779550 _Toc486233183 _Toc369417281 _Toc369417468 _Toc371903871 _Toc373034419 _Toc383328914 _Toc386525780 _Toc391278959 _Toc399050542 _Toc400765959 _Toc401110515 _Toc401110624 _Toc401110954 _Toc417118882 _Toc419615456 _Toc419615698 _Toc472153910 _Toc474830532 _Toc474830906 _Toc474834989 _Toc474835841 _Toc480169304 _Toc482779551 _Toc485188748 _Toc485190188 _Toc485200460 _Toc486233184 _Toc472476345 _Toc474834990 _Toc474835842 _Toc369417282 _Toc485188749 _Toc485190189 _Toc472476346 _Toc474834991 _Toc474835843 _Toc485188750 _Toc485190190 _Toc485188751 _Toc485190191 _Toc485188752 _Toc485190192 _Toc485190193 _Toc485188753 _Toc485190194 _Toc472476349 _Toc474834996 _Toc474835848 _Toc485188754 _Toc485190195 _Toc485188755 _Toc485190196 _Toc485188756 _Toc485190197 _Toc472476362 _Toc474835009 _Toc474835861 _Toc485188757 _Toc485190198 _Toc472476363 _Toc474835010 _Toc474835862 _Toc485188758 _Toc485190199 _Hlt449840615 _Toc472476364 _Toc474835011 _Toc474835863 _Toc485190200 _Toc472476365 _Toc474835012 _Toc474835864 _Toc485188759 _Toc485190201 _Toc472476366 _Toc474835013 _Toc474835865 _Toc485188760 _Toc485190202 _Toc472476367 _Toc474835014 _Toc474835866 _Toc485188761 _Toc485190203 _Toc472476368 _Toc474835015 _Toc474835867 _Toc485188762 _Toc485190204 _Toc472476369 _Toc474835016 _Toc474835868 _Toc485188763 _Toc485190205 _Toc485188764 _Toc485190206 _Toc485188765 _Toc485190207 _Toc350159985 _Toc472476370 _Toc474835017 _Toc474835869 _Toc485188766 _Toc485190208 _Toc472476371 _Toc474835018 _Toc474835870 _Toc485188767 _Toc485190209 _Toc472476372 _Toc474835019 _Toc474835871 _Toc350160538 _Toc362751170 _Toc385821474 _Toc348417780 _Toc350159987 _Toc485188768 _Toc485190210 _Toc472476373 _Toc474835020 _Toc474835872 _Toc485188769 _Toc485190211 _Toc472476374 _Toc474835021 _Toc474835873 _Toc485188770 _Toc485190212 _Toc472476375 _Toc474835022 _Toc474835874 _Toc485188771 _Toc485190213 _Toc472476376 _Toc474835023 _Toc474835875 _Toc485188772 _Toc485190214 _Toc472476377 _Toc474835024 _Toc474835876 _Toc485188773 _Toc485190215 _Toc472476378 _Toc474835025 _Toc474835877 _Toc485188774 _Toc485190216 _Toc485188775 _Toc485190217 _Toc472476391 _Toc474835038 _Toc474835890 _Toc348414473 _Toc348414495 _Toc485188776 _Toc485190218 _Toc472476392 _Toc474835039 _Toc474835891 _Toc485188777 _Toc485190219 _Toc347297047 _Toc350159992 _Toc472476393 _Toc474835040 _Toc474835892 _Toc315001974 _Toc315002016 _Toc315168552 _Toc315178570 _Toc315178613 _Toc315178967 _Toc315626634 _Toc336763916 _Toc337628634 _Toc337629836 _Toc315001978 _Toc315002020 _Toc315168561 _Toc315178571 _Toc315178614 _Toc315178968 _Toc315626635 _Toc336763917 _Toc337628640 _Toc337629839 _Toc485188778 _Toc485190220 _Toc472476394 _Toc474835041 _Toc474835893 _Toc485188779 _Toc485190221 _Toc350159993 _Toc472476395 _Toc474835042 _Toc474835894 _Toc485188780 _Toc485190222 _Toc472476396 _Toc474835043 _Toc474835895 _Toc485188781 _Toc485190223 _Toc350159994 _Toc338822202 _Toc350159995 _Toc472476397 _Toc474835044 _Toc474835896 _Toc485188782 _Toc485190224 _Toc472476398 _Toc474835045 _Toc474835897 _Toc485188783 _Toc485190225 _Toc472476403 _Toc474835048 _Toc474835900 _Toc485188784 _Toc485190226 _Toc472476404 _Toc474835049 _Toc474835901 _Toc485188785 _Toc485190227 _Toc472476405 _Toc474835050 _Toc474835902 _Toc485188786 _Toc485190228 _Toc472476406 _Toc474835051 _Toc474835903 _Toc485188787 _Toc485190229 _Toc472476407 _Toc474835052 _Toc474835904 _Toc485188788 _Toc485190230 _Toc472476408 _Toc474835053 _Toc474835905 _Toc485188789 _Toc485190231 _Toc472476409 _Toc474835054 _Toc474835906 _Toc485188790 _Toc485190232 _Toc472476410 _Toc474835055 _Toc474835907 _Toc485188791 _Toc485190233 _Toc472476411 _Toc474835056 _Toc474835908 _Toc485188792 _Toc485190234 _Toc472476412 _Toc474835057 _Toc474835909 _Toc485188793 _Toc485190235 _Toc472476413 _Toc474835058 _Toc474835910 _Toc485188794 _Toc485190236 _Toc472476414 _Toc474835059 _Toc474835911 _Toc485188795 _Toc485190237 _Toc472476415 _Toc474835060 _Toc474835912 _Toc485188796 _Toc485190238 _Toc472476416 _Toc474835061 _Toc474835913 _Toc485188797 _Toc485190239 _Toc472476417 _Toc474835062 _Toc474835914 _Toc485188798 _Toc485190240 _Toc472476418 _Toc474835063 _Toc474835915 _Toc485188799 _Toc485190241 _Toc472476419 _Toc474835064 _Toc474835916 _Toc485188800 _Toc485190242 _Toc472476420 _Toc474835065 _Toc474835917 _Toc485188801 _Toc485190243 _Toc472476421 _Toc474835066 _Toc474835918 _Toc485188802 _Toc485190244 _Toc472476422 _Toc474835067 _Toc474835919 _Toc485188803 _Toc485190245 _Toc472476423 _Toc474835068 _Toc474835920 _Toc485188804 _Toc485190246 _Toc472476424 _Toc474835069 _Toc474835921 _Toc485188805 _Toc485190247 _Toc472476425 _Toc474835070 _Toc474835922 _Toc485188806 _Toc485190248 _Toc472476426 _Toc474835071 _Toc474835923 _Toc485188807 _Toc485190249 _Toc472476427 _Toc474835072 _Toc474835924 _Toc485188808 _Toc485190250 _Toc472476428 _Toc474835073 _Toc474835925 _Toc485188809 _Toc485190251 _Toc472476429 _Toc474835074 _Toc474835926 _Toc485188810 _Toc485190252 _Toc472476430 _Toc474835075 _Toc474835927 _Toc485188811 _Toc485190253 _Toc472476431 _Toc474835076 _Toc474835928 _Toc485188812 _Toc485190254 _Toc472476432 _Toc474835077 _Toc474835929 _Toc485188813 _Toc485190255 _Toc472476433 _Toc474835078 _Toc474835930 _Toc485188814 _Toc485190256 _Toc472476434 _Toc474835079 _Toc474835931 _Toc485188815 _Toc485190257 _Toc472476435 _Toc474835080 _Toc474835932 _Toc485188816 _Toc485190258 _Toc472476436 _Toc474835081 _Toc474835933 _Toc485188817 _Toc485190259 _Toc472476437 _Toc474835082 _Toc474835934 _Toc485188818 _Toc485190260 _Toc472476438 _Toc474835083 _Toc474835935 _Toc485188819 _Toc485190261 _Toc472476439 _Toc474835084 _Toc474835936 _Toc485188820 _Toc485190262 _Toc472476440 _Toc474835085 _Toc474835937 _Toc485188821 _Toc485190263 _Toc472476441 _Toc474835086 _Toc474835938 _Toc485188822 _Toc485190264 _Toc472476442 _Toc474835087 _Toc474835939 _Toc485188823 _Toc485190265 _Toc472476443 _Toc474835088 _Toc474835940 _Toc485188824 _Toc485190266 _Toc472476444 _Toc474835089 _Toc474835941 _Toc485188825 _Toc485190267 _Toc472476445 _Toc474835090 _Toc474835942 _Toc485188826 _Toc485190268 _Toc472476446 _Toc474835091 _Toc474835943 _Toc485188827 _Toc485190269 _Toc472476447 _Toc474835092 _Toc474835944 _Toc485188828 _Toc485190270 _Toc472476448 _Toc474835093 _Toc474835945 _Toc485190271 _Toc472476449 _Toc474835094 _Toc474835946 _Toc485188829 _Toc485190272 _Toc472476450 _Toc474835095 _Toc474835947 _Toc485188830 _Toc485190273 _Toc472476451 _Toc474835096 _Toc474835948 _Toc485188831 _Toc485190274 _Toc472476452 _Toc474835097 _Toc474835949 _Toc485188832 _Toc485190275 _Toc472476453 _Toc474835098 _Toc474835950 _Toc485188833 _Toc485190276 _Toc399050543 _Toc400765960 _Toc401110516 _Toc401110625 _Toc401110955 _Toc417118883 _Toc419615457 _Toc419615699 _Toc472153911 _Toc474830533 _Toc474830907 _Toc474835099 _Toc474835951 _Toc480169305 _Toc482779552 _Toc485188834 _Toc485190277 _Toc485200461 _Toc486233185 _Toc472476454 _Toc474835100 _Toc474835952 _Toc485188835 _Toc485190278 _Toc472476455 _Toc474835101 _Toc474835953 _Toc485188836 _Toc485190279 _Toc349983829 _Toc472476456 _Toc474835102 _Toc474835954 _Toc369417285 _Toc485188837 _Toc485190280 _Toc472476457 _Toc474835103 _Toc474835955 _Toc485188838 _Toc485190281 _Toc472476458 _Toc474835104 _Toc474835956 _Toc348254438 _Toc349983830 _Toc383932597 _Toc384109121 _Toc384125602 _Toc347288544 _Toc485188839 _Toc485190282 _Toc472476459 _Toc474835105 _Toc474835957 _Toc485188840 _Toc485190283 _Toc472476462 _Toc474835108 _Toc474835960 _Toc347288548 _Toc348254440 _Toc349983834 _Toc485188841 _Toc485190284 _Toc472476463 _Toc474835109 _Toc474835961 _Toc485188842 _Toc485190285 _Toc472476464 _Toc474835110 _Toc474835962 _Toc485188843 _Toc485190286 _Toc472476465 _Toc474835111 _Toc474835963 _Toc485188844 _Toc485190287 _Toc472476468 _Toc474835114 _Toc474835966 _Toc485188845 _Toc485190288 _Toc472476469 _Toc474835115 _Toc474835967 _Toc485188846 _Toc485190289 _Toc485188847 _Toc485190290 _Toc485188848 _Toc485190291 _Toc399050544 _Toc400765961 _Toc401110517 _Toc401110626 _Toc401110956 _Toc417118884 _Toc419615458 _Toc419615700 _Toc472153912 _Toc474830534 _Toc474830908 _Toc474835116 _Toc474835968 _Toc480169306 _Toc482779553 _Toc485188849 _Toc485190292 _Toc485200462 _Toc486233186 _Toc472476470 _Toc474835117 _Toc474835969 _Toc485188850 _Toc485190293 _Toc472476471 _Toc474835118 _Toc474835970 _Toc485188851 _Toc485190294 _Toc472476472 _Toc474835119 _Toc474835971 _Toc485188852 _Toc485190295 _Toc472476473 _Toc474835120 _Toc474835972 _Toc485188853 _Toc485190296 _Toc472476474 _Toc474835121 _Toc474835973 _Toc485188854 _Toc485190297 _Toc472476475 _Toc474835122 _Toc474835974 _Toc485188855 _Toc485190298 _Toc369417292 _Toc472476476 _Toc474835123 _Toc474835975 _Toc485188856 _Toc485190299 _Toc472476477 _Toc474835124 _Toc474835976 _Toc485188857 _Toc485190300 _Toc472476478 _Toc474835125 _Toc474835977 _Toc351353217 _Toc351792716 _Toc369417305 _Toc369417470 _Toc371903872 _Toc373034420 _Toc350125623 _Toc351353218 _Toc351792717 _Toc485188858 _Toc485190301 _Toc472476479 _Toc474835126 _Toc474835978 _Toc485188859 _Toc485190302 _Toc383328915 _Toc386525781 _Toc399050545 _Toc400765962 _Toc401110518 _Toc401110627 _Toc401110957 _Toc417118885 _Toc419615459 _Toc419615701 _Toc472153913 _Toc474830535 _Toc474830909 _Toc474835127 _Toc474835979 _Toc480169307 _Toc482779554 _Toc485188860 _Toc485190303 _Toc485200463 _Toc486233187 _Toc349963204 _Toc369417302 _Toc472476480 _Toc474835128 _Toc474835980 _Toc485188861 _Toc485190304 _Toc472476481 _Toc474835129 _Toc474835981 _Toc349446153 _Toc349446192 _Toc349963231 _Toc485188862 _Toc485190305 _Toc485188863 _Toc485190306 _Toc485188864 _Toc485190307 _Toc485188865 _Toc485190308 _Toc485188866 _Toc485190309 _Toc485188867 _Toc485190310 _Toc485188868 _Toc485190311 _Toc472476482 _Toc474835130 _Toc474835982 _Toc349446184 _Toc349963215 _Toc350048486 _Toc349963161 _Toc349963216 _Toc350125629 _Toc351353219 _Toc351792718 _Toc349963213 _Toc350048484 _Toc485188869 _Toc485190312 _Toc472476483 _Toc474835131 _Toc474835983 _Toc485188870 _Toc485190313 _Toc350155270 _Toc472476484 _Toc474835132 _Toc474835984 _Toc485188871 _Toc485190314 _Toc472476485 _Toc474835133 _Toc474835985 _Toc485188872 _Toc485190315 _Toc340380199 _Toc337508283 _Toc338127163 _Toc338127374 _Toc338127672 _Toc338218395 _Toc339704899 _Toc340365627 _Toc340380201 _Toc340547171 _Toc338221728 _Toc338847202 _Toc340380198 _Toc340547178 _Toc341256602 _Toc346612701 _Toc337603856 _Toc338217248 _Toc338227243 _Toc338847301 _Toc341257709 _Toc472476486 _Toc474835134 _Toc474835986 _Toc485190316 _Toc485188873 _Toc485190317 _Toc485188874 _Toc472476487 _Toc474835135 _Toc474835987 _Toc485188875 _Toc485190318 _Toc350157348 _Toc350157350 _Toc350157351 _Toc337508284 _Toc338127161 _Toc338127372 _Toc338127670 _Toc338218393 _Toc339704897 _Toc340365625 _Toc350157353 _Toc349977546 _Toc485188876 _Toc485190319 _Toc485188877 _Toc485190320 _Toc472476488 _Toc474835136 _Toc474835988 _Toc485188878 _Toc485190321 _Toc472476489 _Toc474835137 _Toc474835989 _Toc485188879 _Toc485190322 _Toc472476490 _Toc474835138 _Toc474835990 _Toc485190323 _Toc485188880 _Toc485190324 _Toc485188881 _Toc369417318 _Toc350125633 _Toc351353220 _Toc351792719 _Toc472476491 _Toc474835139 _Toc474835991 _Toc485188882 _Toc485190325 _Toc346855410 _Toc347286270 _Toc347287192 _Toc348431084 _Toc349967450 _Toc362747654 _Toc362915531 _Toc365431814 _Toc369417322 _Toc369417472 _Toc371903875 _Toc373034425 _Toc383328916 _Toc386525782 _Toc391278964 _Toc394920734 _Toc395079677 _Toc399050546 _Toc400765963 _Toc401110628 _Toc401110958 _Toc415390027 _Toc416409205 _Toc417118886 _Toc419615460 _Toc419615702 _Toc419677949 _Toc419867962 _Toc422135675 _Toc425225754 _Toc431091232 _Toc472153914 _Toc474830910 _Toc480169308 _Toc482779555 _Toc485200628 _Toc486233188 _Toc399050547 _Toc400765964 _Toc401110629 _Toc401110959 _Toc417118887 _Toc419615461 _Toc419615703 _Toc419677950 _Toc419867963 _Toc472153915 _Toc472476492 _Toc474830911 _Toc474835140 _Toc474835992 _Toc480169309 _Toc482779556 _Toc486233189 _Toc344790517 _Toc345837709 _Toc344790544 _Toc345837749 _Toc347286298 _Toc347287221 _Toc399050548 _Toc400765965 _Toc401110519 _Toc401110630 _Toc401110960 _Toc417118888 _Toc419615462 _Toc419615704 _Toc472153916 _Toc474830536 _Toc474830912 _Toc474835141 _Toc474835993 _Toc480169310 _Toc482779557 _Toc485188883 _Toc485190326 _Toc485200464 _Toc486233190 _Toc472476493 _Toc474835142 _Toc474835994 _Toc485188884 _Toc485190327 _Toc472476494 _Toc474835143 _Toc474835995 _Toc485188885 _Toc485190328 _Toc349967451 _Toc369417323 _Toc472476495 _Toc474835144 _Toc474835996 _Toc344790499 _Toc485188886 _Toc485190329 _Toc472476496 _Toc474835145 _Toc474835997 _Toc485188887 _Toc485190330 _Toc485188888 _Toc485190331 _Toc485188889 _Toc485190332 _Toc485188890 _Toc485190333 _Toc349967476 _Toc349967478 _Toc472476497 _Toc474835146 _Toc474835998 _Toc485188891 _Toc485190334 _Toc472476498 _Toc474835147 _Toc474835999 _Toc485188892 _Toc485190335 _Toc472476501 _Toc474835148 _Toc474836000 _Toc485188893 _Toc485190336 _Toc472476502 _Toc474835149 _Toc474836001 _Toc485188894 _Toc485190337 _Toc349967454 _Toc472476503 _Toc474835150 _Toc474836002 _Toc485188895 _Toc485190338 _Toc348431091 _Toc472476504 _Toc474835151 _Toc474836003 _Toc485188896 _Toc485190339 _Toc472476505 _Toc474835152 _Toc474836004 _Toc485188897 _Toc485190340 _Toc472476506 _Toc474835153 _Toc474836005 _Toc485188898 _Toc485190341 _Toc472476507 _Toc474835154 _Toc474836006 _Toc485188899 _Toc485190342 _Toc472476508 _Toc474835155 _Toc474836007 _Toc485188900 _Toc485190343 _Toc349967456 _Toc472476509 _Toc474835156 _Toc474836008 _Toc346855411 _Toc347286282 _Toc347287204 _Toc485188901 _Toc485190344 _Toc472476510 _Toc474835157 _Toc474836009 _Toc485188902 _Toc485190345 _Toc472476513 _Toc474835158 _Toc474836010 _Toc485188903 _Toc485190346 _Toc472476514 _Toc474835159 _Toc474836011 _Toc485188904 _Toc485190347 _Toc472476532 _Toc474835160 _Toc474836012 _Toc485188905 _Toc485190348 _Toc472476533 _Toc474835161 _Toc474836013 _Toc485188906 _Toc485190349 _Toc472476540 _Toc474835162 _Toc474836014 _Toc399050549 _Toc400765966 _Toc401110520 _Toc401110631 _Toc401110961 _Toc485188907 _Toc485190350 _Toc472476541 _Toc474835163 _Toc474836015 _Toc485188908 _Toc485190351 _Toc472476542 _Toc474835164 _Toc474836016 _Toc485188909 _Toc485190352 _Toc472476543 _Toc474835165 _Toc474836017 _Toc485188910 _Toc485190353 _Toc472476544 _Toc474835166 _Toc474836018 _Toc349967464 _Toc347286289 _Toc417118889 _Toc485188911 _Toc485190354 _Toc348431103 _Toc349967465 _Toc472476545 _Toc474835167 _Toc474836019 _Toc485188912 _Toc485190355 _Toc349967467 _Toc347287212 _Toc348431106 _Toc349967468 _Toc362747660 _Toc362915537 _Toc389534584 _Toc389548166 _Toc389980369 _Toc391795479 _Toc394210518 _Toc397141291 _Toc472476546 _Toc474835168 _Toc474836020 _Toc485188913 _Toc485190356 _Toc472476547 _Toc474835169 _Toc474836021 _Toc485188914 _Toc485190357 _Toc474830537 _Toc474830913 _Toc474835170 _Toc474836022 _Toc480169311 _Toc482779558 _Toc485188915 _Toc485190358 _Toc485200465 _Toc486233191 _Toc474835171 _Toc474836023 _Toc485188916 _Toc485190359 _Toc474835172 _Toc474836024 _Toc485188917 _Toc485190360 _Toc474835173 _Toc474836025 _Toc485188918 _Toc485190361 _Toc474835174 _Toc474836026 _Toc485188919 _Toc485190362 _Toc474835175 _Toc474836027 _Toc485188920 _Toc485190363 _Toc485188921 _Toc485190364 _Toc474835188 _Toc474836040 _Toc485188922 _Toc485190365 _Toc474835189 _Toc474836041 _Toc485188923 _Toc485190366 _Toc474835190 _Toc474836042 _Toc485188924 _Toc485190367 _Toc474835191 _Toc474836043 _Toc485188925 _Toc485190368 _Toc474835192 _Toc474836044 _Toc485188926 _Toc485190369 _Toc474835193 _Toc474836045 _Toc485188927 _Toc485190370 _Toc474835194 _Toc474836046 _Toc485188928 _Toc485190371 _Toc474835195 _Toc474836047 _Toc485188929 _Toc485190372 _Toc474835196 _Toc474836048 _Toc485188930 _Toc485190373 _Toc474835197 _Toc474836049 _Toc485188931 _Toc485190374 _Toc419615463 _Toc419615705 _Toc472153917 _Toc474830538 _Toc474830914 _Toc474835198 _Toc474836050 _Toc480169312 _Toc482779559 _Toc485188932 _Toc485190375 _Toc485200466 _Toc486233192 _Toc415390031 _Toc417118890 _Toc419615464 _Toc419615706 _Toc472153918 _Toc415390032 _Toc417118891 _Toc419615465 _Toc419615707 _Toc472153919 _Toc472476548 _Toc474835199 _Toc474836051 _Toc485188933 _Toc485190376 _Toc472476549 _Toc474835200 _Toc474836052 _Toc485188934 _Toc485190377 _Toc472153920 _Toc474830539 _Toc474830915 _Toc474835201 _Toc474836053 _Toc480169313 _Toc482779560 _Toc485188935 _Toc485190378 _Toc485200467 _Toc486233193 _Toc472476550 _Toc474835202 _Toc474836054 _Toc485188936 _Toc485190379 _Toc472476551 _Toc474835203 _Toc474836055 _Toc485188937 _Toc485190380 _Toc472476552 _Toc474835204 _Toc474836056 _Toc485188938 _Toc485190381 _Toc472476553 _Toc474835205 _Toc474836057 _Toc485188939 _Toc485190382 _Toc472476554 _Toc474835206 _Toc474836058 _Toc485188940 _Toc485190383 _Toc472476555 _Toc474835207 _Toc474836059 _Toc485188941 _Toc485190384 _Toc472476556 _Toc474835208 _Toc474836060 _Toc485188942 _Toc485190385 _Toc472476557 _Toc474835209 _Toc474836061 _Toc485188943 _Toc485190386 _Toc472476558 _Toc474835210 _Toc474836062 _Toc485188944 _Toc485190387 _Toc472476559 _Toc474835211 _Toc474836063 _Toc485188945 _Toc485190388 _Toc472476560 _Toc474835212 _Toc474836064 _Toc485188946 _Toc485190389 _Toc472476561 _Toc474835213 _Toc474836065 _Toc485188947 _Toc485190390 _Toc472476562 _Toc474835214 _Toc474836066 _Toc485188948 _Toc485190391 _Toc472476563 _Toc474835215 _Toc474836067 _Toc485188949 _Toc485190392 _Toc472476564 _Toc474835216 _Toc474836068 _Toc485188950 _Toc485190393 _Toc472476565 _Toc474835217 _Toc474836069 _Toc485188951 _Toc485190394 _Toc472476566 _Toc474835218 _Toc474836070 _Toc485188952 _Toc485190395 _Toc472476567 _Toc474835219 _Toc474836071 _Toc485188953 _Toc485190396 _Toc472476568 _Toc474835220 _Toc474836072 _Toc485188954 _Toc485190397 _Toc472476569 _Toc474835221 _Toc474836073 _Toc485188955 _Toc485190398 _Toc472476570 _Toc474835222 _Toc474836074 _Toc485188956 _Toc485190399 _Toc472476571 _Toc474835223 _Toc474836075 _Toc485188957 _Toc485190400 _Toc472476572 _Toc474835224 _Toc474836076 _Toc485188958 _Toc485190401 _Toc472476573 _Toc474835225 _Toc474836077 _Toc485188959 _Toc485190402 _Toc472476574 _Toc474835226 _Toc474836078 _Toc485188960 _Toc485190403 _Toc472476575 _Toc474835227 _Toc474836079 _Toc485188961 _Toc485190404 _Toc472476576 _Toc474835228 _Toc474836080 _Toc485188962 _Toc485190405 _Toc472476577 _Toc474835229 _Toc474836081 _Toc485188963 _Toc485190406 _Toc472476578 _Toc474835230 _Toc474836082 _Toc485188964 _Toc485190407 _Toc472476579 _Toc474835231 _Toc474836083 _Toc485188965 _Toc485190408 _Toc472476580 _Toc474835232 _Toc474836084 _Toc485188966 _Toc485190409 _Toc472476581 _Toc474835233 _Toc474836085 _Toc485188967 _Toc485190410 _Toc472476582 _Toc474835234 _Toc474836086 _Toc485188968 _Toc485190411 _Toc472476583 _Toc474835235 _Toc474836087 _Toc485188969 _Toc485190412 _Toc472476584 _Toc474835236 _Toc474836088 _Toc485188970 _Toc485190413 _Toc472476585 _Toc474835237 _Toc474836089 _Toc485188971 _Toc485190414 _Toc472476586 _Toc474835238 _Toc474836090 _Toc485188972 _Toc485190415 _Toc472476587 _Toc474835239 _Toc474836091 _Toc485188973 _Toc485190416 _Toc472476588 _Toc474835240 _Toc474836092 _Toc485188974 _Toc485190417 _Toc472476589 _Toc474835241 _Toc474836093 _Toc485188975 _Toc485190418 _Toc472476590 _Toc474835242 _Toc474836094 _Toc485188976 _Toc485190419 _Toc472476591 _Toc474835243 _Toc474836095 _Toc485188977 _Toc485190420 _Toc472476592 _Toc474835244 _Toc474836096 _Toc485188978 _Toc485190421 _Toc472476593 _Toc474835245 _Toc474836097 _Toc485188979 _Toc485190422 _Toc399050551 _Toc400765968 _Toc401110522 _Toc401110633 _Toc401110963 _Toc417118892 _Toc419615466 _Toc419615708 _Toc472153921 _Toc474830540 _Toc474830916 _Toc474835246 _Toc474836098 _Toc480169314 _Toc482779561 _Toc485188980 _Toc485190423 _Toc485200468 _Toc486233194 _Toc472476594 _Toc474835247 _Toc474836099 _Toc485188981 _Toc485190424 _Toc472476595 _Toc474835248 _Toc474836100 _Toc485188982 _Toc485190425 _Toc472476596 _Toc474835249 _Toc474836101 _Toc485188983 _Toc485190426 _Toc472476597 _Toc474835250 _Toc474836102 _Toc485188984 _Toc485190427 _Toc472476598 _Toc474835251 _Toc474836103 _Toc485188985 _Toc485190428 _Toc472476599 _Toc474835252 _Toc474836104 _Toc485188986 _Toc485190429 _Toc472476600 _Toc474835253 _Toc474836105 _Toc485188987 _Toc485190430 _Toc472476601 _Toc474835254 _Toc474836106 _Toc485188988 _Toc485190431 _Toc472476602 _Toc474835255 _Toc474836107 _Toc485188989 _Toc485190432 _Toc472476603 _Toc474835256 _Toc474836108 _Toc485188990 _Toc485190433 _Toc472476604 _Toc474835257 _Toc474836109 _Toc485188991 _Toc485190434 _Toc472476605 _Toc474835258 _Toc474836110 _Toc485188992 _Toc485190435 _Toc472476606 _Toc474835259 _Toc474836111 _Toc485188993 _Toc485190436 _Toc472476607 _Toc474835260 _Toc474836112 _Toc485188994 _Toc485190437 _Toc472476608 _Toc474835261 _Toc474836113 _Toc485188995 _Toc485190438 _Toc472476609 _Toc474835262 _Toc474836114 _Toc485188996 _Toc485190439 _Toc472476610 _Toc474835263 _Toc474836115 _Toc485188997 _Toc485190440 _Toc472476611 _Toc474835264 _Toc474836116 _Toc485188998 _Toc485190441 _Toc472476612 _Toc474835265 _Toc474836117 _Toc485188999 _Toc485190442 _Toc472476613 _Toc474835266 _Toc474836118 _Toc485189000 _Toc485190443 _Toc472476614 _Toc474835267 _Toc474836119 _Toc485189001 _Toc485190444 _Toc472476615 _Toc474835268 _Toc474836120 _Toc485189002 _Toc485190445 _Toc472476616 _Toc474835269 _Toc474836121 _Toc485189003 _Toc485190446 _Toc472476617 _Toc474835270 _Toc474836122 _Toc485189004 _Toc485190447 _Toc472476618 _Toc474835271 _Toc474836123 _Toc485189005 _Toc485190448 _Toc472476619 _Toc474835272 _Toc474836124 _Toc485189006 _Toc485190449 _Toc472476620 _Toc474835273 _Toc474836125 _Toc485189007 _Toc485190450 _Toc472476621 _Toc474835274 _Toc474836126 _Toc485189008 _Toc485190451 _Toc472476622 _Toc474835275 _Toc474836127 _Toc485189009 _Toc485190452 _Toc472476623 _Toc474835276 _Toc474836128 _Toc485189010 _Toc485190453 _Toc472476624 _Toc474835277 _Toc474836129 _Toc485189011 _Toc485190454 _Toc399050552 _Toc400765969 _Toc401110523 _Toc401110634 _Toc401110964 _Toc417118893 _Toc419615467 _Toc419615709 _Toc472153922 _Toc474830541 _Toc474830917 _Toc474835278 _Toc474836130 _Toc480169315 _Toc482779562 _Toc485189012 _Toc485190455 _Toc485200469 _Toc486233195 _Toc472476625 _Toc474835279 _Toc474836131 _Toc485189013 _Toc485190456 _Toc472476626 _Toc474835280 _Toc474836132 _Toc485189014 _Toc485190457 _Toc472476627 _Toc474835281 _Toc474836133 _Toc485189015 _Toc485190458 _Toc472476628 _Toc474835282 _Toc474836134 _Toc485189016 _Toc485190459 _Toc472476629 _Toc474835283 _Toc474836135 _Toc485189017 _Toc485190460 _Toc472476630 _Toc474835284 _Toc474836136 _Toc485189018 _Toc485190461 _Toc472476631 _Toc474835285 _Toc474836137 _Toc485189019 _Toc485190462 _Toc472476632 _Toc474835286 _Toc474836138 _Toc485189020 _Toc485190463 _Toc472476633 _Toc474835287 _Toc474836139 _Toc485189021 _Toc485190464 _Toc472476634 _Toc474835288 _Toc474836140 _Toc485189022 _Toc485190465 _Toc413803081 _Toc419615468 _Toc419615710 _Toc472153923 _Toc474830542 _Toc474830918 _Toc474835289 _Toc474836141 _Toc480169316 _Toc482779563 _Toc485189023 _Toc485190466 _Toc485200470 _Toc486233196 _Toc348431125 _Toc349967504 _Toc472476635 _Toc474835290 _Toc474836142 _Toc485189024 _Toc485190467 _Toc472476636 _Toc474835291 _Toc474836143 _Toc485189025 _Toc485190468 _Toc472476637 _Toc474835292 _Toc474836144 _Toc485189026 _Toc485190469 _Toc472476638 _Toc474835293 _Toc474836145 _Toc485189027 _Toc485190470 _Toc472476639 _Toc474835294 _Toc474836146 _Toc485189028 _Toc485190471 _Toc472476640 _Toc474835295 _Toc474836147 _Toc485189029 _Toc485190472 _Toc399050553 _Toc400765970 _Toc401110524 _Toc401110635 _Toc401110965 _Toc417118894 _Toc419615469 _Toc419615711 _Toc472153924 _Toc474830543 _Toc474830919 _Toc474835296 _Toc474836148 _Toc480169317 _Toc482779564 _Toc485189030 _Toc485190473 _Toc485200471 _Toc486233197 _Toc399050554 _Toc400765971 _Toc401110525 _Toc401110636 _Toc401110966 _Toc419615712 _Toc472153925 _Toc474830544 _Toc474830920 _Toc474835297 _Toc474836149 _Toc480169318 _Toc485189031 _Toc485190474 _Toc485200472 _Toc472476641 _Toc474835298 _Toc474836150 _Toc485189032 _Toc485190475 _Toc472476642 _Toc474835299 _Toc474836151 _Toc485189033 _Toc485190476 _Toc472476643 _Toc474835300 _Toc474836152 _Toc485189034 _Toc485190477 _Toc472476644 _Toc474835301 _Toc474836153 _Toc485189035 _Toc485190478 _Toc349529753 _Toc349967492 _Toc472476645 _Toc474835302 _Toc474836154 _Toc485189036 _Toc485190479 _Toc472476646 _Toc474835303 _Toc474836155 _Toc485189037 _Toc485190480 _Toc349529754 _Toc349967493 _Toc472476647 _Toc474835304 _Toc474836156 _Toc347303981 _Toc349102069 _Toc349529683 _Toc349529755 _Toc349967494 _Toc485189038 _Toc485190481 _Toc472476648 _Toc474835305 _Toc474836157 _Toc485189039 _Toc485190482 _Toc472476649 _Toc474835306 _Toc474836158 _Toc485189040 _Toc485190483 _Toc472476650 _Toc474835307 _Toc474836159 _Toc485189041 _Toc485190484 _Toc399050555 _Toc400765972 _Toc401110526 _Toc401110637 _Toc401110967 _Toc419615713 _Toc472153926 _Toc474830545 _Toc474830921 _Toc474835308 _Toc474836160 _Toc480169319 _Toc485189042 _Toc485190485 _Toc485200473 _Toc472476651 _Toc474835309 _Toc474836161 _Toc349529751 _Toc349967490 _Toc485189043 _Toc485190486 _Toc472476652 _Toc474835310 _Toc474836162 _Toc485189044 _Toc485190487 _Toc472476653 _Toc474835311 _Toc474836163 _Toc485189045 _Toc485190488 _Toc472476654 _Toc474835312 _Toc474836164 _Toc485189046 _Toc485190489 _Toc472476655 _Toc474835313 _Toc474836165 _Toc485189047 _Toc485190490 _Toc472476656 _Toc474835314 _Toc474836166 _Toc485189048 _Toc485190491 _Toc472476657 _Toc474835315 _Toc474836167 _Toc485189049 _Toc485190492 _Toc472476658 _Toc474835316 _Toc474836168 _Toc485189050 _Toc485190493 _Toc472476659 _Toc474835317 _Toc474836169 _Toc485189051 _Toc485190494 _Toc472476660 _Toc474835318 _Toc474836170 _Toc485189052 _Toc485190495 _Toc472476661 _Toc474835319 _Toc474836171 _Toc485189053 _Toc485190496 _Toc472476662 _Toc474835320 _Toc474836172 _Toc485189054 _Toc485190497 _Toc474830546 _Toc474830922 _Toc474835321 _Toc474836173 _Toc480169320 _Toc417118895 _Toc419615470 _Toc419615714 _Toc472153927 _Toc482779565 _Toc485189055 _Toc485190498 _Toc485200474 _Toc486233198 _Toc472476663 _Toc474835322 _Toc474836174 _Toc485189056 _Toc485190499 _Toc472476664 _Toc474835323 _Toc474836175 _Toc485189057 _Toc485190500 _Toc472476665 _Toc474835324 _Toc474836176 _Toc485189058 _Toc485190501 _Toc472476666 _Toc474835325 _Toc474836177 _Toc485189059 _Toc485190502 _Toc472476667 _Toc474835326 _Toc474836178 _Toc485189060 _Toc485190503 _Toc472476668 _Toc474835327 _Toc474836179 _Toc485189061 _Toc485190504 _Toc466098879 _Toc474830547 _Toc474830923 _Toc474835328 _Toc474836180 _Toc480169321 _Toc482779566 _Toc485189062 _Toc485190505 _Toc485200475 _Toc486233199 _Toc474835329 _Toc474836181 _Toc464114437 _Toc464114537 _Toc464274107 _Toc464961615 _Toc485189063 _Toc485190506 _Toc474835330 _Toc474836182 _Toc485189064 _Toc485190507 _Toc474835331 _Toc474836183 _Toc485189065 _Toc485190508 _Toc474835332 _Toc474836184 _Toc485189066 _Toc485190509 _Toc464114438 _Toc464114538 _Toc464274108 _Toc464961616 _Toc474835333 _Toc474836185 _Toc485189067 _Toc485190510 _Toc474835334 _Toc474836186 _Toc485189068 _Toc485190511 _Toc391278975 _Toc394920744 _Toc395079687 _Toc399050556 _Toc400765973 _Toc401110638 _Toc401110968 _Toc415390041 _Toc416409218 _Toc417118899 _Toc419615471 _Toc419615715 _Toc419677962 _Toc419867975 _Toc422135688 _Toc425225767 _Toc431091245 _Toc472153928 _Toc474830924 _Toc480169322 _Toc482779567 _Toc485200640 _Toc486233200 _Toc371903880 _Toc373034432 _Toc383328917 _Toc386525783 _Toc399050557 _Toc400765974 _Toc401110639 _Toc401110969 _Toc417118900 _Toc419615472 _Toc419615716 _Toc419677963 _Toc419867976 _Toc472153929 _Toc472476669 _Toc474830925 _Toc474835335 _Toc474836187 _Toc480169323 _Toc350150035 _Toc369417370 _Toc349963223 _Toc482779568 _Toc486233201 _Toc472153930 _Toc474830548 _Toc474830926 _Toc474835336 _Toc474836188 _Toc480169324 _Toc482779569 _Toc485189069 _Toc485190512 _Toc485200476 _Toc486233202 _Toc369417376 _Toc472476670 _Toc474835337 _Toc474836189 _Toc349963225 _Toc485189070 _Toc485190513 _Toc472476671 _Toc474835338 _Toc474836190 _Toc485189071 _Toc485190514 _Toc472476672 _Toc474835339 _Toc474836191 _Toc485189072 _Toc472476673 _Toc474835340 _Toc474836192 _Toc485189073 _Toc485190515 _Toc350150072 _Toc369417389 _Toc472476674 _Toc474835341 _Toc474836193 _Toc485189074 _Toc485190516 _Toc350150070 _Toc365431144 _Toc472476675 _Toc474835342 _Toc474836194 _Toc485189075 _Toc485190517 _Toc472476676 _Toc474835343 _Toc474836195 _Toc371903881 _Toc373034433 _Toc383328918 _Toc386525784 _Toc485189076 _Toc485190518 _Toc472476677 _Toc474835344 _Toc474836196 _Toc485189077 _Toc485190519 _Toc472476678 _Toc474835345 _Toc474836197 _Toc399050558 _Toc400765975 _Toc401110527 _Toc401110640 _Toc401110970 _Toc485189078 _Toc485190520 _Toc472476679 _Toc474835346 _Toc474836198 _Toc485189079 _Toc485190521 _Toc474835347 _Toc474836199 _Toc485189080 _Toc474835348 _Toc474836200 _Toc485190522 _Toc472476680 _Toc474835349 _Toc474836201 _Toc485190523 _Toc485189081 _Toc485190524 _Toc485190525 _Toc485189082 _Toc485190526 _Toc485190527 _Toc485189083 _Toc485190528 _Toc485190529 _Toc485189084 _Toc485190530 _Toc485190531 _Toc485189085 _Toc485190532 _Toc485190533 _Toc485189086 _Toc485190534 _Toc485190535 _Toc485189087 _Toc485190536 _Toc485189088 _Toc485190537 _Toc472476681 _Toc474835350 _Toc474836202 _Toc485189089 _Toc485190538 _Toc472476682 _Toc474835351 _Toc474836203 _Toc485189090 _Toc485190539 _Toc472476683 _Toc474835352 _Toc474836204 _Toc485189091 _Toc485190540 _Toc472476684 _Toc474835353 _Toc474836205 _Toc485189092 _Toc485190541 _Toc472476685 _Toc474835354 _Toc474836206 _Toc485189093 _Toc485190542 _Toc417118901 _Toc419615473 _Toc419615717 _Toc472153931 _Toc474830549 _Toc474830927 _Toc474835355 _Toc474836207 _Toc480169325 _Toc482779570 _Toc485189094 _Toc485190543 _Toc485200477 _Toc486233203 _Toc369417379 _Toc472476686 _Toc474835356 _Toc474836208 _Toc485189095 _Toc485190544 _Toc472476687 _Toc474835357 _Toc474836209 _Toc485189096 _Toc485190545 _Toc472476688 _Toc474835358 _Toc474836210 _Toc485189097 _Toc485190546 _Toc472476689 _Toc474835359 _Toc474836211 _Toc485189098 _Toc485190547 _Toc472476690 _Toc474835360 _Toc474836212 _Toc485189099 _Toc485190548 _Toc472476691 _Toc474835361 _Toc474836213 _Toc485189100 _Toc485190549 _Toc472476692 _Toc474835362 _Toc474836214 _Toc485189101 _Toc485190550 _Toc472476693 _Toc474835363 _Toc474836215 _Toc485189102 _Toc485190551 _Toc472476694 _Toc474835364 _Toc474836216 _Toc485189103 _Toc485190552 _Toc472476695 _Toc474835365 _Toc474836217 _Toc485189104 _Toc485190553 _Toc472476696 _Toc474835366 _Toc474836218 _Toc485189105 _Toc485190554 _Toc472476697 _Toc474835367 _Toc474836219 _Toc485189106 _Toc485190555 _Toc472476698 _Toc474835368 _Toc474836220 _Toc485189107 _Toc485190556 _Toc371903882 _Toc373034434 _Toc383328919 _Toc386525785 _Toc472476699 _Toc350041352 _Toc474835369 _Toc474836221 _Toc485189108 _Toc485190557 _Toc472476700 _Toc474835370 _Toc474836222 _Toc485189109 _Toc485190558 _Toc350041350 _Toc472476701 _Toc474835371 _Toc474836223 _Toc485189110 _Toc485190559 _Toc472476702 _Toc474835372 _Toc474836224 _Toc485189111 _Toc485190560 _Toc472476703 _Toc474835373 _Toc474836225 _Toc485189112 _Toc485190561 _Toc472476704 _Toc474835374 _Toc474836226 _Toc485189113 _Toc485190562 _Toc472476705 _Toc474835375 _Toc474836227 _Toc485189114 _Toc485190563 _Toc472476706 _Toc474835376 _Toc474836228 _Toc485189115 _Toc485190564 _Toc350041376 _Toc472476707 _Toc474835377 _Toc474836229 _Toc485189116 _Toc485190565 _Toc472476708 _Toc474835378 _Toc474836230 _Toc485189117 _Toc485190566 _Toc472476709 _Toc474835379 _Toc474836231 _Toc485189118 _Toc485190567 _Toc348414491 _Toc472476710 _Toc474835380 _Toc474836232 _Toc485189119 _Toc485190568 _Toc472476711 _Toc474835381 _Toc474836233 _Toc485189120 _Toc485190569 _Toc472476712 _Toc474835382 _Toc474836234 _Toc485189121 _Toc485190570 _Toc350041370 _Toc472476713 _Toc474835383 _Toc474836235 _Toc485189122 _Toc485190571 _Toc472476714 _Toc474835384 _Toc474836236 _Toc485189123 _Toc485190572 _Toc350041373 _Toc472476715 _Toc474835385 _Toc474836237 _Toc485189124 _Toc485190573 _Toc472476716 _Toc474835386 _Toc474836238 _Toc485189125 _Toc485190574 _Toc472476717 _Toc474835387 _Toc474836239 _Toc485189126 _Toc485190575 _Toc472476718 _Toc474835388 _Toc474836240 _Toc485189127 _Toc485190576 _Toc350041366 _Toc472476719 _Toc474835389 _Toc474836241 _Toc485189128 _Toc485190577 _Toc472476720 _Toc474835390 _Toc474836242 _Toc485189129 _Toc485190578 _Toc472476721 _Toc474835391 _Toc474836243 _Toc485189130 _Toc485190579 _Toc472476722 _Toc474835392 _Toc474836244 _Toc485189131 _Toc485190580 _Toc472476723 _Toc474835393 _Toc474836245 _Toc485189132 _Toc485190581 _Toc472476724 _Toc474835394 _Toc474836246 _Toc485189133 _Toc485190582 _Toc399050559 _Toc400765976 _Toc401110528 _Toc401110641 _Toc401110971 _Toc417118902 _Toc419615474 _Toc419615718 _Toc472153932 _Toc474830550 _Toc474830928 _Toc474835395 _Toc474836247 _Toc480169326 _Toc482779571 _Toc485189134 _Toc485190583 _Toc485200478 _Toc486233204 _Toc369417382 _Toc350160528 _Toc472476725 _Toc474835396 _Toc474836248 _Toc485189135 _Toc485190584 _Toc472476726 _Toc474835397 _Toc474836249 _Toc485189136 _Toc485190585 _Toc472476727 _Toc474835398 _Toc474836250 _Toc485189137 _Toc485190586 _Toc472476728 _Toc474835399 _Toc474836251 _Toc485189138 _Toc485190587 _Toc472476729 _Toc474835400 _Toc474836252 _Toc485189139 _Toc485190588 _Toc472476730 _Toc474835401 _Toc474836253 _Toc485189140 _Toc485190589 _Toc472476731 _Toc474835402 _Toc474836254 _Toc485189141 _Toc485190590 _Toc472476732 _Toc474835403 _Toc474836255 _Toc485189142 _Toc485190591 _Toc472476733 _Toc474835404 _Toc474836256 _Toc485189143 _Toc485190592 _Toc472476734 _Toc474835405 _Toc474836257 _Toc485189144 _Toc485190593 _Toc472476735 _Toc474835406 _Toc474836258 _Toc485189145 _Toc485190594 _Toc472476736 _Toc474835407 _Toc474836259 _Toc485189146 _Toc485190595 _Toc472476737 _Toc474835408 _Toc474836260 _Toc485189147 _Toc485190596 _Toc350160531 _Toc472476740 _Toc474835409 _Toc474836261 _Toc485189148 _Toc485190597 _Toc472476741 _Toc474835410 _Toc474836262 _Toc485189149 _Toc485190598 _Toc350160533 _Toc472476742 _Toc474835411 _Toc474836263 _Toc485189150 _Toc485190599 _Toc472476743 _Toc474835412 _Toc474836264 _Toc485189151 _Toc485190600 _Toc350160536 _Toc472476744 _Toc347635733 _Toc474835413 _Toc474836265 _Toc485189152 _Toc485190601 _Toc472476745 _Toc474835414 _Toc474836266 _Toc485189153 _Toc485190602 _Toc350160548 _Toc472476746 _Toc474835415 _Toc474836267 _Toc485189154 _Toc485190603 _Toc472476747 _Toc474835416 _Toc474836268 _Toc485189155 _Toc485190604 _Toc350160554 _Toc472476748 _Toc474835417 _Toc474836269 _Toc346612695 _Toc485189156 _Toc485190605 _Toc472476749 _Toc474835418 _Toc474836270 _Toc485189157 _Toc485190606 _Toc350160544 _Toc472476750 _Toc474835419 _Toc474836271 _Toc341257858 _Toc347288555 _Toc485189158 _Toc485190607 _Toc472476751 _Toc474835420 _Toc474836272 _Toc485189159 _Toc485190608 _Toc350160545 _Toc373034436 _Toc383328920 _Toc386525786 _Toc399050560 _Toc400765977 _Toc401110529 _Toc401110642 _Toc401110972 _Toc417118903 _Toc419615475 _Toc419615719 _Toc472153933 _Toc474830551 _Toc474830929 _Toc474835421 _Toc474836273 _Toc480169327 _Toc371903884 _Toc482779572 _Toc485189160 _Toc485190609 _Toc485200479 _Toc486233205 _Toc472476752 _Toc474835422 _Toc474836274 _Toc373034437 _Toc485189161 _Toc485190610 _Toc472476753 _Toc474835423 _Toc474836275 _Toc485189162 _Toc485190611 _Toc472476754 _Toc474835424 _Toc474836276 _Toc485189163 _Toc485190612 _Toc472476755 _Toc474835425 _Toc474836277 _Toc485189164 _Toc485190613 _Toc472476756 _Toc474835426 _Toc474836278 _Toc485189165 _Toc485190614 _Toc472476757 _Toc474835427 _Toc474836279 _Toc485189166 _Toc485190615 _Toc472476758 _Toc474835428 _Toc474836280 _Toc485189167 _Toc485190616 _Toc472476759 _Toc474835429 _Toc474836281 _Toc485189168 _Toc485190617 _Toc472476760 _Toc474835430 _Toc474836282 _Toc485189169 _Toc485190618 _Toc472476761 _Toc474835431 _Toc474836283 _Toc485189170 _Toc485190619 _Toc472476762 _Toc474835432 _Toc474836284 _Toc485189171 _Toc485190620 _Toc472476763 _Toc474835433 _Toc474836285 _Toc485189172 _Toc485190621 _Toc472476764 _Toc474835434 _Toc474836286 _Toc485189173 _Toc485190622 _Toc383328923 _Toc386525789 _Toc399050561 _Toc400765978 _Toc401110530 _Toc401110643 _Toc401110973 _Toc417118904 _Toc419615476 _Toc419615720 _Toc472153934 _Toc474830552 _Toc474830930 _Toc474835435 _Toc474836287 _Toc480169328 _Toc371903887 _Toc482779573 _Toc485189174 _Toc485190623 _Toc485200480 _Toc486233206 _Toc472476765 _Toc474835436 _Toc474836288 _Toc485189175 _Toc485190624 _Toc472476766 _Toc474835437 _Toc474836289 _Toc485189176 _Toc485190625 _Toc371903888 _Toc373034442 _Toc383328924 _Toc386525790 _Toc399050562 _Toc400765979 _Toc401110531 _Toc401110644 _Toc401110974 _Toc415390047 _Toc417118905 _Toc419615477 _Toc419615721 _Toc472153935 _Toc474830553 _Toc474830931 _Toc474835438 _Toc474836290 _Toc480169329 _Toc482779574 _Toc485189177 _Toc485190626 _Toc485200481 _Toc486233207 _Toc472476767 _Toc474835439 _Toc474836291 _Toc485189178 _Toc485190627 _Toc472476768 _Toc474835440 _Toc474836292 _Toc485189179 _Toc485190628 _Toc399050563 _Toc400765980 _Toc401110532 _Toc401110645 _Toc401110975 _Toc417118906 _Toc419615478 _Toc419615722 _Toc472153936 _Toc474830554 _Toc474830932 _Toc474835441 _Toc474836293 _Toc480169330 _Toc482779575 _Toc485189180 _Toc485190629 _Toc485200482 _Toc486233208 _Toc350150064 _Toc472476769 _Toc474835442 _Toc474836294 _Toc369417386 _Toc485189181 _Toc485190630 _Toc472476770 _Toc474835443 _Toc474836295 _Toc485189182 _Toc485190631 _Toc350150065 _Toc472476771 _Toc474835444 _Toc474836296 _Toc485189183 _Toc485190632 _Toc472476772 _Toc474835445 _Toc474836297 _Toc485189184 _Toc485190633 _Toc472476773 _Toc474835446 _Toc474836298 _Toc485189185 _Toc485190634 _Toc472476774 _Toc474835447 _Toc474836299 _Toc485189186 _Toc485190635 _Toc350160557 _Toc472476775 _Toc474835448 _Toc474836300 _Toc485189187 _Toc485190636 _Toc472476776 _Toc474835449 _Toc474836301 _Toc485189188 _Toc485190637 _Toc350160558 _Toc472476777 _Toc474835450 _Toc474836302 _Toc485189189 _Toc485190638 _Toc472476778 _Toc474835451 _Toc474836303 _Toc485189190 _Toc485190639 _Toc472476779 _Toc474835452 _Toc474836304 _Toc485189191 _Toc485190640 _Toc472476780 _Toc474835453 _Toc474836305 _Toc485189192 _Toc485190641 _Toc399050564 _Toc400765981 _Toc401110533 _Toc401110646 _Toc401110976 _Toc417118907 _Toc419615479 _Toc419615723 _Toc472153937 _Toc474830555 _Toc474830933 _Toc474835454 _Toc474836306 _Toc480169331 _Toc482779576 _Toc485189193 _Toc485190642 _Toc485200483 _Toc486233209 _Toc472476783 _Toc474835455 _Toc474836307 _Toc485189194 _Toc485190643 _Toc472476784 _Toc474835456 _Toc474836308 _Toc485189195 _Toc485190644 _Toc472476785 _Toc474835457 _Toc474836309 _Toc485189196 _Toc485190645 _Toc472476786 _Toc474835458 _Toc474836310 _Toc485189197 _Toc485190646 _Toc350150083 _Toc472476791 _Toc474835459 _Toc474836311 _Toc485189198 _Toc485190647 _Toc472476792 _Toc474835460 _Toc474836312 _Toc485189199 _Toc485190648 _Toc350150085 _Toc472476793 _Toc474835461 _Toc474836313 _Toc485189200 _Toc485190649 _Toc472476794 _Toc474835462 _Toc474836314 _Toc485189201 _Toc485190650 _Toc474830556 _Toc474830934 _Toc474835463 _Toc474836315 _Toc480169332 _Toc369417398 _Toc369417475 _Toc482779577 _Toc485189202 _Toc485190651 _Toc485200484 _Toc486233210 _Toc369417400 _Toc472476795 _Toc474835464 _Toc474836316 _Toc485189203 _Toc485190652 _Toc472476796 _Toc474835465 _Toc474836317 _Toc485189204 _Toc485190653 _Toc472476797 _Toc474835466 _Toc474836318 _Toc485189205 _Toc485190654 _Toc472476798 _Toc474835467 _Toc474836319 _Toc485189206 _Toc485190655 _Toc472476799 _Toc474835468 _Toc474836320 _Toc485189207 _Toc485190656 _Toc472476800 _Toc474835469 _Toc474836321 _Toc485189208 _Toc485190657 _Toc472476801 _Toc474835470 _Toc474836322 _Toc485189209 _Toc485190658 _Toc472476802 _Toc474835471 _Toc474836323 _Toc485189210 _Toc485190659 _Toc472476803 _Toc474835472 _Toc474836324 _Toc485189211 _Toc485190660 _Toc472476804 _Toc474835473 _Toc474836325 _Toc485189212 _Toc485190661 _Toc472476805 _Toc474835474 _Toc474836326 _Toc485189213 _Toc485190662 _Toc472476806 _Toc474835475 _Toc474836327 _Toc485189214 _Toc485190663 _Toc472476807 _Toc474835476 _Toc474836328 _Toc485189215 _Toc485190664 _Toc472476808 _Toc474835477 _Toc474836329 _Toc485189216 _Toc485190665 _Toc472476809 _Toc474835478 _Toc474836330 _Toc485189217 _Toc485190666 _Toc472476810 _Toc474835479 _Toc474836331 _Toc485189218 _Toc485190667 _Toc472476811 _Toc474835480 _Toc474836332 _Toc485189219 _Toc485190668 _Toc472476814 _Toc474835481 _Toc474836333 _Toc485189220 _Toc485190669 _Toc472476815 _Toc474835482 _Toc474836334 _Toc485189221 _Toc485190670 _Toc371903890 _Toc373034444 _Toc383328926 _Toc386525792 _Toc399050566 _Toc400765983 _Toc401110535 _Toc401110648 _Toc401110978 _Toc417118909 _Toc419615481 _Toc419615725 _Toc472153939 _Toc474830557 _Toc474830935 _Toc474835483 _Toc474836335 _Toc480169333 _Toc482779578 _Toc485189222 _Toc485190671 _Toc485200485 _Toc486233211 _Toc371903891 _Toc373034445 _Toc383328927 _Toc386525793 _Toc399050567 _Toc400765984 _Toc401110536 _Toc401110649 _Toc401110979 _Toc415390052 _Toc417118910 _Toc419615482 _Toc419615726 _Toc472153940 _Toc474830558 _Toc474830936 _Toc474835484 _Toc474836336 _Toc480169334 _Toc482779579 _Toc485189223 _Toc485190672 _Toc485200486 _Toc486233212 _Toc350150066 _Toc369417403 _Toc472476816 _Toc474835485 _Toc474836337 _Toc485189224 _Toc485190673 _Toc485189225 _Toc485190674 _Toc371903892 _Toc373034446 _Toc383328928 _Toc386525794 _Toc399050568 _Toc400765985 _Toc401110537 _Toc401110650 _Toc401110980 _Toc415390053 _Toc417118911 _Toc419615483 _Toc419615727 _Toc472153941 _Toc474830559 _Toc474830937 _Toc474835487 _Toc474836339 _Toc480169335 _Toc482779580 _Toc485189226 _Toc485190675 _Toc485200487 _Toc486233213 _Toc472476818 _Toc474835488 _Toc474836340 _Toc485189227 _Toc485190676 _Toc472476819 _Toc474835489 _Toc474836341 _Toc485189228 _Toc485190677 _Toc472476820 _Toc474835490 _Toc474836342 _Toc485189229 _Toc485190678 _Toc472476821 _Toc474835491 _Toc474836343 _Toc485189230 _Toc485190679 _Toc369417435 _Toc369417479 _Toc371903873 _Toc373034421 _Toc383328929 _Toc386525795 _Toc371903894 _Toc373034450 _Toc391278990 _Toc394920759 _Toc395079700 _Toc399050569 _Toc400765986 _Toc401110651 _Toc401110981 _Toc415390054 _Toc416409231 _Toc417118912 _Toc419615484 _Toc419615728 _Toc419677975 _Toc419867988 _Toc422135701 _Toc425225781 _Toc431091259 _Toc472153942 _Toc474830938 _Toc480169336 _Toc482779581 _Toc485200654 _Toc486233214 _Toc399050570 _Toc400765987 _Toc401110652 _Toc401110982 _Toc417118913 _Toc419615485 _Toc419615729 _Toc419677976 _Toc419867989 _Toc472153943 _Toc472476822 _Toc474830939 _Toc474835492 _Toc474836344 _Toc480169337 _Toc482779582 _Toc486233215 _Toc399050571 _Toc400765988 _Toc401110538 _Toc401110653 _Toc401110983 _Toc417118914 _Toc419615486 _Toc419615730 _Toc472153944 _Toc474830560 _Toc474830940 _Toc474835493 _Toc474836345 _Toc480169338 _Toc482779583 _Toc485189231 _Toc485190680 _Toc485200488 _Toc486233216 _Toc472476823 _Toc474835494 _Toc474836346 _Toc350125615 _Toc351353215 _Toc351792714 _Toc485189232 _Toc485190681 _Toc472476824 _Toc474835495 _Toc474836347 _Toc485189233 _Toc485190682 _Toc369417439 _Toc472476825 _Toc474835496 _Toc474836348 _Toc485189234 _Toc485190683 _Toc472476826 _Toc474835497 _Toc474836349 _Toc485189235 _Toc485190684 _Toc472476827 _Toc474835498 _Toc474836350 _Toc485189236 _Toc485190685 _Toc472476828 _Toc474835499 _Toc474836351 _Toc485189237 _Toc485190686 _Toc472476829 _Toc474835500 _Toc474836352 _Toc485189238 _Toc485190687 _Toc472476830 _Toc474835501 _Toc474836353 _Toc485189239 _Toc485190688 _Toc369417445 _Toc472476831 _Toc474835502 _Toc474836354 _Toc485189240 _Toc485190689 _Toc472476832 _Toc474835503 _Toc474836355 _Toc485189241 _Toc485190690 _Toc472476833 _Toc474835504 _Toc474836356 _Toc383328935 _Toc386525801 _Toc399050572 _Toc400765989 _Toc401110539 _Toc401110654 _Toc401110984 _Toc383328930 _Toc386525796 _Toc485189242 _Toc472476834 _Toc474835505 _Toc474836357 _Toc485189243 _Toc485190691 _Toc417118915 _Toc419615487 _Toc419615731 _Toc472153945 _Toc474830561 _Toc474830941 _Toc474835506 _Toc474836358 _Toc480169339 _Toc482779584 _Toc485189244 _Toc485190692 _Toc485200489 _Toc486233217 _Toc472476835 _Toc474835507 _Toc474836359 _Toc485189245 _Toc485190693 _Toc472476836 _Toc474835508 _Toc474836360 _Toc485189246 _Toc485190694 _Toc472476837 _Toc474835509 _Toc474836361 _Toc485189247 _Toc485190695 _Toc472476838 _Toc474835510 _Toc474836362 _Toc485189248 _Toc485190696 _Toc391278993 _Toc394920763 _Toc395079704 _Toc399050573 _Toc400765990 _Toc401110655 _Toc401110985 _Toc415390058 _Toc416409235 _Toc417118916 _Toc419615488 _Toc419615732 _Toc419677979 _Toc419867992 _Toc422135705 _Toc425225785 _Toc431091263 _Toc472153946 _Toc474830942 _Toc480169340 _Toc482779585 _Toc485200658 _Toc486233218 _Toc399050574 _Toc400765991 _Toc401110656 _Toc401110986 _Toc417118917 _Toc419615489 _Toc419615733 _Toc419677980 _Toc419867993 _Toc472153947 _Toc472476839 _Toc474830943 _Toc474835511 _Toc474836363 _Toc480169341 _Toc482779586 _Toc486233219 _Toc399050575 _Toc400765992 _Toc401110540 _Toc401110657 _Toc401110987 _Toc417118918 _Toc419615490 _Toc419615734 _Toc472153948 _Toc474830562 _Toc474830944 _Toc474835512 _Toc474836364 _Toc480169342 _Toc482779587 _Toc485189249 _Toc485190697 _Toc485200490 _Toc486233220 _Toc383328931 _Toc386525797 _Toc399050576 _Toc400765993 _Toc401110541 _Toc401110658 _Toc401110988 _Toc415390061 _Toc417118919 _Toc419615491 _Toc419615735 _Toc472153949 _Toc474830563 _Toc474830945 _Toc474835513 _Toc474836365 _Toc480169343 _Toc482779588 _Toc485189250 _Toc485190698 _Toc485200491 _Toc486233221 _Toc472476840 _Toc474835514 _Toc474836366 _Toc371903895 _Toc373034451 _Toc369417409 _Toc369417477 _Toc485189251 _Toc485190699 _Toc472476841 _Toc474835515 _Toc474836367 _Toc485189252 _Toc485190700 _Toc383328932 _Toc386525798 _Toc399050577 _Toc400765994 _Toc401110542 _Toc401110659 _Toc401110989 _Toc415390062 _Toc417118920 _Toc419615492 _Toc419615736 _Toc472153950 _Toc474830564 _Toc474830946 _Toc474835516 _Toc474836368 _Toc480169344 _Toc482779589 _Toc485189253 _Toc485190701 _Toc485200492 _Toc486233222 _Toc472476842 _Toc474835517 _Toc474836369 _Toc369417423 _Toc485189254 _Toc485190702 _Toc472476843 _Toc474835518 _Toc474836370 _Toc485189255 _Toc485190703 _Toc369417429 _Toc472476844 _Toc474835519 _Toc474836371 _Toc485189256 _Toc485190704 _Toc472476845 _Toc474835520 _Toc474836372 _Toc485189257 _Toc485190705 _Toc472476846 _Toc474835521 _Toc474836373 _Toc485189258 _Toc485190706 _Toc472476847 _Toc474835522 _Toc474836374 _Toc485189259 _Toc485190707 _Toc472476848 _Toc474835523 _Toc474836375 _Toc485189260 _Toc485190708 _Toc472476849 _Toc474835524 _Toc474836376 _Toc485189261 _Toc485190709 _Toc472476850 _Toc474835525 _Toc474836377 _Toc485189262 _Toc485190710 _Toc472476851 _Toc474835526 _Toc474836378 _Toc485189263 _Toc485190711 _Toc472476852 _Toc474835527 _Toc474836379 _Toc485189264 _Toc485190712 _Toc472476853 _Toc474835528 _Toc474836380 _Toc485189265 _Toc485190713 _Toc472476854 _Toc474835529 _Toc474836381 _Toc485189266 _Toc485190714 _Toc472476855 _Toc474835530 _Toc474836382 _Toc485189267 _Toc485190715 _Toc472476856 _Toc474835531 _Toc474836383 _Toc485189268 _Toc485190716 _Toc472476857 _Toc474835532 _Toc474836384 _Toc371903896 _Toc373034452 _Toc383328933 _Toc485189269 _Toc485190717 _Toc485189270 _Toc485190718 _Toc472476870 _Toc474835545 _Toc474836397 _Toc386525799 _Toc399050578 _Toc400765995 _Toc401110543 _Toc401110660 _Toc401110990 _Toc415390063 _Toc485189271 _Toc485190719 _Toc485189272 _Toc485190720 _Toc472476883 _Toc474835558 _Toc474836410 _Toc485189273 _Toc485190721 _Toc472476884 _Toc474835559 _Toc474836411 _Toc485189274 _Toc485190722 _Toc472476885 _Toc474835560 _Toc474836412 _Toc485189275 _Toc485190723 _Toc472476886 _Toc474835561 _Toc474836413 _Toc485189276 _Toc485190724 _Toc472476887 _Toc474835562 _Toc474836414 _Toc485189277 _Toc485190725 _Toc472476888 _Toc474835563 _Toc474836415 _Toc485189278 _Toc485190726 _Toc472476889 _Toc474835564 _Toc474836416 _Toc485189279 _Toc485190727 _Toc472476890 _Toc474835565 _Toc474836417 _Toc485189280 _Toc485190728 _Toc472476891 _Toc474835566 _Toc474836418 _Toc485189281 _Toc485190729 _Toc472476892 _Toc474835567 _Toc474836419 _Toc485189282 _Toc485190730 _Toc472476893 _Toc474835568 _Toc474836420 _Toc485189283 _Toc485190731 _Toc472476894 _Toc474835569 _Toc474836421 _Toc485189284 _Toc485190732 _Toc472476895 _Toc474835570 _Toc474836422 _Toc485189285 _Toc485190733 _Toc417118921 _Toc419615493 _Toc419615737 _Toc472153951 _Toc474830565 _Toc474830947 _Toc474835571 _Toc474836423 _Toc480169345 _Toc482779590 _Toc485189286 _Toc485190734 _Toc485200493 _Toc486233223 _Toc472476896 _Toc474835572 _Toc474836424 _Toc485189287 _Toc485190735 _Toc472476897 _Toc474835573 _Toc474836425 _Toc485189288 _Toc485190736 _Toc472476898 _Toc474835574 _Toc474836426 _Toc485189289 _Toc485190737 _Toc472476899 _Toc474835575 _Toc474836427 _Toc485189290 _Toc485190738 _Toc472476900 _Toc474835576 _Toc474836428 _Toc485189291 _Toc485190739 _Toc472476901 _Toc474835577 _Toc474836429 _Toc485189292 _Toc485190740 _Toc472476902 _Toc474835578 _Toc474836430 _Toc485189293 _Toc485190741 _Toc472476903 _Toc474835579 _Toc474836431 _Toc485189294 _Toc485190742 _Toc472476904 _Toc474835580 _Toc474836432 _Toc485189295 _Toc485190743 _Toc472476905 _Toc474835581 _Toc474836433 _Toc485189296 _Toc485190744 _Toc472476906 _Toc474835582 _Toc474836434 _Toc485189297 _Toc485190745 _Toc472476907 _Toc474835583 _Toc474836435 _Toc485189298 _Toc485190746 _Toc472476908 _Toc474835584 _Toc474836436 _Toc485189299 _Toc485190747 _Toc472476909 _Toc474835585 _Toc474836437 _Toc485189300 _Toc485190748 _Toc485189301 _Toc485190749 _Toc485189302 _Toc485190750 _Toc472476922 _Toc474835598 _Toc474836450 _Toc485189303 _Toc485190751 _Toc485189304 _Toc485190752 _Toc485189305 _Toc485190753 _Toc472476935 _Toc474835611 _Toc474836463 _Toc371903897 _Toc373034453 _Toc485189306 _Toc485190754 _Toc472476936 _Toc474835612 _Toc474836464 _Toc485189307 _Toc485190755 _Toc472476937 _Toc474835613 _Toc474836465 _Toc485189308 _Toc485190756 _Toc485189309 _Toc485190757 _Toc485189310 _Toc485190758 _Toc472476950 _Toc474835626 _Toc474836478 _Toc485189311 _Toc485190759 _Toc485189312 _Toc485190760 _Toc485189313 _Toc485190761 _Toc415390064 _Toc417118922 _Toc419615494 _Toc419615738 _Toc472153952 _Toc474830566 _Toc474830948 _Toc474835639 _Toc474836491 _Toc480169346 _Toc482779591 _Toc485189314 _Toc485190762 _Toc485200494 _Toc486233224 _Toc474835653 _Toc474836505 _Toc485189315 _Toc485189316 _Toc485190763 _Toc485189317 _Toc485190764 _Toc485189318 _Toc485190765 _Toc485189319 _Toc485190766 _Toc485189320 _Toc485190767 _Toc485189321 _Toc485190768 _Toc485189322 _Toc485190769 _Toc485189323 _Toc485190770 _Toc485189324 _Toc485190771 _Toc485189325 _Toc485190772 _Toc485189326 _Toc485190773 _Toc485189327 _Toc485190774 _Toc399050579 _Toc400765996 _Toc383328934 _Toc386525800 _Toc401110544 _Toc401110661 _Toc401110991 _Toc417118923 _Toc419615495 _Toc419615739 _Toc472153953 _Toc474830567 _Toc474830949 _Toc474835655 _Toc474836507 _Toc480169347 _Toc482779592 _Toc485189328 _Toc485190775 _Toc485200495 _Toc486233225 _Toc369417413 _Toc472476976 _Toc474835656 _Toc474836508 _Toc485189329 _Toc485190776 _Toc472476977 _Toc474835657 _Toc474836509 _Toc485189330 _Toc485190777 _Toc472476978 _Toc474835658 _Toc474836510 _Toc485189331 _Toc485190778 _Toc472476979 _Toc474835659 _Toc474836511 _Toc485189332 _Toc485190779 _Toc472476980 _Toc474835660 _Toc474836512 _Toc485189333 _Toc485190780 _Toc472476981 _Toc474835661 _Toc474836513 _Toc485189334 _Toc485190781 _Toc472476982 _Toc474835662 _Toc474836514 _Toc485189335 _Toc485190782 _Toc472476983 _Toc474835663 _Toc474836515 _Toc485189336 _Toc485190783 _Toc472476984 _Toc474835664 _Toc474836516 _Toc485189337 _Toc485190784 _Toc472476985 _Toc474835665 _Toc474836517 _Toc485189338 _Toc485190785 _Toc472476986 _Toc474835666 _Toc474836518 _Toc485189339 _Toc485190786 _Toc472476987 _Toc474835667 _Toc474836519 _Toc485189340 _Toc485190787 _Toc472476988 _Toc474835668 _Toc474836520 _Toc485189341 _Toc485190788 _Toc472476989 _Toc474835669 _Toc474836521 _Toc485189342 _Toc485190789 _Toc472476990 _Toc474835670 _Toc474836522 _Toc485189343 _Toc485190790 _Toc369417416 _Toc472476991 _Toc474835671 _Toc474836523 _Toc485189344 _Toc485190791 _Toc472476992 _Toc474835672 _Toc474836524 _Toc485189345 _Toc485190792 _Toc472476993 _Toc474835673 _Toc474836525 _Toc485189346 _Toc485190793 _Toc472476994 _Toc474835674 _Toc474836526 _Toc485189347 _Toc485190794 _Toc472476995 _Toc474835675 _Toc474836527 _Toc485189348 _Toc485190795 _Toc472476996 _Toc474835676 _Toc474836528 _Toc485189349 _Toc485190796 _Toc472476997 _Toc474835677 _Toc474836529 _Toc485189350 _Toc485190797 _Toc472476998 _Toc474835678 _Toc474836530 _Toc485189351 _Toc485190798 _Toc472476999 _Toc474835679 _Toc474836531 _Toc485189352 _Toc485190799 _Toc472477000 _Toc474835680 _Toc474836532 _Toc485189353 _Toc485190800 _Toc472477001 _Toc474835681 _Toc474836533 _Toc485189354 _Toc485190801 _Toc472477002 _Toc474835682 _Toc474836534 _Toc485189355 _Toc485190802 _Toc472477003 _Toc474835683 _Toc474836535 _Toc485189356 _Toc485190803 _Toc371903899 _Toc373034457 _Toc485190804 _Toc485189357 _Toc485190805 _Toc385819029 _Toc386525802 _Toc399050580 _Toc400765997 _Toc401110545 _Toc401110662 _Toc401110992 _Toc417118924 _Toc419615496 _Toc419615740 _Toc472153954 _Toc474830568 _Toc474830950 _Toc474835684 _Toc474836536 _Toc480169348 _Toc369417456 _Toc369417481 _Toc482779593 _Toc485189358 _Toc485190806 _Toc485200496 _Toc486233226 _Toc386525803 _Toc389546461 _Toc399050581 _Toc400765998 _Toc401110546 _Toc401110663 _Toc401110993 _Toc415390067 _Toc417118925 _Toc419615497 _Toc419615741 _Toc472153955 _Toc474830569 _Toc474830951 _Toc474835685 _Toc474836537 _Toc480169349 _Toc482779594 _Toc485189359 _Toc485190807 _Toc485200497 _Toc486233227 _Toc472477004 _Toc474835686 _Toc474836538 _Toc485189360 _Toc485190808 _Toc472477005 _Toc474835687 _Toc474836539 _Toc485189361 _Toc485190809 _Toc472477006 _Toc474835688 _Toc474836540 _Toc485189362 _Toc485190810 _Toc472477007 _Toc474835689 _Toc474836541 _Toc485189363 _Toc485190811 _Toc389546462 _Toc399050582 _Toc400765999 _Toc401110547 _Toc401110664 _Toc401110994 _Toc415390068 _Toc417118926 _Toc419615498 _Toc419615742 _Toc472153956 _Toc474830570 _Toc474830952 _Toc474835690 _Toc474836542 _Toc480169350 _Toc482779595 _Toc485189364 _Toc485190812 _Toc485200498 _Toc486233228 _Toc472477008 _Toc474835691 _Toc474836543 _Toc485189365 _Toc485190813 _Toc472477009 _Toc474835692 _Toc474836544 _Toc485189366 _Toc485190814 _906539800 _906539936 _Toc472477010 _Toc474835693 _Toc474836545 _Toc485190815 _Toc472477011 _Toc474835694 _Toc474836546 _Toc485189367 _Toc485190816 _Toc472477012 _Toc474835695 _Toc474836547 _Toc485190817 _Toc472477014 _Toc474835697 _Toc474836549 _Toc485190818 _Toc472477016 _Toc474835699 _Toc474836551 _Toc485190819 _Toc472477020 _Toc474835703 _Toc474836555 _Toc485190820 _Toc485189368 _Toc485190821 _Toc394920775 _Toc395079716 _Toc399050609 _Toc400766026 _Toc401110691 _Toc401111021 _Toc415390096 _Toc416409246 _Toc417118927 _Toc419615499 _Toc419615743 _Toc419677990 _Toc419868003 _Toc422135716 _Toc425225796 _Toc431091274 _Toc472153957 _Toc474830953 _Toc480169351 _Toc482779596 _Toc485200669 _Toc486233229 _Toc373034473 _Toc383328967 _Toc384454545 _Toc386525823 _Toc399050610 _Toc400766027 _Toc401110692 _Toc401111022 _Toc417118928 _Toc419615500 _Toc419615744 _Toc472153958 _Toc472477024 _Toc474830954 _Toc474835707 _Toc474836559 _Toc480169352 _Toc482779597 _Toc486233230 _Toc369417482 _Toc373034474 _Toc474835708 _Toc474836560 _Toc480169353 _Toc482779598 _Toc485189369 _Toc485190822 _Toc485200499 _Toc486233231toplist _Toc474835709 _Toc474836561 _Toc480169354 _Toc482779599 _Toc485190823 _Toc485190824 _Toc485190825 _Toc485190826 _Toc485190827 _Toc485190828 _Toc485190829 _Toc485190830 _Toc485190831 _Toc485190832 _Toc485190833 _Toc485190834 _Toc485190835 _Toc485190836 _Toc485190837 _Toc485190838 _Toc485190839 _Toc485190840 _Toc485190841 _Toc485190842 _Toc485190843 _Toc485190844 _Toc485190845 _Toc485190846 _Toc485190847 _Toc485190848 _Toc485190849 _Toc485190850 _Toc485190851 _Toc485190852 _Toc485190853 _Toc485190854 _Toc485190855 _Toc485190856 _Toc485190857 _Toc485190858 _Toc485190859 _Toc485190860 _Toc485190861 _Toc485190862 _Toc485190863 _Toc485190864 _Toc485190865 _Toc485190866 _Toc485190867 _Toc485190868 _Toc485190869 _Toc485190870 _Toc485190871 _Toc485190872 _Toc485190873 _Toc485190874 _Toc485190875 _Toc485190876 _Toc485190877 _Toc485190878 _Toc485190879 _Toc485190880 _Toc485190881 _Toc485190882 _Toc485190883 _Toc485190884 _Toc485190885 _Toc485190886 _Toc485190887 _Toc485190888 _Toc485190889 _Toc485190890 _Toc485190891 _Toc485190892 _Toc485190893 _Toc485190894 _Toc485190895 _Toc485190896 _Toc485190897 _Toc485190898 _Toc485190899 _Toc485190900 _Toc485190901 _Toc485190902 _Toc485190903 _Toc485190904 _Toc485190905 _Toc485190906 _Toc485190907 _Toc485190908 _Toc485190909 _Toc485190910 _Toc485190911 _Toc485190912 _Toc485190913 _Toc485190914 _Toc485190915 _Toc485190916 _Toc485190917 _Toc485190918 _Toc485190919 _Toc485190920 _Toc485190921 _Toc485190922 _Toc485190923 _Toc485190924 _Toc485190925 _Toc485190926 _Toc485190927 _Toc485190928 _Toc485190929 _Toc485190930 _Toc485190931 _Toc485190932 _Toc485190933 _Toc485190934 _Toc485190935 _Toc485190936 _Toc485190937 _Toc485190938 _Toc485190939 _Toc485190940 _Toc485190941 _Toc485190942 _Toc485190943 _Toc485190944 _Toc485190945 _Toc485190946 _Toc485190947 _Toc485190948 _Toc485190949 _Toc485190950 _Toc485190951 _Toc485190952 _Toc485190953 _Toc485190954 _Toc485190955 _Toc485190956 _Toc485190957 _Toc485190958 _Toc485190959 _Toc485190960 _Toc485190961 _Toc485190962 _Toc485190963 _Toc485190964 _Toc485190965 _Toc485190966 _Toc485190967 _Toc485190968 _Toc485190969 _Toc485190970 _Toc485190971 _Toc485190972 _Toc485190973 _Toc485190974 _Toc485190975 _Toc485190976 _Toc485190977 _Toc485190978 _Toc485190979 _Toc485190980 _Toc485190981 _Toc485190982 _Hlt485189371 _Hlt485189372 _Toc485190983 _Toc485190984 _Toc485190985 _Toc485190986 _Toc485190987 _Toc485190988 _Toc485190989 _Toc485190990 _Toc485190991 _Toc485190992 _Toc485190993 _Toc485190994 _Toc485190995 _Toc485190996 _Toc485190997 _Toc485190998 _Toc485190999 _Toc485191000 _Toc485191001 _Toc485191002 _Toc485191003 _Toc485191004 _Toc485191005 _Toc485191006 _Toc485191007 _Toc485191008 _Toc485191009 _Toc485191010 _Toc485191011 _Toc485191012 _Toc485191013 _Toc485191014 _Toc485191015 _Toc485191016 _Toc485191017 _Toc485191018 _Toc485191019 _Toc485191020 _Toc485191021 _Toc485191022 _Toc485191023 _Toc485191024 _Toc485191025 _Toc485191026 _Toc485191027 _Toc485191028 _Toc485191029 _Toc485191030 _Toc485189370 _Toc485191031 _Toc485200500 _Toc486233232midlist _Toc417118929 _Toc419615501 _Toc419615745 _Toc472153959 _Toc472477025 _Toc474830955 _Toc474835710 _Toc474836562 _Toc480169355 _Toc482779600 _Toc486233233 _Toc472153960 _Toc472477026 _Toc474830956 _Toc474835711 _Toc474836563 _Toc480169356 _Toc482779601 _Toc486233234  r!r!r!r!r!r!r!r!r!r!r!r!r!BBBBBBBBBBBBBFFFFFFFFFFFFFFFFFFFFFFFFFFFF;L;L;L;L;L;L;L;L;LFMFMFMFMFMFMFMFMFMFMFMFMFMFMFMMMMMMMMMMMMMMMMMMMMMMTTTTTTTTTTTTTTTTTTTTT\\\\\\\\\\\\\\\\\\\\\\\\ffffffffffffff.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.gooooooooooooooooottt%%%%%%%%%%%%%%%%%%%%%%%%OOOOOOOOOOOOOOOOOOOOYYYYYYYYYYYYYYYYYYYYYYYYYY]]]]]]]]]]]]]]]]]]]]---------------AAAAAAAAAAAAAAAGGGGGGGGGGGGGGGGGGGGGGGGGG;;;;;$$$$$YYYYY3\\\\\eeeeMM MM>>ggggPPPPPaaaaN N N N N | | | | | ggggSSSS!!!!%%%%%&&&&&&&&&&'&'&'&'&'&0&0&0&0&0&:&:&:&:&:&F&F&F&F&F&O&O&O&O&O&X&X&X&X&X&b&b&b&b&b&h&h&h&h&h&q&q&q&q&q&z&z&z&z&z&1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2|2|2|2|2|2|222222x3x3x3x355557777u9u9u9u9::::F>F>F>>>>>>>>U@U@U@hHhHhHNNN8U8U8UUUUUeWeW5Y5Y5Y]]]q`q`q`ubcd^g^g^g^g^ggggggrh:lmmmmmmmmmmmmmmmmmmmmNnNnNnNnNnNnNnNnNnNnNnNnNnNnNnNnnnnnn#t#t#t#t#ttttttttttt[w}}}}}}j}j}j}j}j} kk#pJYY\Iqáááááá֡֡֡֡"""""jj׫8 <<OOOOOOOOOOOOOOOOOOOOOOOOOOвввввв``ĹĹ  ܽܽܽܽܽ99999TTTTT~~~~~FFFFFFVVVVVVVVVV/////\\\\\HHHHH/////ee.......ttttttttttttttttttttttttttt"""""+88888_____%%%%%,,,,,88888\\\\\CCCCCQQQQQ]]]]]iiiiivvvvvmmmmm{{{{{<<<<<aaaaagggggpppppyyyyy     UUUUUbbbbb@ @ @ @ @                        ''$$$$$$$$$$$$$$$$$$$xxxxx?????vvvvv%%%%%%%%%%%%%%%%%%%%%'''''''''''''''1)1),,--0000223355555555555555555555:;=;=;=;=;======EEEEEEEEEEEEEFFFFFFFFFFFFFFNGGGGGGRSV?X?X?X?X?X?X?X?X~_````aaaaa b b b b bcccc(d(dqeueueueueeeeeehhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh=h=h=h=h=h=hnnnnnnnnnnnnnnnnnnnSrSrSrSrSrrrrrrrrrrrrrrsssssssuuxxLzLz~~~~~=====TTTTT]RRRRRKKKKKMMMMMÉÉÉÉÉEEEEEЎЎЎЎЎߏߏߏߏߏߏߏߏߏߏҔ=====>>>>>>>>>>++++YYYYnnnnQQQQbbbbgggg????֯֯֯֯""""             $$%%%UUUUURhhhhhhhhhh     =====     MMMMM[[[[[gggggppppp}}}}}JJJJJ     #####,,,,,66666BBBBBKKKKKTTTTT^^^^^dddddppppp|||||)))))ppppp     HHHHHIIIII44444jjjjj[[[[[ZZZZZxxxxxnnnnn,,,,,,,,,,,,,,,,,,,#####:::::xxxxxzzzzzssssssssssssssmmmmm%%%%%     99999ZZZZZ"""""""X"X"X"X"X"a"a"$$$$$$$$$$$$$$$%%%%%&&&&&&&&&&&&&&&&&&&&Q'Q'Q'Q'Q'Q'Q''''''(((((@(@(@(@(@()))))k)k)k)k)k)----------..........2222222222U4U4U4U4U4U4U4U4U4U4U4U4U4U4#7#7#7#7#7d7d7d7d7d777777888888888899999<<<<<<<<<<<F?F?F?F?F?F?F?F?????@@@@j@j@j@j@ZAZAZAZAZAZAZAZAAAAAfBfBfBfBfBfBfBfBfBfBfBfBfBfBfBfBfBfBfBfBfBfBfBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBpBhFhFhFhFhFhFhFhFhFhFhFGGGGGGGGGGGGHHHHOIOIOIOIOI:J:J:J:J:J:J:J?J?J}J}J}J}J}JKKKKKKKKKLLLLL}O}O}O}O}O}O}O}O}O}OOOOOOOOO$Q$Q$QSRSRSRSRRRS.T.TU,V,VWWWXYY{]]]v^^^``aaaaa.b.b.b.b.bobobobobobcccccccccccccccmdmdmdmdmdmdmdmdmdmdmdmdmdmdeeeeeepfpfpfpfpf~f~f~f~f~fffffffffffffffffffffffffffffffffffffffffffffffffffbhbhbhbhbhbhZiZiZiZiiiiiillllll-m-m-m-m-mppppp5q5q5q5q5q0r0r0r0r0r{r{r{r{r{rttttttitititititvvvvv3w3w3w3w3w3wwwwwwwwwwwxxxxxxxxxxx { { { { { {D{D{D{D{D{|||||7|7|7|7|7|)})})})})})}|}|}|}|}|}     PPPPP22222ccccccc*****66666?????LLLLLRRRRR^^^^^gggggÓÓÓsssssnnnnnnȕȕȕȕȕזזזזזޘޘޘޘޘyyyyyyyyyyyyyyyyyyyyyyy,,,,,,ǛǛǛǛǛӛӛӛӛӛߛߛߛߛߛ#####,,,,,55555''''''''''''''''''''''pppppiiiiiiiiiiiiiiiiiiiiiiiiܥܥܥܥܥssssssߨߨߨߨߨ     ˬˬˬˬˬ!!!!!!uuuuuGGGGGvvvvv۲۲۲۲۲ִִִִִ,,,,,,wwwwwZZZZZZ*****99999HHHHHXXXXXdddddsssss;;;;;qqqqqGGGGGGGGGGGGGGGGGGGGGGGGIIIIIII$$$$$$$$$$$$$$$$$$$$$$$${{{{{ddddd6666666666666666666$$$$$ttttt\\\\\\\\\\\\\\ddddddddddddddddddd@@@@@@@@@ppppp))))))))))))))))))))))zzzzzz999999          -----33333?????KKKKK,,,,,,,,__))%%%%%33333?????HHHHHUUUUUaaaaammmmmvvvvv(((((44444@@@@@IIIIIVVVVV\\\\\hhhhhqqqqq       3 3 [ [ [ [ [     ddddd  ttttttttttttttt 88888%%%%%+++++77777@@@@@l l l l l z z z z z                                                   h"h"###M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'M'),,,,,,,,,,,,,,,,,,,,,=-=-=-=-=------/////%0%0%0%0%0!5!5!5!5!5!5!5!5!5!5!5!5!5!5!5!5!5!5!5!5!56666666666777777M7M7M7M7M78888[;[;[;[;C=C=C=C=>>>>&?&???????????????????????@@@@@@@@@@@@@@@@@@@#@@@@@@@@@@@ A A A ABB!CpCFFFFGGG$G.G4G=GFGUU"VFVkVwVVVVVVVWWWWWWWWWXXXXXXXY+YOYsYYYYYjjjjjjjjk kk klllmmm%m.m8m>mJmVmo-o9oBoOo[ogopo}oooo|||||| }} }&}2};}"0<ER^jsÅυۅ (1̊ڊ#2BHWfʐ֐#/;N\hq~ǒlzʓГܓǗ՗ %1: ,8DMZ`luesÚɚ՚ޚAAAA\xxxxxxxxxxx]]]]]]]]  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@AB]^_CDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`a}~bcdefghijklmnopqrstuvwxyz{|      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\`abcdefghijklpmnoqrstuvwx|}yz{~stuvwxyz      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefglhjkimnopqrstuvwxyz{|}~!"#$%&'()*+ ,-     ./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[s\]^_`abcdefghijklmnopqrtuvwxyz{|}~       !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~     !"#$%&'()*+,-./01234567:89;<=>?@ABJKLMNOCDEFGHIPQRUVWSTXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~DEFJKLMNOP      !"#$%&'()*+,23456789-./01:;<=>?@ABCRSTGHIUQ VWXYZrstuvwxyz{|}~[\]^_`abcdefghijklmnopq       !"#$%&'()*+,-./9;012345678:<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~                           ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~                            ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~                            ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 > ? 7 8 9 : ; < = @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n o p q r s t u v | } ~  w x y z {           *                " # $ % & ' ( ! ) * + , - . / 0 { | } ~ 1 2 3 4 5 6 7 8 9 :  ; < = > ? @ A B C D E F G ] ^ _ H I J K L M N O P Q R S T U V W X Y Z [ \ ` a b c d e f g h i j k l m n o p q r s t u v w x y z ] ^ _ `                           ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~       UV !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTWXYZ[\]^_`abcdefvghijklmnopqrstuwxyz{|}~      !"#$%&'()+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<cde=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abfghijklmnopqrsz{|}~tuvwxyij     h !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefgijklmnopqrstuvwxyz{|}~      !"#$%kl&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghmnopqrstuvwxyz{|}~      !"#${|%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqr}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklm@n@opqrstuvwxyz{|}~"C  !!!!!!!!!!!!!BBBBBBBBBBBBBFFFFFFFFFFFFFFFFFFFFdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMdMNNNNNNNNNNNNNNNNNNNNN%U%U%U%U%U%U%U%U%U%U%U%U%U%U%U%U%U%U%U%U%U\\\\\\\\8]8]8]8]8]8]8]8]8]8]8]8]8]8])f)f)f)f)f)f)f)f)f)f)f)f)f)f)f)f)f)f)f)f)f)f)f)fcgcgcgcgcgcgcgcgcgcgcgcgcgcgcgdgdgdgdgdgooooooooooooooXrXrXrttt444444444444444444444444XXXXXXXXXXXXXXXXXXXXaaaaaaaaayyyyyyyyyyyyyyyyy11111111111111111111111111CVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]QQQQQ(((((WWWWWaaaaa[[[[[dddddOOO)6666LLLUUZZ=....................MMMM{ { { { {      \"\"\"\"%%%%%&&&&&&&&&&&&&&&/&/&/&/&/&8&8&8&8&8&E&E&E&E&E&N&N&N&N&N&W&W&W&W&W&`&`&`&`&`&g&g&g&g&g&p&p&p&p&p&y&y&y&y&y&&&&&& 2 2 2 2'2'2'2'2'2'2'2'2'2'2'2'2'2'2'2'2'2'2'2'2222222222223333,6,6,6,677779999::::>>>>>>>>>>@@@HHHhNhNNUUUUUUUWzY{Y{Y]F^F^F^```bcseggggggggggh|l n n n n n n n n n n n n n n n n n n n nnnnnnnnnnnststststst|t|t|t|t|t}i}i}i}i}i}i}r}r}r}r}r}jwXiiաաաաաաաաաաա!!!!*****NNNNܦܦܦܦ k;DDcccccccccccccccccccccccccc     ù̹̹  XXĽ۽۽۽۽۽88888AAAAA}}}}}J[[[[[dddddGGGGGPPPPPcccccmm.....tt          !!!!!!*****     ^^^^^ggggg$$$$$-----aaaaa*****77777[[[[[PPPPP\\\\\hhhhhtttttzzzzz;;;;;_____fffffoooooxxxxx    TTTTT]]]]]aaaaajjjjj? ? ? ? ? H H H H H e e e e e                         &&//:::::::::::::::::::uuuuu~~~~~!!!!!%%%%%%%%%%%%%%%%%%%%%%%%%%%''''''''''''u)u)--(.(.0022445555555555555555;=e=e=e========FFFFFFFFFFFFFGGGGHHHHHHHHHHHHHHHHR(TW_``aaaaaaaaaa b b b b bbbbbbccc'd0d0dueueueueueueueeeeeeeeeeehhhhhhhhhhhhhhhhhhhhhhh>>>GGGG!!!!****%%FFFyyyyy<<<<<EEEEEZZZZZfffffooooo{{{{{XXXXX"""""+++++44444AAAAAJJJJJSSSSS\\\\\cccccooooo{{{{{'''''                   oooooxxxxxBBBBB     HHHHHQQQQQiiiiirrrrrwwwwwDDDDDDDDDDDDDDDDDDD""""".....wwwww$$$$$-----88888AAAAAW"W"W"W"W"W"W"`"`"`"`"`"$$$$$$$$$$$$%%%%%&&&&&#&#&#&#&#&&&&&&&&&&&&&&&&''''''''''((?(?(?(?(?(H(H(H(H(H(j)j)j)j)j)s)s)s)s)s)----------..........2222222222u4u4u4u4u4u4u4u4u4u4v4v4v4v4c7c7c7c7c7l7l7l7l7l788888888889999999999<<<<<<<<<<<????????i@i@i@i@i@i@i@i@r@r@r@r@AAAAAAAAAAAAoBoBoBoBoBoBoBoBoBoBoBoBoBoBoBoBoBoBoBoBoBoBoBpBpBpBpBpBpBpBpBpBBBBBBBBBBBBBBBBBBBBBBFFFFFFFFFFFGGGGGGGGGGGGGGNINININIWIWIWIWIWIdJdJnJnJ|J|J|J|J|JJJJJJLLLLLLLLLLOOOOOOOOOO$P$P$P;Q;QQRRR-T6T6T+V4V4VWWW?YYY]]]^^^aaaaaaaaaanbnbnbnbnbwbwbwbwbwbccccccccccddddddddddddddddddddddd f f f f f f}f}f}f}f}ffffffffffffffffffffffffffffffffffffffffffffffffffffffffiiiiiiiiiil,m,m,m,m,m,m5m5m5m5m5m4q4q4q4q4q=q=q=q=q=qzrzrzrzrzrrrrrrJthththththtqtqtqtqtqt2w2w2w2w2w;w;w;w;w;w;wwwwwwwwwwwxxxxxxxxxxx{C{C{C{C{C{L{L{L{L{L{6|6|6|6|6|?|?|?|?|?|j}j}j}j}{}{}}}}}}OOOOO[[[[[11111:::::)))))55555>>>>>JJJJJQQQQQ]]]]]fffffrrrrr؄$$$$$eOrrrrr{{{{{nǕǕЕЕЕЕЕ֖֖֖֖֖֖ߖߖߖߖߖ՘ݘݘݘݘݘyyyiiiiiƛƛƛƛƛқққққޛޛޛޛޛ"""""+++++44444====='';;;;;;;;;;;;;;;;;;;;;izzzzzzzzzzzzzzzzzzzzzzzzɤɤɤɤɤɤɤɤɤɤɤɤɤɤɤɤɤɤɤϥۥۥۥۥۥ(((((ĬɬɬɬɬɬӬӬӬӬӬlttttt}}}}}uuuuu~~~~~ڲڲڲڲڲմմմմմմ޴޴޴޴޴1vvvvv          o)))))88888GGGGGVVVVVcccccrrrrrpppppyyyyyRRRRRRRRRRRRRRRRRRRRRRRRdBBBBBBBBBBBBBBBBBBBBBBBBRRRRRRRRRRRRRRRRRRRssssss|||||zzzzzzzzzzzzzzzzzzzzz+++++++++++++++++oo{{ooooo{{{{{555555555555555555555555||||||     +++++22222>>>>>JJJJJVVVVV,^^^^^gg(((((1122222>>>>>GGGGGSSSSS`````llllluuuuu''''''''''''''''''''''''&&&&&33333?????HHHHHTTTTT[[[[[gggggppppp|||||     2 2 v v          ccEEEwwwwww#####*****66666?????KKKKK      y y y y y                                                        #$$M'M'['p'p'p'p'p'p'p'p'p'p'p'p'p'p'p'p'p'p'p'p',,,,,,,,,,,,,,,,,,,,,,----------$0$0$0$0$00000000000U5U5U5U5U5U5U5U5U5U5U5U5U5U5U5U5U5U5U5U5U56666666666777777777777L7L7L7L7U7U7U7U7U7l8l8l8l8;;;;====%?%?%?%?.?.?@@@@@@@@@@@@@@@@@@@@@@"@"@"@"@"@"@"@"@"@"@"@"@"@"@"@"@"@"@"@@@AA A A A A A ABCoCCFFFGGG#G,G3G*urn:schemas-microsoft-com:office:smarttags PostalCode9*urn:schemas-microsoft-com:office:smarttagsState=*urn:schemas-microsoft-com:office:smarttags PlaceType=*urn:schemas-microsoft-com:office:smarttags PlaceName;*urn:schemas-microsoft-com:office:smarttagsaddress8*urn:schemas-microsoft-com:office:smarttagsCityB*urn:schemas-microsoft-com:office:smarttagscountry-region9*urn:schemas-microsoft-com:office:smarttagsplace 1  du&v||Z3\ZZZZ]]]]]]²̲ͲӲԲٲ۲½ý^_bcTUXZcd#$-.56:;EFLNWX]^efrs::::::DDDDDDDDDDDDDDcccccc҉Ӊډۉ   +,68EFHIgimnyzŋNj׋ً܋݋  lnqr89>?efijÍύэ܍ݍސߐ#%()^`cd%&./79@AHJQRWX_`ђӒՒגڒے35:;68;=JKMNUVghno ,.9:@AKL\]`afgrtwy$%,-JKRT\]deklwxיؙۙܙ  YZ]^bcrsyzӚԚښۚVW\]morsBCKMUV[]eflnvw!#%'89@BOPXZabhinoz{ݡޡ  KLUW_`gh!#&(45@BOPSTXYmorsǣɣѣңף٣ߣ(),-ϥХڥۥ&(+,PQ[\ªê   DEHIMN\]gh)+0189HIOPvx}~?ACOYr(++A]үү 8Bnxְgg߱5@DO~ֲKKLWp  0 h -+e+`EbE!NNOOPPRVSfThT}XY p7p#q>qu&vxx||~~~Z3\lpÇć2@AACDEFGHIJKLOYr(A] 8Bnxְ߱5@DO~ֲLWp ::::::::::::::::::9oGG#HsHwIIcKKKKY\YZZ]^d{eܓ@ѳ=[)O\@ACOYr(++A]үүӯӯ   8BEEnx{{ְgghh߱5@DORR~ֲKKLWZZp  @AACDEFGHIJKLOYr(A] 8Bnxְ߱5@DO~ֲLWp |d}@~n lN$('5v@ܩtf-,)M:0)|'Iް{ Q^`.^`.88^8`.^`. ^`OJQJo( ^`OJQJo( 88^8`OJQJo( ^`OJQJo(hh^h`. hh^h`OJQJo(*@xh h^h`OJQJo(@xh ^`OJQJo(o@xh 8^8`OJQJo(@xh ^`OJQJo(@xh ^`OJQJo(o@xh p^p`OJQJo(@xh  ^ `OJQJo(@xh @ ^@ `OJQJo(o@xh  ^ `OJQJo(@xh h^h`OJQJo(@xh ^`OJQJo(o@xh 8^8`OJQJo(@xh ^`OJQJo(@xh ^`OJQJo(o@xh p^p`OJQJo(@xh  ^ `OJQJo(@xh @ ^@ `OJQJo(o@xh  ^ `OJQJo( h^h`OJQJo( ^`OJQJo(o pp^p`OJQJo( @ @ ^@ `OJQJo( ^`OJQJo(o ^`OJQJo( ^`OJQJo( ^`OJQJo(o PP^P`OJQJo(@xh h^h`OJQJo(@xh ^`OJQJo(o@xh 8^8`OJQJo(@xh ^`OJQJo(@xh ^`OJQJo(o@xh p^p`OJQJo(@xh  ^ `OJQJo(@xh @ ^@ `OJQJo(o@xh  ^ `OJQJo(o~ f-,WXM:0{ QlX~}||'I(Q @h h^h`OJQJo(W @ ^`OJQJo(X e@xh h^h`OJQJo(xX @t@h h^h`OJQJo(L         @ @%Zi  tpo r!BFFGGGGG"H#HLHrHsHHHHIvIwIIII=JJJKbKcKKKKK9L:Lbc|dddddddd ee"e.e/e5e>eGePeQe]efeoexeyeze{effkmogooo78cMB\]>}~.%%%%%&&&'&0&9&:&F&O&X&a&b&h&q&z&&&.bcw+,8\ ,BCQ]iuvC3Vlm{<`agpy?XYZZZZ[ [ [[[[["[#[/[3[4[6LM[gp|}!  #,56BKT]^dp|y-'23Xcdlyz{CDX{ 'LLLLLLL@MAMkMMMMNN6NsNtNN O O3O{O|Oe!f"f6fYfofpf~fffffffffffffffcׁ*6?KLR^gst,jkǛӛߛ#,5>?*9HWXds/78CINO]ino~!)/0GNTU\otu9}~  ,-3?KWX@$%3?HTUamv('(4@IUV\hq}~FG[~ 8xy$%+7@LMS  2 U k l z               BB[BBBBB C!CpCCCFFFFFFFFFGGGG$G-G.G4G=GFGOGPGUUUUUUU"VFVjVkVwVVVVVVVVWWLWMWaWWWWWWWWWWWWWWXXX X!XUXVXjXXXXXXXYY+YOYsYYYYYYYY_j`jsjjjjjjjjjjjjkk kk k,k-kllllllllmmmm%m.m7m8m>mJmVmbmcmnnnooo-o9oBoNoOo[ogopo|o}oooooos|t||||||||||| }}} }&}2};}G}H}Ӂԁ !"0<EQR^jsfg{Åυۅ (1:;}~ˊ̊ڊ#2ABHWfuvmnʐ֐#/;GH7MN\hq}~ǒӒԒ2UklzɓʓГܓxyƗǗ՗ %1:FG˜ +,8DMYZ`lu+NdesšÚɚ՚ޚҠӠ $%+4=FG#9:Hl -.4=FOPέ $0<HIOXajk׮ Dhiu $%+7@LM&/0<ENWX^jv(>?MYbno{nJ&239ENZ[45COXdeq}z{ ,-3<ENO (7FUV\kz#F\]kw +7@LMS_htu  '0<=IU^jkq}4JKYenz{efz$-9:Ai@1~ (&&`@``@UnknownGz Times New Roman5Symbol3& z Arial+  ?5 z Courier New;WingdingsA& Arial Narrow5"Geneva"h\=F\=F`F^ID *^ID *!xx4da 2QX ?%Z2CHardware Design Guide Version 3.0 for Microsoft Windows 2000 ServerH          Oh+'00 <H h t  DHardware Design Guide Version 3.0 for Microsoft Windows 2000 Server Normal.dot2Microsoft Office Word@@@Hsk@HskI^՜.+,D՜.+,    (08@ H *D  DHardware Design Guide Version 3.0 for Microsoft Windows 2000 Server TitleP :B_PID_LINKBASEA  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrtuvwxyz|}~Root Entry Fy?}kData  1TableaCWordDocumentN SummaryInformation(sDocumentSummaryInformation8{CompObjq  FMicrosoft Office Word Document MSWordDocWord.Document.89q