System for the Identification and Configuration of Computer Hardware Peripherals

The present invention relates generally to a system for configuring computers, and more particularly, to a system for identifying and configuring computer data storage devices.

The use of computers, especially personal computers (PCs) is widespread. The computing power of the PC, whether coupled to a network or operating as a stand-alone device, has increased significantly as new computer designs move into production. While the new computer designs have consistently increased computing power, it also increases the complexity of the programs that run the computer. To take advantage of the increased computing power, operating systems, such as Microsoft MSDOS.RTM. and Microsoft Windows.RTM. 95, have become more complex. As a result, the installation and set-up of a new computer can be extremely complex, especially for individuals with little or no technical training. Similarly, the recovery from a computer "crash" may require the reinstallation or configuration of certain software components, which also requires a significant amount of technical expertise.

Some computer interface boards, known as "plug and play" boards, have the ability to be identified and configured by the operating system. These boards contain extensive additional circuitry beyond that required to control the peripheral device. However, the identification of the boards is performed by the operating system. If the operating system is malfunctioning, the identification of boards cannot proceed.

Therefore, it can be appreciated that there is a significant need for a system to aid in the installation and/or reinstallation of computer software in a simplified and automated manner. The present invention provides this and other advantages as will be apparent from the following detailed description and accompanying figures.

The present invention is embodied in a system for the automatic identification and configuration of computer hardware peripherals. In one embodiment, the system permits the automatic identification and configuration of a peripheral device, such as a compact disk read-only memory (CD-ROM) drive. The system includes a plurality of software driver files for operation of a plurality of different peripheral device types. An initialization program executes a query instruction, which includes an identification request to the peripheral device. A response from the peripheral device includes identification data for the peripheral device. The response, including the identification data, is interpreted to permit the selection of one of the plurality of driver files corresponding to the identified peripheral device type. A driver loader then loads the selected driver file.

In one embodiment, the peripheral device is a CD-ROM drive having an integrated device electronics (IDE) device, and the query instruction includes an attention application programming interface (ATAPI) identify device instruction to the IDE CD-ROM drive. Alternatively, the CD-ROM drive may include a small computer system interface (SCSI) device, and the query instruction includes an SCSI device instruction to the SCSI interface coupled to the CD-ROM drive.

The system may also include a bootable floppy disk containing the plurality of driver files. The bootable floppy disk may also contain the initialization program as an executable file.

The system also permits the configuration of a hard disk drive by executing an additional query instruction that checks the hard disk drive for partitions and proper formatting. If the hard disk drive does not contain the proper partitions and formatting, the system can automatically execute instructions to partition and format the hard disk drive. The additional query instruction to the hard disk drive may be executed following the loading of the selected driver file corresponding to the CD-ROM drive.

FIG. 1 is a functional block diagram of a conventional computer system.

FIG. 2 is a flowchart of the start-up procedures used by the conventional computer of FIG. 1.

FIG. 3 is a functional block diagram of the system of the present invention.

FIG. 4 is a flowchart detailing the operation of the system of FIG. 3.

A typical personal computer (PC) contains many different components. The user must typically be familiar with the hardware components, the associated interfaces, and the software drivers used to operate the hardware interfaces in order to properly install and maintain the PC. A conventional computer 10 is illustrated in the functional block diagram of FIG. 1. The computer 10 includes a central processing unit (CPU) 12, such as an Intel Pentium.RTM. microprocessor. The computer 10 also includes a memory 14, which may include both random access memory (RAM) and read only memory (ROM). The ROM portion of the memory 14 is typically used by the computer 10 when power is first applied to the computer or if the computer is reset. The ROM portion of the memory 14 includes a basic input/output system (BIOS) 16, which contains a set of instructions that initialize the CPU 12, and other components in the computer 10. The various components in the computer 10 are coupled together by a bus system 20, which may carry power and control signals in addition to data. The bus system 20 may consist of a single bus or several busses interconnected by bus bridges. However, for the sake of brevity and clarity, the bus system 20 is represented in FIG. 1 by a single bus. Also, for the sake of simplicity, other conventional components such as the power supply, mouse and the like are not shown in FIG. 1.

