Build to order personal computer manufacturing fast boot method

Establish a method to command a personal computer to make a quick start

[Related application cross-reference]

This application is a continuation-in-part application of U.S. Patent Application Serial No. 09/562,870, filed on May 1, 2000, which is hereby incorporated by reference. /090,118, continuation of US Patent 6,080,207. These U.S. Patent Application Serial Nos. and 09/090,118 are hereby incorporated by reference in their entirety.

The present invention relates generally to the field of computer manufacturing, and more particularly to apparatus and methods for providing efficient computer delivery of a computer during manufacture.

The software installation during personal computer manufacturing is a slow procedure. When installing the software to a hard drive, the hard drive must be initialized and formatted. Then copy or load the software from the floppy or CD ROM disc onto the hard drive.

Another aspect of making software installation a timely procedure is the need to reboot the system after installing a piece of software. For example, after installing a collection of software programs, you must restart your computer system before installing additional software. In general, the computer system may need to be restarted several times before the complete software installation is complete. It usually takes at least 3 to 4 minutes to start each time, during which the computer system cannot be further installed. Reducing the amount of time spent in startup will reduce the amount of time to fully integrate the computer system, thereby delivering software to the computer system more efficiently. Therefore, there is a need to provide a device and method for quick start of a computer system during software installation.

Accordingly, the present invention is directed to an apparatus and method for providing a quick start of a computer system. In one embodiment of the invention, the quick start procedure in accordance with the present invention is generated by capturing sleep state file content similar to a hardware system and incorporating sleep state file content into the installation software. In accordance with an embodiment of the present invention, the manufacturing unit can simultaneously receive image and sleep state file content in the software delivery during the manufacturing process. The fabricated unit can use the sleep state to reduce its startup time, thereby reducing the startup time of the manufactured unit for a more efficient software installation.

The above general description and the following detailed description are merely exemplary and illustrative, and are not intended to limit the scope of the invention. The drawings are incorporated in and constitute a part of the specification,

Reference will now be made in detail to the preferred preferred embodiments embodiments

Figure 1 illustrates a disc image program for generating and delivering a disc image corresponding to a desired software configuration. The disc imaging program utilizes computerized network system 10 to generate and deliver custom software configurations defined by the ordering customer. The disc image program utilizes intelligence and granularity in generating the desired software configuration. The computerized network system 10 includes an image builder 20 for generating a disc image of the desired software configuration and then transmitting the image to the storage component 30. Storage element 30 is coupled to image server 40, which performs the task of delivering images. The image can be delivered directly to the hard disk 50 during the manufacturing and assembly process of the computer system. The image can also be delivered to a disc duplicator 52 for copying images on a computer readable medium for use at a ground based transmitter 54 or a management information system (MIS) 56 for broadcast images. At the office.

The first step of the disc image delivery program includes entering a customer command into the command registration system 15 to create a bill of materials (BOM). The bill of materials includes the customer's choice of the required software configuration for a particular computer system. The material included in the bill of materials is the hardware parameters of the computer system that receives the software configuration, including BIOS and CMOS settings plus other relevant required information. This information is used by the image builder to produce a digital image of the desired software configuration.

In a specific embodiment, the command registration system 15 is a mini computer. The mini computer is a multi-processing system that can support four to about two hundred users at the same time. Mini computers are well known to those skilled in the art. For example, the IBM AS/400 minicomputer acts as a command registration system 15 in one particular embodiment. In terms of size and power, the mini computer is between the workstation and the host. It is acceptable to use the equivalent input method as an alternative to using a mini computer, such as using a workstation or a host.

The information contained in the bill of materials corresponds to the specific software configuration required by the customer, plus a description of the computer system that receives the software configuration. The required configuration can be updated to an application already installed on the computer system, or the configuration can be updated to a new hard disk configured with the operating system and various applications. The description of the computer system includes but is not limited to the following parameters: hard disk size, installed accessories, current software configuration, BIOS and CMOS settings. The information of the corresponding bill of materials generated by the command registration system is applied to the image builder on interface 17. Interface standards between the mini computer and image builder 20 are well known in the art.

