Booting a computer system using the last valid configuration

Abstract: The present invention provides a current set of configuration data to be used in a first attempt to boot the computer system, and the LastKnownGood set of configuration data which stores the last set of configuration data that successfully booted the computer system. The present invention first attempts to boot the computer system from the current set of configuration data. In response to an unsuccessful attempt to boot the computer system using the current set of configuration data, the present invention automatically boots the computer system using the LastKnownGood set of configuration data. In response to a successful boot of the computer system using the LastKnownGood set of configuration data, the present invention makes a new current set of configuration data that is equivalent to the LastKnownGood set of configuration data that successfully booted the computer system. In response to a successful boot from the current set or configuration data, the present invention makes a new LastKnownGood set of configuration data that is equivalent to the current set of configuration data which successfully booted the computer system. If boot appears to succeed to software, but fails in a way apparent to a human user, the system may be manually forced to use the LastKnownGood configuration set.

Description: Technical Field This invention relates generally to a method and system for booting a computer, and more specifically, to a method and system which ensures that the boot-up procedure will always be successful. Background or the Invention When a user starts a personal computer system, the computer system goes through a complex set of operations to make sure that all of its components are working properly. This operation is but the first step in an even more complicated process called the system boot-up procedure ( i.e ., the boot). Booting the system activates all of the computer system's components long enough to load an operating system. The operating system is a computer program that allows the computer system to use other computer programs. Before attempting to load the operating system, the computer system insures that the system's input-output hardware, central processing unit, and main memory are all functioning. This is accomplished through the use of a power-on self-test, or Post. After the Post checks all of the hardware components of the computer system, a boot program contained in the computer's ROM BIOS chips checks drive A of the computer to see if drive A contains a formatted floppy disk. If a formatted floppy disk is positioned in drive A, then the boot program loads the first sector of the disk into memory and executes it. If there is no formatted floppy disk in drive A, then the first sector on the first hard drive is loaded into memory and executed. The first sector on the hard drive contains a program that reads the partition table of the hard drive and determines which partition is marked active. The first sector from the active partition is then loaded into memory and executed. The first sector on the active partition or floppy disk contains a program that searches for files that comprise the first files of the operating system. On most personal computer systems, the files are named IO.SYS and MSDOS.SYS. On IBM computers, the two files are named IO.SYS and IBMDOS.COM. For purposes of this discussion, it will be assumed that the two system files are IO.SYS and MSDOS.SYS. IO.SYS provides a low level interface to the ROM BIOS device routines. MSDOS.SYS is the DOS program itself and provides a high-level interface for user programs. It consists of file management routines, data blocking/deblocking for the disk routines, and a variety of built-in functions easily accessible by user programs. When these function routines are invoked by a user program, they accept high-level information via register and control block contents, then translate the requirements into one or more calls to IBMBIO.COM to complete the request. The boot record takes control of the computer system and loads the two operating system files into memory. The IO.SYS file contains extensions to the ROM BIOS and includes a routine called SYSINIT that manages the rest of the system boot procedure. After loading IO.SYS, the boot record is replaced in memory by other program code, and SYSINIT assumes control of the system boot procedure. In doing so, SYSINIT loads MSDOS.SYS into memory. SYSINIT then searches the root directory of the computer memory for a file named CONFIG.SYS. If CONFIG.SYS exists in the computer system, then SYSINIT requests that MSDOS.SYS execute the commands in the CONFIG.SYS file. CONFIG.SYS is a file created by the computer user and contains commands which tell the operating system how to handle certain operations, such as how many files may be opened at one time, and how many system buffers may be used at any one time. CONFIG.SYS also contains instructions to load device drivers. A device driver is a program that the operating system uses to control hardware that communicates with the computer system. For example, MS-DOS uses a device driver to control how information is written to and read from a floppy disk drive. MS-DOS also has built-in device drivers for the computer system keyboard, monitor, hard drives, and communication ports. Next, SYSINIT tells MSDOS.SYS to load the file COMMAND.COM. One function of COMMAND.COM is to search the root directory of the computer memory for a file named AUTOEXEC.BAT. AUTOEXEC.BAT is a file created by the computer user and contains a series of MS-DOS batch file commands and/or the names of programs that the user wants to run each time the computer system is actuated. Typically, the computer system is now fully booted and ready to be used. However, as new hardware components are added to the computer system or as user needs change, it becomes necessary to modify the two user created system boot files, CONFIG.SYS and AUTOEXEC.BAT. Prior art systems allow the user to add and change CONFIG.SYS commands or AUTOEXEC.BAT commands to configure the computer system to suit the user's needs. To edit the CONFIG.SYS file, the MS-DOS editor or a text editor that saves files as unformatted (ASCII text) is typically used. Once the changes to the CONFIG.SYS file or the AUTOEXEC.BAT file have been completed, the user must restart the computer system in order to have the changes take effect because MS-DOS reads the CONFIG.SYS file and the AUTOEXEC.BAT file only during the boot-up procedure ( i.e ., when the computer system is started). Occasionally, the changes to the CONFIG.SYS file or the AUTOEXEC.BAT file will cause the computer system to "hang" ( i.e ., not boot) in a way that prevents the user from editing, and therefore correcting, the system boot files. For example, in some cases where the system boot files are unusable, the device driver for the computer system's hard disk cannot be loaded. Therefore, the system boot files stored on the hard drive cannot be accessed or edited. In order to overcome this deadlock, the user must load an operating system such as MS-DOS from a floppy diskette. The user then edits the system boot files using the operating system editor and attempts to reboot the computer system using the edited system boot files on the hard drive. This process continues until the computer system is successfully booted. European patent application 0 364 127 describes a system in which different boot programs may be loaded from different input devices, such as a hard drive and a floppy drive. It would desirable to have a computer system which automatically boots even if some configuration data has become unusable so that the user of the computer system can access the system boot files without the need of loading additional files from an external storage medium. It is an object of the invention to provide a method and an apparatus that boot a computer system even after some configuration data has become unusable. This object is solved by the method as claimed in independent claim 1 and the apparatus as claimed in independent claim 10. Preferred embodiments of the invention are subject-matters of dependent claims. The invention provides a method and an apparatus for booting the computer system from a set of configuration data that last booted the computer system properly. The invention first attempts to boot the computer system from a current set of configuration data. If the attempt is unsuccessful, the invention automatically boots the computer system using the last set of configuration data which successfully booted the computer system and which was previously stored. In response to a successful boot of the computer system using the last set of configuration data that properly booted the computer system, the invention makes a new current set of configuration data that is equivalent to the last set of configuration data that successfully booted the computer system. If the attempt to boot from the current set of configuration data is successful, the present invention stores it as the last set of configuration data that successfully booted the computer system. Brief Description of the Drawings Figure 1 is a block diagram of a system embodying the present invention for booting a computer system. Figure 2 is a preferred tree structure of the System hive for the registry of Figure 1. Figure 3 is a preferred tree structure for a Control subkey of the System hive. Figure 4 is a preferred tree structure for a Services subkey of the System hive. Figure 5 shows a preferred structure of a node under the Services subkey of the System hive. Figure 6 is a flow diagram of the method BootSystem for the system of Figure 1. Figure 7 is a flow diagram of a method ChooseControlSet for the system of Figure 1. Figure 8 is a flow diagram of the method InitializeRegistry for the system of Figure 1. Figure 9 is a flow diagram of a method LoadDeviceDrivers for the system of Figure 1. Figure 10 is a flow diagram of a method InitializeDeviceDrivers for the system of Figure 1. Figure 11 is a flow diagram of a method UpdateRegistry for the system of Figure 1. Figure 12 is a flow diagram of a method ManageLastKnownGoodMenu for the system of Figure 1. Figure 13 is a flow diagram of a method PressOn for the system of Figure 1. Figure 14 is a flow diagram of a method UpdateLastKnownGood for the system or Figure 1. Figure 15 is a block diagram of a preferred LastKnownGood user interface menu. Detailed Description of the Invention The present invention provides a method and system for successfully booting a computer system 100 (Figure 1) even after some configuration data has become unusable. For illustrative purposes, the present invention will be described as residing in the Windows NT™ operating system of Microsoft Corporation, Redmond, Washington. The components of a preferred operating system 101, all of which are preferably stored in a computer memory 103, boot a computer 105 ( i.e ., "the system") using configuration data stored in a registry 107. Before discussing the operation of the present invention in detail, it will be helpful to understand how configuration data is preferably stored within the computer system 100 of Figure 1. The Registry: The registry 107 is a unified and centralized data base for storing operating system, application, and hardware configuration data. The registry 107 preferably stores this data in a hierarchical form which supports multiple users. Thus, the registry 107 eliminates the need for multiple configuration files such as AUTOEXEC.BAT, CONFIG.SYS, and other such configuration data files. The registry 107 is preferably structured as a tree. The preferred tree of the registry 107 is named: HKEY_LOCAL_MACHINE Tree 131 (which is described in more detail below and is shown in Figures 2, 3, 4, and 5). The HKEY_LOCAL_MACHINE Tree 131 contains data about the local computer system. This data includes hardware and operating system characteristics such as bus type, system memory, installed device drivers, and boot configuration data (also known as boot control data). Each of the trees' nodes or keys are named. Each key may contain zero or more data items called value entries which are associated with the key. Keys are analogous to directories while value entries are analogous to files. A standard syntax used with the present invention defines names that begin with "\" as key names, and defines names that are followed by "=" as value entries, i.e ., attributes of a key, as illustrated by way of example in Figure 2 Physically, the registry 107 exists as a set of files on a hard disk (not shown). For the purpose of creating these files, the registry 107 is divided into sections called hives. Each hive maps directly to a file on the hard disk. The data in the System hive of the registry 107 ( i.e ., HKEY_LOCAL_MACHINE Tree 131 System) is organized into control sets. A control set is simply an instance or a set of system parameters. Figure 2 shows a preferred tree structure of the System hive. Each key in the System hive will now be described in more detail. Each key named ControlSet nnn 201-203 describes a different configuration for the computer 105. Each ControlSetnnn preferably resides in a non-volatile store. The clone 204 is a copy or the ControlSet nnn that is currently used to attempt system boot, made very early in the boot process, before any change to the current control set has occurred. The clone 204 is preferably stored in volatile memory. Each ControlSet nnn key has two subkeys, a Control subkey 206 (shown in more detail in Figure 3) and a Services subkey 207 (shown in more detail in Figures 4 and 5). The Services subkey 207 lists all of the entities that can be loaded and set to running by the boot process on the computer 105. Each subkey name listed in Figure 4 describes a different device driver to install on the computer system 100. A device driver is a software component that permits the computer system 100 to communicate with a device. For example, a printer driver is a device driver that translates computer data into a form understood by a printer (not shown) connected to the computer system 100 through the input/output unit 125. Those of ordinary skill in the art will understand that different computer systems will list different entities under the Services subkey 207. Likewise, different computer systems will assign different values to the value entries shown in Figure 4. The Control subkey 206 holds all of the miscellaneous values needed to boot the computer 105. 55For example, a value entry service_group_order 301 (Figure 3) of the Control subkey 206 describes an order in which to invoke device drivers used by the computer system 100. As will be described in more detail below, the ControlSet nn keys, along with the clone 204, prevent unusable configuration data from creating a computer that cannot be started. When unusable configuration data initially prevents the system from starting, the present invention searches a Select key 205 (discussed in more detail below) and retrieves the last control set that was successfully used to boot the computer 105. The present invention then uses the retrieved control set to complete the system boot procedure. The Select key 205 maintains information about the control sets. The Select key 205 preferably contains the value entries Current 208, Default 209, LastKnownGood 210, Failed 211, and AutoSelect 212 (see Figure 2). Current 208 contains a data value that represents the control set that the computer 105 is currently booting from ( i.e ., a Current control set 208). Default 209 contains a data value that identifies a default control set ( i.e ., a Default control set 209) LastKnownGood 210 contains a data value that identifies a control set containing the data values that last successfully booted the computer 105 ( i.e ., a LastKnownGood control set 210). Failed 211, if set, identifies the control set that failed when the LastKnownGood control set 210 was last used ( i.e ., a Failed control set 211). AutoSelect 212 contains a data value that controls whether a LastKnownGood user interface menu will be displayed. The LastKnownGood user interrace menu allows the user to choose whether to boot the computer 105 from the LastKnownGood control set 210 or by the Default control set 209. To retrieve the Current control set 208, the Default control set 209, the LastKnownGood control set 210, or the Failed control set 211, the operating system 101 (1) retrieves the data value stored in the value entry Default 209, Current 208, Failed 211, or LastKnownGood 210, respectively, (2) formats this data value as a zero filled three digit string ( e.g ., 001), and (3) appends this three digit string to the end of the string "ControlSet" to arrive at the name of the control set to select ( e.g ., ControlSet001). A discussion of how the components of the preferred operating system 101 interact to boot the computer 105 using the control set indicated by the value entry LastKnownGood 210 of the registry 107, will help illustrate the method and system of the present invention. General Operation: In response to a user requestto boot the computer 105 received via an input/output unit 125, the computer 105 executes a boot system program 109 of the operating system 101 to manage the system boot procedure for the computer 105. The BootSystem program 109, when executing on a central processing unit (CPU) 127, invokes a ChooseControlSet program 113 which chooses a set or configuration data ( i.e ., a control set) with which to boot the computer 105. The ChooseControlSet program 113 will either choose the Default control set 209 or the LastKnownGood control set 210 of the registry 107. The BootSystem program 109 then invokes an InitializeRegistry program 111 which, when executing on the CPU, 127, retrieves configuration data for the computer 105 and stores the retrieved configuration data in the registry 107. Next, the BootSystem program 109 invokes a LoadDeviceDrivers program 121 which, when executing on the CPU 127, attempts to load and initialize a set of device drivers listed in the chosen control set. Figure 1 shows a state of the system 101 after the device drivers 129 have been loaded into computer memory 103. If any of the device drivers should fail to load or initialize, then the LoadDeviceDrivers program 121 decides whether the system boot procedure currently underway should continue in spite of the failure to properly initialize the device driver, or whether a new system boot procedure should be initiated using the LastknownGood control set 210 of the registry 107. If a decision is made to reboot the computer 105 using the LastKnownGood control set 210 then the system boot procedure is reinitiated using the configuration data stored in the LastKnownGood control set 210. Upon a successful boot of the computer 105, using either control set, the BootSystem program 109 invokes the UpdateRegistry program 123. In response to a successful boot from the Default control set 209, the UpdateRegistry program 123 makes a new LastKnownGood control set 210 that is equivalent to the Default control set 209 which successfully booted the computer 105. The method UpdateRegistry, in response to a successful boot of the computer 105 using the LastKnownGood control set 210, causes the Default control set 209 to be set to the Current control set 208 that successfully booted the system, and creates a new LastKnownGood control set 210 that is equivalent to the Current control set 208 that successfully booted the computer 105. In this way the present invention ensures that the computer 105 will successfully boot even after some configuration data in the Default control set 209 has become unusable. Flow Diagrams: Figure 6 is a flow diagram of the method BootSystem which controls the system boot procedure for the computer 105. The method BootSystem is preferably performed by the BootSystem program 109. In step 601 the method BootSystem calls the method ChooseControlSet which chooses a set of configuration data ( i.e ., a control set) with which to boot the computer 105. The method ChooseControlSet will choose either the Default control set 209 or the LastKnownGood control set 210 of the registry 107. The method ChooseControlSet is discussed in more detail below and is shown in Figure 7. In step 603 the method BootSystem calls the method InitializeRegistry which retrieves configuration data for the computer 105 and stores the retrieved configuration data in the registry 107. The stored configuration data is used to boot the computer 105. The method InitializeRegistry is discussed in more detail below and is shown in Figure 8. Once the proper control set has been chosen and the registry has been initialised, the method BootSystem, in step 605, calls the method LoadDeviceDrivers. The method LoadDeviceDrivers loads into the computer memory 103 and initializes a set of device drivers listed in the chosen control set. If any of the device drivers should fail to load or initialize then the method LoadDeviceDrivers decides whether the currently executing system boot procedure should continue in spite of the failure to properly load or initialize the device driver, or whether a new system boot procedure should be initiated using the LastKnownGood control set 210 of the registry 107. The method LoadDeviceDrivers is discussed in more detail below and is shown in Figure 9. Upon a successful boot of the computer 105, using either control set, the method BootSystem, in step 607, invokes the method UpdateRegistry. The method UpdateRegistry, in response to a successful boot of the computer 105 using the LastKnownGood control set 210, causes the Default control set 209 to be set to the Current control set 208 that successfully booted the system, and creates a new LastKnownGood control set 210 that is equivalent to the Current control set 208 that successfully booted the computer 105. The method UpdateRegistry, in response to a successful boot of the computer 105 from the Default control set 209, creates a new LastKnownGood control set 210 that is equivalent to the Current control set 208 which successfully booted the computer 105. In this way the present invention ensures that the computer 105 will successfully boot even after some configuration data in the Default control set 209 has become unusable. In step 609, the method BootSystem ends processing. However, processing on the computer 105, which is unrelated to the method BootSystem, can continue. Figure 7 is a flow diagram of the method ChooseControlSet which chooses a set of configuration data ( i.e ., a control set) with which to boot the computer 105. The method ChooseControlSet will either choose the Default control set 209 or the LastKnownGood control set 210 of the registry 107. The method ChooseControlSet is preferably performed by the ChooseControlSet program 113 of the operating system 101. In step 701 the method ChooseControlSet sets the variable UseLastKownGood equal to the value False. The variable UseLastKnownGood is set to True when the LastKnownGood control set 210 of the registry 107 is to be used to boot the computer 105. The variable UseLastKnownGood is set to False when the Default control set 209 of the registry 107 is to be used to boot the computer 105. In step 703, the method ChooseControlSet retrieves a LastKnownGood environment variable. The LastKnownGood environment variable is set to True when the immediately previous attempt to boot the computer 105 failed using the Default control set 209 of the registry 107, else the LastKnownGood environment variable is set to the value False. The LastKnownGood environment variable is preferably stored in a non-volatile storage medium. In step 705 the method ChooseControlSet determines if the user of the computer 105 entered a breakin key. The breakin key indicates to the method ChooseControlSet that the user wants to view a LastKnownGood user interface menu which gives the user of the computer 105 the option of booting the computer 105 from the LastKnownGood control set or booting the computer 105 from the Default control set. In the preferred embodiment the breakin key is the space-bar and is invoked by holding down the space-bar. If the method determines that the user did hit the breakin key then, in step 706, the method ChooseControlSet displays a LastKnownGood user interface menu. The LastKnownGood user interface menu is shown in Figure 15. The LastKnownGood user interface menu provides the user of the computer 105 with options for booting the computer 105. Using the LastKnownGood user interface menu of Figure 15, the user can choose to boot the computer 105 using the Default control set 209 of the registry 107 or the LastKnown Good control set 117 of the registry 107. Upon completion of step 706, the method ChooseControlSet calls the method ManageLastKnownGoodMenu which processes data entries from the user which were entered in response to LastKnownGood menu options. The method ManageLastKnownGood is discussed in more detail below and is shown in Figure 12. Upon completion of step 707 the method ChooseControlSet, in step 709, determines if the variable UseLastKnownGood is set equal to the value True. If the variable UseLastKnownGood is set equal to the value True then in step 711, the method ChooseControlSet sets the value entry Current 208 of the registry 107 equal to the control set indicated by the value entry LastKnownGood 210 of the registry 107. In this way the control set indicated by the value entry LastKnownGood 210 is used to boot the system. Upon completion of step 711 the method ChooseControlSet in step 713 returns processing control to the method BootSystem of Figure 6. Returning to the discussion of step 709, if the method ChooseControlSet determines that the variable UseLastKnownGood is set equal to the value False then in step 715 the method sets the value entry Current 208 equal to the value entry Default 209. Upon completion of step 715, the method ChooseControlSet, in step 713, returns processing control to the method BootSystem of Figure 6. Returning to the discussion of step 705, if the user did not hit the breakin key then in step 717 the method ChooseControlSet determines whether the LastKnownGood environment variable is set equal to the value True. If the LastKnownGood environment variable is set equal to the value False, then processing continues with steps 709, 711, 713, and 715 (discussed above). Returning to the discussion of step 717, if the LastKnownGood environment variable is set equal to the value True then in step 719 the method determines whether the value entry AutoSelect 212 of the registry 107 is set equal to the value True. The value entry AutoSelect 212 controls whether the LastKnownGood user interface menu is displayed. If AutoSelect 212 is set equal to the value False then steps 701, 707, 708, 711, 713, and 715 are performed as discussed above. If the value entry AutoSelect 212 is set equal to the value True then in step 721 the variable UseLastKnownGood is set to the value True. After completion of step 721, steps 709-715 are performed as discussed above Figure 8 is a flow diagram of the method InitializeRegistry which obtains configuration data for the computer 105 and stores the obtained configuration data in the registry 107. The stored configuration data is used by the present invention to successfully boot the computer 105. The method InitializeRegistry is preferably performed by the InitializeRegistry program 111 of the operating system 101. In step 801 the method InitializeRegistry obtains configuration data for the computer 105 and stores the configuration data in the registry 107. Software configuration data is read from the System hive file and hardware configuration data is extracted from the system by computation. The store, configuration data is later used to boot the computer 105. In step 803 the method InitializeRegistry creates a symbolic link to the control set indicated by the value entry Current 208 of the registry 107. A symbolic link is a way of making all references to a particular key with a defined name ("CurrentControlSet") actually refer to a different key ("ControlSetnnn") with a different name. In step 805 the method InitializeRegistry initializes the symbolic link by creating a link from the key "CurrentControlSet" to the key at the root of the ControlSetnnn control set used to boot the system. In step 807 the method InitializeRegistry creates the clone 204 by copying the Current control set 208 to the clone 204. Upon completion of step 807, the method InitializeRegistry, in step 809, returns processing control to the method BootSystem (Figure 6). Figure 9 is a flow diagram of the method LoadDeviceDrivers which loads into the computer memory 103 and initializes a set of device drivers listed in the control set currently being used to boot the computer 105. If any of the device drivers should fail to load into the computer memory 103 or should fail to initialize then a decision to continue the current boot process or to reboot the system using the LastKnownGood control set is made. The method LoadDeviceDrivers is preferably performed by the LoadDeviceDrivers program 121 of the operating system 101. In step 901 the method LoadDeviceDrivers retrieves, from the control set indicated by the value entry Current 208, a list of device drivers to load into the computer memory 103 and to initialize. In step 903, the method determines if any unprocessed device drivers remain. If unprocessed device drivers do remain, then in step 905 the method loads the first unprocessed device driver into the computer memory 103. In step 907, the method determines if the device driver failed to load into the computer memory 103. If the device driver properly loaded into the computer memory 103, then in step 909 the method LoadDeviceDrivers calls the method IntializeDeviceDrivers which initializes the device driver loaded into the computer memory 103. The method LoadDeviceDrivers is discussed in detail below and is shown in Figure 10. Upon completion of step 909, processing continues with step 903. Returning to the discussion of step 907, if the device driver failed to load into the computer memory 103, then in step 911 the method LoadDeviceDrivers calls the method PressOn which determines whether the system boot procedure currently underway should continue in spite of a failure to properly load or initialize a device driver or whether a new system boot procedure should be initiated using the LastKnownGood control set 210 of the registry 107. The method PressOn is discussed in detail below and is shown in Figure 13. Upon completion of step 911, the method LoadDeviceDrivers, in step 913, determines if the variable PressOn which was returned from the method PressOn is set equal to the value True. If the variable PressOn is set equal to the value False, then in step 915, the method LoadDeviceDrivers reboots the system. However, if the method LoadDeviceDrivers determines that the variable PressOn is set equal to the value True, then in step 909, the method LoadDeviceDrivers calls the method InitializeDeviceDrivers which initializes the device driver loaded into the computer memory 103. The method InitializeDeviceDrivers is discussed in detail below and is shown in Figure 10. Upon completion of step 909 processing continues with step 903. If in step 903 the method LoadDeviceDrivers determines that all of the device drivers have been processed, then in step 917 the method LoadDeviceDrivers returns processing control to the method BootSystem (Figure 6). Figure 10 is a flow diagram or the method InitializeDeviceDrivers which initialises the device driver previously loaded into the computer memory 103 in the method LoadDeviceDrivers (Figure 9). The method InitializeDeviceDrivers is preferably performed by the InitializeDeviceDrivers program 139 of the operating system 101. In step 1001 the method InitializeDeviceDrivers initializes the device driver previously loaded into the memory 103. In step 1003 the method InitializeDeviceDrivers determines if the loaded device driver failed to initialize properly. If the device driver initialized properly then in step 1005, the method InitializeDeviceDrivers returns processing control to the method LoadDeviceDrivers (Figure 9). Returning to the discussion of step 1003, if the device driver did fail to initialize properly then in step 1007, the method InitializeDeviceDrivers determines whether the boot should proceed by calling the method PressOn. The method PressOn is discussed in more detail below and is shown in Figure 13. Upon completion of step 1007, the method InitializeDeviceDrivers, in step 1009, determines whether the variable PressOn which was returned from the method PressOn is set equal to the value True. If the variable PressOn is set equal to the value False, then the method InitializeDeviceDrivers, in step 1011, reboots the system. Returning to the discussion of step 1009, if the variable PressOn returned from the method PressOn is set equal to the value True, then in step 1005, the method InitializeDeviceDrivers returns processing control to the method LoadDeviceDrivers of Figure 9. Figure 11 is a flow diagram of the method UpdateRegistry which, in response to a successful boot of the computer 105 using the LastKnownGood control set 210, causes the Default control set 209 to be set to the Current control set 208 that successfully booted the system, and creates a new LastKnownGood control set 210 that is equivalent to the Default control set 209 that successfully booted the computer 105. In response to a successful boot from the Default control set 209, the method UpdateRegistry creates a new LastKnownGood control set 210 that is equivalent to the Current control set 208. In this way the present invention ensures that the computer 105 will successfully boot even after some configuration data in the Default control set 209 has been unusable. In step 1101 the method UpdateRegistry calls the method UpdateLastKnownGood which updates the value entry LastKnownGood 210 of the registry 107to point to the control set in the registry 107 which last successfully booted the computer 105. The method UpdateLastKnownGood is discussed in more detail below and is shown in Figure 14. Upon completion of step 1101 the method UpdateRegistry, in step 1103, determines whether the computer 105 just successfully booted from the control set indicated by the value entry LastKnownGood 210 of the registry 107. System boot is preferably considered successful or unsuccessful based on a default set of criteria. For example, if the system appeared to the operating system 101 to properly boot but in fact failed because of a problem that the operating system cannot detect ( e.g ., the screen is unreadable because the wrong video mode is set) then the current boot is not considered successful. However, in the preferred embodiment, the system boot is considered successful if two criteria are met. First, the system must attempt to start all relevant device drivers. If any driver fails to start, AND its ErrorControl value is Severe or Critical, the boot will NOT be declared good. Every device driver has a named node under the Services subkey 207 of the System hive, and every driver's node contains the value entry ErrorControl 401 (see Figure 4). ErrorControl has one of four values: (1) Ignore, (2) Normal, (3) Severe, and (4) Critical. The value Ignore indicates that the current system boot should continue, and that even if the driver fails to initialize, the user is not notified of the failure in the form of a pop-up message. The value Normal indicates that the current system boot should continue. However, in the preferred embodiment a message is displayed to the user indicating that an error has occurred during system boot. The value Severe indicates that the system should be rebooted using the LastKnownGood control set 210, unless the system is currently being booted from the LastKnownGood control set 210, in which case the current boot from the LastKnownGood control set 210 should continue. The value Critical indicates that if the system boot is currently from the control set identified by the value entry Default 209, then the system should be rebooted using the LastKnownGood control set 210. The value Critical also indicates that if the system boot is currently from the LastKnownGood control set 210 that the system boot fails. Second, at least one user must successfully logon to the system. While the set of criteria set forth above is the default set of criteria, the preferred embodiment also allows the user to define a set of criteria for successful boot different than the default set discussed above. If the computer 105 was successfully booted from the LastKnownGood control set then, in step 1105, the method deletes the control set currently indicated by the value entry Failed 211 of the registry 107. In step 1107 the method sets the value entry Failed 211 equal to the data value contained in the value entry Default 209. In step 1109 the method sets the value entry Default 209 equal to the data value of the value entry LastknownGood 210 of the registry 107. In step 1111 the method UpdateRegistry returns processing control to the method BootSystem (Figure 6). Returning to the discussion of step 1103, if the computer 105 successfully booted from a control set other than the control set indicated by the value entry LastKnownGood 210 then the method UpdateRegistry, in step 1111, returns processing control to the method BootSystem (Figure 6). Figure 12 is a flow diagram of the method ManageLastKnownGoodMenu which processes user requests entered in response to options presented in the LastknownGood user interface menu. The method ManageLastKnownGoodMenu is preferably performed by the ManageLastknownGood menu program 133 of Figure 1. In step 1201 the method ManageLastKnownGood displays the LastKnownGood user interface menu of Figure 15. In step 1203 the method determines whether the user of the computer 105 entered a request in response to LastKnownGood menu options to boot the computer 105 from the control set referred to by the value entry LastKnownGood 210 of the registry 107. If the user did enter a request to boot the computer 105 from the control set referred to by the value entry LastKnownGood 210 then in step 1205 the method sets the variable UseLastKnownGood equal to the value True. In step 1207 the method ManageLastKnownGoodMenu returns processing control to the method ChooseControlSet (Figure 7). Returning to the discussion of step 1203, if the user entered a request in response to the LastKnownGood menu to boot the system from the control set referred to by the value entry Default 209 of the registry 107, then in step 1209, the method sets the variable UseLastKnownGood equal to the value False. Upon completion of step 1209 the method ManageLastKnownGoodMenu, in step 1207, returns processing control to the method ChooseControlSet (Figure 7). Figure 13 is a flow diagram of the method PressOn which determines whether the system boot procedure currently underway should continue in spite of a failure to properly load or initialize at least one device driver or whether a new system boot procedure should be initiated using the LastKnownGood control set 210 of the registry 107. The method PressOn determines whether the current system boot procedure should continue by testing both a value entry ErrorControl 401 (Figure 4) associated with each device driver, and by testing a LastKnownGood environment variable. If the driver's ErrorControl is Ignore or Normal, then the boot continues. If the driver's ErrorControl is Severe, and the system is booting from the Default control set 209, the boot is failed and the system should be rebooted using the LastKnownGood control set to retry the boot. If ErrorControl is Severe, and the system is booting from the LastKnownGood control set 210, the boot continues. If ErrorControl is Critical, and the system is booting from the Default control set 209, the boot is failed, and the system reverts to the LastKnownGood control set on the next boot. If the ErrorControl is Critical, and the system is booting from the LastKnownGood control set 210, the boot fails entirely. A driver's ErrorControl value entry is set when the driver is installed, but can be programmatically changed at anytime while the system is running. The LastKnownGood environment variable indicates that the system failed to boot from the Default control set 209 of the registry 107 and should be rebooted using the LastKnownGood control set 210 of the registry 107. The LastKnownGood environment variable is preferably stored in non-volatile memory. The method PressOn is preferably performed by the PressOn program 135 of Figure 1. In step 1301, the method PressOn determines whether the value entry ErrorControl is set equal to the value Ignore or the value Normal. If the value entry ErrorControl is set equal to the value Normal or Ignore, then in step 1303 the method PressOn sets the variable PressOn equal to the value True. Upon completion of step 1303, the method PressOn returns to its caller (i.e., the method LoadDeviceDrivers of Figure 9 or the method InitialiazeDeviceDrivers of Figure 10). Returning to the discussion of step 1301, if the value entry ErrorControl is not set equal to the value Normal or Ignore, then in step 1307 the method PressOn determines whether the value entry ErrorControl is set equal to the value Severe. If the value entry ErrorControl is set equal to the value Severe, then in step 1309 the method PressOn determines whether the LastKnownGood environment variable is set equal to the value True. If the LastKnownGood environment variable is set equal to the value True, then in step 1303 the method PressOn sets the variable PressOn equal to the value True. In step 1305, the method PressOn returns to its caller. Returning to the discussion of step 1309, if the LastKnownGood environment variable is set equal to the value False, then in step 1311, the method PressOn sets the LastKnownGood environment equal to the value True. In step 1313, the method PressOn sets the variable PressOn equal to the value False. Upon completion of step 1313, the method PressOn, in step 1305, returns to its caller. Returning to the discussion of step 1307, if the value entry ErrorControl is not set equal to the value Severe, then in step 1315, the method PressOn determines whether the value entry ErrorControl is set equal to the value Critical. If the value entry ErrorControl is not set equal to the value Critical, then in step 1303, the method PressOn sets the variable PressOn equal to the value True. Upon completion of step 1303, the method PressOn, in step 1305, returns to its caller. Returning to the discussion of step 1315, if the value entry ErrorControl is set equal to the value Critical, then in step 1317, the method PressOn determines whether the LastKnownGood environment variable is set equal to the value True. If the LastKnownGood environment variable is set equal to the value False, then in step 1311, the method PressOn sets the LastKnownGood environment variable equal to the value True. In step 1313, the method sets the variable PressOn equal to the value False. Upon completion of step 1313, the method PressOn, in step 1305, returns to its caller. Returning to the discussion of step 1317, if the method determines that the LastKnownGood environment variable is set equal to the value True, then in step 1319, the system crashes. Figure 14 is a flow diagram of the method UpdateLastKnownGood whose primary task is to reset the value entry LastKnownGood 210 to point to a copy of the clone 204 in order to update the LastKnownGood value entry after a successful system boot using the Current control set 208 of the registry 107. The method UpdateLastKnownGood is preferably performed by the UpdateLastknownGood program 137 of Figure 1. In step 1401 the method UpdateLastKnownGood copies the clone 204 from volatile memory to non-volatile memory. In step 1403 the method flushes the registry 107. A flush of the registry 107 forces all changes made to a hive, for example, the System hive of Figure 2, since the last flush, to be committed to disk. The flush is preferably performed in such a way that either all changes occur, or no changes occur. In step 1405 the method deletes the control set referred to by the value entry LastKnownGood 210 of the registry 107. In step 1407 the method flushes the registry 107. In step 1409 the method sets the value entry LastKnownGood 210 of the registry 107 to refer to the copy of the Clone control set now residing in non-volatile memory. In step 1411 the method UpdateLastKnownGood returns processing control to the method UpdateRegistry (Figure 11). Those of ordinary skill in the art will understand that other system architectures can be used to implement the methods of the present invention described above, including, but not limited to, a network in which a plurality of computers are coupled with file servers to share access to data among computer users through a data communications network. While the discussion herein focuses on device drivers, those of ordinary skill in the art will recognize that the scope of the discussion is not so limited but applies equally to file systems and user mode program services.