The computer also includes a keyboard 22, keyboard interface 22a, display 24, such as a video display, flat screen display, or the like, and a display interface 24a. The computer 10 also includes a floppy disk drive 26, a hard disk drive 28, and a CD-ROM drive 30, as well as a floppy disk drive interface 26a, hard disk drive interface 28a, and CD-ROM drive interface 30a, respectively. It should be understood that some peripheral devices can share a common interface board. For example, the floppy disk drive 26 and the hard disk drive 28 are often controlled by a single interface instead of the separate floppy disk drive interface 26a and hard disk drive interface 28a illustrated in FIG. 1.

When the computer 10 is powered up or reset, instructions in the BIOS 16 are executed by the CPU 12. The BIOS 16 contains instructions for the CPU 12 to perform basic functions such as setting internal registers (not shown) in the CPU to predetermined values. The BIOS 16 also causes the CPU to perform basic operations for peripheral devices, such as the keyboard 22 and the display 24, by setting registers (not shown) in the keyboard interface 22a and display interface 24a to predetermined values. The BIOS 16 typically includes instructions for setting registers (not shown) in the floppy disk drive interface 26a and hard disk drive interface 28a to permit proper operation of the floppy disk drive 26 and hard disk drive 28.

The BIOS 16 provides instructions for basic I/O operations. Once the CPU 12 has completed execution of the BIOS instructions, the computer 10 can start the operating system, such as Microsoft MSDOS.RTM.. The typical computer 10 checks the floppy disk drive 26 for a bootable operating system. A bootable operating system is one that contains all the necessary files to start the operating system. For example, MSDOS includes three files called "IO.SYS," "MSDOS.SYS," and "COMMAND.COM." Instructions within the BIOS 16 transfer control of the computer 10 to the file IO.SYS, which further initializes the computer 10 in a well known fashion. The IO.SYS file completes its initialization and loads the file MSDOS.SYS. The file MSDOS.SYS also functions in a well known manner and is responsible for loading the COMMAND.COM file, which is a user interface for the MSDOS.SYS file. The operation of these files are well known to those of ordinary skill in the art, and need not be discussed in detail. Operating systems, other than MSDOS, have similar data files and characteristics.

In addition to loading the COMMAND.COM file, the IO.SYS file instructs the CPU 12 to load a data file called "CONFIG.SYS" to configure hardware and software components of the computer 10 for proper operation. For example, the memory 14 can be configured to reserve space for certain application programs or I/O devices. The number of I/O channels and buffers sizes are also selected. These configuration parameters are well known to those of ordinary skill in the art and need not be described in detail herein.

Of particular importance to the present invention is the configuration of certain I/O devices, such as the CD-ROM drive 30. The CPU 12 sequentially executes the lines of code in the CONFIG.SYS file to load the software drivers for the CD-ROM drive 30 into the memory 14. An example of a typical CONFIG.SYS file is illustrated below in Table 1.

device=c:.backslash.soundfx.backslash.sscd.sys /b:330

device=c:.backslash.soundfx.backslash.cdmke.sys /d:sscd.sub.-- 000 /p:338 /v

lastdrive=e

device=c:.backslash.dos.backslash.himem.sys

device=c:.backslash.dos.backslash.emm386.exe ram i=e800-efff x=c901

buffers=10

files=100

stacks=9,256

dos=high,umb

devicehigh=c:.backslash.dos.backslash.setver.exe

device=c:.backslash.turbocom.sys

FIG. 2 is a flowchart used by the computer 10 to start up the computer in the proper configuration. At a start 50, it is assumed that the computer 10 has just been turned ON or that the user has manually depressed a reset button (not shown). In either case, the computer 10 generates a hardware reset in step 52. In response to the hardware reset, the CPU 12 starts BIOS in step 54 by beginning the execution of instructions in the BIOS 16. Following completion of the BIOS instructions, the computer starts the disk operating system (DOS) in step 56. While the previous discussion has used Microsoft MS-DOS as an example, those of ordinary skill in the art can appreciate that other operating systems have similar start-up procedures.

In step 58, the computer 10 loads the CONFIG.SYS data file in step 58. As previously discussed, the CONFIG.SYS data file instructs the CPU 12 to load software drivers for the various peripheral devices and configures the interfaces associated with the peripherals. The computer 10 ends the start-up process at an end 60 with the DOS now running on the computer.