The image builder 20 is coupled to the command registration system 15 via interface 17 for receiving a bill of materials that provides image related information that produces or establishes the desired software configuration. Wisdom is provided in the step of the image delivery program because the image builder 20 sorts the stored images of a database to first determine if the image of the desired configuration has been generated as a prior computer configuration. The images are stored in a mass storage element 30 or a plurality of storage elements. If the image of the desired configuration is not previously generated, the image builder 20 selects an appropriate baseline image from the storage component 30 and then determines which additional image should be layered to the top of the baseline image to obtain the desired final configuration. .

These additional images, also known as incremental images, contain only additional information beyond the baseline image used to achieve the desired software configuration. Since this linear flow is associated with obtaining the desired configuration by adding incremental images to the baseline image, one level of granularity can be achieved. If the incremental image is not in the library, the image builder builds the appropriate incremental image. The configuration number is assigned to all baseline images and incremental images, which helps image builder 20 sort all possible images that can be used in the configuration program.

The actual steps that must be performed to produce a digital image of a hard disk of a computer system are well known to those skilled in the art. The image builder 20 monitors the data stream loaded on the hard disk 50 of the computer system. Since the disc image delivery program is a linear program as shown in FIG. 1, the image builder 20 can check the baseline image on a file-by-file basis, identify different regions, and decide which part to replace. The file name is checked not only by its name, but also by its date of creation. The image builder 20 monitors a particular file by a specific name or code when the file is generated.

In the case where the baseline is checked on a file-by-file basis, a bitwise comparison can be performed. In addition to the image builder 20 performing this comparison task, when the image builder 20 decides to change in the registration settings and the interrupt settings, another level of intelligence can be obtained, so that the new software configuration can be appropriately implemented in the computer system. Operation. If the required software configuration is not compatible with the hardware of the computer system, the Image Builder rejects the bill of materials as a non-functional configuration.

Full images (baseline and increments) or only incremental images may be loaded into a computer system (not shown). The method of loading any image into a computer system is well known to those skilled in the art. If the hard drive of the computer system (the hard drive shown in Figure 1) is currently in the configuration configuration and all required updates to an application, only incremental images are generated and installed. However, if the new hard disk 50 is being configured (as in the manufacturing and assembly process), the full image will be mounted to the hard disk 50.

The image delivery program avoids creating a new baseline for each image that needs to be delivered. Moreover, the image builder 20 includes an editor, for example, which can determine appropriate registration settings and add directory information corresponding to the installed application and its file location. An additional advantage of tiered information at the top of the baseline is that it isolates the problem areas between technical support staff and software engineers, and debugs and corrects problems. Due to the granularity, if the problem occurs after the incremental configuration has covered the top of the baseline image and the image is known to be error-free, it is easy to isolate the problem to the newly added incremental configuration. Once another incremental image is fixed, the correct image is mounted to a computer system with a known error.

The image builder 20 is a computer having a processor (preferably an Intel Pentium processor), a random access memory (RAM) (preferably at least 32 million bytes), a read only memory (ROM), and One or more storage elements_，Such as a hard disk drive, a floppy disk drive (a floppy disk can be inserted), a CD drive and a tape drive. Memory, hard disk, floppy disk, etc. are all types of computer readable media. Image builder 20 is coupled to a monitor 22, an indicator component 24, and a keyboard 26. The image builder is not limited to any particular type of computer. In one embodiment, image builder 20 is a PC compatible computer that runs a version of the Microsoft Windows operating system. The construction and operation of such computers is well known in the art.

