A setup data rewriting device has a nonvolatile memory device that stores rewriting data including registry data. Before the operating system refers to the registry data, the rewriting data is read from the storage device and stored in a memory region of a RAM different from a region where the operating system generates the registry data. Also, before the operating system refers to the registry data, the rewriting data stored in the RAM is used to rewrite the registry data stored in the RAM to the registry data included in the rewriting data.
|
1. A setup data rewriting apparatus comprising a first storage device, for generating setup data in the first storage device and applying the generated setup data to a system that refers to the setup data when the system is operated, characterized in that
rewriting data for rewriting the setup data is automatically read in the first storage device before the system refers to the setup data, and the setup data in the first storage device is automatically rewritten by using the rewriting data in the first storage device after the system generates the setup data and before the system refers to the setup data.
4. A setup data rewriting apparatus including a first storage device, for generating setup data for computer setting in the first storage device and applying the generated setup data to an operating system that refers to the setup data when the operating system is operated, the apparatus comprising:
a non-volatile second storage device that stores rewriting data for rewriting the setup data, the rewriting data including setup data;
a reading device that reads the rewriting data from the second storage device, and stores the rewriting data in a region in a memory region of the first storage device that is different from a region where the operating system is to generate the setup data; and
a rewriting device that rewrites the setup data in the first storage device to the setup data included in the rewriting data by using the rewriting data in the first storage device,
wherein the reading device automatically performs reading before the operating system generates setup data and the rewriting device automatically performs rewriting before the system refers to the setup data.
6. A computer readable storage device comprising a first storage device and a non-volatile second storage device that stores rewriting data for rewriting setup data, the rewriting data including setup data, the computer readable storage device storing in the first storage device a program for generating the setup data for setting up a computer and applying the generated setup data to an operating system that refers to the setup data when the operating system is operated,
wherein the computer readable storage device stores a setup data rewriting program that makes a computer execute a step of automatically reading the rewriting data from the second storage device and storing the rewriting data in a memory region of the first storage device that is different from a region where the operating system is to generate the setup data before the operating system generates setup data and a step of automatically rewriting the setup data in the first storage device to the setup data included in the rewriting data by using the rewriting data in the first storage device before the operating system refers to setup data.
2. A setup data rewriting apparatus according to
3. A setup data rewriting apparatus according to
wherein reading by the reading device and rewriting by the rewriting device are performed before the system generates setup data.
5. A system comprising the setup data rewriting apparatus and the operating system according to
|
|||||||||||||||||||
1. Technical Field
The present invention relates to an apparatus and a storage media that are used, upon starting up a computer, to generate registry data of computer setting in a RAM and install the generated registry data in an operating system that refers to the registry data. In particular, in a system that requires a power shut down, the present invention relates to a setup data rewriting apparatus, a setup data rewriting system and a storage media that stores a setup data rewriting program in which registry data can be accurately and readily changed.
2. Discussion
Conventionally, an operating system that is installed in a mobile computer or a card computer, such as Windows CE (Registered Trademark), generates registry data for setting up a computer in a RAM upon start-up, and refers to the generated registry data when device drivers are installed or the system is operated.
However, since the conventional operating system described above generates registry data in the RAM upon start-up, the computer is always set up based on the initial data that is previously installed in the operating system, when the computer is powered on. Therefore, in order to set up the computer to a user fs desired setting, the user is required to change the registry data to his desired setting after the startup. Alternatively, when a program that is required to execute the operating system is generated, registry data for the desired setting needs to be installed.
However, when the registry data is modified after the startup, a relatively long time is required for such a modification work because the registry data is enormous. Also, unlike Windows 95 or 98 (Registered Trademark), the above described operation system reads a single execution file of several megabytes (MB) into a RAM at a predetermined address, and directly executes the program from the address. Therefore, even pretended predetermined region of the RAM 34. In step S102, by the loader, a rewriting data file is read from the storage device 42, and the rewriting data is stored in a predetermined region of the RAM 34, and then step S104 is executed. More specifically, in step 102 S102, upon storing the rewriting data in the RAM 34, the rewriting data in a text format is converted to a binary file, and then stored in the RAM 34.
In step S104, by the loader, an execution file for the operating system is read from the storage device 42 and the execution program is stored in a predetermined region of the RAM 34. Then, in step S106, the program is executed from a predetermined address among the addresses of the RAM 34 that stores the execution program. Then, step S108 is executed to initialize the devices, and then step S110 is executed.
In step S110, registry data is generated at a predetermined region of the RAM 34 based on initialization data that is implemented in the execution program. In step S112, the registry data stored in the RAM 34 is rewritten to registry data that is included in the rewriting data stored in the RAM 34 by using the rewriting data in the RAM 34, and then step S114 is executed. More particularly, in step S112, by the loader, an execution file that is composed of a rewriting program for execution of rewriting of the registry data by using the rewriting data is read, and the rewriting program is stored in a predetermined region of the RAM 34. By the rewriting program, the registry data stored in the RAM 34 is rewritten to registry data that is included in the rewriting data by using the rewriting data stored in the RAM 34.
In step S114, the registry data stored in the RAM 34 is referred rewritten to thereby install device drivers, and a series of processes is thus completed.
Next, an operation of the above-described embodiment will be described with reference to FIG. 3.
When the computer 20 is powered on, a specified program stored in a predetermined region of the ROM 32 is started by the CPU 30, and the startup process is executed according to the program.
When the startup process is executed, first, in step S100, a loader is read from the storage device 42. Then, as shown in FIG. 3(a), the loader is stored in a predetermined region of the RAM 34. Then, in step S102, a rewriting data file is read from the storage device 42 by the loader, and as shown in FIG. 3(b), the read rewriting data file is stored in a predetermined region of the RAM 34.
Then, in step S104, an execution file for the operating system is read from the storage device 42. As shown in FIG. 3(c), an execution program of the read execution file is stored in a predetermined region of the RAM 34. Then, in step S106 through step S110, the program is executed from a predetermined address among addresses of the RAM 34 that stores the execution program, and devices are initialized by the operating system. Then, as shown in 3(d) FIG. 3(d), registry data is generated in a predetermined region of the RAM 34 based on initialization data implemented in the execution program.
Then, in step S112, the registry data stored in the RAM 34 is rewritten to the registry data included in the rewriting data by using the rewriting data stored in the RAM 34, as shown in 3(e) FIG. 3(e). Then, the operating system refers to the registry data of the RAM 34, as shown in FIG. 3(f), and installs the device drivers. Then, the operating system installs a GUI, a shell and the like, and the startup operation of the operating system is completed.
In this manner, the present embodiment is equipped with the volatile storage device 42 that stores rewriting data including registry data. Before the operating system refers to the registry data, the rewriting data is read from the storage device 42 and stored in a region of the RAM 34 different from a region thereof where the operating system generates registry data, and the registry data stored in the RAM 34 is rewritten to the registry data included in the rewriting data by using the rewriting data stored in the RAM 34.
Accordingly, by storing rewriting data that includes registry data for settings desired by the user in the storage device 42, the computer is always set to the settings desired by the user without modifying the registry data at each startup. Therefore, the time required to modify the registry data is reduced, and the possibility to erroneously set the registry data is reduced. Also, when systems that implement an operating system are provided to many users, only rewriting data that includes registry data for each user may be generated. Therefore, the time required for the data generation work is reduced compared to the conventional technology.
Moreover, in accordance with the present embodiment, before the operating system refers to the registry data, the rewriting data is read from the storage device 42 and stored in a memory region of the RAM 34 different from a region thereof where the operating system is to generate registry data.
It is noted that, after the operating system is started, the processing contents of the operating system are complicated and difficult to analyze, and therefore it is difficult to add a program that is created by the user. In this respect, the rewriting data is read before the operating system starts up, such that the data can be readily installed in the operating system.
It is noted that, in the above-described embodiment, whenever any one of the processes shown in the flowchart of
The storage device described above includes semiconductor storage media, such as RAM and ROM, magnetic storage type memory media, such as FD and HD, optically readable storage memory media, such as CD, CDV, LD and DVD, and magnetic storage/optically readable storage media such as MO. Therefore, the storage device includes any type of computer readable storage media without regard to the reading methods including electronic, magnetic, and optical reading methods.
In the above-described embodiment, the registry data corresponds to setup data. The RAM 34 corresponds to a first storage device. The storage device 42 corresponds to a second storage device. Step S102 corresponds to reading means. Step S112 corresponds to rewriting means.
As described above, by a setup data rewriting device in accordance with the present invention, setup data can be accurately and readily modified in a system that requires a power shut down compared to the conventional technique.
Furthermore, by a setup data rewriting device in accordance with the present invention, setup data can be readily installed in an operating system.
Moreover, by a system in accordance with the present invention, setup data can be accurately and readily modified in a system that requires a power shut down compared to the conventional technique.
Furthermore, by a storage media that stores a setup data rewriting program in accordance with the present invention, setup data can be accurately and readily modified in a system that requires a power shut down compared to the conventional technique.
| Patent | Priority | Assignee | Title |
| 10049225, | Jun 01 2006 | Intellectual Ventures II LLC | Data access control systems and methods |
| 10599859, | Jun 01 2006 | Intellectual Ventures II LLC | Data access control systems and methods |
| 11449622, | Jun 01 2006 | Intellectual Ventures II LLC | Data access control systems and methods |
| 8800008, | Jun 01 2006 | ZOFILLIP PRO GROUP LLC | Data access control systems and methods |
| 9171176, | Jun 01 2006 | Intellectual Ventures II LLC | Data access control systems and methods |
| 9740872, | Jun 01 2006 | Intellectual Ventures II LLC | Data access control systems and methods |
| Patent | Priority | Assignee | Title |
| 5758154, | Jun 05 1996 | Microsoft Technology Licensing, LLC | Method and system for storing configuration data into a common registry |
| 6405309, | Jun 18 1999 | LEHIGH GROUP LIMITED | Method and apparatus for creating and deploying smaller Microsoft Windows applications for automatic configuration of a computing device |
| JP9034705, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Oct 20 2004 | Seiko Epson Corporation | (assignment on the face of the patent) | / |
| Date | Maintenance Fee Events |
| Sep 07 2007 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Aug 31 2011 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Nov 06 2015 | REM: Maintenance Fee Reminder Mailed. |
| Mar 30 2016 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
| Date | Maintenance Schedule |
| May 08 2010 | 4 years fee payment window open |
| Nov 08 2010 | 6 months grace period start (w surcharge) |
| May 08 2011 | patent expiry (for year 4) |
| May 08 2013 | 2 years to revive unintentionally abandoned end. (for year 4) |
| May 08 2014 | 8 years fee payment window open |
| Nov 08 2014 | 6 months grace period start (w surcharge) |
| May 08 2015 | patent expiry (for year 8) |
| May 08 2017 | 2 years to revive unintentionally abandoned end. (for year 8) |
| May 08 2018 | 12 years fee payment window open |
| Nov 08 2018 | 6 months grace period start (w surcharge) |
| May 08 2019 | patent expiry (for year 12) |
| May 08 2021 | 2 years to revive unintentionally abandoned end. (for year 12) |