WHQL Derivative System Program Rules
Last updated on November 11, 1999

Introduction

The WHQL Derivative System program allows OEMs to logo systems based on a Base System that has been logo'd by WHQL. The Derivative System program helps OEMs, Design Houses, and WHQL in several ways:

Definitions

Terminology

  1. Original Equipment Manufacturer (OEM): Manufacturer or originator of a product. In the context of this document, OEM refers to a maker of computer components and systems.
  2. OEM System: A system that originates from its producer or manufacturer.
  3. Design House: A creator of hardware or software components that can be used in computer systems by OEMs.
  4. Base System: A system that is used as the basis and design model for OEMs to base Derivative Systems on.
  5. Base System Configuration: A list of hardware, software and firmware that must be included in Derivative Systems based on a Base System.
  6. Derivative System: A system that is based on the general design model defined by a Base System.
  7. Independent Hardware Vendor: A vendor of hardware components intended for use in computer systems.
  8. Firmware: Programable, Flashable instructions included on microchips in the system.

Base System Configuration

A Base System Configuration is a list of hardware, software and firmware that must be included in Derivative Systems based on a Base System (exceptions are listed below, under "Acceptable Variations for Derivative Systems"). All device/driver combinations and peripherals must be logo'd or in the testing process at WHQL. A Base System configuration must specify:

  1. A motherboard of a specific make, model and revision.
  2. A processor of a specific class/family, cache size, manufacturer. The highest processor speed that the Base System tested with must also be specified.
  3. Memory of a specific type or specification (ECC, PC100, 4CLK, etc.). The maximum amount of memory that the Base System tested with must also be specified.
  4. BIOS of a specific make, revision and date.
  5. A video controller of a specific make, model, revision and chipset.
  6. An audio controller (excluding servers) of a specific make, model, revision and chipset.
  7. A storage controller (ATAPI, SCSI, RAID, IDE, 1394 or Fibre Channel) of a specific make, model, revision and chipset.
  8. A network adapter (Ethernet, Modem, etc.) of a specific make, model, revision and chipset. A network adapter that is not a modem is required for Servers and Workstations.
  9. Firmware of a specific make, revision, and date.
  10. A power supply of a specific type and wattage.
  11. The operating systems that the Base System was tested with, including specific versions of Windows 2000. For a list of the Operating Systems that a Base System must test with, see the Derivative System FAQ:

If additional hardware is included as part of the Base System configuration, then it must be included in Derivative Systems based on that Base System.

Acceptable Variations for Derivative Systems

Derivative Systems are allowed to deviate from the Base System configuration they are based on in the following ways, provided that all device/driver combinations and peripherals are logo'd:

  1. Processor can change to a lower speed and to a lower cache size, but must still be of the same class/family and manufacturer as the Base System .
  2. Keyboards and mice may change brands, models and interface type (PS2, USB), unless the Base System uses a custom keyboard.
  3. Floppy Disk Drives (FDD) can change brands and models, but must be of the same capacity (1.44MB, 2.88MB, LS120, etc.) and must be of the same interface or bus design as the Floppy Disk Drives in the Base System .
  4. CD-ROM drives can change brands, models, and speed, but must still use the same interface type (ATAPI, SCSI or Fibre Channel) as the Base System .
  5. Hard Disk Drives (HDD) can change brands, models and capacity but must be of the same interface type (ATAPI or SCSI) as the Base System .
  6. Removable Media Drives, such as the Iomega® Zip drive, can be added, as long as they are supported by the storage controller used in the Base System .
  7. DVD drives can be added or substituted for CD-ROM drives, but the following rules must be observed:
    1. The DVD drive must be of the same interface type (ATAPI, SCSI, SCSI-2, etc.) as the DVD drive or CD-ROM drive used in the Base System.
    2. The Derivative System can use a software DVD movie solution only if the Base System configuration includes a software DVD movie solution. Derivative Systems that use a software DVD movie solution must:
      • Have a processor that runs at 400 MHz or faster
      • Use the same software DVD movie solution that is used in the Base System
    3. If the Base System configuration does not include a software DVD movie solution, the Derivative System must use a hardware MPEG decoder if shipping with a software DVD movie solution. A hardware decoder is not required if DVD is used only for non-video playback purposes.