The monitor 22 allows display of information observed by the computer user. The invention is not limited to any particular monitor 22. Such monitors include cathode ray tube (CRT) displays, and also include flat panel displays such as liquid crystal displays (LCDs). The indicator component 24 allows control of screen metrics provided by a graphical user interface such as the Microsoft Windows version of the operating system. The invention is not limited to any particular indicator element 24. Such indicator components include a mouse, trackpad, trackball, and indicator stick. In one embodiment, the image builder 20 is a Gateway Inc desktop personal computer, the monitor 22 includes a super VGA CRT display, and the indicator component 24 is a mouse. Finally, as is well known in the art, the keyboard 26 allows text information to be entered into the image builder 20, and the image builder 20 is not limited to any particular keyboard type.

Image builder 20 is coupled to mass storage element 30 by interface 28. Once the image builder 20 defines the image and specifies the corresponding configuration number, the image is stored in the storage element 30. Similarly, when the image builder 20 produces a disc image, to establish a baseline to generate an image, the storage component 30 is first checked to find the desired configuration or the desired configuration exact match. The storage element 30 is not limited to any particular format or structure, as long as it includes a computer readable medium for use as an interface. The storage component 30 may be a family of hard disk drives, a floppy disk drive (a floppy disk insertable), a compact disk drive, or a tape drive. As shown in FIG. 1, the storage element 30 employed may be internal to the image builder 20 or may exist as a separate entity.

After the image builder 20 produces the image of the desired software configuration, the image is transferred from the storage component 30 to the image server 40 via the interface 32. Image server 30 is another computer system similar to image builder 20. The image server 30 is a disc image delivery point. The image server 30 shown in Figure 1 may have numerous interfaces. A particular embodiment of the illustration has an image server coupled to the hard disk 50 via interface 60. This embodiment allows the hard disk 50 to be configured with the image of the desired software configuration before being installed in the computer system. In another embodiment of the illustration, image server 30 is coupled to disc replicator 52 via interface 61. The disc replicator 52 copies the disc image on a computer readable medium such as a floppy disk, a readable CD or a compressed drive. Other components that copy the disc image are acceptable.

In another embodiment of the illustration, image server 40 is coupled to ground emitter 54 via interface 62 for wireless transmission of the disc image to the end user. According to the operating parameters of the transmitter 54 and the delay performance of the transmitter_，Images can be launched anywhere in the world. In the location of the ground based transmitter 54, the image server 40 can be connected to the internet in any particular manner, and the invention is not so limited and is not shown in FIG. Internet connections are well known in the art.