If any of the software programs used to initialize the computer 10 are corrupted in any manner, the CPU 12 will be unable to execute instructions to properly configure the computer and start the DOS. For example, if the start-up program, such as IO.SYS, is corrupted, or the CONFIG.SYS data file is corrupted, the DOS will not function. Corruption of data files may be caused by the improper installation of computer hardware and its associated software, or the improper installation of an application software program. Corruption may also be caused by electrical transients, accidental erasure of data files, a computer virus, an actual hardware failure or the like. No matter what has caused the corruption of these critical data files, the computer 10 will not operate properly until the user corrects the problem. This is true even with plug and play boards, which are identified by the operating system, because the operating system cannot be started without the proper configuration of the computer 10. Similarly, operating systems such as Windows.RTM. 95 may have the ability to identify peripheral devices, such as the CD-ROM drive 30. However, the Windows 95 operating system cannot be started if there is an error in one of the required startup data files, such as CONFIG.SYS. Thus, the identification and configuration of interfaces cannot occur until the source of the error is determined and the corrupted file repaired or replaced. Unfortunately, the user often does not know the source of the problem. Furthermore, the typical user is unfamiliar with the computer hardware and software and is ill-prepared to load the proper drivers and to properly configure the computer 10.

In a preferred embodiment, the present invention is directed to a system that automatically identifies certain peripheral components and selects the correct software drivers for those identified components. Specifically, the preferred embodiment of the present invention can identify the particular type of CD-ROM drive 30 installed in the computer 10. Following the identification, the preferred embodiment of the present invention can select and load the appropriate software driver to properly configure the CD-ROM interface 30a to operate the CD-ROM drive. Similarly, the preferred embodiment of the present invention can analyze the hard disk drive 28 and prepare the hard disk drive to receive data. The the preferred embodiment of present invention is significantly different from other interface identification techniques, such as plug and play interface boards. Plug and play techniques are directed to the configuration of the hardware interface or controller for a peripheral device, rather than the software drivers that operate the peripheral device. For example, the CD-ROM drive interface 30a may be a plug and play type device. The plug and play techniques may be used to identify and configure the CD-ROM drive interface 30a, with parameters such as I/O address, interrupt request line, direct memory access (DMA) request line, and the like. However, the CD-ROM drive 30 itself is not a plug and play device. The CD-ROM drive 30 requires the hardware control provided by the CD-ROM drive interface 30a and a software driver that operates the CD-ROM drive. In a preferred embodiment, the present invention is directed to a bootable system that identifies and loads the required software drivers.

One embodiment of the present invention is embodied in a system 100, illustrated in the functional block diagram of FIG. 3. It should be noted that the system 100 comprises a series of software data files that are typically stored on a computer readable media, such as a floppy disk, illustrated in FIG. 3 by the dashed line and a reference numeral 102. The floppy disk 102 containing the system 100 can be used on any computer, such as the computer 10 (see FIG. 1). The user can insert the floppy disk 102 into the floppy disk drive 26 if the computer 10 does not function properly due to corrupted data files. The system 100 includes a plurality of software driver files 104. It should be noted that the term "software drivers" refer to a computer program used to operate an interface while the term "software driver file" refers to a physical data file stored on the floppy disk 102. Each of the software driver files 104 is intended for use with a specific type of CD-ROM drive 30. For example, a particular manufacturer may make three different models of CD-ROM drive. Thus, the system 100 would include a software driver file 104 for each of the three models of the CD-ROM drive 30 manufactured by that manufacturer. It should be noted that some software drivers can be used for more than one type of CD-ROM drive. In this situation, the system 100 need only store one copy of the software driver file 104 rather than a duplicate copy of the same software driver file for each of the CD-ROM drives 30 that use the same software driver.

