WO2000010085A1 - A method, computer, and article of manufacturing for fault tolerant booting - Google Patents
A method, computer, and article of manufacturing for fault tolerant booting Download PDFInfo
- Publication number
- WO2000010085A1 WO2000010085A1 PCT/US1999/018071 US9918071W WO0010085A1 WO 2000010085 A1 WO2000010085 A1 WO 2000010085A1 US 9918071 W US9918071 W US 9918071W WO 0010085 A1 WO0010085 A1 WO 0010085A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- driver
- computer
- device driver
- operating system
- registry
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1417—Boot up procedures
Definitions
- the present invention relates to software and, in particular, tolerating faults during the booting of computer software.
- a device driver is a software program that links a peripheral device or internal computer function to the operating system.
- the device driver contains the precise machine language necessary to activate all device functions and includes detailed knowledge of the device's characteristics, such as the number of keys in a keyboard or the number of pixels of screen resolution of a display.
- a computer typically includes a keyboard device driver for activating keyboard functions.
- Device drivers may interface with hardware, the operating system, or other device drivers.
- Booting a computer refers to causing a computer to start executing instructions.
- computers contain built-in instructions in a read-only-memory (ROM) that are automatically executed at start-up or when the computer is powered on.
- ROM read-only-memory
- These set of computer instructions are typically called a bootstrap routine.
- the bootstrap routine searches for the operating system, loads the operating system and passes control to the operating system.
- the operating system may search for device drivers and store device driver specific information in predetermined memory locations. Often, testing and debugging a newly designed device driver is a difficult task. When designing device drivers, as with all software development, bugs or run time errors occur throughout the development process.
- the device driver caused the operating system to crash.
- the operating system accessing the device driver may have bugs.
- the device driver may also have bugs causing the operating system to crash.
- One method for avoiding an operating system crash involves a manual fix to disable the newly designed device driver. This consists of booting into another operating system and renaming and copying files around on the disk drive. For example, if a computer has multiple operating systems which have access to the same file system which includes the faulty device driver, a user could boot into the operating system which is operable and delete the faulty device driver. While this is faster than re-installing the operating system, it is still a painstaking and time-consuming process. In addition, the user must have a good working knowledge of the operating system and file structure. If a faulty device driver is loaded onto multiple computers in a network, the device driver installed on each computer would have to be deleted.
- a method for preventing a device driver in a computer from causing an operating system to crash during a bootstrap routine includes identifying the device driver in the computer. Registry information associated with the device driver is altered in order for the operating system to initiate an associated filter driver. The filter driver then initiates the device driver. The device driver then may be disabled in response to an error.
- the method includes restoring the registry information after the registry information has been altered.
- a name of the disabled device driver is displayed.
- a method for preventing a device driver in a computer from rendering an operating system inoperative includes the step of setting a BootlnProgress registry flag.
- An AutoReboot OS registry state is saved and the AutoReboot OS registry flag is set to "on.”
- a filter driver is then attached to the device driver.
- the AutoReboot OS registry state is restored, and the BootlnProgress registry flag is removed.
- the device driver is a video driver, keyboard driver and/or pointing driver.
- the operating system is a Windows NT operating system.
- a computer comprising a processor and operating system is provided.
- the processor is coupled to an operating system stored in memory.
- a fault tolerant booting software program which is also stored in memory, prevents a device driver from disabling the operating system during initialization.
- the fault tolerant booting software program includes a first software module for restoring the initial registry settings.
- a second software module attaches a filter to the device driver, and a third software module displays a device driver failure message.
- the computer further comprises a remote control software program including the fault tolerant booting software, and a remote computer, coupled to the computer, for displaying video in response to user input.
- an article of manufacture including a computer readable medium having computer readable program code means.
- the computer readable program code means comprises computer readable program code means for causing a computer to restore an initial registry setting and computer readable program code means for attaching a filter to a device driver.
- Computer readable program code means is also provided for displaying a device driver failure message.
- Fig. 1 B illustrates the registry illustrated in Fig. 1 A according to the present invention.
- Fig. 2 illustrates software modules of the fault tolerant booting software illustrated in Fig. 1 A according to the present invention.
- Fig. 3 illustrates a control flow diagram of the GERNUWA.SYS software module as illustrated in Fig. 2 according to the present invention.
- Fig. 4 illustrates a control flow diagram of the AW HOST.SYS software module as illustrated in Fig. 2 according to the present invention.
- Fig. 5. illustrates a control flow diagram of the AWGINA.DLL software module as illustrated in Fig. 2 according to the present invention.
- Fig. 1 A illustrates a simplified computer hardware and software block diagram according to the present invention.
- Host computer 100 includes operating system 106. Operating system 106 as well as other software is stored in memory 1 1 1.
- Memory 1 1 1 may be a single type of memory or a variety of types, such as ROM, random-access-memory (RAM), electrically erasable programmable read only memory (EEPROM), magnetic/optical disk drive or equivalent type of memory.
- Processor 1 12 accesses memory 1 1 1 by bus 120 in order to control the operation of host computer 100.
- host computer 100 is a Pentium-based computer.
- Host computer 100 is coupled to display 122 by bus 123. Display 122 is provided to display information to users.
- Host computer 100 may be coupled to other computers by a local area network (LAN), wide area network (WAN), or other equivalent type of network.
- operating system 106 is Windows NT 4.0 supplied by Microsoft Corporation of Redmond, Washington.
- Operating system 106 may be a Windows 9x operating system or equivalent operating system.
- Operating system 106 accesses libraries 106a and registry 106b.
- An embodiment of registry 106b is illustrated in Fig. 1 B.
- Host computer 100 also includes remote control software 101.
- remote control software 101 is pcANYWHERE 8.0 supplied by Symantec Corporation of Cupertino, California. Remote control software 101 includes fault tolerant booting software 102.
- fault tolerant software 102 may not be included in remote control software 101 and may be a separate software module or set of computer instructions.
- Remote control software 101 interfaces with operating system 106 as well as library 106a and Registry 106b.
- Host computer 100 also includes a variety of device drivers. For clarity, exemplary device drivers 103, 104, and 105 are shown. It should be understood by one of ordinary skill in the art that many other device drivers may be included in a particular embodiment of host computer 100.
- video driver 103, keyboard driver 104, and pointing device (mouse) driver 105 interact with remote control software 101 , and in particular, fault tolerant booting software 102 as described below.
- connection 107 may be by way of modem ("TAPI"), Integrated Services Digital Network (“ISDN”), Transmission Control Protocol/Internet Protocol (“TCP/IP”), Internet Packet Exchange (“IPX”), Sequenced Packet Exchange (“SPX”), Banyon Vines, infrared, direct serial, and direct parallel.
- TAPI modem
- ISDN Integrated Services Digital Network
- TCP/IP Transmission Control Protocol/Internet Protocol
- IPX Internet Packet Exchange
- SPX Sequenced Packet Exchange
- Banyon Vines infrared, direct serial, and direct parallel.
- Remote computer 108 also includes memory 1 17 which is coupled to a processor 1 14 by bus 1 18.
- Memory 1 17 may be a single type of memory or a variety of types, such as ROM, RAM, EEPROM, magnetic/optical disk drive or an equivalent type of memory.
- Remote computer 108 is also coupled to a display 1 16 by bus 1 15.
- Operating system 1 19 is stored in memory 1 17 for controlling the operation of remote computer 108.
- Remote computer 108 also includes remote control software 1 13, stored in memory 1 17, which allows a user to control host computer 100.
- host computer 100 sends video output 109 to remote computer 108 in response to remote computer 108 sending keyboard and pointing device input data 1 10 to host computer 100.
- applications 121 are executed on host computer 100 with corresponding data (video 109) generated on connection 107 to remote computer 108.
- Video output 109 is the most difficult information to send to remote computer 108 because of the size of data transferred.
- Various methods used for trapping the video output 109 offers different advantages, in order to obtain high performance, remote control software 101 traps video output at the device driver level.
- AW HOST.SYS driver 220 essentially wraps or attaches a video filter driver, such as video drive filter 220a shown in Fig. 2, to video driver 103.
- remote control software 101 interfaces with keyboard driver 104 and pointing device driver 105.
- a driver filter is a layer of code or set of computer instructions used as an interface between the operating system 106 and an associated device driver.
- a driver filter is generally loaded before the associated device driver and identities which device drivers are present on the computer.
- the driver filter attaches or hooks to the device driver by altering information in the registry 106b such that operating system 106 loads the associated driver filter during the bootstrap routine instead of the associated device driver.
- the operating system calls the driver filter which executes an initialization routine.
- the driver filter then initializes the associated device driver and passes information from operating system 106 to the device driver.
- the driver filter is responsible for passing information between operating system 106 and the associated device driver and acts as a bidirectional filter. For example, if the device driver fails and generates a failure message (or code), the filter driver receives the driver failure message and will then notify the operating system 106 which may generate a message to the filter driver.
- Fig. 2 illustrates the three main software modules for fault tolerant booting software 102 illustrated in Fig. 1 .
- the first software module is GERNUWA.SYS driver 210 which loads at the earliest possible time that operating system 106 allows.
- GERNUWA.SYS driver 210 undos all the registry 106b changes that AWJHOST.SYS driver 220 made during the last time that operating system 106 booted.
- AWJHOST.SYS driver 102 includes software instructions for identifying device drivers in a computer and attaching a bidirectional filter driver to the identified device drivers.
- AWJHOST.SYS driver 220 includes video filter 220a, keyboard filter 220b, and display filter 220c.
- GERNUWA.SYS driver 210 is loaded first by the operating system 106 and AWJHOST.SYS driver 220 is loaded second with AWGINA.DLL 230 loaded third. It should be noted software modules 210, 220, and 230 may not necessarily be loaded consecutively by operating system 106.
- the naming convention of the software modules is significant.
- the "GERNUWA.SYS” name is based on spelling “awunreg” backwards.
- pcANYWHERE software modules beginning with “aw” which stands for “anywhere” and the “unreg” refers to undo registry.
- the name is spelled backwards so users will not improperly delete the GERNUWA.SYS driver 210 before the module can make the necessary undo registry changes.
- users without the proper deinstall software will improperly delete all "aw” files in order to remove the pcANYWHERE software.
- the GERNUWA.SYS driver 210, AWJHOST.SYS driver 220, and AWGINA.DLL library may be combined into a single driver.
- the GERNUWA.SYS driver 210, AWJHOST.SYS driver 220, and AWGINA.DLL library are written in C computer language.
- the next device driver to be loaded by operating system 106 is the main or master fault tolerant booting device driver, AWJHOST.SYS driver 220.
- the device driver 220 is responsible for attaching to various devices, such as video, keyboard and pointing device (mouse). In an embodiment, the majority of the fault tolerant booting code resides in AWJHOST.SYS driver 220.
- AWGINA.DLL library 220 The main purpose of AWGINA.DLL library 220 is for trapping the operating system security subsystem.
- AWGINA.DLL library 230 is a multifunction library.
- One function of AWGINA.DLL library 230 includes displaying messages from fault tolerant booting software 102.
- remote control software 101 and fault tolerant booting software 102 are illustrated in memory 1 1 1 of host computer 100, software 101 and/or software 102 may be stored in an article of manufacturing including a magnetic or optical disk or diskette or equivalent thereof. Remote control software 101 and/or fault tolerant booting software 102 may also be downloaded via the Internet or world wide web ("www").
- Fig. 3 illustrates a logic flow diagram 300 for GERNUWA.SYS driver 210 as illustrated in Fig. 2.
- GERNUWA.SYS driver 210 undos all the registry modifications to registry 106b that were made by AWJHOST.SYS driver 220 during the last time that the operating system 106 was booted or the last time the bootstrap routine was executed.
- GERNUWA.SYS driver 210 reads registry 106b for AWJHOST.SYS information which includes information copied from the operating system information portion of registry 106b as illustrated in Fig. 1 B.
- a decision is then made as to whether registry 106b has been modified in logic block 303. If registry 106b has been modified, the original values are restored in logic block 304. Otherwise, the GERNUWA.SYS driver 210 transfers control to logic block 305 and exits. After restoring the original registry 106b values in logic block 304, control is also passed to logic block 305 and GERNUWA.SYS driver 210 exits.
- Fig. 4 illustrates a logic flow diagram 400 for AWJHOST.SYS driver 220 as illustrated in Fig. 2.
- AWJHOST.SYS driver 220 is the main driver and is responsible for attaching a bidirectional device filter to an identified device driver.
- AWJHOST.SYS driver 220 may attach a video filter, keyboard filter, and/or pointer filter to a video driver, keyboard driver and/or pointer (mouse) driver, respectively.
- a decision is made in logic block 402 whether BootlnProgress registry flag is set.
- the BootlnProgress memory location, as well as other AWJHOST.SYS information, is located in registry 106b as illustrated in Fig. 1 B.
- Fig. 1 B is provided to illustrate the various logical memory locations in registry 106b and may not represent actual physical memory locations of information.
- Registry 106b includes, but is not limited to, AWJHOST.SYS information, pcANYWHERE application information and operating system information.
- a memory location in registry 106b may be flagged (set) or toggled to a one value or zero value depending upon the particular application. The value of a particular memory location is considered its state.
- BootlnProgress flag is set (or a one value is stored in the BootlnProgress memory location), control is transferred to logic block 403; otherwise, logic is passed to logic block 406.
- control from logic block 405 is passed to logic block 412 where AWJHOST.SYS driver 220 exits.
- Control from logic block 413 is passed to logic block 414.
- the pcANYWHERE compatibility mode registry flag is set in logic block 414.
- all filters except the video driver is attached to respective device drivers.
- Control is then passed to logic block 410.
- control is transferred to logic block 407 where the AutoReboot OS registry flag is read and saved.
- the AutoReboot OS registry flag is then set to "on" or a one value is stored in the AutoReboot OS memory location in logic block 408.
- Control is then transferred to logic block 409 where resident device drivers are identified and device driver filters are attached to respective device drivers. A large amount of registry information in registry 106b is altered by code represented by logic block 409.
- GERNUWA.SYS driver 210 undos these alterations to registry 106b. If a device driver disable flag is set, AWJHOST.SYS does not attach to the corresponding device driver, but will attach respective filters to the other remaining identified device drivers. For example, if the VideoDriverDisabled flag is set, AWJHOST.SYS driver 220 will not attach video filter 220a to video driver 103, but will attach keyboard filter 220b and pointer filter 220c to keyboard driver 104 and pointing driver 105, respectively.
- Logic block 409 is the point in which the computer will crash if an incompatibility with a device, for example a video card, or an internal bug occurs. If this happens, the computer will AutoReboot itself and flow chart 400 will be followed as the operating system 106 loads AWJHOST.SYS driver 220.
- Fig. 1 B and Figs. 3-5 illustrated an embodiment of the present invention in which a video filter is attached to a video driver.
- the attaching of a video filter to a video driver embodiment is provided for illustration.
- device drivers such as keyboard drivers, pointer drivers, or other internal drivers may likewise be implemented within the scope of the present invention.
- the sequence of attaching the device filters may be altered and still be within the scope of the present invention.
- Fig. 4 illustrates disabling a filter driver, such as AWJHOST.SYS driver 220, after a crash
- other embodiments of the present invention include disabling a device driver.
- Fig. 5 illustrates control flow chart 500 for AWGINA.DLL library 230 illustrated in Fig. 2.
- a determination is made whether VideoDriverDisabled registry flag is set in logic block 502. If the VideoDriverDisabled registry flag is set, logic is passed to logic block 503 where the pcANYWHERE compatibility mode message is displayed. In an embodiment, the message is displayed on display 122. If the VideoDriverDisabled registry flag is not set, logic is passed to logic block 506 where AWGINA.DLL exits the execution thread illustrated in Fig. 5 and completes other AWGINA.DLL functions.
- Logic is passed from logic block 503 to logic block 504 where a determination is made whether AWJHOST.SYS driver 220 is disabled. If the AWJHOST.SYS driver is disabled, logic is passed to logic block 505. Otherwise, logic is passed to logic block 506 where AWGINA.DLL continues to complete other functions. In logic block 505, the pcANYWHERE device driver failure message identifying the name of the faulty device driver filter is displayed on display 122.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE69907928T DE69907928D1 (en) | 1998-08-12 | 1999-08-10 | METHOD, COMPUTER AND PRODUCED OBJECT FOR TROUBLESHOOTING URLADEN |
CA002340342A CA2340342A1 (en) | 1998-08-12 | 1999-08-10 | A method, computer, and article of manufacturing for fault tolerant booting |
EP99941001A EP1110146B1 (en) | 1998-08-12 | 1999-08-10 | A method, computer, and article of manufacturing for fault tolerant booting |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/132,956 | 1998-08-12 | ||
US09/132,956 US6275930B1 (en) | 1998-08-12 | 1998-08-12 | Method, computer, and article of manufacturing for fault tolerant booting |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2000010085A1 true WO2000010085A1 (en) | 2000-02-24 |
Family
ID=22456349
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1999/018071 WO2000010085A1 (en) | 1998-08-12 | 1999-08-10 | A method, computer, and article of manufacturing for fault tolerant booting |
Country Status (5)
Country | Link |
---|---|
US (1) | US6275930B1 (en) |
EP (1) | EP1110146B1 (en) |
CA (1) | CA2340342A1 (en) |
DE (1) | DE69907928D1 (en) |
WO (1) | WO2000010085A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1887759A1 (en) * | 2005-06-15 | 2008-02-13 | Huawei Technologies Co., Ltd. | Method and system for realizing automatic restoration after a device failure |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7017075B1 (en) * | 2000-05-12 | 2006-03-21 | Intel Corporation | Recovering from video driver errors |
US6807269B1 (en) | 2000-07-20 | 2004-10-19 | Cisco Technology, Inc. | Call management implemented using call routing engine |
US6801613B1 (en) | 2000-08-31 | 2004-10-05 | Cisco Technology, Inc. | Associating call appearance with data associated with call |
US6690789B1 (en) | 2000-08-31 | 2004-02-10 | Cisco Technology, Inc. | Fault tolerant telephony control |
US6674852B1 (en) | 2000-08-31 | 2004-01-06 | Cisco Technology, Inc. | Call management implemented using call routing engine |
JP2002278783A (en) * | 2001-03-19 | 2002-09-27 | Funai Electric Co Ltd | System for rewriting firmware |
US20030084337A1 (en) * | 2001-10-03 | 2003-05-01 | Simionescu Dan C. | Remotely controlled failsafe boot mechanism and manager for a network device |
US20060126706A1 (en) * | 2004-12-10 | 2006-06-15 | Kevin Brand | Auto-reboot modem |
US10733288B2 (en) | 2013-04-23 | 2020-08-04 | Hewlett-Packard Development Company, L.P. | Verifying controller code and system boot code |
US9880908B2 (en) * | 2013-04-23 | 2018-01-30 | Hewlett-Packard Development Company, L.P. | Recovering from compromised system boot code |
CN105122214B (en) | 2013-04-23 | 2019-03-01 | 惠普发展公司,有限责任合伙企业 | Reparation to the system data damaged in nonvolatile memory |
WO2020159533A1 (en) | 2019-02-01 | 2020-08-06 | Hewlett-Packard Development Company, L.P. | Security credential derivation |
WO2020167283A1 (en) | 2019-02-11 | 2020-08-20 | Hewlett-Packard Development Company, L.P. | Recovery from corruption |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1995022794A1 (en) * | 1994-02-18 | 1995-08-24 | Apple Computer, Inc. | System for automatic recovery from software problems that cause computer failure |
GB2294568A (en) * | 1994-04-12 | 1996-05-01 | Ntt Data Tsushin Kk | Updating and restoration method of system file |
EP0747819A1 (en) * | 1995-06-06 | 1996-12-11 | International Business Machines Corporation | Disk drive incompatible firmware recovery |
US5745669A (en) * | 1993-10-21 | 1998-04-28 | Ast Research, Inc. | System and method for recovering PC configurations |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4663707A (en) * | 1984-05-25 | 1987-05-05 | Scientific Micro Systems, Inc. | Multilevel bootstrap apparatus |
US5247659A (en) * | 1988-10-06 | 1993-09-21 | International Computers Limited | Method for bootstrap loading in a data processing system comprising searching a plurality of program source devices for a bootstrap program if initial data indicating a bootstrap program source device fails a validity check |
DE69230306T2 (en) * | 1991-09-09 | 2000-04-13 | Compaq Computer Corp | Remote bootstrap system and method for bootstrapping a computer system |
US5564054A (en) * | 1994-08-25 | 1996-10-08 | International Business Machines Corporation | Fail-safe computer boot apparatus and method |
US5675800A (en) * | 1994-11-30 | 1997-10-07 | Digital Equipment Corporation | Method and apparatus for remotely booting a computer system |
US5630049A (en) * | 1994-11-30 | 1997-05-13 | Digital Equipment Corporation | Method and apparatus for testing software on a computer network |
JP3088269B2 (en) * | 1995-07-26 | 2000-09-18 | 日本電気通信システム株式会社 | Computer network system and operating system version management method |
US5974546A (en) * | 1997-05-08 | 1999-10-26 | Micron Electronics, Inc. | Apparatus and method to determine cause of failed boot sequence to improve likelihood of successful subsequent boot attempt |
US5987605A (en) * | 1998-02-28 | 1999-11-16 | Hewlett-Packard Co. | Methods and apparatus for dual-boot memory selection, update, and recovery in a programmable device |
US6067628A (en) * | 1998-04-09 | 2000-05-23 | Intel Corporation | Method to monitor universal serial bus hub overcurrent |
-
1998
- 1998-08-12 US US09/132,956 patent/US6275930B1/en not_active Expired - Lifetime
-
1999
- 1999-08-10 DE DE69907928T patent/DE69907928D1/en not_active Expired - Lifetime
- 1999-08-10 WO PCT/US1999/018071 patent/WO2000010085A1/en active IP Right Grant
- 1999-08-10 CA CA002340342A patent/CA2340342A1/en not_active Abandoned
- 1999-08-10 EP EP99941001A patent/EP1110146B1/en not_active Expired - Lifetime
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5745669A (en) * | 1993-10-21 | 1998-04-28 | Ast Research, Inc. | System and method for recovering PC configurations |
WO1995022794A1 (en) * | 1994-02-18 | 1995-08-24 | Apple Computer, Inc. | System for automatic recovery from software problems that cause computer failure |
GB2294568A (en) * | 1994-04-12 | 1996-05-01 | Ntt Data Tsushin Kk | Updating and restoration method of system file |
EP0747819A1 (en) * | 1995-06-06 | 1996-12-11 | International Business Machines Corporation | Disk drive incompatible firmware recovery |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1887759A1 (en) * | 2005-06-15 | 2008-02-13 | Huawei Technologies Co., Ltd. | Method and system for realizing automatic restoration after a device failure |
EP1887759B1 (en) * | 2005-06-15 | 2011-09-21 | Huawei Technologies Co., Ltd. | Method and system for realizing automatic restoration after a device failure |
US8375252B2 (en) | 2005-06-15 | 2013-02-12 | Huawei Technologies Co., Ltd. | Method, device and system for automatic device failure recovery |
Also Published As
Publication number | Publication date |
---|---|
CA2340342A1 (en) | 2000-02-24 |
EP1110146B1 (en) | 2003-05-14 |
EP1110146A1 (en) | 2001-06-27 |
DE69907928D1 (en) | 2003-06-18 |
US6275930B1 (en) | 2001-08-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7000229B2 (en) | Method and system for live operating environment upgrades | |
US6804774B1 (en) | Software image transition aid comprising building a disk image based on identified hardware | |
US7734945B1 (en) | Automated recovery of unbootable systems | |
JP4932781B2 (en) | Method, system and program for creating a reduced operating system image on a target medium | |
US8032740B2 (en) | Update in-use flash memory without external interfaces | |
US6205558B1 (en) | Recovery of file systems after modification failure | |
JP3593241B2 (en) | How to restart the computer | |
US6317826B1 (en) | Booting a computer system from a network | |
US8886995B1 (en) | Fault tolerant state machine for configuring software in a digital computer | |
US20030005037A1 (en) | Crash recovery system | |
US8230210B1 (en) | Interactive firmware recovery | |
US20080270583A1 (en) | Method, system and program product for remotely deploying and automatically customizing workstation images | |
US20040172578A1 (en) | Method and system of operating system recovery | |
EP1110146B1 (en) | A method, computer, and article of manufacturing for fault tolerant booting | |
US7962736B1 (en) | Interactive pre-OS firmware update with repeated disabling of interrupts | |
US20060036832A1 (en) | Virtual computer system and firmware updating method in virtual computer system | |
US7480793B1 (en) | Dynamically configuring the environment of a recovery OS from an installed OS | |
US6205561B1 (en) | Tracking and managing failure-susceptible operations in a computer system | |
US8806474B2 (en) | Computer-hardware, life-extension apparatus and method | |
US8140475B1 (en) | Dynamic configuration archival and retrieval | |
CN111090546A (en) | Method, device and equipment for restarting operating system and readable storage medium | |
CN116841629A (en) | Network card function configuration method, device and medium thereof | |
KR102423056B1 (en) | Method and system for swapping booting disk | |
JP4165423B2 (en) | System board with core I / O card | |
EP3798831B1 (en) | Resilient upgradable boot loader with power reset |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CA |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
ENP | Entry into the national phase |
Ref document number: 2340342 Country of ref document: CA Ref country code: CA Ref document number: 2340342 Kind code of ref document: A Format of ref document f/p: F |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1999941001 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1999941001 Country of ref document: EP |
|
WWG | Wipo information: grant in national office |
Ref document number: 1999941001 Country of ref document: EP |