Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Autorestore for emulators

IP.com Disclosure Number: IPCOM000010313D
Original Publication Date: 2002-Nov-20
Included in the Prior Art Database: 2002-Nov-20
Document File: 2 page(s) / 62K

Publishing Venue



By constantly capturing the state of an emulator, users can automatically and transparently be restored to a prior working state after an emulator crash.

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

Page 1 of 2

Autorestore for emulators


This disclosure uses concepts from two types of software: emulator and state capturer.

Emulator is a type of software that creates virtual hardware. For example, users can execute a non-x86 emulator on their x86 machine. This software emulates non-x86 hardware so the user can execute non-x86 programs. Modern emulators have the ability to stop, pause, and play. Some emulators can be controlled by emulator managers. An emulator manager tracks the state of [multiple] local and/or remote emulators.

State Capturer is a type of software that allows users to backup specific information at the present time. Then, if something undesired occurs, the user can restore to a previous known state. For example, a user installs software that corrupts their registry. The user may elect to restore to a previous state with a non-corrupt registry. In general, a modern state capturer deals with registry-like information only. It does not provide full machine backup and restore functionality.


1) In general, any software, including emulator software, can crash.
2) State capture is typically user initiated and limited to saving only a subset of the machine's information.


Autorestore for emulators:
1) After a crash occurs, the user is automatically restored to a previous state or a user specified state.
2) Because the environment is emulated, physical hardware does not need to be rebooted or have its power recycled.
3) Constant and complete state capture.

Example OS implementation concepts:

Imagine installing OS "Z" with autorestore for emulators built-in:
1) The first thing that is installed is an emulator manager. This install process may be hidden from a users view. The emulator manager could be run on a different OS, like OS "R"...