Registry emulation
A method for running a software application on a computer having an operating system that provides a local database containing consistent configuration data to be accessed by programs running on the computer. The method includes providing a file containing further configuration data required by the application, which further data are not stored in the local database. A request by the application to access the local database is intercepted, and an item of the further configuration data is returned from the file to the application, responsive to the request.
1. A method for servicing requests for configuration data from an application, comprising:
generating an emulation database for a user, the emulation database containing emulation data for the application that is unique to the user;
combining the emulation database with a local database to create a combined database;
intercepting a request from the application; and
servicing the request using configuration data unique to the user that is maintained in the local database or the emulation data stored in the combined database, whereby the application configuration is tailored to the user in a manner transparent to the application.
2. A method for servicing requests for configuration data from an application, comprising:
generating an emulation database for a user, the emulation database containing emulation data for the application that is unique to the user;
combining the emulation database with the local database to create a combined database;
intercepting a request for the application; and
servicing the request using configuration data unique to the user that is maintained in the combined database, whereby the application configuration is tailored to the user in a manner transparent to the application.
3. The method of claim 2 , wherein the local database and the emulation database have different root keys.
4. The method of claim 2 , wherein the combining step further comprises storing the emulation database in an alternate file or an alternate path in the local database.
5. The method of claim 2 , wherein the servicing step further comprises:
servicing a write request with the emulation data; and
determining whether to write the emulation data to the local database or to the emulation database in the combined database.
6. The method of claim 2 , wherein the servicing step further comprises:
servicing a read request for the emulation data; and
deciding whether to read the emulation data from the local database or from the emulation database in the combined database.
7. A non-transitory computer-readable storage medium having instructions stored thereon, execution of which by a processor cause the processor to perform operations for servicing requests for configuration data from an application, the operations comprising:
generating an emulation database for a user, the emulation database containing emulation data for the application that is unique to the user;
combining the emulation database with the local database to create a combined database;
intercepting a request from the application; and
servicing the request using configuration data unique to the user that is maintained in the local database or the emulation data stored in the combined database, whereby the application configuration is tailored to the user in a manner transparent to the application.
8. A non-transitory computer-readable storage medium having instructions stored thereon, execution of which by a processor cause the processor to perform operations for servicing requests for configuration data from an application, the operations comprising:
generating an emulation database for a user, the emulation database containing emulation data for the application that is unique to the user;
combining the emulation database with the local database to create a combined database;
intercepting a request from the application; and
servicing the request using configuration data unique to the user that is maintained in combined database, whereby the application configuration is tailored to the user in a manner transparent to the application.
9. The non-transitory computer-readable medium of claim 8 , wherein the local database and the emulation database have different root keys.
10. The non-transitory computer-readable medium of claim 8 , wherein the combining comprises storing the emulation database in an alternate file or an alternate path in the local database.
11. The non-transitory computer-readable medium of claim 8 , wherein the servicing comprises:
servicing a write request with the emulation data; and
determining whether to write the emulation data to the local database or to the emulation database in the combined database.
12. The non-transitory computer-readable medium of claim 8 , wherein the servicing comprises:
servicing a read request for the emulation data; and
deciding whether to read the emulation data from the local database or from the emulation database in the combined database.