Patent Application
20130311731
This application claims all benefits accruing under 35 U.S.C. §119 from China Patent Application No. 201210149633.X, filed on May 15, 2012 in the State Intellectual Property Office of China. The contents of the China Application are hereby incorporated by reference. In addition, subject matter relevant to this application is disclosed in: co-pending U.S. Patent Applicant entitled “SYSTEM AND METHOD OF MAKING GOLDEN MASTER,” Attorney Docket Number US44552, Application No. [to be advised], filed on the same day as the present application. This application and the co-pending U.S. Patent Application are commonly owned, and the contents of the co-pending U.S. Patent Application are hereby incorporated by reference.
1. Technical Field
The disclosure generally relates to a system and method of making golden master.
2. Description of Related Art
A golden master is a hard disk drive on which a user image stays. The user image is to be delivered to end user. Once the golden master is made, a factory can mass-produce hard disk drives that have the same data as the golden master through the way of cloning the golden master by a hard disk copy machine or the like. The manufactory can then install these hard disk drives into computers. Commonly each of the computers has to pass a set of test procedures by running a diagnostic program before being shipped out. On one hand, the user image may be corrupted if the diagnostic program is stored within the golden master. On the other hand, the diagnostic program is confidential and is not to be delivered with the user image to end user.
Therefore, there is room for improvement within the art.
Many aspects of the embodiments can be better understood with reference to the following drawings. The components in the drawings are not necessarily drawn to scale, the emphasis instead being placed upon clearly illustrating the principles of the embodiments. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the views.
The disclosure is illustrated by way of example and not by way of limitation in the figures of the accompanying drawings, in which like reference numerals indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references can mean “at least one.”
In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language such as Java, C, or assembly. One or more software instructions in the modules may be embedded in firmware, such as in an erasable-programmable read-only memory (EPROM). The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of non-transitory computer-readable medium or other storage device. Some non-limiting examples of non-transitory computer-readable media are compact discs (CDs), digital versatile discs (DVDs), Blu-Ray discs, Flash memory, and hard disk drives.
The CPU 101 is operably coupled to the storage device 102, the display 103, the input device 104, and the hard disk interface 105. The CPU 101 may include one or more processors that provide the processing capability to execute the operating system, programs, user and application interfaces, and any other functions of the computing device 10. The CPU 101 may include one or more microprocessors and/or related chip sets. For example, the CPU 101 may include “general purpose” microprocessors, a combination of general and special purpose microprocessors, instruction set processors, graphics processors, video processors, related chips sets, and/or special purpose microprocessors. The CPU 101 also may include onboard memory for caching purposes.
Information, such as programs and/or instructions, used by the CPU 101 may be located within the storage device 102. The storage device 102 may store a variety of information and may be used for various purposes. For example, the storage device 102 may store firmware for the computing device 10 (such as a basic input/output instruction or operating system instructions), various programs, applications, or routines executed on the computing device 10, user interface functions, processor functions, and so forth. In addition, the storage device 102 may be used for buffering or caching during operation of the computing device 10.
The storage device 102 may include any suitable manufacture that includes one or more tangible, computer-readable media. For example, the storage device 102 may include a volatile memory, such as random access memory (RAM), and/or as a non-volatile memory, such as read-only memory (ROM). The components may further include other forms of computer-readable media, such as non-volatile storage, for persistent storage of data and/or instructions. The non-volatile storage may include flash memory, a hard drive, or any other optical, magnetic, and/or solid-state storage media. The non-volatile storage may be used to store firmware, data files, software, wireless connection information, and any other suitable data.
The display 103 may provide a visual output interface between the computing device 10 and a user. The visual output may include text, graphics, video, and any combination thereof. The display 103 may use LCD (liquid crystal display) technology, or LPD (light emitting polymer display) technology, although other display technologies may be used in other embodiments. In some embodiments, the display 103 may be a touch-sensitive display which also accepts input from the user based on haptic and/or tactile contact through a touch-sensitive surface.
The input device 104 may provide an input interface between the computing device 10 and a user. The input device 104 may be a keyboard, a mouse or a touch pad, for the input of information.
The hard disk interface 105 may provide connectivity channels for reading/writing data from/to the golden master 20. The hard disk interface 105 may represent, for example, a serial advanced technology attachment (SATA) controller or a small computer system interface (SCSI).
The image burning module 301 may burn a user image 21 to the golden master 20. Referring to
The sector address obtaining module 302 may read a starting sector address and a partition size of a user partition from the user partition record 24, and calculate an ending sector address of the user partition according to the starting sector address and the partition size of the user partition. As shown in
The partition record backup module 303 may duplicate the user partition record 24. In some embodiments, the partition record backup module 303 may copy the user partition record 24 to a specified sector which has an identity number between 1 and 63. The sectors with identity numbers from 1 to 63 in a hard disk drive are always idle and free to use. Therefore, the duplication of the user partition 24 will not damage or negatively affect the user image.
The DPT clearing module 304 may clear the DPT 23 by removing the user partition record 24 from the DPT 23. As shown in
The partition establishing module 305 may establish a diagnostic partition 205 between a starting sector address and a ending sector address of a user partition in the golden master 20. As shown in
The partition establishing module 305 may further generate a diagnostic partition record 25 pointing to the diagnostic partition 205, and write the diagnostic partition record 25 into the DPT 23. The diagnostic partition record 25 in
The program writing module 306 may store a diagnostic program in the diagnostic partition 205 after the diagnostic partition record 25 is written into the DPT 23. The diagnostic program may be used to launch a set of testing procedures in the factory product line.
The partition record resuming module 307 may add the user partition record 24 into the DPT 23. Thus, both the user partition record 24 and the diagnostic partition record 25 reside in the DPT 23. In one embodiment, the partition record resuming module 307 retrieves the user partition record 24 from the specified sector of the golden master 20 and writes the user partition record 24 into the DPT 23.
The partition marking module 308 may mark the diagnostic partition 205 as active after the diagnostic partition record 25 has been written into the DPT 23. Thus, when a computer is equipped with a clone of the golden master 20, the computer may be booted from the diagnostic partition 205 and run the diagnostic program. In some embodiments, the diagnostic program may remove the diagnostic partition record 25 from the DPT 23 and mark the OS partition 211 as active after the diagnostic process is complete, so that the diagnostic program itself will not be delivered with the user image to end user.
In step S601, the image burning module 301 burns a user image 21 to the golden master 20. Referring to
In step S602, the sector address obtaining module 302 obtains a starting sector address and an ending sector address of a user partition. As shown in
In step S603, the partition record backup module 303 duplicates the user partition record 24. In some embodiments, the partition record backup module 303 copies the user partition record 24 to a specified sector which has an identity number between 1 and 63. Sectors with identity numbers from 1 to 63 in a hard disk drive are always idle and free to use. Therefore, the duplication of the user partition 24 will not damage or negatively affect the user image.
In step S604, the DPT clearing module 304 clears the DPT 23 by removing the user partition record 24 from the DPT 23. The user partition record 24 in
In step S605, the partition establishing module 305 establishes a diagnostic partition 205 between the starting sector address and the ending sector address of the data partition 213 in the golden master 20. The partition establishing module 305 generates a diagnostic partition record 25 pointing to the diagnostic partition 205, and writes the diagnostic partition record 25 into the DPT 23. The diagnostic partition record 25 in
In step S606, the program writing module 306 stores a diagnostic program in the diagnostic partition 205. The diagnostic program may be used to launch a set of testing procedures in the factory production line.
In step S607, the partition record resuming module 307 adds the user partition record 24 into the DPT 23. Thus, the user partition record 24 and the diagnostic partition record 25 co-exist in the DPT 23. In one embodiment, the partition record resuming module 307 retrieves the user partition record 24 from the specified sector of the golden master 20 and writes the user partition record 24 into the DPT 23.
In step S608, the partition marking module 308 marks the diagnostic partition 205 as active. Thus, when a computer uses a hard disk drive cloned from the golden master 20, the computer may be booted from the diagnostic 205 and run the diagnostic program. In some embodiments, the diagnostic program removes the diagnostic partition record 25 from the DPT 23 and marks the OS partition 211 as active after the diagnostic process is complete, so that the diagnostic program will not be delivered with the user image to end user.
Although numerous characteristics and advantages have been set forth in the foregoing description of embodiments, together with details of the structures and functions of the embodiments, the disclosure is illustrative only, and changes may be made in detail, especially in the matters of arrangement of parts within the principles of the disclosure to the full extent indicated by the broad general meaning of the terms in which the appended claims are expressed.
In particular, depending on the embodiment, certain steps or methods described may be removed, others may be added, and the sequence of steps may be altered. The description and the claims drawn for or in relation to a method may give some indication in reference to certain steps. However, any indication given is only to be viewed for identification purposes, and is not necessarily a suggestion as to an order for the steps.
| Number | Date | Country | Kind |
|---|---|---|---|
| 201210149633.X | May 2012 | CN | national |
