Browse Prior Art Database

Auto-rescue Operation In Desktop Computers

IP.com Disclosure Number: IPCOM000241801D
Publication Date: 2015-Jun-01
Document File: 1 page(s) / 29K

Publishing Venue

The IP.com Prior Art Database

Abstract

AUTO RESCUE OPERATION IN DESKTOP COMPUTERS ABSTRACT The present disclosure relates to the area of Desktop Computers, Storage and back up methods. The proposed “Auto-Rescue" process is where we could restore the unsaved work after System Crash or Power failure. The method involves caching the unsaved work in the offline-cloud or registry, thereby restoring it in erroneous situations like System Crash or Power Failure. BACKGROUND A normal mankind, who’s at a location where the power outage is common, would have to face the adverse effectsof any primary Data Loss.Affording a UPS, just to prevent the system crash or data loss isn’t feasible forall kinds of organizations or a common person. In building a cache or registry cloud that couldstore the unsaved work or a process to hibernate the unsaved work in an offline cloud would be more feasible than to have a separate device like UPS.The existing method in Laptops provides restore option by utilizing the minimal battery power before closing down the system. However, this couldn’t be implemented in a Desktop Computer as including an extra battery to the Desktop Computer might be costlier and non-suggestible. This could be resolved by incorporating an extra-registry that could hold the temporary data but it would again add cost to the product. Overcoming these lines, the proposed work suggests the method to hibernate the unsaved work in the offline-cloud.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 95% of the total text.

Page 01 of 1

Auto-rescue Operation In Desktop Computers

DESCRIPTION

The method to hibernate the unsaved work can be achieved following two methods.


I. Method to "Hibernate" the unsaved work in offline cloud storage.

The process to hibernate the unsaved work in offline cloud can be achieved by caching any document that the user works upon. Whenever an erroneous exit is noticed i.e., a System crash or a Power Failure, the document is found to be in unsaved state, the cached file would automatically get saved in the offline cloud. Once the system gets restart, a searched would be performed in a way that unsaved work would be restored and the user would get back to the state where they left.

Method:

Step 1: A temporary file gets created in the offline cloud

Step 2: If file is exited successfully (i.e., when the file is saved in the system):

Step 2.1: Temporary file in the offline cloud is killed or terminated

Step 3: Else, the cached file would be saved in the offline cloud.

Step 3.1: On system restart, the cached file would be called which thereby reverts user to the last state.

Step 3.1.1: If the file is saved, or killed by the user:

Step 3.1.2: The cached file in the offline cloud would be terminated.


II. System where an extra-registry can be added to save the unsaved data.

An extra registry could be incorporated in the central processing unit, so that the unsaved work can be cached and retrieved after a system crash or power failure. Any working document or thread can be cac...