United States Patent [w]
`Todd et al.
`
`[54] SYSTEM AND METHOD FOR
`DISTRIBUTING CONFIGURATION-
`DEPENDENT SOFTWARE REVISIONS TO A
`COMPUTER SYSTEM
`
`[75]
`
`Inventors: David K. Todd, Atlanta, Ga.; Michael
`R. Terrell, Spencerport, N.Y.
`
`[73] Assignee: NCR Corporation, Dayton, Ohio
`
`[21] Appl. No.: 740,584
`
`Oct. 31, 1996
`
`[22] Filed:
`Int. CI.6
`G06F 9/445
`[51]
`395/712; 395/500; 395/651;
`[52] U.S. CI
`395/653; 707/10; 707/104; 707/201; 707/203
`[58] Field of Search
`395/712, 500,
`395/651, 653, 200.5, 200.51-200.54, 200.47-200.49,
`182.01, 182.05, 183.01, 183.03, 183.07,
`183.13, 183.14, 183.2, 184.01, 828, 830;
`707/1, 10, 104, 200, 201, 203; 364/550,
`551.01, 944.61, 946.1, 949.4, 191, 192,
`131, 132, 138, 147, 184; 702/119, 112,
`123, 183-186, 188
`
`[56]
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`US005867714A
`[ii] Patent Number:
`[45] Date of Patent:
`
`5,867,714
`Feb. 2, 1999
`
`5,155,847
`5,247,683
`5,287,505
`5,579,529
`5,619,716
`5,664,093
`
`10/1992
`9/1993
`2/1994
`11/1996
`4/1997
`9/1997
`
`Kirouac et al
`Holmes et al
`Calvert et al
`Terrell et al
`Nonaka et al
`Barnett et al
`
`395/200.51
`395/200.51
`707/10
`395/828
`395/712
`395/183.07
`
`Primary Examiner—Hal Dodge Wachsman
`Attorney, Agent, or Firm—-William A. Munck
`
`[57]
`
`ABSTRACT
`
`There is disclosed a system for detecting and avoiding laults
`stemming from conflicts in hardware and/or software con(cid:173)
`figurations in a computer system. The system comprises
`communications circuitry that, from time to time, automati(cid:173)
`cally transmits at least part ol the current hardware and
`software configuration data ol the computer system to a
`remote data source capable ol identifying inherent conflicts
`in the hardware and software configuration. The remote data
`source then transmits to the computer system software
`revisions that are capable ol resolving the inherent conflicts.
`Alter the communications circuitry receives the software
`revisions, processing circuitry in the computer system modi(cid:173)
`fies the current software configuration according to the
`received software revisions.
`
`5,019,963 5/1991 Alderson et al
`
`707/201
`
`20 Claims, 3 Drawing Sheets
`
`f 100
`
`JL 130 ( REMOTE DATA SOURCE )
`
`REGISTRATION
`DATABASE
`
`-132
`
`-REVISIONS
`
`CONFIGURATIONDATA-_
`
`COMMUNICATION LINK-
`
`-140
`
`MEMORY
`DEVICE
`
`PROCESSING
`CIRCUITRY
`
`,116
`
`NONVOLATILE
`MEMORY
`
`r118
`
`COMMUNICATIONS
`CIRCUITRY
`
`,120
`
`CONFIGURATION
`DETECTION CIRCUITRY
`
`--110 (COMPUTER SYSTEM)
`
`Page 1 of 13
`
`

`

`U.S. Patent
`
`Feb. 2, 1999
`
`Sheet 1 of 3
`
`5,867,714
`
`FIG. 1
`
`f 100
`
`L 130 ( REMOTE DATA SOURCE )
`
`REGISTRATION
`DATABASE
`
`-132
`
`REVISIONS
`
`COMMUNICATION LINK-
`
`CONFIGURATION DATA-
`
`-140
`
`L 112
`
`MEMORY
`DEVICE
`
`L 114
`
`PROCESSING
`CIRCUITRY
`
`L 116
`
`NONVOLATILE
`MEMORY
`
`L 118
`
`COMMUNICATIONS
`CIRCUITRY
`
`L 120
`
`CONFIGURATION
`DETECTION CIRCUITRY
`
`I 110 (COMPUTER SYSTEM)
`
`Page 2 of 13
`
`

`

`U.S. Patent
`
`Feb. 2, 1999
`
`Sheet 2 of 3
`
`5,867,714
`
`FIG. 2A
`
`(START
`
`205
`
`DETECT CHANGES
`IN CONFIGURATION
`
`210
`
`ALTER CURRENT
`CONFIGURATION DATA
`
`215
`
`200-
`
`STORE CURRENT
`CONFIGURATION DATA
`
`220
`
`FIG. 2B
`
`CM
`
`225
`
`( START
`
`235
`
`ESTABLISH
`COMMUNICATIONS LINK
`
`240
`
`IDENTIFY CONFLICTS
`
`245
`
`SELECT
`SOFTWARE REVISIONS
`
`250
`
`TRANSMIT
`SOFTWARE REVISIONS
`
`— 255
`
`MODIFY SOFTWARE
`CONFIGURATION
`
`— 260
`
`(END
`
`265
`
`Page 3 of 13
`
`

`

`U.S. Patent
`
`Feb. 2,1999
`
`sheet 3 of 3
`
`5,867,714
`
`FIG. 3
`
`330
`
`CENTRAL
`DATA SOURCE
`
`REMOTE
`
`)
`
`( REMOTE
`
`•31 OB
`
`^310C
`
`Page 4 of 13
`
`

`

`5,867,714
`
`SYSTEM AND METHOD FOR
`DISTRIBUTING CONFIGURATION-
`DEPENDENT SOFTWARE REVISIONS TO A
`COMPUTER SYSTEM
`
`TECHNICAL FIELD OF THE INVENTION
`
`The present invention is directed, in general, to a com(cid:173)
`puting apparatus and, more specifically, to a computer
`system capable of distributing or receiving software revi(cid:173)
`sions that are a function of a specific system hardware and
`software configuration.
`
`BACKGROUND OF THE INVENTION
`Immeasurable gains in technology offered in personal
`computers ("PCs") have allowed PCs to assume roles per(cid:173)
`formed only by mainframe or minicomputers in the past.
`Many companies and individual users rely solely on
`commercially-available PCs, such as those provided by
`NCR, to meet their information processing needs. Thus, it is
`vital that their PCs perform reliably. If, however, a PC
`experiences a fault, it is equally vital that the PC commu(cid:173)
`nicate existence of the fault to inform the user of a need to
`repair the fault so the PC can return to active service. For
`computer systems in general, it is most helpful for the
`computer system itself to provide an indication of the
`specific location and nature of the fault to help the user more
`quickly isolate and more economically repair the fault. To
`that end, today's PCs are typically equipped with some form
`of internal diagnostics, the purpose of which is to detect and
`subsequently isolate specific hardware and software com(cid:173)
`ponent failures and faults brought about by interactions
`among the PC's hardware and software components (so-
`called "conflicts" leading to so-called "configuration
`faults").
`For years, PCs have been provided with diagnostic rou(cid:173)
`tines that test and report on the operational status or func(cid:173)
`tionality of hardware and software components within the
`computer, allowing a user to repair or replace hardware or
`software components that are not functioning to the desired
`degree or to resolve certain conflicts manually.
`As PC systems become more and more complex and as
`users come more and more to rely on the services of remote,
`skilled technicians to maintain and repair their PCs, it is
`growing less desirable to force the user to diagnose PC faults
`alone. The general direction in the development of diagnos(cid:173)
`tic software systems to this point has been to isolate the user
`somewhat from the intricate and technically complex opera(cid:173)
`tions of diagnostic routines by: (1) providing more user-
`friendly diagnostic programs to the user, with interfaces
`written in clear text and presented in an aesthetically pleas(cid:173)
`ing manner and (2) providing remote diagnostic capability
`so the remote technician may query the PC directly and
`determine faults without the user's substantial participation.
`However, the user is still forced to undergo a fault and
`contact a remote technician for help.
`Unlike outright hardware or software failures, conflicts
`arise quite frequently and are entirely predictable. Quite
`often, technicians see the same conflicts over and over again.
`Users having similar hardware and software configurations
`tend to experience the same conflicts, some earlier than the
`rest. Therefore, the user may not have had to experience the
`conflict in the first place.
`The solution to such configuration problems usually
`involves manually correcting the computer's configuration
`by revising (usually updating) portions (such as libraries and
`hardware drivers) of the computer's operating system. The
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`remote technician or the user may effect these revisions.
`Unfortunately, the above-described solutions to the diagnos(cid:173)
`tic problem still require the user to suffer a fault and contact
`a technician, even if it is an avoidable fault due to a conflict.
`In the past, the answer has seemed to lie merely in
`automating the diagnostic process. For example, U.S. Pat.
`No. 5,287,505, issued on Feb. 15, 1994, to Calvert, et al,
`and entitled "On-line Problem Management of Remote Data
`Processing Systems, Using Local Problem Determination
`Procedures and a Centralized Database" is directed to auto(cid:173)
`mated problem analysis and resolution of a customer data-
`processing system in which a central service data-processor
`system communicates with the customer system. Included is
`a database for converting machine, software and symptom
`data into instructions, hardware and software module lists,
`and service call schedules. The customer system detects data
`concerning its own configuration and problem symptoms for
`communication to the service system. The service system
`itself orders repair modules, and electronically communi(cid:173)
`cates software fixes to the customer system.
`Unfortunately, Calvert, et al., is expressly directed to
`repair of a fault once it has occurred and does not provide a
`means by which to anticipate and avoid faults, particularly
`configuration faults arising out of hardware/software con(cid:173)
`flicts.
`In the past, some effort has been given to automating the
`process of software revision to avoid prospective, purely
`software-based faults. For example, U.S. Pat. No. 5,155,847,
`issued on Oct. 13, 1992, to Kirouac, et al., and entitled
`"Method and Apparatus for Updating Software at Remote
`Locations" is directed to a method and system for updating
`the software used in remote computer systems from a central
`computer system. The method includes storing, in the cen(cid:173)
`tral computer system, copies of the software executable used
`in each remote computer system. When the copies of the
`software in the central computer system are upgraded, for
`example, to correct the software, to add new facilities, to
`change user interfaces, to make cosmetic changes, to
`improve performance, etc., each change made to the soft(cid:173)
`ware is monitored and stored. The remote computer systems
`are permitted access to the central computer system via
`communications links and the software in the remote com(cid:173)
`puter systems and the corresponding software in the central
`computer system are compared. All of the changes that have
`been made to the software in the central computer system
`which have not been made to the corresponding software at
`the remote computer system accessing the central computer
`are detected. The detected changes are then transmitted to
`the remote computer system and applied to the software
`therein in order to upgrade the software in the remote
`computer system. The upgraded software in the remote
`computer system is examined to ensure that the software has
`been changed correctly. The method allows the software at
`the remote computer systems to be upgraded even while the
`software at the remote site is being used. The system and
`method also allow the software used in the remote computer
`systems to be upgraded when the remote computer systems
`use different versions of the software and allow the software
`to be upgraded in a variety of hardware environments and
`operating systems.
`
`Unfortunately, Kirouac, et al., is directed only at revising
`application-level software. Kirouac, et al. is not directed to
`analyzing the complete hardware and software configuration
`of a computer system in an effort to identify hardware/
`software conflicts and potential configuration faults. Further,
`Kirouac, et al., is not directed to revising components of the
`computer's operating system.
`
`Page 5 of 13
`
`