Example: Company A's logo'd video controller can not be used in place of Company B's video controller which is included in the Base System configuration, because video controllers are not listed as one of the "Acceptable Variations for Derivative Systems".

Revising and Refreshing Base Systems

Revising Base Systems:

Base Systems can be revised after they have been logo'd by WHQL with changes that do not alter the basic design of the system. The purpose of allowing Base Systems to be revised is to eliminate the need for design houses to to send new systems when making minor changes to a base system. To revise the Base System, the originator of the Base System must send any changes to WHQL, including:

A full set of testing logs is also required. Allow five (5) days for changes to be implemented and tested by WHQL. When the new version of the Base System has been logo'd by WHQL, the Base System configuration will be displayed on the Microsoft Base System List (BSL). The design house can decide to replace the previous version of the Base System Configuration with the revised one, or to keep both Base System configurations on the Base System HCL.

The following changes can be made when a Base System is revised:

Refreshing Base Systems:

When the design guide the Base System was approved with expires, the Base System can be refreshed. There is no fee for Base System refreshes. Follow the System Refresh Guidelines to refresh your Base System .

Derivative System Frequently Asked Questions (FAQ):

Q: How are pre-install images for Derivative Systems distributed?

A: When submitting a Derivative system to WHQL, send a extra pre-install image on a hard disk drive or CD-ROM. One pre-install image must be submitted for each OS that will be pre-installed and supported on the Derivative System. For more information, see Derivative System Submission Procedures


Q: What if the pre-install is not in English?

A: At this time, you must use English versions of Microsoft operating systems.


Q: What if there are multiple pre-install images? Which pre-install images must be provided?

A: The pre-install image of the highest configuration of Windows 2000 that the Base System is designed to support must be provided. Windows 98, Windows 98 SE, and Windows NT 4.0 (SP6) testing is optional for Server and Workstation submissions.

When logo'd, Derivative Systems can only be pre-installed with configurations of Windows 2000 that the Base System was tested with, or with Windows 2000 configurations that are "lower" than the configuration that the Base System was tested with. Derivative Systems can only be pre-installed with Windows 98, Windows 98 SE, and Windows NT 4.0 if the Base System was tested with these operating systems.

The following table shows which Operating Systems are required for Base System and Base Server submissions and lists server-oriented Windows 2000 configurations in order from "highest" to "lowest":

Required: Optional: These operating systems are not required unless you plan to pre-install them on the system, or wish to display logos for these operating systems.

Servers: Provide a pre-install image for one of the following:

  1. Windows 2000® Datacenter Server (RC3 or greater) (ACPI mode)
  2. Windows 2000® Advanced Server (RC3 or greater) (ACPI mode)
  3. Windows 2000® Server (RC3 or greater) (ACPI mode)

Servers: Provide a pre-install image for:

  • Windows NT 4.0® Server Enterprise Edition with Service Pack 6 (SP6)
  • Windows NT 4.0® Server Standard Edition with Service Pack 6 (SP6)

Systems: Provide a pre-install image log for:

  • Windows 2000® Professional (RC3 or greater) (ACPI mode)

Systems: Provide a pre-install image for any of the following:

  • Windows® 98 Golden Edition (mode that ships: ACPI or APM)
  • Windows NT® 4.0 with Service Pack 6 (SP6)
  • Windows® 98 Second Edition (ACPI Mode)

Note: When the final version of Windows 2000 is released, only Windows 2000 pre-install images will be required for systems and servers that are only pre-installed with Windows 2000.

Example 1: A Base System is submitted with pre-install images for Windows 2000 Datacenter Server. Derivative Systems based on this Base System can use any of the server-oriented configurations of Windows 2000.

Example 2: A Base System is submitted with pre-install images for Windows 2000 Advanced Server. Derivative Systems based on this Base System can use any of the the server-oriented configurations of Windows 2000 except Windows 2000 Datacenter Server. Derivative Systems based on this Base System can not use Windows 2000 Datacenter Server, because this is a "higher" configuration of Windows 2000 than the Base System was tested with.


Submissions

Please make sure that you read and understand this document before assembling your test submission: