Ghost partition

• US 5,974,567 A
• Filed: 06/20/1997
• Issued: 10/26/1999
• Est. Priority Date: 06/20/1997
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Compaq Computer Corporation (HP Inc.)
• Inventors: Marler, Anthony Ty, Harsany, J. Scott, Dickson, Charles Hudgens Jr., Armold, Matthew W.
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Baderman, Scott T.
• Application Number:
  US08/879,912
• Time in Patent Office: 858 Days
• Field of Search: 395/183.01, 395/183.06, 395/183.03-183.12, 713/1, 713/2, 713/100, 711/173
• US Class Current: 714/27
• CPC Class Codes: G06F 11/2284 by power-on test, e.g. power-on self test [POST]
• CPC Class Codes: G06F 11/2635 using a storage for the test inputs, e.g. test ROM, script files
• CPC Class Codes: G06F 9/4406 Loading of operating system

Abstract

An apparatus and a method for storing diagnostic software on a data storage device provides one or more ghost partitions overlapping a user partition on a data storage device. During a factory download of the application software as well as the diagnostics software, the apparatus creates a user partition and one or more overlapping ghost partitions. Next, it determines a minimum and maximum partition size for the ghost partition(s) and allocates the ghost partition size(s) appropriately. The apparatus then creates one or more master boot records (MBRs), one for each created partition. The ghost partition containing the diagnostics software is set as the active partition to allow the diagnostic software to be executed. Upon completion of the diagnostics process, the MBR for a second ghost partition is enabled so that upon reboot, download verification software located on a second ghost partition can be executed to ensure the correctness of the software downloading process. Next, the ghost partitions are disabled to reclaim storage space back to the user partition and the MBR for the user partition is set as the active partition so that upon reboot, only user partitions are visible. Further, in the event that the diagnostics software needs to be executed for quality control purposes, the MBR containing data on the ghost partition with the diagnostics software replaces the MBR for the user partition so that the ghost partition with diagnostics software can be resurrected after it has been previously disabled. No master boot records for any of the user or system partitions are modified at any time during the process. Additionally, the MBR and file allocation table (FAT) for the ghost partition may be cleared so test data cannot be accessed after the factory test processes. Since the ghost partitions overlap user partitions, after the ghost partitions have been disabled, data storage is automatically reclaimed by the user partitions when needed. The ghost partitions can properly function while overlapping the user partitions because while in the controlled environment of the factory, data will not be arbitrarily written to the user partition (otherwise both user and ghost partition data could become corrupt). Thus, the present invention avoids the need to set up a large system partition and avoids wasting disk space associated with manufacturing diagnostics.

Claims

1. A method for storing software on a data storage device, comprising:

creating a user partition;

creating a ghost partition overlapping said user partition;

transferring said software to said ghost partition; and

disabling said ghost partition after said ghost partition is not needed.

2. The method of claim 1, wherein said software is a diagnostics software.

3. The method of claim 1, wherein said ghost partition creating step creates a plurality of ghost partitions.

4. The method of claim 3, wherein one of said ghost partitions is adapted to contain diagnostics software and wherein another of said ghost partitions is adapted to contain download verification software.

5. The method of claim 1, further comprising the step of creating one or more master boot records (MBRs) on said data storage device.

6. The method of claim 5, wherein said data storage device is used in one or more phases, further comprising the step of creating one MBR for each of said phases.

7. The method of claim 5, further comprising an extended partition and a system partition, wherein said MBRs point to said user partition, said ghost partition, said system partition and said extended partition.

8. The method of claim 5, wherein said data storage device is used in a first phase and a second phase with corresponding MBRs, further comprising the step of copying the MBR for said second phase over the MBR for said first phase after the completion of said first phase.

9. The method of claim 1, further comprising the step of determining a minimum and maximum partition size for said ghost partition.

10. The method of claim 9, wherein said determining step further comprises:

(a) determining a last sector containing data;