`

`5,867,714
`
`Given that potential faults due to conflicts are diagnosable
`and readily repairable, what is needed in the art is a system
`and method for automatically correcting hardware/software
`conflicts that have potential for causing a fault, preferably
`well before they actually become faults. The system and 5
`method should be capable of distributing or receiving soft(cid:173)
`ware revisions that are a function of a specific system
`hardware and software configuration to address the conflict.
`
`SUMMARY OF THE INVENTION
`To address the above-discussed deficiencies of the prior
`art, the present invention provides, for use with a computer
`system having a hardware and software configuration sub(cid:173)
`ject to change over time, a system for, and method of,
`receiving software revisions as a function of the hardware
`and software configuration. The system includes: (1) current
`configuration data, stored in a memory device associated
`with the computer system, containing a current description
`of at least a portion of the hardware and software
`configuration, (2) communications circuitry, associated with
`the computer system, that automatically establishes a com(cid:173)
`munications link between the computer system and a remote
`data source to transmit the current configuration data to the
`remote data source, the remote data source able to identify
`conflicts
`inherent
`in
`the hardware and software
`configuration, select configuration-dependent software revi(cid:173)
`sions (revisions that are a function of the hardware and
`software configuration) and transmit the software revisions
`to the computer system to address at least some of the
`conflicts and (3) processing circuitry, associated with the
`computer system, that modifies a software configuration of
`the computer system in accordance with the software revi(cid:173)
`sions thereby to avoid a configuration fault.
`The above-described system therefore allows at least a
`portion of a computer's hardware and software configuration 35
`to be stored and remotely monitored. If the hardware and
`software configuration indicates a conflict and therefore a
`potential configuration fault ahead for the user, the remote
`data source can distribute the necessary configuration revi(cid:173)
`sions to address the conflict and thereby avoid the configu- 40
`ration fault entirely. In this way, valuable user and technician
`time can be saved.
`The remote data source should preferably be able to
`identify conflicts inherent in the hardware and software
`configuration. Most preferably, the power of identification is 45
`had by experience. In other words, when a user or other
`party (such as a manufacturer) identifies or experiences a
`fault brought about by a conflict, the knowledge required to
`identify the conflict and the necessary configuration revi(cid:173)
`sions are added to the remote data source. Thus, the remote 50
`data source acts as a conflict and revision database.
`However, this need not be the case. The remote data source
`may alternatively take the form of an expert system that is
`able to identify conflicts before anyone experiences them.
`In one embodiment of the present invention, the remote 55
`data source comprises a registration database containing
`other data pertaining to the computer system, the remote
`data source able to identify the conflicts by analyzing the
`current configuration data and the other data.
`Often, proper diagnosis of a conflict is enhanced when 60
`information about the computer system, other than configu(cid:173)
`ration data, is known. The other data may comprise, for
`instance, the make, model and serial number of the computer
`system and data indicating the personal working habits of
`the computer system's user. Of course, still other data may 65
`be desired; the present invention is not limited by the type
`of data used for diagnosis and revision.
`
`In one embodiment of the present invention, the commu(cid:173)
`nications circuitry periodically automatically establishes the
`communications link between the computer system and the
`remote data source. This may, most advantageously, result in
`nightly or weekend contacts for the purpose of receiving
`configuration revisions. Of course, the present invention is
`not limited to automatic, periodic contact; the user may
`contact the remote data source at will or aperiodically.
`In one embodiment of the present invention, the system
`further comprises configuration detection circuitry that
`detects changes in the hardware and software configuration
`and automatically alters the current configuration data as a
`function thereof. Preferably, the user does not need to
`intervene in altering the current configuration data. The
`computer system can be programmed to perform the func(cid:173)
`tion automatically. However, the broad scope of the present
`invention certainly encompasses manual alteration of the
`current configuration data by the user.
`In one embodiment of the present invention, the software
`revisions include revisions to operating system software
`stored in nonvolatile memory associated with the computer
`system. As previously described, conflicts are often resolved
`by revising portions of the computer's operating system,
`some of which may reside in nonvolatile memory (such as
`Electrically-Erasable Programmable Read-Only Memory
`("EEPROM")) within the computer system. However, the
`broad scope of the present invention is not so limited.
`Revisions may be made to other operating system software
`or to application programs.
`In one embodiment of the present invention, the current
`configuration data includes usage pattern tracking data. The
`usage pattern tracking data may be employed to monitor the
`manner in which the user employs the computer system.
`Thus, the present invention may be regarded as not only a
`solver of potential problems, but also as a finder of oppor(cid:173)
`tunity. As will be explained in greater detail below, the
`present invention may be employed to allow a manufacturer
`to track how its customers are using their computers, giving
`the manufacturer specific access and insight to its custom(cid:173)
`ers' needs and allowing the manufacturer to target its
`customer base with appropriate advertising.
`In one embodiment of the present invention, the commu(cid:173)
`nications circuitry establishes the communications link via a
`selected one of a telecommunications system and a com(cid:173)
`puter network. Thus, the present invention, in its broadest
`form, contemplates any mode of contact to effect the com(cid:173)
`munications link.
`Another aspect of the present invention provides a system
`for automatically distributing configuration-dependent soft(cid:173)
`ware revisions, comprising: (1) a central data source, (2) a
`plurality of remote computer systems, each of the plurality
`of remote computer systems having an associated system for
`receiving software revisions from the central data source, the
`associated system including: (2a) current configuration data
`containing a current description of at least a portion of a
`hardware and software configuration of the associated
`remote computer system, (2b) communications circuitry that
`automatically establishes a communications link between
`the remote computer system and the central data source to
`transmit the current configuration data to the central data
`source and receive software revisions from the central data
`source in response thereto and (2c) processing circuitry,
`associated with the remote computer system, that modifies a
`software configuration of the computer system in accor(cid:173)
`dance with software revisions and (3) revision selection
`circuitry, associated with the central data source that
`
`Page 6 of 13
`
`

`

`5,867,714
`
`receives current configuration data from the plurality of
`remote computer systems, identifies conflicts inherent in the
`hardware and software configurations of the plurality of
`remote computer systems, selects software revisions as a
`function of the hardware and software configurations and 5
`transmits the software revisions to respective ones of the
`remote computer system to address at least some of the
`conflicts. In alternate embodiments, the revision selection
`circuitry may identify conflicts inherent in the hardware and
`software configuration of a single computer system, select 10
`software revisions as a function of that hardware and soft(cid:173)
`ware configuration and transmit the software revisions to the
`computer system to address at least some of the conflicts.
`An advantageous embodiment for employing or distrib(cid:173)
`uting the present invention is as software. The software 15
`embodiment includes a plurality of processing system
`instructions that may suitably be stored to a conventional
`storage medium. Preferred storage media include without
`limitation magnetic, optic and electric, as well as suitably
`arranged combinations of the same. The processing system 20
`instructions are readable and executable by one or more
`computer or processing systems
`to distributing
`configuration-dependent software revisions to a computer
`system in accordance with the principles of the present
`invention.
`The foregoing has outlined, rather broadly, preferred and
`alternative features of the present invention so that those
`skilled in the art may better understand the detailed descrip(cid:173)
`tion of the invention that follows. Additional features of the
`invention will be described hereinafter that form the subject 30
`of the claims of the invention. Those skilled in the art should
`appreciate that they can readily use the disclosed conception
`and specific embodiment as a basis for designing or modi(cid:173)
`fying other structures for carrying out the same purposes of
`the present invention. Those skilled in the art should also 35
`realize that such equivalent constructions do not depart from
`the spirit and scope of the invention in its broadest form.
`
`25
`
`("RAM"), read-only memory ("ROM"), a conventional
`mass storage device, such as a floppy or hard disk drive, or
`the like). "Include," as the term is used herein, means
`inclusion without limitation. The memory device 112 is
`conventionally capable of storing data of many
`types.
`However, the present invention advantageously employs the
`memory device 112 to store current configuration data
`pertaining to the hardware and software configuration of the
`computer system 110. The kind of data contained in the
`current configuration data will be set forth in greater detail
`below.
`The computer system 110 is further illustrated as includ(cid:173)
`ing processing circuitry 114. The processing circuitry 114
`generally governs the flow of software
`instructions and
`substantive data within the computer system 110. In FIG. 1,
`the processing circuitry 114 is used to provide, among other
`things, read/write access to the memory device 112.
`The computer system
`further
`includes nonvolatile
`memory 116. The nonvolatile memory 116 may be ROM,
`EEPROM or a conventional mass storage device and may be
`used to store, among other things, operating system software
`components, such as hardware drivers (not shown). In
`conventional PC systems, the nonvolatile memory employed
`for this purpose is ROM or EEPROM. Because the revisions
`distributed according to the present invention may suitably
`include revisions to operating system components stored in
`the nonvolatile memory 116, it is advantageous that the
`nonvolatile memory 116 be EEPROM, such that the revi(cid:173)
`sions may be written to the nonvolatile memory 116.
`The computer system 110 is further illustrated as includ(cid:173)
`ing communications circuitry 118. The communications
`circuitry 118 may be, for example, a modem (allowing the
`computer system 110 to communicate via a telecommuni(cid:173)
`cations system (not shown)) or a network interface card
`("NIC") (allowing the computer system 110 to communicate
`via a computer network (not shown)). It should be
`understood, however, that the present invention in its broad(cid:173)
`est form is indifferent to the type of system or mode of
`communication in which the communications circuitry 118
`is designed to operate.
`The computer system 110 further includes configuration
`detection circuitry 120. The configuration detection circuitry
`120 is responsible for obtaining data pertaining to at least a
`portion of the current hardware and software configuration
`of the computer system 110. The configuration detection
`circuitry 120 may be as simple as a software program,
`executable within the computer system 110, for querying the
`user as to the current hardware and software configuration.
`More preferably, however, the configuration detection cir(cid:173)
`cuitry 120 determines the hardware and software configu(cid:173)
`ration automatically, by polling hardware components and
`cataloging software components to create a list of current
`configuration data setting forth the components that com(cid:173)
`prise the computer system 110. Such a list might read as
`follows:
`
`Manufacturer Name:
`Manufacturer No.
`Serial No.
`Computer Name
`ID Bytes
`Bus
`Processor
`CPU State
`
`COMPUTER
`
`Dell Computer Corp.
`99999
`99999
`Generic AT Compatible
`FC, 01 (IBM AT 339)
`ISA (16 bit)
`Cyrix 486DLC, 50 Mhz
`V8086 Mode, A20 On
`
`45
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`For a more complete understanding of the present
`invention, reference is now made to the following descrip(cid:173)
`tions taken in conjunction with the accompanying drawings,
`in which like numbers designate like parts and in which:
`FIG. 1 illustrates a block diagram of a system constructed
`according to the principles of the present invention; and
`FIG. 2A illustrates a flow diagram of a method of ensuring
`that configuration data are current;
`FIG. 2B illustrates a flow diagram of a method of estab(cid:173)
`lishing a communications link and receiving software revi- 50
`sions; and
`FIG. 3 illustrates a block diagram of a centralized system
`for automatically distributing configuration-dependent soft(cid:173)
`ware revisions.
`DETAILED DESCRIPTION
`Referring initially to FIG. 1, illustrated is a block diagram
`of a system constructed according to the principles of the
`present invention. The system, generally designated 100, is
`illustrated as residing locally on a computer system 110 so
`(which may advantageously be a PC or any other conven(cid:173)
`tional suitably arranged processing system), using existing
`circuitry within the computer system 110 to perform novel
`functions according to the present invention. "Or," as the
`term is used herein, is inclusive, meaning and/or.
`The computer system 110 is illustrated as including a
`memory device 112 (which may be random access memory
`
`55
`
`65
`
`Page 7 of 13
`
`

`

`5,867,714
`
`Coprocessor
`Setup Type
`Clock
`
`7
`-continued
`
`Cyrix 80387, 50 Mhz
`CMOS RAM
`CMOS
`BIOS/DOS
`
`BIOS Mfr
`BIOS Size
`DOS Version
`BIOS Date
`
`AMI
`64K
`7.00
`06/06/92
`PRIMARY VIDEO
`1-1991 TRIDENT MICROSYSTEMS INC
`Copyright 1985
`
`Adapter
`RAM Size
`Video BIOS
`Chip Set
`VESA Installed
`Max Resolution
`Max Colors
`Max Text Mode
`Monitor
`
`VESA
`1,024K
`Trident
`Unknown
`Yes (Version 1.02)
`1280X1024, 16 colors (106h)
`640X480, 16777216 colors (112h)
`132X60, 16 colors (lOch)
`VGA Color
`SECONDARY VIDEO
`
`No Adapter
`PHYSICAL MEMORY
`
`Base... Total
`Available
`Upper Memory...
`Largest Block
`Extended... Total
`Available
`
`Total
`
`640K
`619K
`156K
`OK
`7,168K
`None
`MANAGED MEMORY
`
`XMS... Total
`Available
`HMA
`Version
`Driver Rev.
`EMS...
`
`Total Size
`DOS Free
`Partition 1
`Size
`Partition 2
`Partition 3
`Partition 4
`BIOS Geometry
`Real Geometry
`Interleave
`Sectors Wasted
`CMOS Type
`Best Match
`Interface
`Encoding
`Translated
`Model
`Rev.
`Manufacturer No.
`
`Total Size
`DOS Free
`Partition 1
`Size
`Partition 2
`Partition 3
`Partition 4
`BIOS Geometry
`Real Geometry
`Interleave
`Sectors Wasted
`CMOS Type
`Interface
`Encoding
`Translated
`Model
`Rev
`
`14,044K
`6,876K (taken from Extended Memory)
`64K (in-use)
`3.00
`3.5
`No Driver Installed
`HARD DRIVE 0
`
`169M
`11M
`Big DOS (C:)
`169M
`Not Defined
`Not Defined
`Not Defined
`902 Cyls, 8 Heads, 46 Sectors
`Unknown
`(undetermined)
`Unknown
`47
`47
`IDE/ESDI (BIOS driver)
`Advanced
`Unknown
`Unknown
`N/A
`N/A
`HARD DRIVE 1
`
`169M
`11M
`Big DOS (D:)
`169M
`Not Defined
`Not Defined
`Not Defined
`902 Cyls, 8 Heads, 46 Sectors
`Unknown
`(undetermined)
`Unknown
`47
`Best Match: 47
`IDE/ESDI (BIOS driver)
`Advanced
`Unknown
`Unknown
`N/A
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`Mfr S/N
`
`Size
`DOS Name
`Geometry
`Media Support
`
`Disk Size
`
`Size
`DOS Name
`Geometry
`Media Support
`
`Disk Size
`
`PortO
`Name
`I/O Address
`Chip Type
`FIFO
`Settings
`Portl
`Port 2
`Port3
`
`PortO
`Name
`I/O Address
`Bidirectional
`Port 1
`Port 2
`
`Adapter
`Monitor
`Max Colors
`Max Resolution
`
`Sound Device
`Compatibility:
`Features
`
`Interface
`I/O Address
`Version
`
`Interface
`Driver
`Version
`DOS Name(s)
`
`Type
`Num Lock
`Caps Lock
`Scroll Lock
`
`Type
`Speed
`Driver Revision
`
`8
`-continued
`
`N/A
`FLOPPY DRIVE 0
`
`1.2M(5.25")
`A:
`80 Tracks, 2 Heads, 15 Sectors
`1.2M High Density
`360K Double Density
`(no disk in drive)
`FLOPPY DRIVE 1
`
`1.44M(3.5")
`B:
`80 Tracks, 2 Heads, 18 Sectors
`1.44M High Density
`720K Double Density
`(no disk in drive)
`SERIAL PORTS
`
`DOS
`COM1:
`3F8h
`16550A
`No
`2400 Baud, None, 8, 1
`No Port
`No Port
`No Port
`PARALLEL PORTS
`
`DOS
`LPT1:
`378h
`No
`No Port
`No Port
`VIDEO
`
`VESA
`VGA Color
`640X480, 16777216 colors (112h)
`1280X1024, 16 colors (106h)
`SOUND
`
`Sound Blaster Compatible
`Sound Blaster, Adlib
`FM Synthesis
`Digital Playback
`Microphone Input
`Internal Card
`220h
`3.0
`CD-ROM
`
`Microsoft CD-ROM Extensions
`MSCDEX.EXE
`2.23
`E:
`KEYBOARD
`
`101-key Enhanced
`On
`Off
`Off
`MOUSE
`
`Serial (2 button)
`Medium
`8.48
`A i!/~\T\T7"fc It -1
`MODEM 1
`
`Not Determined Yet
`MODEM 2
`
`Not Determined Yet
`FAX
`
`No FAX Found
`
`Page 8 of 13
`
`

