Error detection/correction and fault detection/recovery – Data processing system error or fault handling – Reliability and availability
Reexamination Certificate
2000-06-05
2004-03-02
Baderman, Scott (Department: 2184)
Error detection/correction and fault detection/recovery
Data processing system error or fault handling
Reliability and availability
C714S038110
Reexamination Certificate
active
06701454
ABSTRACT:
TECHNICAL FIELD
This invention relates to software program modules. More particularly, this invention relates to a method and system for recovering information contained in open files during a failure in a program module.
BACKGROUND OF THE INVENTION
Despite the best efforts of software developers, software programs inevitably fail at one time or another. Unhandled failures may result in a crash, at which time the operating system terminates the, software program execution. When a program crashes, all of its state data is lost. As a result, users that were in the process of modifying a file, such as a document or spreadsheet, may lose substantial amounts of information. Information loss may create a significant amount of work and frustration to users.
To minimize the information lost as a result of a crash, several different approaches have been taken. For example, one prior art method comprises capturing a screen shot at the time of the crash. That method, however, is limited to salvaging only the information displayed on the screen at the time of the crash, if any. Thus, information that was not directly displayed is lost.
Another approach taken to recover information caused by program crashes involves saving open files automatically before the crash. More particularly, files are periodically saved in the background. This approach, however, only recovers the files as of the last auto-save. Accordingly, information that was not previously saved is lost.
A further prior art method uses exception handlers to clean up, or fix, the cause of the failure and return the user to a state before the failure. The user is then given the option of performing a normal save of the open document. For example, the application program POWERPOINT manufactured and sold by Microsoft Corporation of Redmond, Wash., has utilized such exception handlers. A crash, however, may be the culmination of a series of unexpected events that have occurred before the ultimate failure. Thus, considerable information may be lost in merely giving the user the option of doing a normal save as if the exception has never occurred.
Returning the user to the state before the failure and attempting to save the document often causes another failure while saving the document. Furthermore, if the save attempt is unsuccessful, then the modified changes in the document is lost and no other attempt is made to recover the information.
The above-described prior art methods for limiting information loss caused by a program crash suffer from varying disadvantages. Accordingly, there is a need for a method and system for saving the most recent version of an open file at the time of a program failure.
There is another need for a method and system for selecting the best version of the recovered file.
There is still a further need for using system APIs to implement the present invention that may be easily added to a software program without extensive changes to the program's architecture.
SUMMARY OF THE INVENTION
The present invention satisfies the above-described needs by providing a method and system for recovering information during a program failure. An exception handler is provided that performs an emergency save of any file that is open at the time of the crash.
Once a failure of the program module is detected, control passes to an exception handler that attempts to minimize the amount of information that might be lost. The exception handler allows a user to attempt an emergency save of all open files that have been modified. When the program is restarted, the most recent verified version is reloaded and displayed to the user.
More particularly, once a failure occurs in an application program module, the operating system passes control to the exception handler, which may display a user interface, such as a dialog box, asking the user whether an open file should be saved.
If the user selects to save the open file, then a determination is made whether the open file has been modified from the version currently saved to disk. The reader should appreciate that this determination can also be made before questioning the user. The exception handler then saves the file to a temporary location.
The exception handler then creates a Document Recovery Persistence (“DRP”) in the computer registry for the file. A DRP comprises the data needed to analyze the best version available to the user subsequent to the failure. More particularly, the DRP is a record block that includes a path name, a time stamp, a process identifier, a unique numeric identifier for a version of the file, and a numeric identifier that is shared among the DRPs for each version of the file.
The program is then terminated and restarted. Upon restart, the DRP for each recovered file is accessed and compared with the DRPs, if any, for the original file and the timed auto-saved version of the file. Information in these DRPs is used to determine the best version based on the recentness and confidence level of each version. After determining which version of the file is the best, that version is then opened and displayed to the user.
In another embodiment of the invention, a user interface, such as a dialog box, may be displayed to the user providing the functionality of selecting between the different versions of the file. For example, the user may select and compare from the recovered, auto-saved, and user-saved versions. The selected version may then be stored as the original file or saved as a new file.
Although the present invention has been described above as implemented in a preferred application program module, it will be understood that alternative embodiments will become apparent to those skilled in the art to which the present invention pertains without departing from its spirit and scope. Accordingly, the scope of the present invention is defined by the appended claims rather than the foregoing description.
REFERENCES:
patent: 5241672 (1993-08-01), Slomcenski et al.
patent: 5524190 (1996-06-01), Schaeffer et al.
patent: 5682551 (1997-10-01), Pawlowski et al.
patent: 5948112 (1999-09-01), Shimada et al.
patent: 6009258 (1999-12-01), Elliott
patent: 6044475 (2000-03-01), Chung et al.
patent: 6256751 (2001-07-01), Meth et al.
patent: 6393584 (2002-05-01), McLaren et al.
patent: 6430703 (2002-08-01), Connor et al.
patent: 6438709 (2002-08-01), Poisner
patent: 6457142 (2002-09-01), Klemm et al.
patent: 6591379 (2003-07-01), LeVine et al.
Fischer Kevin Joseph
Fox Eric
Hill Brian T.
Larsson Jeffrey
LeVine Eric A.
Baderman Scott
Lohn Joshua
Merchant & Gould
Microsoft Corporation
LandOfFree
Method and system for recovering information during a... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method and system for recovering information during a..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and system for recovering information during a... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3247278