(b) determining a minimum and maximum partition size for said ghost partition;

(c) allocating said maximum partition size;

(d) if said allocating step failed, subtracting a predetermined amount from said maximum partition size;

(e) repeating step (c) until said allocating step succeeds or until said subtracted maximum partition size equals said minimum partition size; and

indicating an error if said minimum partition size exceeds said subtracted maximum partition size.

11. A program storage device having a computer readable code embodied therein for storing software on a data storage device, said program storage device comprising:

code for creating a user partition; and

code for creating a ghost partition overlapping said user partition, said ghost partition adapted to receive said software, said ghost partition further adapted to be disabled after said ghost partition is no longer needed to release data storage space occupied by said ghost partition to said user partition.

12. The program storage device of claim 11, wherein said software is a diagnostics software.

13. The program storage device of claim 11, further comprising code for creating a plurality of ghost partitions.

14. The program storage device of claim 13, wherein one of said ghost partitions is adapted to contain diagnostics software and wherein another of said ghost partitions is adapted to contain download verification software.

15. The program storage device of claim 11, further comprising code for creating one or more master boot records (MBRs) on said data storage device.

16. The program storage device of claim 15, wherein said data storage device is used in one or more phases, further comprising a code for creating one MBR for each of said phases.

17. The program storage device of claim 15, further comprising an extended partition and a system partition, wherein said MBRs point to said user partition, said ghost partition, said system partition and said extended partition.

18. The program storage device of claim 15, wherein said data storage device is used in a first phase and a second phase with corresponding MBRs, further comprising a code for copying the MBR for said second phase over the MBR for said first phase after the completion of said first phase.

19. The program storage device of claim 11, wherein said ghost partition occupies a space between a minimum and a maximum partition size.

20. The program storage device of claim 19, wherein said maximum partition size is determined by iteratively subtracting a predetermined amount from said maximum partition size until said maximum partition size is allocable or until said minimum partition size exceeds said subtracted maximum partition size.

21. A computer system for downloading software to a disk drive, comprising:

a processor; and

a data storage device coupled to said processor, said data storage device having a computer readable code embodied therein for transferring software onto said disk drive, including;

a code for creating a user partition on said disk drive;

a code for creating a ghost partition overlapping said user partition on said disk drive;

a code for transferring said software to said ghost partition; and

a code for disabling said ghost partition after said ghost partition is not needed.

22. The computer system of claim 21 wherein said software is a diagnostics code.

23. The computer system of claim 21, wherein said ghost partition creating code creates a plurality of ghost partitions on said disk drive.

24. The computer system of claim 23, wherein one of said ghost partitions on said disk drive is adapted to contain diagnostics software and wherein another of said ghost partitions on said disk drive is adapted to contain download verification software.

25. The computer system of claim 21, further comprising a code for creating one or more master boot records (MBRs) on said disk drive.

26. The computer system of claim 25, wherein said data storage device is used in one or more phases, further comprising a code for creating one MBR for each of said phases.

27. The computer system of claim 25, further comprising an extended partition and a system partition on said disk drive, wherein said MBRs point to said user partition, said ghost partition, said system partition and said extended partition.

28. The computer system of claim 25, wherein said data storage device is used in a first phase and a second phase with corresponding MBRs, further comprising a code for copying the MBR for said second phase over the MBR for said first phase after the completion of said first phase.

29. The computer system of claim 21, further comprising a code for determining a minimum and maximum partition size for said ghost partition.

30. The computer system of claim 29, wherein said determining code further comprises:

(a) a code for determining a last sector containing data;

(b) a code for determining a minimum and maximum partition size for said ghost partition;

(c) a code for allocating said maximum partition size;

(d) a code for subtracting a predetermined amount from said maximum partition size if said allocating step failed;

(e) a code for repeating code (c) until said allocating code succeeds or until said subtracted maximum partition size equals said minimum partition size; and

a code for indicating an error if said minimum partition size exceeds said subtracted maximum partition size.