Basic PC 98 General System Requirements

This section presents a summary of the general system requirements and recommendations, including system board, memory, and BIOS requirements.

1. System performance meets PC 98 minimum requirements
Consumer PC 98 Office PC 98 Entertainment PC 98
Required Required Required

The performance requirements for PC 98 systems are based on the minimum computational capabilities and performance necessary to support the demands of Windows-based applications. The increased requirements over those defined in PC 97 Hardware Design Guide represent the estimated processing demand and processing capability of the lowest-end processor by mid-1998.

For systems based on Intel Architecture processors, the minimum PC 98 performance requirement consists of the following:

Recommended: 64 MB. Memory should be 66-MHz Dynamic Random Access Memory (DRAM) or better.


For a PC 98 system with 32 MB or more of memory, only 4 MB of memory can be locked and unavailable for the system to use at boot time. The remaining memory cannot be locked from use by the operating system. This minimum requirement does not preclude applications that use dynamically allocated memory for audio or video playback or other temporary uses.


For systems based on RISC architecture, the requirement is a Windows NT-compatible RISC processor. Notice that all PC 98 requirements for RISC-based PCs are for the Windows NT operating system only. There are no plans to enable Windows to run on RISC-based PCs.

Note: If multiprocessor support is provided in any system using Intel Architecture, such support must comply with MultiProcessor Specification, Version 1.4 or higher, and the Advanced Programmable Interrupt Controller (APIC) extension to the ACPI 1.0 specification.

For guidelines and exceptions for other system types, see the “Workstation PC 98” and “Mobile PC 98” chapters in Part 2 of this guide.

2. System design meets ACPI 1.0 specification and PC 98 requirements

Consumer PC 98 Office PC 98 Entertainment PC 98
Required Required Required

Recommended: Thermal model and fan control as defined in Section 12 of the ACPI 1.0 specification.

The system board must support the Advanced Configuration and Power Interface Specification, Revision 1.0 or higher. This requirement ensures that the system correctly supports Plug and Play and power management as described in Part 1 of this guide. ACPI support must include the following:

Implementing the thermal model and fan control as defined in the ACPI 1.0 specification is recommended as a means of running the PC quietly while working, and turning the fan off while the PC is sleeping. Notice that a hardware-based open-loop thermal control is an acceptable implementation for system cooling if it meets the capabilities defined in the “Audible noise meets PC 98 requirements” item later in this chapter. However, the recommended implementation is a closed-loop control using the PC’s processor, an embedded controller, or both. If a closed-loop implementation is used, it must comply with the ACPI 1.0 specification.

Note: Any other system-board power management or Plug and Play features must be implemented in compliance with the ACPI 1.0 specification, even if a particular feature is not a specific PC 98 requirement or recommendation.

3. Hardware design supports OnNow initiative

Consumer PC 98 Office PC 98 Entertainment PC 98
Required Required Required

Recommended: If telephone answering machine (TAM) capabilities are built into the system, then a Message Waiting indicator should be included on desktop systems.

Elements of the OnNow design initiative ensure that the operating system and device drivers control the state of individual devices and the system board. The following support is required for PC 98 hardware:

The system must provide an easily accessible power switch that can be controlled by software and that supports the functionality required in Section 4.7.2.2.1 of the ACPI 1.0 specification.


To meet this requirement, an OnNow PC can have either a power button or a sleep button. The recommended implementation for both desktop and mobile PCs is to have both. If both buttons are implemented, the sleep button should be the user’s primary switch interface and must be easily distinguishable from the power button. The preferred implementation is to hide the power button.


The function of these buttons is determined by the operating system. In single-button configurations, it can be used for either sleep/wake transitions (G0< – >G1/S1-S4) or off/on transitions (G0< – >G2/S5), depending on user preference and the policy set in the operating system and use of an operating system–provided user interface. The default action for the sleep button is to cause the machine to enter a sleep state. The default action for the power button is to shut down the operating system and power off the machine. In a two-button configuration that includes separate power and sleep buttons, the operating system user interface will allow only the default actions.


For PC 98, in the 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 PC. Notice that the override mechanism is not an alternative way for the user to turn off the PC in normal operation; it is only a fail-safe function for fault conditions.


The implementation recommended in Section 4.7.2.2.1 of the ACPI 1.0 specification is a 4-second override mechanism. The override can be on either the power button or the sleep button in a two-button configuration.


Note: It is strongly recommended that the override be associated with the sleep button in order to establish an industry-standard implementation.


An acceptable but not recommended alternative is a separate hidden or recessed switch that cannot be mistaken for either the power button or the sleep button. Notice that although the ACPI 1.0 specification suggests the override be associated with the power button, the recommended implementation for an OnNow PC is to have the primary and most accessible button be the sleep button.


Equivalent button functionality can be provided using a keyboard key. 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 PC. (Two keystrokes are permissible for turning off the PC.) The single keystroke ensures accessibility for persons with disabilities. For information about the correct scan codes for keyboard power switches, see http://www.microsoft.com/hwdev/pcfuture/.


