System and method for inserting one or more files onto mass storage

• US 6,449,682 B1
• Filed: 06/18/1999
• Issued: 09/10/2002
• Est. Priority Date: 06/18/1999
• Status: Expired due to Term

• Current Assignee: Phoenix Technologies Limited (Pharaoh Acquisition LLC)
• Original Assignee: Phoenix Technologies Limited (Pharaoh Acquisition LLC)
• Inventors: Toorians, Arman
• Primary Examiner(s): Yoo, Do Hyun
• Assistant Examiner(s): Encarnacion, Yamir
• Application Number:
  US09/336,281
• Time in Patent Office: 1,180 Days
• Field of Search: 711/1, 711/100, 709/221, 709/222, 713/1, 713/2, 713/100, 717/11, 717/170, 717/168, 717/169, 717/171, 717/172, 717/173, 717/174, 717/175, 717/176
• US Class Current: 711/100
• CPC Class Codes: G06F 9/4401 Bootstrapping security arrangements therefor G06F21/57

Abstract

The present invention relates to a system and method for inserting one or more files onto a mass storage device during a boot sequence. The method includes loading a content module containing at least one file into memory. The method further includes replacing a target module that is typically executed during a boot sequence with a utility module. The method also includes executing the utility module during the boot sequence to move the content module onto a mass storage device.

Claims

1. A system for inserting files onto a mass storage device, comprising:

a target module that is typically executed during a boot sequence;

a content module including at least one file;

a utility module to move the content module onto a mass storage device; and

a locate/swap module to replace the target module with the utility module so that the utility module is executed during the boot sequence to move the content module onto the mass storage device, wherein said locate/swap module saves a copy of the target module prior to replacing the target module with the utility module.

2. The system of claim 1, wherein the content module includes at least one executable file.

3. The system of claim 1, wherein the content module includes at least one data file.

4. The system of claim 1, wherein the content module is loaded in memory prior to starting the boot sequence.

5. The system of claim 1, wherein the utility module is capable of performing at least the following functions:

moving files from memory to the mass storage device, and inserting commands into a system start-up file.

6. The system of claim 1, wherein the utility module inserts commands into a system start-up file so that executable files in the content module are automatically started after an operating system is loaded and operational.

7. The system of claim 1, wherein the utility module places the target module onto the mass storage after moving the content module onto the mass storage so that the target module can be executed.

8. The system of claim 1, wherein the load/swap module is capable of performing at least the following functions:

reading and writing information to the mass storage device, and locating file at a root level of the mass storage device.

9. A system for transferring files onto a mass storage device, comprising:

a target module that is typically executed during a boot sequence;

an initial start-up application (ISUA) to allow automatic launching of preinstalled programs;

a utility module to move the ISUA onto a mass storage device; and

a locate/swap module to replace the target module with the utility module so that the utility module is executed during the boot sequence to move the ISUA onto the mass storage device, wherein the load/swap module saves a copy of the target module prior to replacing the target module with the utility module.

10. The system of claim 9, wherein the ISUA searches for pre-loaded and pre-installed applications and creates short cuts to launch those applications.

11. The system of claim 9, wherein the ISUA is loaded in memory prior to starting the boot sequence.

12. The system of claim 9, wherein the utility module inserts commands into a system start-up file so that the ISUA is automatically started after an operating system is loaded and operational.

13. The system of claim 9, wherein the utility module places the target module onto the mass storage after moving the ISUA onto the mass storage so that the target module can be executed.

14. A method for transferring files onto a mass storage device, comprising:

loading a content module including at least one file into memory;

replacing a target module that is typically executed during a boot sequence with a utility module;

executing the utility module during the boot sequence to move the content module onto a mass storage device; and

saving a copy of the target module prior to replacing the target module with a utility module.

15. A method of claim 14, further comprising:

writing the saved target module back onto the mass storage device after moving the content module on the mass storage.

16. A method of claim 14, further comprising:

inserting commands into a registry to automatically start up executable files in the content module.

17. A method of claim 14, further comprising:

inserting commands into a system start-up file to automatically start up executable files in the content module.