`

`9
`-continued
`
`Interrupt
`
`Vectors Usage
`
`5,867,714
`
`10
`-continued
`
`5
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`OOh
`Olh
`02h
`03h
`04h
`05h
`06h
`07h
`08h
`09h
`OAh
`OBh
`OCh
`ODh
`OEh
`OFh
`lOh
`l lh
`12h
`13h
`14h
`ISh
`16h
`17h
`18h
`19h
`lAh
`IBh
`ICh
`IDh
`lEh
`IFh
`20h
`21h
`22h
`23h
`24h
`25h
`26h
`27h
`28h
`29h
`2Ah
`2Bh
`2Ch
`2Dh
`2Eh
`2Fh
`30h
`31h
`32h
`33h
`34h
`35h
`36h
`37h
`38h
`39h
`3Ah
`3Bh
`3Ch
`3Dh
`3Eh
`3Fh
`40h
`41h
`42h
`43h
`44h
`45h
`46h
`47h
`48h
`49h
`4Ah
`4Bh
`4Ch
`4Dh
`
`Divide Error
`Debug Exceptions
`Non-Maskable Interrupt
`Breakpoint
`Overflow
`Print Screen Handler
`Invalid Opcode
`No Coprocessor
`IRQO-Timer
`IRQl-Keyboard
`IRQ2-EGA Vert. Retrace
`IRQ3-COM2
`IRQ4-COM1
`IRQ5
`IRQ6-Diskette
`IRQ7-Printer
`Video
`Equipment Determination
`Mem. Size Determination
`Diskette & Fixed Disk
`Serial
`System Services
`Keyboard
`Printer
`Transfer to ROM BASIC
`Bootstrap Loader
`Timer & Real-Time Clock
`Ctrl-Break
`Clock Tick
`Video Init Tables
`Diskette Parameters
`Graphics Set 2
`DOS Prog. Termination
`DOS System Services
`DOS Terminate Address
`DOS Ctrl-C Address
`Critical Error Handler
`DOS Absolute Disk Read
`DOS Absolute Disk Write
`Terminate Stay Resident
`DOS Keyboard Busy Loop
`DOS Fast Putchar
`NETBIOS, Other Networks
`Reserved for DOS
`Reserved for DOS
`Reserved for DOS
`DOS Internal EXECUTE
`Multiplex
`CP/M JMP Command
`DPMI
`Reserved for DOS
`MOUSE
`on
`Float
`ng Pt. Emulat
`on
`Float
`ng Pt. Emulat
`on
`Float
`ng Pt. Emulat
`on
`Float
`ng Pt. Emulat
`on
`Float
`ng Pt. Emulat
`on
`Float
`ng Pt. Emulat
`on
`Float
`ng Pt. Emulat
`on
`Float
`ng Pt. Emulat
`on
`Float
`ng Pt. Emulat
`on
`Float
`ng Pt. Emulat
`Floating Pt. Emulation
`Overlay & DLL Managers
`Orig Diskette Handler
`1st Fixed Disk Params
`Orig Video Handler
`EGA/VGA UserFontTable
`EGA/VGA Fonts
`Unused
`2nd Fixed Disk Params
`S QL Base API
`Unused
`Unused
`User Alarm
`Unused
`Unused
`Unus ed
`
`0520:0139
`0070:0465
`0520:025E
`0070:0465
`0070:0465
`F000:FF54
`F000:EB43
`F000:EAEB
`0498:0000
`CE69:0028
`CE69:003A
`CE69:0052
`CE69:006A
`CE69:0082
`CE69:009A
`0070:0465
`DC17:000A
`F000:F84D
`F000:F841
`FD5B:2532
`F000:E739
`0251:053A
`0070:042D
`CC9D:0A28
`F000:E000
`
`F000:FE6E
`CC9D:0604
`0498:001D
`F000:F0A4
`
`C000:4E16
`00C9:0FA8
`CC9D:04A0
`FDA9:2052
`FD45:2692
`03B6:080B
`00C9:0FBC
`00C9:0FC6
`00C9:0FD0
`00C9:106F
`0070:0466
`CC9D:05B4
`00C9:106F
`00C9:106F
`00C9:106F
`03A8:0000
`03B6:03CC
`C90F:E4EA
`F000:EA00
`00C9:106F
`0492:0001
`152E:0306
`152E:0306
`152E:0306
`152E:0306
`152E:0306
`152E:0306
`152E:0306
`152E:0306
`152E:0306
`152E:0306
`152E:03C6
`00C9:106F
`F000:EC59
`F000:E13D
`F000:F065
`C000:5216
`F000:EA97
`F000:EA97
`F000:E14D
`F000:EA97
`F000:EA97
`F000:EA97
`F000:EA97
`FD49:2652
`F000:EA97
`F000:EA97
`
`Available
`DOS Kernel
`Available
`DOS Kernel
`DOS Kernel
`System ROM
`System ROM
`System ROM
`vmm32
`UMB
`UMB
`UMB
`UMB
`UMB
`UMB
`DOS Kernel
`UMB
`System ROM
`System ROM
`System ROM
`System ROM
`EMM386
`DOS Kernel
`UMB
`System ROM
`
`System ROM
`UMB
`vmm32
`System ROM
`
`Video ROM
`DOS Kernel
`UMB
`System ROM
`System ROM
`WIN
`DOS Kernel
`DOS Kernel
`DOS Kernel
`DOS Kernel
`DOS Kernel
`UMB
`DOS Kernel
`DOS Kernel
`DOS Kernel
`W IN Data
`WIN
`UMB
`System ROM
`DOS Kernel
`vmm32
`Available
`Available
`Available
`Available
`Available
`Available
`Available
`Available
`Available
`Available
`Available
`DOS Kernel
`System ROM
`System ROM
`System ROM
`Video ROM
`System ROM
`System ROM
`System ROM
`System ROM
`System ROM
`System ROM
`System ROM
`System ROM
`System ROM
`System ROM
`
`4Eh
`4Fh
`50h
`51h
`52h
`53h
`54h
`55h
`56h
`57h
`58h
`59h
`5Ah
`5Bh
`5Ch
`5Dh
`5Eh
`5Fh
`60h
`61h
`62h
`63h
`64h
`65h
`66h
`67h
`68h
`69h
`6Ah
`6Bh
`6Ch
`6Dh
`6Eh
`6F