This section summarizes the Plug and Play requirements for IDE controllers and peripherals.
13. Operating system recognizes the boot drive in a multiple-drive system
Required
The implementation of boot-drive determination in multiple-drive systems is defined in Section 5.0 of the Compaq, Intel, Phoenix BIOS Boot Specification. This is the format that both Windows and Windows NT operating systems use for determining the boot drive as new bootable devices are introduced for PCs. The system designer can use an equivalent method for boot-drive determination, but the method must ensure that the Windows and Windows NT operating systems recognize the boot drive.
14. Each device has a Plug and Play device ID
Required
For a system-board device, there must be a Plug and Play device-specific ID.
Each IDE controller or peripheral device must provide device IDs in the manner required for the bus it uses, as defined in the related chapter for the specific bus in Part 3 of this guide.
For example, an add-on PCI IDE device must comply with PCI 2.1 and also must provide a Subsystem ID and Subsystem Vendor ID as defined in the “PCI” chapter in Part 3 of this guide. PCI IDE controllers integrated into core logic on the system board do not have to provide Subsystem IDs and Subsystem Vendor IDs, but must meet other PCI 2.1 requirements.
15. Dynamic resource configuration supported for all devices
Required
All devices must be capable of being automatically disabled by the system. Also, disabling the device must result in freeing all its resources for use by other devices.
Changing or adding a controller to the system must not require changing jumpers or switches on either the controller or the system board.
16. Resource configuration meets bus requirements
Required
Plug and Play resource-configuration requirements are defined by the bus used by the IDE/ATAPI controllers and peripheral devices, as defined in the related chapter for the specific bus in Part 3 of this guide.
17. ISA address ranges 3F7h and 377h are not claimed by IDE controllers
Required
Although IDE controllers might use these addresses, 3F7h and 377h also contain registers used by the FDC. To prevent resource conflicts, these addresses must not be claimed as device-register resources.