Phoenix Technologies Ltd. Product info and technical docs for developers FAQs and help info for PC users Employment opportunities at Phoenix News and events, investor relations, and office locations
  Go to the Phoenix home page Search the Phoenix web site

Product Finder
Product Finder

Phoenix in the News The Phoenix Events Calendar

Sales Contact

    PC Industry Specifications

Adobe Acrobat DocumentsSome of the following documents are in Adobe Acrobat format. If you do not have the Acrobat Reader, you can download the Reader now.

1394 Specifications

Review our comprehensive index of 1394 Specification documents and guides.

ATAPI Removable Media Device BIOS Specification Ver. 1.0

ATAPI Removable Media Device BIOS Specification, Ver. 1.0 provides the pseudo code for all INT 13 services that a BIOS must provide for an ATAPI controller to boot a Big Floppy drive (2.88 MB) and provide Removable Media Run Time Services to DOS 95 and Windows 95. Today's standard 1.44-MB floppy diskette has become inadequate as executables, data, and program files continue to increase in size. To meet this need, several manufacturers have developed high-capacity removable media , which cannot use existing floppy controllers. This new specification is now the industry standard for accessing the data on ATAPI Removable Media devices.

BIOS Boot Specification Version 1.01

The BIOS Boot Specification Version 1.01 is an emerging standard co-developed by Phoenix, Compaq, Intel, and Microsoft. The purpose of this new functionality is to allow the end user selection of multiple boot devices and the ability to change the boot order. In addition, this functionality utilizes Plug and Play technology to identify boot devices.

BIOS32 Service Directory

This BIOS Run-Time Service (standard in PhoenixBIOS 4.0) provides a single searchable signature for all those services in the BIOS that are designed for BIOS clients running in a 32-bit code segment, such as 32-bit operating systems and 32-bit device drivers. The BIOS32 Service Directory itself is a 32-bit BIOS service that provides the entry points for the other 32-bit services. The providers of this service are BIOS vendors that implement one or more 32-bit BIOS services. This document is the Standard BIOS 32-Bit Service Directory Proposal, Rev 0.4 published by Phoenix on May 24, 1993.

Enhanced Disk Drive Specification Ver 3.0

The EDD Specification Ver. 3.0 builds on EDD Specification Ver. 1.1 (See below). It provides a linkage between the device assignments of the BIOS and the drive-letter assignments of the Operating System. The benefits include:

  • Gives new drive-letter compatibility between the BIOS and the Operating System such as DOS, Win '98 and Win NT. Adding new drives to the system does not change the drive letters.
  • Gives new compatibility between fixed and removable media such as the Iomega Zip, Fujitsu MO, and MKE LS-120/SuperDisk, allowing them to work with any drive letters.

Enhanced Disk Drive Specification Ver 1.1

The EDD specification describes the Phoenix implementation of ATA drives with more than 1024 cylinders, Mode 3/4 PIO, DMA and the Microsoft/IBM INT 13 Extensions

El Torito CD-ROM Boot v1.0

The El Torito specification provides information for making a bootable CD-ROM, and the services a BIOS must provide to boot from a CD-ROM in the "El Torito" format.

IrDA Specifications

Review our comprehensive index of IrDA Specification documents and guides.

Plug-and-Play Specifications
links to the Microsoft web site

Plug and Play (PnP) automatically configures PC hardware and attached devices without requiring changes in the device jumpers or Setup. You can install a new device such as sound or fax card and start using it immediately.

To work properly, however, Plug and Play must be supported in the hardware and software, including the BIOS, the operating system (such as Microsoft Windows 95), and the hardware drivers. Each Plug-and-Play device must have all of the following capabilities:

  1. It must be uniquely identified.
  2. It must state the services it provides and the resources it requires.
  3. It must allow software to configure it.

There are a variety of Plug-and-Play technologies, including BIOS, ISA, SCSI, IDE, CD-ROM, LPT, COM, PCMCIA, and drivers. To download PnP BIOS Specification Ver. 1.0a and the other PnP specifications supported by Phoenix, click on the above link.

To register a new unique vendor ID or manufacturer ID for a new Plug-and-Play device, send e-mail to pnpid@microsoft.com.

POST Memory Manager Specification, Version 1.01

The growing number of add-in cards has created a need for a memory manager to control access to RAM during POST (Power On Self Test), which initializes system hardware. Option ROMs, like those on SCSI and Network-Interface cards, often require the use of a dedicated memory buffer during POST. The POST Memory Manager (PMM) Specification defines a method for allocating RAM buffers that do not collide with one another or the system BIOS. The PMM specification allocates buffers in both conventional (0-640 KB) and extended (1 MB and up) memory. Phoenix is currently developing a BIOS that is compliant with this new specification. Updated 1/8/98.

Smart Battery and SMBus Specifications
links to the SBS Implementers Forum web site

  • System Management Bus (SMBus) - Defines the communications protocols between the intelligent battery, the SMBus host (most likely the keyboard controller) and a Smart Charger (if one exists in the system). This communication protocol is based on the I2C Bus.
  • Smart Battery Data (SBD) - Defines the data set that is communicated to or from a Smart Battery. This spec is independent of battery characteristics (chemistry, voltage, capacity).
  • System Management Bus BIOS Interface (SMBus BIOS extensions) - Defines how Operating System level applications communicate with SMBus components utilizing the BIOS layer as an intermediary.

System Management BIOS Reference Specification, Ver 2.3

Previously known as the Desktop Management BIOS Specification, this paper describes the BIOS component of the Desktop Management Interface (DMI). DMI is a method of managing computers throughout an enterprise. Using DMI, a system administrator can obtain the types, capabilities, operational status, installation date, and other information about the system components.

USB Specifications

Review our comprehensive index of USB Specification documents and guides.

© 1998, 1999 Phoenix Technologies Ltd. All Rights Reserved. Legal Notices.