Startup Support Requirements

This section defines the BIOS and other requirements to support system startup.

System BIOS meets boot support requirements

Required

This requirement does not apply for DEC Alpha servers. Notice that the Extended System Configuration Data (ESCD) calling interface is not supported by Windows NT 5.0.

The requirements for boot support include the following:

• Support for unique system ID structure. The unique system ID structure is described in “Attachment B: Preboot Execution Environment” of Network PC System Design Guidelines, Version 1.0b or later.

In addition, the unique system ID 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 unique system ID on the system chassis or case, or printed on the shipping carton.

• Support for preboot execution environment. If a server provides support for network adapters that provide remote boot capabilities using DHCP and TFTP, the server must also provide support for preboot execution environment as described in “Attachment B: Preboot Execution Environment” of Network PC System Design Guidelines, Version 1.0b or later.
  
  
• Implementation of 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 BIOS. This capability prevents end users from accidentally or purposefully circumventing operating system-level security and control as applied by an administrator.
  
  
• BIOS boot support for CD drives. If a server includes a CD drive, the system BIOS or option ROM must support the No Emulation mode in El Torito—Bootable CD-ROM Format Specification, Version 1.0, by IBM and Phoenix Technologies Ltd., or an equivalent method that supports the Windows NT CD-ROM installation process.
  
  
• BIOS boot support for network adapter. 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 the Compaq, Intel, Phoenix BIOS Boot Specification, Version 1.01, which describes the requirements for Initial Program Load (IPL) devices.

The system 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 that would allow 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 the Compaq, Intel, Phoenix BIOS Boot Specification, Version 1.01. Note that this feature is a Hardware Design Guide Version 2.0 for Windows NT Server requirement, although it is optional in the BIOS Boot Specification.

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 actions. It is expected that F12 or another standard key sequence will become a requirement in a future version of this design guide.

• BIOS boot support for USB keyboards and hubs. For a server that includes a USB keyboard as the only keyboard in the system, the system BIOS must provide boot support for USB keyboards and hubs as defined in Universal Serial Bus PC Legacy Compatibility Specification, Version 0.9 or later.

The BIOS must also support the keyboard if attached to a hub. This support must provide the ability for the user to enter the system’s BIOS SETUP program and provide enough functionality to get USB-aware versions of Windows NT Server installed and booted.

• Implementation of BIOS updates. System administrators must be able to upgrade BIOS ROMs to a new image. The following methods can be used to meet this requirement:
  • The remote new system setup mechanism that will 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.

Recommended:

• 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.
  
  
• System BIOS support for console redirection of a serial port. This capability provides support during system startup for debugging and troubleshooting activities. The BIOS 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 BIOS and is intended to be usable by components as a diagnostic port in the event that system debugging is required by either the BIOS or the operating system.

Recommendations for boot support are:

• 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 the ACPI 1.0 specification, which states that the E820 specification has been updated and lists the new memory range types.
  
  
• System BIOS or option ROM provides boot support for ATAPI bootable floppy disk drive in compliance with ATAPI Removable Media BIOS Specification (ARMD), Version 1.0 or later. Complying with this specification provides Int 13h and Int 40h support for bootable floppy drives as the primary or secondary floppy device.