The system 100 determines the identity of the particular CD-ROM drive 30 and loads the corresponding software driver from the plurality of software driver files 104. This is in contrast to the conventional computer 10 (see FIG. 1) in which the user must identify the particular type of CD-ROM drive, locate the software driver file developed for that particular CD-ROM drive, and load the particular software driver file. When the conventional computer 10 is first powered up, or reset, the CONFIG.SYS file provides the file name of the correct software driver file for the particular CD-ROM drive 30 and sets other parameters, such as buffer size, interrupt request line, and the like. However, the system 100 includes software driver files 104 for all known types of CD-ROM drives 30 or all types of CD-ROM drives supported by the computer manufacturer. When the computer 10 is first powered up, or reset, the system 100 automatically identifies the particular type of CD-ROM drive 30 and loads the appropriate software driver file. Thus, the system 100 may be thought of having a specialized CONFIG.SYS file 106 that contains lines of code to load all the software driver files 104. The system 100 automatically identifies the CD-ROM drive 30 and modifies the specialized CONFIG.SYS file 106 to load only the appropriate software driver file from the floppy disk 102 without the need for the user to identify a particular type of CD-ROM drive 30. Similar procedures can be used with other peripheral devices. This is especially advantageous for less experienced users who may have difficulty identifying the particular model of the CD-ROM drive 30, or may have forgotten the relevant information if the installation was completed some time ago.

The system 100 includes an initialization program 108, which begins execution following the execution of the instructions in the BIOS 16 (see FIG. 1). Thus, the initialization program 108 is a bootable program. The user operates the system 100 by simply inserting the floppy disk 102 in the floppy disk drive 26 and resetting the computer 10. The initialization program 108 contains one or more query instructions directed to the CD-ROM drive 30. The query instructions are generically labeled as a "FINDCD.SYS" instruction 112. The initialization program 108, including the FINDCD.SYS instruction 112, are automatically executed by the CPU 12 (see FIG. 1).

In a preferred embodiment, the CD-ROM drive interface 30a is an "integrated drive electronics" (IDE) interface. As is well known to those of ordinary skill in the art, the IDE type CD-ROM drive interface 30a can be used with a variety of different CD-ROM drives 30 because electrical circuitry (not shown) that is unique to the particular model of CD-ROM drive 30 is integrated into the CD-ROM drive itself. The FINDCD.SYS instruction 112 is designed to determine the type of CD-ROM drive 30 coupled to the IDE CD-ROM drive interface 30a. With the IDE type CD-ROM drive interface 30a, the FINDCD.SYS instruction 108 is an "Attention Application Programming Interface" (ATAPI) device identification instruction. The ATAPI device ID instruction is transmitted via the IDE type CD-ROM drive interface 30a to the CD-ROM drive 30. In response, the CD-ROM drive 30 returns a sequence of data bytes, including a vendor identification and model number for the CD-ROM drive 30. A typical response from the CD-ROM drive 30 to the receipt of an ATAPI device ID instruction is illustrated below in Table 2.

The response from the CD-ROM drive provides the necessary data to uniquely identify the particular CD-ROM drive 30. The initialization program 108 causes the CPU 12 to read the data and determine therefrom the model number of the particular CD-ROM drive 30.

The software driver files 104 are each associated with a particular CD-ROM drive 30. With the unique identification of the CD-ROM drive 30, the system 100 uses a look-up table 114 to identify the filename of the appropriate software driver file 104. The look-up table 114 contains a list of possible types of the CD-ROM drive 30 as inputs and outputs the name of the software driver file 104 corresponding to the identified CD-ROM drive type. The system 100 automatically selects the appropriate software driver from the software driver files 104 and loads the selected software driver into the appropriate location in the memory 14 (see FIG. 1).

An example of the specialized CONFIG.SYS file 106 is illustrated below in Table 3.

›common!

set cdrom=none.sub.-- yet

device=himem.sys/testmem:off

device=.backslash.cdrom.backslash.find-cd.sys

dos=high,umb

files=60

buffers=30

stacks=9,256

lastdrive=e:

;›menu!

;menuitem=mitsumi, Mitsumi 2x/4x

;menuitem=sanyo, Sanyo 4x

;menuitem=aspi4dos,NEC or Plextor CD W/adaptec 1542b/cf

;menuitem=aspi2dos,NEC or Plextor CD W/adaptec 6360/6260 chip

;menuitem=aspi8dos,NEC or Plextor CD W/adaptec 2940

;menuitem=amd,NEC or Plextor CD W/AMD scsi or scsi/lan chip

;menuitem=buslogic,NEC or Plextor CD W/Bus Logic PCI controller

;menuitem=hitachi,Hitachi IDE CDROM

;menuitem=sony,Sony IDE CD-ROM

;menuitem=teac,Teac IDE CD-ROM

;menuitem=flashpt,NEC or Plextor CD W/Bus Logic Flashpoint controller

;menuitem=future,NEC or Plextor CD W/Future Domain TMC- 1610 controller

;›mitsumi!

Device=cdrom.backslash.mtmcdai.sys /d:mtmide01

;set cdrom=mtmide01

;›aspi4dos!

device=cdrom.backslash.aspi4dos.sys /d

device=cdrom.backslash.aspi4cd.sys /d:aspi4cd0

;set cdrom=aspi4cd0

;›aspi2dos!

device=cdrom.backslash.aspi2dos.sys /z /d

device=cdrom.backslash.aspi2cd.sys /d:aspi2cd0

;set cdrom=aspi2cd0

;›aspi8dos!

device=cdrom.backslash.aspi8dos.sys /d

device=cdrom.backslash.aspi8cd.sys /d:aspi8cd0

;set cdrom=aspi8cd0

;›amd!

device=cdrom.backslash.amsida.sys

device=cdrom.backslash.cdromsys.sys /d:amdaspi

;set cdrom=amdaspi

;›buslogic!

device=cdrom.backslash.btdosm.sys /d

device=cdrom.backslash.aspiblcd.sys /d:busaspi

;set cdrom=busaspi

;›hitachi!

device=cdrom.backslash.hit.sub.-- ide.sys /d:mscd001

;set cdrom=mscd001

;›sony!

device=cdrom.backslash.atapi.sub.-- cd.sys /d:sony.sub.-- cd0

;set cdrom=sony.sub.-- cd0

;›sanyo!

device=cdrom.backslash.sjcdapi.sys /d:sanyocd0

;set cdrom=sanyocd0

;›teac!

device=cdrom.backslash.teac.sub.-- cdi.sys /d:teac.sub.-- cd0

;set cdrom=teac.sub.-- cd0

;›flashpt!

device=cdrom.backslash.flashpt.sys /d

device=cdrom.backslash.btcdrom.sys /d:busflpt

;set cdrom=busflpt

;›future!

device=cdrom.backslash.fdcd.sys /d:fdcd01

;set cdrom=fdcd01

;›common!

set endflag=1

;rem flag to denote the end of the config.sys file

The specialized CONFIG.SYS file 106 on the floppy disk 102 initially contains program lines to load all of the software driver files 104. The lines of code that configure the computer 10 (see FIG. 1) such as "files," "buffers," "stack," and the like are necessary for proper operation of the computer. However, only the lines of code that load the software driver file 104 (see FIG. 3) for the identified CD-ROM drive 30 are required for proper operation of the CD-ROM drive. The lines of code that refer to software driver files 104 for all other types of CD-ROM drives are unnecessary. The system 100 removes the unnecessary lines of code from the specialized CONFIG.SYS file 106 before they are executed by the CPU 12 (see FIG. 1). In a presently preferred embodiment, the system 100 effectively removes the unnecessary lines of code from the specialized CONFIG.SYS 106 by placing a remark (REM) command at the start of each unnecessary line of code. The CPU 12 will not execute any lines of code that begin with a REM. Thus, the system 100 automatically and uniquely identifies the CD-ROM drive 30 and selects the appropriate software driver file corresponding to the particular CD-ROM drive. The system 100 can be periodically updated to include new revisions of the software drivers and to add additional software drivers to the software driver files 104. This can be readily accomplished by replacing old versions of the software driver files 104 on the floppy disk 102 or adding new software driver files to the floppy disk and updating the specialized CONFIG.SYS file 106. Thus, the system 100 can be readily updated to include previously unknown types of CD-ROM drives 30.

In an alternative embodiment, the CD-ROM drive 30 is coupled to a small computer system interface (SCSI) 30a. As described above, the IDE type CD-ROM drive interface 30a uses a single common design to operate with a variety of different CD-ROM drives 30 using the appropriate software driver for that particular CD-ROM drive. In contrast, the SCSI type CD-ROM drive interface 30a is unique to each manufacturer, but typically uses a generic software driver file for all CD-ROM drives 30 for that manufacturer. Therefore, the system 100 must identify the model number of SCSI type CD-ROM drive interface 30a rather than the model number of the CD-ROM drive 30 itself.