Claims: A method in a computer system (100) for booting the computer system (100), the method using a boot program (109), the boot program (109) utilizing in its execution a selectable configuration profile (203, 206, 207), the method comprising: executing the boot program (109) using a first configuration profile; and if execution of the boot program (109) using the first configuration profile fails, loading a second configuration profile, the second configuration profile having been previously used by the boot program (109) to successfully boot the computer system (100), and executing the boot program (109) using the loaded second configuration profile. The method of claim 1 wherein the loaded second configuration profile is the last configuration profile used by the boot program (109) to successfully boot the computer system (100). The method of claim 1 or 2 wherein the first and second configuration profiles are each a set of device drivers (129). The method of one of claims 1 to 3 wherein the first and second configuration profiles are each a set of hardware devices. The method of one of claims 1 to 4 wherein the boot program (109) attempts to load particular device drivers (129) based upon the configuration profile used further comprising: determining that execution of the boot program (109) using the first configuration profile fails where an attempt by the boot program (109) to load a device driver (129) fails. The method of one of claims 1 to 4 wherein the boot program (109) attempts to initialize particular device drivers (129) based upon the configuration profile used, further comprising: determining that execution of the boot program (109) using the first configuration profile fails where an attempt by the boot program (109) to initialize a device driver (129) fails. The method of one of claims 1 to 6 wherein the second configuration profile is stored in persistent storage, further comprising: if execution of the boot program (109) using the first configuration profile succeeds, replacing the second configuration profile stored in persistent storage with the first configuration profile. The method of one of claims 1 to 7, further comprising: loading the first configuration profile. The method of one of claims 1 to 8, further comprising: dynamically determining the first configuration profile. An apparatus for booting a computer system (100) using a boot program (109), the boot program (109) utilizing in its execution a selectable configuration profile (203, 206, 207), comprising: means (127) for executing the boot program (109) using a first configuration profile; and means (113, 127) for loading a second configuration profile, the second configuration profile having been previously used by the boot program (109) to successfully boot the computer system (100), and executing the boot program (109) using the loaded second configuration profile if execution of the boot program (109) using the first configuration profile fails. The apparatus of claim 10 wherein the loaded second configuration profile is the last configuration profile used by the boot program (109) to successfully boot the computer system (100). The apparatus of claim 10 or 11 wherein the first and second configuration profiles are each a set of device drivers (129). The apparatus of one of claims 10 to 12 wherein the first and second configuration profiles are each a set of hardware devices. The apparatus of one of claims 10 to 13 wherein the boot program (109) attempts to load particular device drivers (129) based upon the configuration profile used, further comprising: means (121, 127) for determining that execution of the boot program (109) using the first configuration profile fails where an attempt by the boot program (109) to load a device driver (129) fails. The apparatus of one of claims 10 to 13 wherein the boot program (109) attempts to initialize particular device drivers (129) based upon the configuration profile used, further comprising: means (127, 139) for determining that execution of the boot program (109) using the first configuration profile fails where an attempt by the boot program (109) to initialize a device driver (129) fails. The apparatus of one of claims 10 to 15 wherein the second configuration profile is stored in persistent storage, further comprising: means (127, 137) for replacing the second configuration profile stored in persistent storage with the first configuration profile if execution of the boot program (109) using the first configuration profile succeeds. The apparatus of one of claims 10 to 16, further comprising: means for loading the first configuration profile. The apparatus of one of claims 10 to 17, further comprising: means (111, 127) for dynamically determining the first configuration profile.

Inventors: HINSLEY DAN ALVIN, HOVEL DAVID OTTO, VERT JOHN DAVID, WILLMAN BRYAN M, WONG RITA MANG CHEE, HINSLEY, DAN ALVIN, HOVEL, DAVID OTTO, VERT, JOHN DAVID, WILLMAN, BRYAN M., WONG, RITA MANG CHEE
Applicants: MICROSOFT CORP, MICROSOFT CORPORATION
Application year: 1994
Main classification: G06F9
IPC codes: G06F9, G06F1