Abstract:
A computer system with self-describing feature table, accessible by device drivers. Thus a simple process can access these feature tables to fully customize the device drivers at installation, or at boot; or the device driver can branch on the data in the feature table. Thus, a new degree of flexibility is achieved without degrading performance.

Description:
PARTIAL WAIVER OF COPYRIGHT 
     All of the material in this patent application is subject to copyright protection under the copyright laws of the United States and of other countries. As of the first effective filing date of the present application, this material is protected as unpublished material. 
     Portions of the material in the specification and drawings of this patent application are also subject to protection under the maskwork registration laws of the United States and of other countries. 
     However, permission to copy this material is hereby granted to the extent that the owner of the copyright and maskwork rights has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure, as it appears in the United States Patent and Trademark Office patent file or records, but otherwise reserves all copyright and maskwork rights whatsoever. 
     BACKGROUND AND SUMMARY OF THE INVENTION 
     The present invention relates to computer systems, and particularly to single-user or few-user small systems. 
     How Application Programs Interact with Hardware 
     One of the most basic needs in computer architecture is making it easier for a variety of software programs to interact correctly and efficiently with a variety of hardware configurations. Much of the development in computer architecture can be seen as a steady progression of techniques for addressing this need. 
     Note the emphasis on efficiency in the foregoing statement. Even where existing standards can assure compatibility, the search for greater speed or expanded functionality will frequently draw programmers to circumvent the software standards. A good example of this countercurrent appeared in the early days of graphics development on the IBM PC: the BIOS provided a standard interface to video driver operations, but software developers discovered that they could vastly improve performance by making calls directly to the video driver hardware. Thus adherence to the standard architecture was not enough to assure computer designers that their customers would be able to run popular IBM=compatible software, such as Flight Simulator™, on their supposedly IBM-compatible machines. Thus, there is a continuing tension between compatibility and efficiency. 
     When any particular piece of hardware is examined in isolation, it can usually be best described in terms of electrical relationships. For example, a memory specification may state that, within a certain range of delay after certain voltages appear on certain lines, certain other lines will be driven to a corresponding state (which is dependent on the data previously stored in the memory). The specification for an input device, such as a keyboard, may state that, when certain voltages appear on certain lines, a particular input operation may be considered to have occurred. The specification for an output device, such as a video card, may state that, when certain voltages appear on certain lines within a certain timing relationship and protocol, each pixel within a certain defined display device will be driven to an optical state which corresponds to a certain portion of the protocol. However, a commercial application program will be written in a programming language (e.g. in assembly language or in C) which is somewhat machine-independent. There is a great difference between these two levels of description; but this gap must be bridged in order to economically develop application software which can run on a wide range of machines. 
     Several layers of software and firmware structure are used to mediate between application programs and the underlying hardware. To better show the context of the invention, these layers will be described below in greater detail. 
     Hardware Variability 
     Computer hardware configurations are inherently diverse. The complexity of any modern computer system is high enough that even a very detailed standard architecture (such as the &#34;AT&#34; architecture which was introduced with IBM&#39;s 80286-based machines) will not prevent variations from occurring. Whenever designers independently work within a standard, they are likely to find ways to make improvements. As such variations occur, some of them will be seen to be significant. Thus the future will often find that any standard contained significant &#34;gray&#34; areas. 
     This is true not only in motherboard design, but also in I/O devices. For example, two display drivers which both conform to the VGA standard may nevertheless differ in timing, to an extent which may be significant to some software applications. Moreover, there will always be users with needs for specialized input or output devices. 
     Even within the very restricted world of &#34;PC&#34; architectures (where all machines must conform to numerous constraints of the &#34;standard&#34; architectures), hardware variability continues to be a problem. The range of hardware variability in (for example) computers which can run UNIX is far larger. 
     This hardware variability is not merely accidental, but will continue: users are eager to take advantage of new developments, and the pace of innovation is generally far too rapid to permit stabilization of standardized hardware configurations. 
     Layers of Software and Firmware Structure 
     In order to mediate between application programs and the underlying hardware, several layers of software and firmware structure are used. To better show the context of the invention, these layers will be described below in greater detail. 
     Startup Software (POST, Bootstrap, etc.) 
     When power is first applied to a computer, the various hardware elements (chips and subsystems) will each have their own internal procedures (reset procedures) to regain a stable and known state. However, at some point (if the hardware is intact), these reset procedures will have ended, and at this point the CPU performs various important overhead tasks. These include, for example, surveying the system configuration, performing sanity checks on system hardware, issuing diagnostic signals (such as sounding beeps through a speaker or turning on LEDs), and permitting the user to branch into an NVRAM configuration program under software control. This phase of operation is generally referred to as &#34;POST&#34; (Power-On-Self-Test). After POST, a &#34;bootstrap&#34; program is run, to permit the CPU to begin execution of other software. For robustness, the POST and bootstrap software is normally stored in a read-only memory. The bootstrap program launches the CPU on execution of the primary operating system software; Depending on how the system has been set up, the boot software may direct program execution into DOS, Unix, PS/2, a DOS variant, or another operating system. This is normally automatic and predetermined, but is manually user-selectable in some systems. However, the choice of operating system is not particularly relevant to the inventions described in the present application, the primary operating system can then be used by the user to launch an application program, either manually or automatically. 
     Basic Input/Output System Software (BIOS) 
     In many types of modern personal computers (and in all &#34;IBM-compatible&#34; personal computers), a key part of the system software is a &#34;basic input/output system&#34; (BIOS) program. See generally, e.g., the P. Norton, THE PETER NORTON PROGRAMMER&#39;S GUIDE TO THE IBM PC (1985), which is hereby incorporated by reference. The BIOS program contains frequently-used routines for interfacing to key peripherals, The term &#34;peripheral&#34; or &#34;peripheral component&#34; normally refers to those components of a computer system which are not on the motherboard, i.e. which must be addressed through a system bus or over a defined port. However, the usage of this term is somewhat variable; sometimes it is used to refer to any I/O device, or only to refer to components which are optional add-ons. For interrupt handling, and so forth. Thus, the BIOS software provides some degree of machine-independence. However, in PC-class computers, this independence is not fully exploited by the available commercial software. Many programs bypass the BIOS software, and directly access the underlying hardware addresses or devices. See generally Glass, &#34;The IBM PC BIOS,&#34; BYTE, April 1989, pp. 303ff. 
     For system robustness, the BIOS software is normally packaged in a read-only-memory. However, in 1991 IBM introduced a PS/2 system in which the BIOS is at least partially stored on disk. In fact, it is normally packaged together with the startup software mentioned above. Packaging the BIOS, POST and boot routines in ROM makes a very robust firmware system. Short of hardware damage, it is very difficult for a user to distort the system to the point where it will not start up and run (if the operating system software is present). However, this system also provides a considerable degree of flexibility. As the operating system up (after the POST and boot routines), the user can remap address pointers to revector BIOS calls away from the standard BIOS routines, if desired. (It is also common for users to map out the entire BIOS contents into fast RAM, for greater speed). Thus, nowadays the term &#34;BIOS&#34; is often used, somewhat more broadly, to refer to this whole collection of basic system routines. However, in the present application references to &#34;BIOS&#34; will normally refer to the BIOS in its narrower sense, i.e. to the collection of I/O handling routines (and associated routines) which can be called on by the operating system or by the application software. 
     Customized BIOS and BIOS Extensions 
     The BIOS in IBM-compatible computers is accessed by interrupts, but the vectors for those interrupts can be diverted to other addresses (by overwriting an address pointer in system RAM). This capability significantly expands the flexibility of the BIOS, and programmers use it very frequently. 
     However, while the capability to divert BIOS vectors is useful, it is not sufficient to address many needs. Changes to the interrupt-handling vectors will not affect other portions of the BIOS. Computer designers have found it highly desirable to prepare (or obtain) customized BIOS routines to fully exploit the advantage of their systems. For example, such customized BIOS routines are commonly necessary in very-low-power portable systems, to implement power-saving features which maximize battery lifetime. BIOS customization has increasingly been recognized as an important element in rapidly developing a reliable advanced system. See generally Scheier, &#34;Phoenix counters competitors with diversified BIOS offerings,&#34; PC Week, vol. 4 no. 38 (Sep. 22, 1987) at 135f; Guterman, &#34;CompuAdd adopts new ROM BIOS for clones,&#34; PC Week Vol. 5 no. 28 (Jul. 11, 1988) at 6; both of which are hereby incorporated by reference. 
     One function often provided by BIOS customization is &#34;hot-key&#34; access to a setup menu, or to low-level system hardware features (e.g. monitor brightness adjustment). Such capability is very useful to system designers, but normally it has had to be realized in a machine-dependent way (so that large chunks of BIOS have had to be rewritten every time a change was made). 
     Another problem with prior hot-key add-ons is that, if the BIOS interrupt vector for key-handling was diverted, the hot-key capability could be lost. Since many applications do divert the keyboard interrupt (INT9), no critical functionality could be made dependent on such a hot-key operation. 
     Operating System Software 
     The application software will normally interface to an operating system (such as DOS, DOS+Windows, OS/2, UNIX of various flavors, or UNIX plus X-windows). The operating system is a background software program Some operating systems run continuously, or at least start up at regular intervals, even while an application program is running; other operating systems merely provide capabilities which can be called on by the application software. which provides an application programming interface (API) for use by the application software. Thus, the programmers writing application software can write their software to fit the API, rather than having to find out and fit the peculiarities of each particular machine. See e.g., Quedens, &#34;Windows virtual machine,&#34; PC Tech Journal vol. 5, no. 10 p. 90, 92-3, 95, 97, 99-100, 102 (Oct. 1987), which is hereby incorporated by reference. 
     Graphical User Interface (GUI) Operating System Add-Ons 
     Some operating systems have been enhanced by the addition of overlaid supplemental operating systems. For example, Windows is a supplement to DOS, and X is a supplement for UNIX. The use of such hybrids does not greatly affect the foregoing considerations, except that it makes the compatibility issues even more difficult: the designer of a DOS machine must expect that customers will be running some DOS programs, and some Windows programs, on the same machine. 
     Device Driver Software 
     A device driver is a lower level of operating system software. Typically a device driver interfaces to the actual peripheral hardware components, and provides routines which application software can use to access the hardware components. Thus, the application software can simply make a call to an installed software subroutine, instead of having to find the specifications of each peripheral device and branch accordingly, whenever a peripheral I/O operation is needed. This permits application software to ignore the detailed specifications of peripheral hardware. 
     Normally device driver software must contain a description of each target hardware platform. Thus, the software must be revised repeatedly, for reasons which are beyond the control of the companies making peripherals. 
     In personal computers, installable device drivers were first introduced in DOS 2.0. The role of device drivers has since been expanded, in subsequently introduced operating systems. 
     In particular, OS/2 provided expanded support for device drivers, including a library of &#34;DevHlp&#34; routines which can be called by device drivers. See generally Duncan, &#34;An examination of the DevHlp API (writing OS-2 bimodal device drivers),&#34; 3 Microsoft Systems Journal no.2 (March 1988) at 39ff; Schmitt, &#34;Designing drivers for OS/2: I,&#34; PC Tech Journal vol.5, no. 12, p. 164 (1987); and Schmitt, &#34;Designing drivers for OS/2: II,&#34; PC Tech Journal vol.6, no.2 p. 136-155 (Feb. 1988), all of which are hereby incorporated by reference. 
     System Configuration Tables 
     Some computer systems have previously used a feature table, stored in nonvolatile memory, to describe various characteristics of the machine. The IBM AT BIOS uses such a feature table (stored in battery-backed CMOS memory). This feature table, in expanded form, has also been used in the IBM PS/2 systems and has been utilized in the system BIOS of all IBM AT- and PS/1-compatible personal computers. This table is in the form of a bit map where each bit refers to specific hardware implementations employed by the designers of the machine. A pointer to this table may be obtained through executing a software interrupt. More specifically, executing interrupt 15h with AH=COH will return a pointer to the table in ES:BX. However, this feature table is restricted to merely listing certain hardware features in the machine, such as the number of DMA controllers, and does not provide an interface to these features. Furthermore, the elements of the list are fixed. 
     In the Phoenix Technologies BIOS, there are specified entry points at bard-coded addresses which will perform certain machine-specific functions. These are few in number, must be at fixed addresses, do not support protected mode applications and it is not possible to easily see which features are supported by which machines except by restricting to the common subset. 
     Under the EISA standard, an EISA Configuration memory is used to store a limited feature table of EISA peripherals on the EISA bus. See generally Glass, &#34;Inside EISA,&#34; BYTE magazine, November 1989, at 417ff, which is hereby incorporated by reference. 
     Application Software 
     From a system designer&#39;s point of view, the application software is (subject only to the minimal constraints of the architectural standards) wholly unpredictable. Many clever people are constantly looking for new ways to exploit the standard architecture, and many innovations continually result. Thus, hardware architects must expect that the application software will not only be unpredictable, but will be as unpredictable as possible. Common applications include spreadsheets, word processors and publishing programs, databases, games, project managers and a wide variety of others; but inevitably users will also run customized applications, and new types of applications. 
     Utility Programs and Hardware 
     In recent years, many personal computer manufacturers have expanded their product lines. This has dramatically increased the difficulty of supporting an entire product line in terms of the standard software products that a manufacturer may choose to include or sell with its computers. 
     Examples are diagnostic programs, operating system software and utility software. It is increasingly necessary to provide a means for such software to identify the individual machines and their unique features, without having to be rewritten each time a new product is introduced. 
     Furthermore, it may be difficult or undesirable to implement even similar features in exactly the same way, since each design has different constraints in terms of cost and each will incorporate the knowledge gained by building the previous product. The problem gets worse as a product line ages. It is desirable to continue to support older products with newer versions of software, and it is also desirable for older versions of software to run unmodified on newer platforms. One solution to this problem is to write the software to the common subset of functions supported by all platforms. However, this does not allow the manufacturer to differentiate his product from the competition. Consequently, it is desirable for each individual machine to have the capability to identify its own unique feature set to such software, while at the same time providing the individualized means for carrying out those functions. 
     Innovative Computer System with Self-Describing Extensions to BIOS 
     The present invention provides a personal computer architecture with an additional layer of overhead software (or firmware) structure. This additional layer of software structure is used to provide access to additional low-level hardware-specific features in a manner which is independent of the operating system. In the present application, these additional low-level hardware-specific features are referred to as &#34;extended features.&#34; 
     Extended Features 
     An &#34;extended feature&#34;, in the presently preferred embodiment, is normally a system level routine used to service hardware components or to obtain system information unique to Dell hardware systems. The detailed disclosure below lists some of the numerous extended features which have been implemented to date. However, of course, other functions can be provided as well. 
     The disclosed self-describing system software extension provides a lower level of software-hardware interface &#34;cushioning,&#34; which device drivers can call on. Thus, the self-describing system software extension can also be exploited to permit device drivers to be more hardware-independent. 
     The self-describing system software extension is particularly advantageous in its application to an evolving product line within the same overall standard. 
     Self-Describing Feature Table 
     The disclosed innovations provide methods by which a computer with some quantity of non-volatile storage can present a self-describing interface which also provides a means for carrying out machine-specific functions in a non-specific way. 
     In the presently preferred embodiment, the feature table and the machine-specific routines are programmed into EPROM devices, at the start of the &#34;OEM reserved&#34; block of addresses in the BIOS memory space. In IBM-compatible computers, the BIOS commonly occupies the 64K or 128K of address space just below the top of the lowest megabyte of the total memory address space. 
     An important element of the method is a table which contains a signature to identify it with the system software architecture described herein, and a series of entries with the following information: 
     Feature ID--a unique identifier for each specific machine-specific function. 
     Attributes--describe the operating environment for proper access to the function. May limit access to real or protected mode or possibly even to specific operating environments. 
     Service Routine--a pointer to the program code that performs the requested function. 
     Data Block--Features may also include an optional data block. 
     The self-describing system software extension of the presently preferred embodiment includes a self-describing feature table, which can track the peculiarities of the actual hardware configuration of each system as configured. The self-describing system software extension, with this feature table, provides low-level translation for hardware peculiarities. 
     By use of this feature table, the disclosed innovations provide a computer system which can be updated with self-defining extensions to the basic BIOS (which remains in read-only memory). The basic BIOS must be modified to make use of these self-defining extensions; but, once such a modified BIOS has been installed, it does not have to be updated frequently. Instead, the routines in the modified BIOS can make use of the self-defining feature table without further changes to other portions of BIOS. Thus, for example, in one class of alternative embodiments, the feature table is located in NVSRAM, and a ROM holds the basic BIOS and a pointer to the feature table. 
     Application Programming Interface to Self-Describing Feature Table 
     One contemplated and advantageous class of embodiments uses a standard API to the feature table to provide increased portability (across applications) of access to the extended features. (Thus, for example, an OS/2 device driver can be written to wrap this API around calls to the feature table in such a way that any OS/2 software can make feature-table calls through this API.) This provides optimal access to the machine-specific routines across the whole family of computers.) In the sample embodiment described in detail below, this function is not yet included. However, as will be apparent to those skilled in the art, this can readily be implemented in various ways, within the architecture described below, if desired. 
     Device Drivers in the Innovative System 
     The disclosed architecture provides access to machine-specific features, with enough information to permit device drivers to be written in a machines-independent way (within the Dell family of computers). Some specific examples of such drivers are given herein, but of course other drivers can also make use of the extended BIOS features as well. 
     Keyboard Driver 
     One very advantageous piece which is included in the presently preferred embodiment is the keyboard driver, which permits the user to access extended system functions, without exiting his application, by hitting &#34;hot key&#34; combinations. This is highly advantageous in portable systems, since the user can fine-tune his system&#39;s hardware parameters to match changing conditions. Thus, the disclosed system allows the user to send BIOS-level function calls right through an application, without saving the context of the application. 
     This keyboard driver runs under DOS, so it is still possible for a user to disrupt this driver by remapping the keyboard interrupt (INT9); but at least this driver does permit language customization to be combined with hot-key access to extended-BIOS functions. 
     An important point is that, even when a user remaps the keyboard interrupt under BIOS, he can still preserve the hot-key calls to the extended BIOS features without knowing what the features are or even which key combinations call them. (This is accomplished, in the presently preferred embodiment, by building a quick-reference table in system RAM during an initialization phase.) 
     OS/2 Initialization Driver 
     Another advantageous part of the presently preferred embodiment is an OS/2 initialization driver, which permits easy initialization of hardware-specific functions for OS/2 initialization. This driver, in its presently preferred embodiment, is listed in the appendix. 
     Common Device Drivers across a Family of Computers 
     The disclosed innovations have been implemented on a number of different computer systems within the Dell system product line. As of the effective filing date of the present application, these include all Dell computer models shipped after September 1990, plus a few models which were retrofitted. 
     As discussed below, the disclosed innovations are believed to be advantageous not only as applied to a single computer, but also as applied to a whole family of computers. In the case of the preferred embodiment, suppliers of computer peripherals can be increasingly confident that a device driver which takes advantage of the self-describing system software extension of the presently preferred embodiment will apply to every current Dell computer, and also to future models which the supplier has not yet seen or heard of. 
     Backward Software Compatibility 
     A substantial advantage of the disclosed architecture is that additional BIOS-level functions can be readily added into computer system designs, as soon as the innovations occur, without any necessity for radical BIOS changes. The self-describing system software extension of the presently preferred embodiment itself does not degrade BIOS compatibility with prior ISA or EISA machines; and once the self-describing system software extension of the presently preferred embodiment is installed, further extensions to BIOS functionality can readily be achieved. 
     Additional Background 
     Two previous proposals for achieving machine-independence will now be discussed, with reference to the present inventions, in order to provide a clearer discussion of how the teachings of the present application differ from these prior teachings. 
     The &#34;Advanced BIOS&#34; (ABIOS) in PS/2 Architectures 
     The PS/2 architecture, which IBM introduced in 1987, included a so-called &#34;advanced BIOS&#34; or &#34;ABIOS&#34; There are actually two versions of ABIOS available, since IBM has offered a simplified ABIOS for use on machines other than IBM PS/2s. However, the full functionality of ABIOS is available only on an IBM PS/2. The features of this version of ABIOS are most germane to the background of the present invention. (In additional to a more conventional BIOS, known as the &#34;compatibility BIOS&#34; or &#34;CBIOS&#34;). The user can elect to use the CBIOS instead of the ABIOS if he wishes, for downward compatibility; the CBIOS and ABIOS are not designed to run simultaneously. 
     The ABIOS is a more high-level software structure than ordinary BIOS, and has many features added to enhance performance in OS/2 (which, unlike DOS, is a multi-threaded operating system). However, ABIOS is so complex and ambitious that very few operating system designs have used it. 
     The ABIOS must normally be initialized: the initialization process surveys the system configuration, and builds a data structure (the CDA) in System RAM. Process threads (or system software called by process threads) can call on this data structure to get information about the hardware they are running on. 
     The ABIOS is somewhat analogous to a large-scale machine-specific device driver: a process thread can make calls to the ABIOS by submitting a &#34;request block&#34; into the ABIOS&#39;s request-handling queue. 
     When running on an IBM PS/2 under OS/2, the OS/2+ABIOS combination does make additional DevHlp functions available to device drivers, including provision of a standardized interface which provides some hardware-independence to the device driver software. Thus, the device driver software programs in such a system can include substantially increased functionality. See generally Mizell, &#34;Understanding device drivers in Operating System/2,&#34; IBM Systems Journal vol.27, no.2 p.170-84 (1988), which is hereby incorporated by reference. 
     Within the IBM PS/2 family, the interface to ABIOS is identical, regardless of which IBM PS/2 machine it is running on. Within the IBM PS/2 family, the ABIOS provides a significant degree of machine-independence. Thus the ABIOS has some, but not all, of the same goals as the presently preferred embodiment disclosed herein. 
     Note that the self-describing system software extension of the presently preferred embodiment provides a lower-level component of system software than the ABIOS referenced above. The ABIOS is itself a full standalone BIOS, and may be thought of as a fancy device driver. By contrast, the conventional BIOS is interrupt-driven. By contrast, the self-describing system software extension will not work as a standalone BIOS, and does not even work as a device driver: instead, the self-describing system software extension merely provides services to device drivers and to standalone application programs. 
     The self-describing system software extension provides functions which are not addressed by the ABIOS, and conversely the ABIOS addresses a great deal of functionality which is not addressed by self-describing system software extension. Thus, these two software systems are complementary. In fact, it would readily be possible to prepare a modification of self-describing system software extension for use as an ABIOS extension. The ABIOS also includes &#34;hooks&#34; for extending ABIOS; insofar as known to the present inventors, nobody has ever taken the trouble to implement this in a practical system, but there is no apparent reason why this could not be done if desired. 
     The disclosed self-describing system software extension also provides particular advantages in system diagnostics, which are not provided by ABIOS. 
     The &#34;XBIOS&#34; of the Atari ST 
     In internal documentation, the self-describing system software extension of the presently preferred embodiment has frequently been referred to as the &#34;XBIOS,&#34; and reflections of that terminology can be seen in the source code appended to the present application. However, to prevent confusion, it must be noted that the term &#34;XBIOS&#34; has also been used for a component of the operating system software in the Atari ST computer. While this software is believed not to have included any of the innovative concepts claimed herein, the similarity in terminology should be noted. See generally, e.g. Rothman, &#34;Atari ST software development, BYTE magazine, vol. 11 no. 9 (Sep. 1986) at223ff, which is hereby incorporated by reference. The Atari ST is a 68000-based machine. The ST&#39;s operating system (called &#34;TOS&#34;) has two main parts: The &#34;GEM&#34; (Graphics Environment Manager) is a complete operating system developed by Digital Research, and is meant to support applications that are portable to other machines. Atari&#39;s &#34;XBIOS&#34; (extended BIOS) is meant to support ST-specific capabilities not accessible through GEM. 
     Additional Background Literature 
     U.S. Pat. No. 4,589,063, which is hereby incorporated by reference, purports to disclose a &#34;method and apparatus for automatic configuration of a computer system . . . wherein one or more system peripheral or I/O devices can be interfaced to the computer system through I/O boards that plug into a system motherboard. Each of the I/O devices includes a controlling device driver module that operates under a program code stored in a read only memory resident on the I/O board and by which the device driver module allows the computer system to communicate with its associated peripheral and I/O devices. Accordingly, a system user is not required to change the computer operating system kernel to support each new I/O device or system configuration change.&#34; 
    
    
     BRIEF DESCRIPTION OF THE DRAWING 
     The present invention will be described with reference to the accompanying drawings, which show important sample embodiments of the invention and which are incorporated in the specification hereof by reference, wherein: 
     FIG. 1 diagrams the layout of the extended feature table (XFT) used in the presently preferred embodiment. 
     FIG. 2 schematically shows an object-oriented paradigm wherein, by viewing every DELL hardware system as a subclass of a generic DELL hardware system class, supporting all extended features across every systems, BIOS programmers can choose to inherit or modify any or all of these features for their particular system. 
     FIG. 3 shows additional details of the structure of each individual feature entry. 
     FIG. 4 shows how a pointer is used to allow BIOS programmers to relocate the feature table, and enables uniform access to the table regardless of the Dell system type. 
     FIG. 5 shows how the feature table interface in the application interface (API) library, in the presently preferred embodiment, locates and executes self-describing system software extension feature routines. 
     FIG. 6 shows how the system-software-extension API library, in the presently preferred embodiment, communicates with the device driver via the I/O control API supplied by the operating environment. 
     FIG. 7 shows a typical system-software-extension feature routine organization. 
     FIG. 8 diagrams a flow chart of an implementation of the preferred embodiment of the invention. 
     FIG. 9 illustrates a preferred embodiment of the present invention. 
    
    
     DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     The numerous innovative teachings of the present application will be described with particular reference to the presently preferred embodiment. However, it should be understood that this class of embodiments provides only a few examples of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present application do not necessarily delimit any of the various claimed inventions. Moreover, some statements may apply to some inventive features but not to others. 
     In particular, the following text frequently references the &#34;XBIOS&#34; system software, which is the presently preferred embodiment of the claimed system extension software. The following text also makes frequent references to DeII™ computers, since the preferred embodiment of the system extension software has been implemented in this line of computers. However, of course, the claimed inventions can readily be adapted to a tremendous range of computers and of software implementations. 
     Even the specific disclosed embodiment is not inherently limited to Dell computers, but provision for other makers&#39; computers, of comparable architecture, can readily be added. 
     Preferred Embodiment: Family of Computers with Shared General Architecture 
     The disclosed innovations have been implemented on a number of different computer systems within the Dell system product line. As of the effective filing date of the present application, these include all Dell computer models shipped after September 1990, plus a few models which were retrofitted. The specific models include at least Dell models 325D, 333D, 433P, 333P, 325P, 425E, 433E, 425TE, 433TE, 433DE, 450SE, 433SE, 420DE, 420SE, 320LT, 320N, and 212N. These models include tower, desktop, laptop, and notebook models; EISA- and ISA-bus systems; systems based on 80486, 80386, and 386SX microprocessors; systems running at 50 MHz, 33 MHz, 25 MHz, 20 MHz, and 12 MHz clock rates; systems with one or two hard disks, or up to 10 disks in a drive array; systems with monochrome, VGA, or high-resolution graphics adapters; and a wide variety of other configuration options. Moreover, the disclosed innovations are currently being made available in all new Dell computer designs. As of the filing date of the present application, every computer which is currently being shipped in the Dell product family includes a version of the XBIOS described below. (Of course, this is not necessarily true of the many older models which are already in service in the field.) 
     As discussed below, the disclosed innovations are believed to be advantageous not only as applied to a single computer, but also as applied to a whole family of computers. In the case of the preferred embodiment, suppliers of computer peripherals can be increasingly confident that a device driver which takes advantage of the self-describing system software extension of the presently preferred embodiment will apply to every current Dell computer, and also to future models which the supplier has not yet seen or heard of. 
     A sample source code implementation is set forth in the Appendix to insure the fullest possible compliance with the best mode requirements of U.S. patent law. Although the sample source code does represent the state of this code as of the effective filling data of the present application, it must be noted that this specific example is still under development. It is expected that this source code will later be modified to add functionality, improve performance, and possibly also to remove bugs. 
     To give a more clear example of the workings and advantages of the disclosed innovative system and method ideas, the following is an excerpt from an OS/2 loader that uses several XBIOS features. This code includes the following functions (in several modules): 
     check for existence of XBIOS table in system BIOS (EPROM); 
     Looks for SYSTEM --  IDENTIFY routine (find xbios routine); 
     Call SYSTEM --  IDENTIFY routine in EPROM; 
     Save the data returned by SYSTEM --  IDENTIFY for later use; 
     Look for OS/2 13  INIT routine (in EPROM), and call it if it exists; 
     Look for the SMARTVU routine, and, if it exists, display &#34;OS/2&#34; on the diagnostic display; 
     Looks for GATEA20 routine, and, if it exists, save the GATEA20 address (from table) for later use. 
     Part of the source code shown on Appendix Page A-ii checks for the existence of an XBIOS table. 
     The source code shown on Appendix Pages A-ii and A-iii checks for the existence of a System Identify Routine. 
     The source code shown on Appendix Pages A-iii and A-iv checks for the existence of a SmartVu routine, and uses it, if it exists, to display &#34;OS/2&#34;. 
     The source code shown on Appendix Pages A-iv and A-v calls the OS/2 initialization routine, if it exists. 
     The source code shown on Appendix Pages A-v and A-vi checks for the existence of a Gate-A20 routine, and stores its address, if it exists, for use in switching between real and protected modes. 
     The source code shown on Appendix Pages A-vi and A-vii scans the XBIOS table in EPROM looking for a requested function id. 
     To give a more clear example of the workings and advantages of the disclosed innovative system and method ideas, the source code shown on Pages A-vii to A-xii is an excerpt from a DOS keyboard driver. 
     The source code shown on Appendix Page A-xii swaps the INT 9 vectors. 
     The source code shown on Appendix Pages A-xiii to A-xiv checks for a key chord which would require a call to XBIOS. 
     The source code shown on Appendix Pages A-xiv to A-xvi actually handles keystrokes as desired. 
     To give a more clear example of the workings and advantages of the disclosed innovative system and method ideas, the source code shown on Appendix Pages A-xvi to A-xviii is an excerpt from a DOS memory manager (HIMEM.SYS) that uses XBIOS functions. It looks for the GATE A20 routine in XBIOS and saves the address for later use by the operating system. 
     To give a more clear example of the workings and advantages of the disclosed innovative system and method ideas, the source code shown on Appendix Pages A-xviii to A-xxvi is a sample XBIOS table definitions in Assembler. 
     To give a more clear example of the workings and advantages of the disclosed innovative system and method ideas, the source code shown on Appendix Pages A-xxvi to A-xxviii is a sample of XBIOS table definitions in C. 
     To give a more clear example of the workings and advantages of the disclosed innovative system and method ideas, the source code shown on Appendix Pages A-xxviii to A-xxxvii is a sample of XBIOS test code (written in C). This is an 80386-based 33 MHz desktop ISA machine, with a typical configuration of a 200M IDE disk drive, 4M of DRAM, 64K cache SRAM, and an 8 MHz ISA bus. However, as detailed above, the disclosed innovations have been implemented on many other computers too. 
     System Software Extension--Technical Specification 
     The presently preferred embodiment provides a family of &#34;IBM-compatible&#34; computers. In this family, the disclosed innovations are applied to augment the ROM BIOS by self-defining ROM BIOS feature extensions in a manner independent of the operating environment and extends the system software support for disparate hardware features in a standardized fashion. This strategy is the culmination of ideas arising from the necessity to make the access procedure to the BIOS uniform, and thereby reduce the number of releases of Dell supported operating environment, to provide support for extended system features across all system software platforms, to accommodate enhanced diagnostic support, and to obtained standardized access to system services. 
     Dell computer systems support various ROM BIOS (hereafter referred as &#34;BIOS&#34;) extensions that enhance the standard AT architecture providing added value to Dell&#39;s customers. Hitherto, a keyboard interface and various DOS utilities have been provided for Dell&#39;s customers to access these extended features. However, this access procedure is inadequate for computer systems sold overseas and various operating environments. The keyboard interface is sufficient for DOS only systems sold in the US since these systems, by default, use BIOS to process keystrokes that access extended features. Systems sold outside the US, however, use a memory resident DOS utility that traps the BIOS INT 9 (keyboard handler) routine in order to process requested services. This utility requires frequent modifications and testing whenever new features are added to hardware systems since the supporting code is imbedded within the utility. 
     Moreover, operating systems and graphical environments such as OS/2, WINDOWS, and UNIX intercept keystrokes and process them in a manner which bypass the BIOS keyboard handler. Thus the extended features are not available to users via the keyboard in these environments. 
     Some utilities written for DOS require direct BIOS accessibility, and hence cannot execute in operating environments that prevent direct access. In order to support compatibility with current systems that access extended features via the keyboard, operating environments that place restrictions on BIOS accessibility, and the additional requirement to improve system diagnostic support, a standardized access method to BIOS extended features independent of the operating environment and hardware system is provided. 
     The disclosed architecture permits access to extended BIOS features independently of the operating environment. This is accomplished by letting the features be &#34;self-defining&#34;. This refers to the ability of the operating environment to access features in a manner independent of the hardware system. An extended feature is viewed by the operating environment as an abstract hardware device or service processed by BIOS with its characteristics embedded in BIOS. The operating environment&#39;s only reference to the extended feature is through an identifier that is subsequently defined by BIOS. 
     The centerpiece of this architecture is a table embedded in BIOS that contains a list of extended features supported by the hardware and its respective attributes. Through the use of this table, the operating environment and the extended features are totally isolated from one another. This allows the operating environment to access extended features in a consistent manner independent of the BIOS. Conversely, the extended features can be developed independently of the specific operating environment, since they are redefined by the BIOS in each specific machine. 
     The table improves upon the current software interrupt access method to BIOS, since this is not supported by all operating environments. OS/2, for example, does not allow this. DOS has a different problem: programmers can generally redefine any software interrupt, which means that access to extended feature support could be cut off by applications or even by users. 
     By using the disclosed innovations, BIOS programmers can modify extended features without affecting other parts of the architecture. This reduces the need to update vendor source code. Utilities that take advantage of these extended features can be developed independently of the operating environment, and thus will have greater portability. 
     Object-Oriented Paradigm for Feature Inheritance 
     By utilizing the embedded BIOS table as a method table, the architecture can be developed around an object-oriented paradigm to access the extended features in BIOS. As shown in FIG. 2, by viewing every Dell hardware system as a subclass of a generic Dell hardware system class, supporting all extended features across every systems, BIOS programmers can choose to inherit or modify any or all of these features for their particular system. (Thus, this is only a two-level hierarchy, which avoids problems with &#34;grandchild inheritance.) Each extended feature is assigned a unique identifier. When utility applications need to access this feature, they can use this unique identifier in a message that is dispatched to an interface. This interface subsequently determines the behavior of the extended feature by matching the message to the identifier within the table. 
     The Self-describing System Software Extension 
     The &#34;XBIOS&#34; self-describing system software extension contains hardware specific features that extend the standard BIOS operations. An &#34;extended feature&#34; is either a system level routine or data used to service hardware components or to obtain system information unique to Dell hardware systems. Since XBIOS is an extension to BIOS, access to all the standard BIOS functions will remain intact via the interrupt vector table, but an additional access method is provided for the extended features. To implement this access scheme, in the presently preferred embodiment, a table called the extended feature table (&#34;XFIT&#34;) is embedded in BIOS. The XFT is used to match service requests for extended features from the operating environment to identifiers representing the extended features listed in the table. Corresponding attributes associated with each feature identifier determine whether the extended feature is an XBIOS function or a pointer to a block of data. The XF-F permits BIOS programmers to define, modify and support extended features for any system without having support built directly into the operating environment or utilities. 
     Extended Feature Table (&#34;XFT&#34;) 
     The XFT is a table containing extended system features supported by XBIOS. FIG. 1 diagrams the layout of the XFT. The table consist of a header followed by an array of extended hardware feature entries that can be fragmented throughout XBIOS. The header is composed of a signature used to detect XBIOS support by verifying the existence of the XFT, and the XFT version number. 
     FIG. 3 shows additional details of the structure of each individual feature entry. Each entry contains at least three fixed members: a feature ID, attribute flags, and a 32-bit XBIOS pointer. Each table may also contain two optional members (as determined by the attribute flag settings): a feature keystroke trigger and an appendix-block of additional data. 
     The XFT is relocatable, as are all the XBIOS extended features. Anchoring an XFT pointer at the same XBIOS address in all systems provides a standard method of finding the XFT regardless of the system, and allows BIOS programmers the flexibility to locate the table anywhere in XBIOS. 
     XFT Header 
     Signature: At header offset 0, the signature (&#34;DELLXBIOS&#34;) is a null terminated string of bytes used to identify the existence of an XFT confirming that XBIOS is supported by the system. 
     XFT Version Number: At header offset 2, the XFT version is a 2-byte value used to verify the current XFT version. 
     XFT Feature Entry 
     Feature ID: At feature offset 0, the feature ID is a 2-byte value serving as a selector to identify system supported features. The XFT is scanned to match a feature request against the XFT feature ID list. If a match is found then the request is processed. No match indicates that the request is unsupported. Two feature ID&#39;s are reserved for XFT support operations: Chain ID and NULL ID. The Chain ID (0×FFFF) is used to indicated that the corresponding 32-bit pointer references the next table fragment in XBIOS. The NULL ID (0×0000) is used as the XFT termination entry. 
     Attributes: At feature offset 2, the attributes is a 2-byte bit field containing various characteristics about the feature entry. The flags describes the type of the corresponding XBIOS pointer, whether the features supports a DOS compatible keystroke trigger, and determines if the feature entry record contains extended information. The attribute flags are described as follows: 
     real mode: 1 bit. Real mode code pointer flag. 
     protect mode: 1 bit. Protected mode code pointer flag. 
     XBIOS ptr format: 1 bit. Denotes linear or seg:offset. 
     keystroke trigger: 1 bit. Optional keystroke trigger. 
     appendix flag: 1 bit. Feature entry has appended data. 
     To indicate that the corresponding XBIOS pointer references bimodal code, both real mode and protected mode flags are set. If neither the flags are set then it is assumed that the XBIOS pointer references data and an XBIOS address is returned. The pointer format flag indicates the address format. When set, the pointer format is segment:offset; when clear, the pointer format is linear. 
     XBIOS Pointer: At feature offset 4, the XBIOS pointer is a 32-bit pointer that references either code or data depending upon the corresponding attribute flag settings. If the real mode or protected mode flag is set then the pointer contains an XBIOS feature routine entry point. If the data mode is set then the pointer simply contains an address to a block of data. The XBIOS pointer is either a linear address or an address of segment:offset form. Whenever there is a conflict between the usage of either address format, segment:offset should be used since conversion to linear form will always yield a valid address. 
     Keystroke: A keystroke trigger is used to maintain compatibility with systems that can access features through the keyboard. Whenever the keystroke trigger attribute flag is set a two byte keystroke field immediately follows the permanent members of the feature entry at offset 8. The keystroke field is a 2-byte field consisting of the keyboard shift state in the high byte and the scan code in low byte. For example, if a keystroke trigger is designated as ctrl-alt-enter, the ctrl and alt state bits are set in the high byte and low byte value is set to hex 1C (enter key scan code). 
     Appendix: The appendix contains supplemental information attached to the feature entry. This provides greater control and flexibility to XBIOS feature design. The appendix follows either the permanent members of the feature entry record at offset 8, or the keystroke field at offset 10 (if one is designated by the keystroke trigger attribute flag). The first two bytes of the appendix contain the length of the subsequent data block. 
     XFT Pointer 
     The XFT pointer is a 32 bit pointer in segment:offset format anchored at the start of the OEM reserved area--location F000:ED00--in YBIOS. This allows BIOS programmers to relocate the XFT and enables uniform access to the table regardless of the Dell system type (FIG. 4). XFT isolates BIOS programmers and reduces the impact from changes made to XBIOS. This isolation allows BIOS programmers to continue to deploy the development environment that comply best with their needs. XFT requires only the extended features supported by the system and BIOS programmers can add or remove features as desired. 
     Standard and Generic Interface Configurations 
     The XBIOS interface is organized into two configurations: standard and generic. In the standard XBIOS interface configuration, which is used in the presently preferred embodiment, direct access to XBIOS is provided by the XBIOS API library that is linked to the utility application. The library contains an XFT interface that locates XBIOS features and executes XBIOS feature routines (FIG. 5). In the generic XBIOS interface configuration, access to XBIOS is accomplished indirectly through a device driver that contains the XFT interface. The XBIOS API library communicates with the device driver via the I/O control API supplied by the operating environment (FIG. 6). 
     Generic Interface through API 
     In this alternative version, access to XBIOS is provided via an application programming interface (API) used by utilities. Utilities are applications that interact with users and need control of the system-dependent features. The XBIOS API corresponds to the features provided by XBIOS and is consistent among all operating environments and Dell computer systems. By restricting the access to XBIOS only through the API, portable system dependent utilities can be developed in a machine independent style with a high level language. The utilities thus developed will be portable to other operating environments and to other Dell systems. This also permits the XBIOS interface to be organized into various configurations based upon the strategy that best supports the operating environment and customers needs. 
     Access to XBIOS Feature Routines 
     XBIOS feature routines are machine specific functions embedded in the ROM BIOS of each hardware system. The XFT interface executes feature routines indirectly using the XBIOS feature pointer when either the real or protect attribute flag is set. The routines must adhere to a standardize XBIOS function call protocol. This protocol enables the XFT interface to call any XBIOS function in a uniform manner. 
     Each routine defines a set of input and output variables that are passed to and from the feature routine via a parameter buffer and returns a status value back to the XFT interface. Routines can optionally define subfunctions under a single feature ID which are executed through a subfunction identifier also placed in the parameter buffer. XBIOS internal variables are defined within the routine&#39;s code segment (usually in segment F000h), and addressability is obtained by assigning the data segment register (DS) to the code segment register (CS). 
     Upon entry, the XBIOS routine assigns DS to CS (after saving DS on the stack), and receives a pointer to the parameter buffer in ES:BX. The input variables within the parameter buffer are addressed incrementally from ES:BX followed by the output variables and the optional subfunction identifier. Various status flag are passed to the routine in the AX register that can be used to convey information such as the processor modes (real/protected; USE16JLJSE32). One alternative which was dropped from the presently preferred embodiment was to use the system XFT interface stack for parameter variables. This would have allowed a &#34;C&#34; language interface to the XBIOS routines. Due to the possible stack addressing discrepancies from the base pointer (BP) in the USE16 and USE32 address modes of the processor, the current model using ES:BX was chosen. However, as 32-bit architecture and operating environments become increasingly standard, it may be advantageous to implement such alternative XBIOS routines to support the &#34;C&#34; language interface. 
     Upon exit, the XBIOS routine returns successful (zero) or failure (non-zero) status in AX and restores the DS register. FIG. 7 shows a typical XBIOS feature routine organization. 
     Specific XBIOS Features in the Presently Preferred Embodiment 
     XBIOS &#34;features&#34; are extensions to standard BIOS that support hardware extensions. A feature is either a hardware routine or data that is embedded into XBIOS. The following list describes various XBIOS features: 
     Identify: Identifies the current system 
     Setup Entry: Entry point to the ROM based setup program; optional keystroke trigger via ctrl-alt-enter. 
     Toggle Speed: Selects the next speed setting; optional keystroke trigger via ctrl-alt-backslash. 
     Speed: Set of routines to handle the system speed 
     Returns the number of system speed settings. 
     Returns the current speed setting. 
     Sets the system speed. 
     Reverse Video: Reverses the monitor video attributes; optional Keystroke Trigger: via ctrl-alt-backspace. 
     Monitor Toggle: Toggles between video monitors; optional keystroke trigger via ctrl-alt-F11. 
     Contrast: Set video contrast; optional keystroke trigger via ctrl-alt-F12. 
     Shadow RAM: Enable/Disable Shadow Ram 
     EMS: Enable/Disable EMS 
     Standby: Enable/Disable Standby 
     Gate A20: Used to set up fast gate A20. 
     Diagnostics: Entry point to memory diagnostic routines. 
     Battery: Returns the Battery Voltage Level 
     SmartVu: Controls the SmartVu device The SmartVu™ device is a very small character display in the computer chassis, which is used, under low-level control, to output status and diagnostic messages. 
     Password: Set/Alter the system password 
     Peripheral: Enables/Disable peripheral devices 
     Reset: Controls the Reset Button 
     Speaker: Controls the speaker volume 
     OS2Init: Machine specific initialization for OS/2. 
     Of course, the disclosed innovative system architecture can be used to add other such features if desired. 
     Further Modifications and Variations 
     It will be recognized by those skilled in the art that the innovative concepts disclosed in the present application can be applied in a wide variety of contexts. Moreover, the preferred implementation can be modified in a tremendous variety of ways. Accordingly, it should be understood that the modifications and variations suggested below and above are merely illustrative. These examples may help to show some of the scope of the inventive concepts, but these examples do not nearly exhaust the full scope of variations in the disclosed novel concepts. 
     For example, the set of extended features can readily be expanded. One way to use this capability is to provide the user with additional debug functions which can be used to interrupt the application software, as desired, to monitor register values, memory usage, etc. 
     Another advantageous use of the extended feature routines is for dial-up diagnostics (and/or debug). One example of a hardware configuration which is suitable for such dial-up operation is disclosed in published PCT application WO 90/06548, which is hereby incorporated by reference; but of course other hardware configurations can be used instead. 
     The contemplated primary advantage of the self-describing system software extension feature routines provided by the present invention is for system-operate functions, such as those listed above; but the capabilities of the disclosed architecture can also be exploited advantageously by device drivers for third-party-peripherals. For example, a power-hungry peripheral in a small portable computer can use an XBIOS call to check the battery status before initiating a high-current operation. 
     The self-describing system software extension feature routines can also be highly advantageous in controlling closely-bundled peripherals. For example, one optional add-on available with most computers in the DelI™ line is a disk drive array controller, known as the Dell Drive Array™ (DDA). The present inventors have already begun work on implementing some control functions for the Dell Drive Array™ with the X-BIOS of the presently preferred embodiment, and this direct interface is contemplated as one example of an advantageous use of the disclosed concepts. 
     For another example, many application developers are struggling with the problem of the range of installed hardware capabilities. Business software may run on a wide range of &#34;IBM-compatible&#34; machines. Even if very old or very low-end machines are excluded, a commercial package such as WordPerfecty™ or Paradox™ may be expected to run on anything from an 8-MHz 80286 ISA EGA machine with a crowded 40 msec disk to a 50-MHz 80486 EISA TIGA machine with a disk drive array. This range of machines will provide more than an order of magnitude difference in real-world performance, which poses a dilemma for application software developers: the features which provide product differentiation, and which run well on high-end machines, will completely bog a lesser machine. Some vendors have responded to this problem by preparing scaled-down versions of their current primary products, to permit operation on machines with less power (such as 8088- or 80286-based portable machines). However, this presents more difficulty in product distribution and support. One way to advantageously exploit the disclosed innovations is for such application software (at installation or startup, or on user command) to use the extended feature table to find out the basic system configuration, and modify its own software configuration or installation accordingly. 
     Referring to FIG. 8, there is illustrated a flow chart depicting a preferred embodiment of the present invention. At step 800, the CPU initiates operation. Next, at step 801, the CPU retrieves the startup software from nonvolatile memory. Thereafter, at step 802, the CPU automatically begins running the startup software on the CPU including self-test and bootstrap software. Next, at step 803, from execution of the startup software, the CPU launches into execution of the operating system software. At step 804, from execution of the operating system software, the CPU launches into execution of the application software. The CPU, under control of the application software, may programmably call on the basic system software (step 805) from the nonvolatile memory to interface to an I/O device according to a format which is substantially independent of the type of hardware being used within the computer system. 
     The CPU may also proceed to step 806 where, under control of the application software, it programmably calls on device driver software to interface with an I/O device according to a from at which is substantially independent of the computer system hardware. Also, the CPU may proceed to step 807 where, under control of the operating system software it programmably calls on machine-specific system feature extension software to provide a low-level interface to electrical operations. The system feature extension software is partly stored in nonvolatile memory and contains a self-describing feature table and a plurality of machine-dependent routines which are be executed by the CPU. Note that device driver programs are also able to make calls to the machine-dependent routines which are dependent upon data in the self-describing feature table. 
     Referring next to FIG. 9, there is illustrated a preferred embodiment of the present invention whereby CPU 900 is coupled to program storage unit 901 from where CPU 900 can read and programmably execute application software programs. CPU 900 is also coupled to I/O devices 902, which include at least one input device and at least one output device. CPU 900 is also coupled to nonvolatile memory (ROM) 903 which contains basic system software at addresses which are accessible by application software programs to provide translation for at least some input and output operations. Startup software stored within nonvolatile memory 903 is called up by CPU 900 whenever CPU 900 initially commences operation. Operation system software configured within either or both nonvolatile memory 903 and volatile memory 904, which is also coupled to CPU 900, is executed by CPU 900 after the startup software is launched. The operating system software allows a user to command the CPU to begin execution of application software programs. 
     System feature extension software is also stored in nonvolatile memory 903. The system features extension software contains a plurality of machine-dependent routines and a self-describing feature table which contains pointers to the machine-dependent routines. Multiple device driver programs each accessible by the application software programs running on the CPU define a software interface to specific features of at least one of the I/O devices. The device driver programs are able to make calls to the machine-dependent routines which are dependent upon data in the self-describing feature table. 
     The disclosed innovations have been described with primary reference to a uniprocessor CPU, but they can also be advantageously applied to multiprocessor system. 
     As will be recognized by those skilled in the art, the innovative concepts described in the present application can be modified and varied over a tremendous range of applications, and accordingly the scope of patented subject matter is not limited by any of the specific exemplary teachings given. ##SPC1##