The SCSI type CD-ROM drive interface 30 does not respond to the ATAPI identification instruction, as does the IDE type CD-ROM drive interface 30a. Therefore, the query instruction in the FINDCD.SYS instructions 112 for the SCSI type CD-ROM drive interface 30a comprises one or more instructions unique to each manufacturer of the SCSI type CD-ROM drive interface. The query instructions to the SCSI type CD-ROM drive interface 30 are unique to each manufacturer, and thus will not be discussed in greater detail herein. However, each model of SCSI type CD-ROM drive interface 30a will only respond appropriately to query instructions that are unique to that model, thus allowing the system 100 to uniquely identify the model number of the SCSI type CD-ROM drive interface. Once the system 100 has determined the model number of SCSI type CD-ROM drive interface 30a, the generic driver for that particular model of SCSI type CD-ROM drive interface is selected from the software driver files 104 and loaded into the appropriate location in the memory 14 (see FIG. 1). Thus, the system 100 determines the model number of the CD-ROM drive 30 coupled to the IDE type CD-ROM drive interface 30a, or the model number of the SCSI type CD-ROM drive interface 30a, and automatically loads the appropriate software driver. This is particularly advantageous for a user who has little or no technical knowledge about the computer 10.

The operation of the system 100 is illustrated in the flowchart of FIG. 4 where at a start 200 the computer 10 (see FIG. 1) has just been powered up or reset. In step 202, the computer 10 performs a hardware reset operation. In step 204, the computer 10 starts executing instructions from the BIOS 16. In step 206, the computer starts the DOS from the floppy disk 102 (see FIG. 3). As previously discussed, the computer 10 can be booted from the floppy disk 102. The system 100 begins execution of the initialization program 108 (see FIG. 3) in step 208. In step 212, the system 100 sends one or more query instructions to the CD-ROM drive 30 and the CD-ROM drive interface 30a. As discussed above, The query instruction may be an ATAPI instruction or query instructions unique to the particular manufacturer of the SCSI type CD-ROM drive interface 30a. In either event, a response from the CD-ROM drive 30 or CD-ROM drive interface 30a is used to identify the particular model number in step 214. In step 218, the system 100 modifies the specialized CONFIG.SYS file 106 to remove the unnecessary lines of code so that the computer 10 selects and loads the appropriate software driver from the software driver files 104 on the floppy disk 102. The system 100 ends at step 220 with the CD-ROM drive 30 having been configured and ready for operation. With a functioning CD-ROM drive 30, the user can readily reload any corrupted software data files or application software programs.

The system 100 is also capable of verifying proper operation of the hard disk drive 28 (see FIG. 1). In normal operation, the hard disk drive 28 is formatted and has at least one data partition. The use of partitions on the hard disk drive 28 are well known to those of ordinary skill in the art, and need not be described in detail herein. The system 100 automatically verifies the proper formatting and partitioning of the hard disk drive 28. If the hard disk drive is not properly formatted or partitioned, the system can automatically perform these functions.

In this aspect of the invention, the initialization program 108 on the floppy disk 102 also includes a series of DOS commands to check the partition and the formatting of the hard disk drive 28. If the hard disk drive 28 is not properly formatted and partitioned, the floppy disk 102 contains DOS commands, such as "FORMAT" that can be used to format and partition the hard disk drive 28. Other conventional DOS commands can be used by the system 100 to verify proper operation of the hard disk drive 28. As those skilled in the art can readily appreciate, the system 100 cannot perform these functions if the hard disk drive 28 has sustained actual damage and is non-functional. However, if the hard disk drive 28 is operational, but is not functioning due to corrupted formatting, partitioning, or the presence of other corrupted files, the system 100 can be used to automatically reformat and partition the hard disk drive.

The advantage of the system 100 is its ability to automatically identify and configure devices such as the CD-ROM drive 30 without the need for technical expertise on the part of the user. Although the system 100 has been described as being loaded on the floppy disk 102, the present invention is not limited to this embodiment. For example, the initialization program 108 and FINDCD.SYS instructions 112 could be part of the BIOS 16 (see FIG. 1). Similarly, the software driver files 104 could be part of the BIOS 16 as well. However, the installation of the software driver files 104 on a computer readable media such as the floppy disk 102 simplifies the process of revising and updating the software driver files 104.

It is, to be understood that even though various embodiments and advantages of the present invention have been set forth in the foregoing description, the above disclosure is illustrative only, changes may be made in detail, yet remain within the broad principles of the invention. Therefore, the present invention is to be limited only by the appended claims.