In one embodiment, image server 40 includes a data machine and corresponding communication driver that is coupled to the Internet via a "dial-up connection" as is well known in the art. In another embodiment, image server 40 includes an Ethernet or similar hard card connected to a local area network (LAN), which itself is "directly connected" as is well known in the art ( Connect to the Internet, such as the T1 line. In another embodiment, image server 40 can be connected to the Internet using a cable modem or a satellite internet connection (as shown by transmitter 54).

In another embodiment of the illustration, image server 40 is coupled to a management information system (MIS) via interface 63. Management information systems can be used to support the infrastructure of transactions and organizations, such systems are well known to those skilled in the art.

Referring to Figure 2, a logic flow for generating a disc image of a desired software configuration is illustrated. Block 200 is the beginning of a logic flow that represents that a client command has been received. Block 200 produces a bill of materials (BOM).

The receipt of the bill of materials is represented by block 204. The image builder 20 begins with the top recording and calculates all registered configuration identifications (ConFig ID). In block 208, image builder 20 groups similar commands together. Due to the commonality between commands, grouping similar commands together can improve efficiency.

In block 212, image builder 20 compares the configuration ID to the configuration history. If the configuration ID corresponds to the image of the previously configured configuration, as shown in FIG. 1, the image builder 20 monitors whether the image is in the storage element 30. If the image is found in storage element 30, block 224 marks the configuration as ready for delivery and notifies computer network 10 that the desired image is ready. Otherwise, if the image is not found in the storage element 30, the image is generated by the image builder 20 as a newly created image in accordance with block 216. As part of the newly established procedure, block 230 requires image builder 20 to process the bill of materials to determine the parameters of the image to be created in accordance with the desired software configuration and to ensure that it is compatible with the client's hardware, software, and specific requirements. The final result or output of block 230 is an image or "digital image" of the desired software configuration based on the bill of materials.

FIG. 3 illustrates the structure of a disc image 280 generated by the image builder 20. The image builder 20 creates an image 280 in the software in accordance with the desired software configuration and delivers the image to the storage element 30. The sections of the disc image 280 will be described in the order shown in FIG. Other embodiments of the image structure will be apparent to those skilled in the art.

Section 300 includes a BIOS flash feature. The next two segments (sections 302 and 304) include the primary operating system and primary application code or instructions. The hardware characteristics of the computer system receiving the disc image 280 are addressed by a section 306 that sets the CMOS settings, the section 308 includes the primary BIOS command, the section 310 supports LOC information, and the section 312 supports the desktop of the primary operating system. parameter.

Section 314 support includes, but is not limited to, the following information: operating system registration, initialization information, and configuration files. Section 316 includes test information. Similar to section 314, section 318 includes, but is not limited to, the following information: application system registration, initialization information, and configuration files. The last two sections contain the identification of the particular image itself 320, and the last section contains the identification of the customer 322. The identification number allows future reference to the generated image, which aids in troubleshooting issues in the software configuration, and can also add incremental images to previously delivered images to update existing applications.

4 is an exemplary embodiment of an identification scheme 380 for a disc image structure. The image recognition system has a tree structure with a configuration identification number. The tree structure also includes an identification number corresponding to the lower part of the main file and a lower identification number corresponding to the edited dynamic file (EDF).

More specifically, the identification scheme 380 includes a configuration number 380 that is required to identify the desired image. This is the basis for the work of the image builder 20 when the desired image is produced. Once the configuration ID 380 has been identified, the primary file corresponding to the operating system 402 (e.g., Windows 95), and the desired application 404 are layered at the top of the configuration ID 400 base file. The edit dynamic file corresponds to the registration settings 406, the operating system initialization file 408, and the application EDF file 410.

The image creation software delivery procedure has been described above. The program generates an image of the customer's command in the software before placing the image on the hard drive or other storage component for the customer. Once the image is created, the baseline image can be easily changed or incremented without having to redefine the baseline. Adding an incremental image to the baseline image allows the desired image to be achieved. This method provides several levels of granularity in which incremental changes can be established in the system without the need to redefine the baseline to perform the primary work. This allows for easy updates and enables technical support to work effectively.

Referring to Figure 5, a specific embodiment of a sleep program 500 in accordance with the present invention is shown. The hibernation routine 500 begins when the computer system is up and running 510. In this state, all components of the computer system may be up and running immediately. When the computer system enters a sleep state, a representative of the computer memory and the contents of the computer component 520 can be generated. Once the computer is restarted, the sleep representative can be loaded from the hard disk 530 into the memory. This is extremely beneficial when the sleep representative loads quickly. This can result in a very fast computer system booting into its state before it goes to sleep.

In one embodiment of the invention, the operating system of the computer system controls the sleep program 500 of the present invention. In this mode, the operating system can determine when the computer system should go to sleep. In one embodiment of the invention, the sleep routine 500 can be implemented in accordance with the Advanced Configuration and Power Interface (ACPI) specifications. The ACPI specification includes S0 to S5 states, where S0 is on, S1 to S3 is sleep, S4 is soft off, and S5 is off. With the basic input/output system (BIOS) of the computer system, the discernible table can define what each state represents for individual components. The operating system of the computer system can decide when to transfer a component or the entire system from one state to another.

Referring to Figure 6, a specific embodiment of a software installation capture quick launch procedure 600 is shown. The program begins with the configuration of the hardware system 610. The hardware system is similar to the unit being fabricated, thereby adapting the quick start procedure of the present invention to the unit being fabricated. The hardware system is placed in a sleep state 620. Putting the hardware system into a sleep state includes generating image and component content of the computer memory. In one embodiment of the invention, the hardware system can be placed in the S4 sleep state of the ACPI specification.

When the hardware system is put into a sleep state, the file content of the sleep state can be retrieved (630 places). The captured dormant profile content can be incorporated into a soft body (640) installed in the fabricated unit. In this manner, the software installed in the manufactured unit includes code or instructions that include sleep state file content. In one embodiment of the invention, the captured sleep state file can be incorporated into the disc image of the present invention, as illustrated and described with respect to Figures 1 through 4. However, it should be understood that the dormant state file content that is captured can be incorporated into the software and installed in various ways well known in the art without departing from the scope and spirit of the invention.

Reference is now made to Fig. 7, which is a specific embodiment of a software installation procedure 700 employing a quick start procedure in accordance with the present invention. The program can be configured by starting the initial state of the manufactured unit (at 710). In one embodiment of the invention, the motherboard BIOS can be configured to be in a sleep state. The software with the dormant file content can be loaded into the manufactured unit (at 720). In a specific embodiment of the present invention, the manufactured unit can receive the software having the dormant file content by the disc image of the present invention. Therefore, the disc image, as shown in FIG. 3, can be generated according to FIG. 1 including the contents of the sleep state file. It will be appreciated that the dormant state profile content captured may be incorporated into the software and installed in a different manner, as is well known in the art without departing from the spirit and scope of the invention.

After receiving the software with the dormant file content, the manufactured unit can operate according to the sleep behavior state (at 730). This is extremely advantageous because the unit being manufactured can be quickly restarted during software installation. A more efficient software installation will result from a reduction in the stopping time of the manufacturing process during the restart of the manufactured unit.

In a particular embodiment of the invention, in accordance with the procedure 700 of the present invention, the first power-up procedure after manufacture can be less time consuming. For example, the manufactured unit can be configured to operate in accordance with the sleep behavior state during the first power-up procedure. For example, the hard disk of the unit can be preset to a sleep state. Therefore, if the unit has been purchased and first launched by the customer, the customer can benefit from the quick start-up procedure of the purchased unit. It is extremely advantageous because it provides customers with a pleasant out of the box experience.

The system and method of the present invention, as well as its numerous attendant advantages, will be apparent from the foregoing description. It is also apparent that various changes can be made in the form, structure, and arrangement of components without departing from the scope and spirit of the invention, The form previously described is merely an illustrative specific embodiment thereof. The following patent claims are intended to cover such variations.

<p>10. . . Computerized network system</p><p>15. . . Command registration system</p><p>17. . . interface</p><p>20. . . Image builder</p><p>twenty two. . . Monitor</p><p>twenty four. . . Indicator component</p><p>26. . . keyboard</p><p>28. . . interface</p><p>30. . . Storage element</p><p>32. . . interface</p><p>40. . . Image server</p><p>50. . . Hard disk</p><p>52. . . Disc replicator</p><p>54. . . Ground emitter</p><p>56. . . Management information system</p><p>61. . . interface</p><p>62. . . interface</p><p>63. . . interface</p><p>64. . . interface</p>

A number of advantages of the present invention will become apparent to those skilled in the art from a &lt;RTIgt; &lt;/ RTI&gt; &lt;RTIgt; &lt;/ RTI&gt; &lt;RTIgt; &lt;/ RTI&gt; &lt;RTIgt; &lt;/ RTI&gt; &lt;RTIgt; &lt;/ RTI&gt; &lt;/ RTI&gt; FIG. 1 is an exemplary system for generating and delivering a disc image corresponding to a desired software configuration; A logic flow for generating a disc image of a desired software configuration; FIG. 3 is a block diagram of an exemplary structure of a disc image; FIG. 4 is an exemplary embodiment of an identification scheme for disc image structure; FIG. A specific embodiment of a sleep program according to the present invention; FIG. 6 illustrates a specific embodiment of a software installation capture quick start procedure in accordance with the present invention; and FIG. 7 is a quick start procedure for installing software in accordance with the present invention. Specific embodiment.