This requirement for an easily accessible power switch does not preclude power-control capabilities such as closing the lid on a mobile PC.


Power management is supported for any of the following buses present on the system: PCI, USB, IEEE 1394, and PC Card. Any of these buses must support power management requirements as defined in the related bus standard in Part 3 of this guide.

All devices and drivers must support the D0 and D3 power states consistent with the definitions in the relevant device class power management reference specification or the Default Device Class Power Management Specification, Version 1.0 or higher.


This means that each device can successfully survive a system sleep/wake transition (D3 to D0) without losing functionality and without requiring user intervention to restore functionality. This applies whether or not system power is removed while the device is in the D3 power state.


Notice that there is no power consumption requirement for devices in the D3 power state. It is strongly recommended, however, that devices implement the D3 power state such that device power consumption is reduced to near zero. This recognizes 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 power state.


It is recommended that devices and drivers support the D1, D2, or both low-power states and also support the defined wake-up events as designated in the related device class power management reference specification.


4. BIOS meets PC 98 requirements for OnNow support

Consumer PC 98 Office PC 98 Entertainment PC 98
Required Required Required

This requirement does not apply for RISC-based PCs, except for the requirement for fast power-on self test (POST). For PC 98, the following BIOS support is required:

Resume from sleep state (S1–S4) to operating system handoff must occur within 500 ms. This requirement does not apply for the S4BIOS state. For all other sleep states, the time to operating system handoff is measured from when the processor starts running (first instruction) until the BIOS jumps to the Waking Vector in the ACPI firmware control structure table, as described in Section 5.2.6 in the ACPI 1.0 specification.


The default configuration must allow a beep during the boot process only in case of an error. The only screen display allowed is the OEM splash screen, which can include information such as copyright notices. By default, the system must be configured so the screen display does not display memory counts, device status, and so on, but presents a “clean” BIOS start-up. However, this requirement does not preclude the following:


The intention of this requirement is to ensure that the end user is not presented with confusing information and unnecessary visual display, and to ensure that access to error information remains available using a hot key.

5. BIOS meets PC 98 requirements for boot support
Consumer PC 98 Office PC 98 Entertainment PC 98
Required Required Required

This requirement does not apply for RISC-based PCs. ACPI BIOS entries, as defined in Section 1.6 of the ACPI 1.0 specification, should be the same for supporting either Windows 98 or Windows NT 5.0. In general, the run-time services portion of the Plug and Play BIOS is replaced by ACPI and therefore is not required. In fact, the Plug and Play BIOS must be disabled when ACPI is enabled. The Extended System Configuration Data (ESCD) calling interface is not supported by Windows 98 or Windows NT 5.0.

The PC 98 requirements include the following:

  • Preboot execution environment supported.

For Office PC 98, the execution environment provided by the PC system must conform to the description given in “Attachment B: Preboot Execution Environment” of Network PC System Design Guidelines.


For Consumer PC 98 and Entertainment PC 98, this means providing a PXENV unique system ID structure in the system BIOS or CMOS, as defined in “Attachment B: Preboot Execution Environment” of Network PC System Design Guidelines.


  • BIOS boot for CD-ROM supported.

For any system that includes a CD-ROM, 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, Limited, or an equivalent method that supports the Windows NT CD-ROM installation process.


  • BIOS boot for network adapter supported.

For any PC 98 system that includes 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, Phoenix, Intel BIOS Boot Specification, Version 1.01 or higher, which describes the requirements for Initial Program Load (IPL) devices.

  • Dates beyond the year 2000 correctly supported in BIOS and CMOS.

The following features are required for Office PC 98 systems to ensure manageability and security:

  • Security such as a pre-boot password provided to protect enable/disable capabilities for hardware components before the operating system boots.

This capability is required for Office PC 98 systems and is recommended for other system types. The purpose of this feature is to prevent end users from accidentally or purposefully circumventing operating system–level security and control as applied by an administrator.

  • BIOS updates and revisions supported.

This item is required for Office PC 98 and Net PC systems. BIOS updates must be implemented in order for BIOS ROMs to be upgraded to a new image through OEM-provided programs using either (1) the remote new system setup mechanism that will be downloaded and executed at boot time or (2) normal file access and execution methods when the system is fully booted into the normal operating system environment. For information about requirements related to the remote new system setup mechanism, see the “Network Communications” chapter in Part 4 of this guide.


Recommended: Implement a mechanism to authenticate the requester of the update programming. Implement a mechanism to validate that the program arrived intact after download.


A working group is developing a mechanism to implement this requirement for non-volatile storage update capabilities. When available, this information will be available on the web site at http://www.teleport.com/~nsispec/.


If option ROMs are provided, they must also be capable of being upgraded.


  • BIOS boot for USB keyboard supported if USB is the only keyboard.

For any Intel Architecture system with a USB keyboard as the only keyboard in the system, the system BIOS must provide boot support as defined in Universal Serial Bus PC Legacy Compatibility Specification, Version 0.9 or higher.