Method and apparatus for fast booting a computer system

Device and method for quickly starting computer system

[Cross Reference for Related Applications]

This application is a part of US Patent Application No. 09 / 562,870 (currently pending) filed on May 1, 2000, and 09 / 562,870 is US Patent Application No. 09 filed on June 4, 1998 / 090,118, which is a continuation of US patent 6,080,207. These U.S. patent application numbers and 09 / 090,118 are all incorporated herein by reference.

The present invention relates generally to the field of computer manufacturing, and more specifically to a device and method for providing computer-efficient software delivery during manufacturing.

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

Another aspect that makes software installation a timely process is the need to restart the system after installing a piece of software. For example, after installing a software program collection, the computer system must be restarted before installing additional software. In general, the computer system may need to be restarted several times before the complete software installation is complete. Each boot usually takes at least 3 to 4 minutes, during which time the computer system cannot be further installed. Reducing the amount of time spent in startup will reduce the amount of time it takes to fully integrate the computer system, thereby delivering software to the computer system more efficiently. Therefore, it is necessary to provide a device and method for quickly starting a computer system during software installation.

Therefore, the present invention focuses on explaining a device and method for providing a fast startup of a computer system. In a specific embodiment of the present invention, the quick startup procedure according to the present invention is generated by retrieving the hibernation state file content of a similar hardware system and incorporating the hibernation state file content into the installation software. According to a specific embodiment of the present invention, during the manufacturing process, the manufactured unit can receive the image and the hibernation file content in the software delivery at the same time. The manufactured unit can use the hibernation state to reduce its startup time, which can reduce the startup time of the manufactured unit for more efficient software installation.

It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and thus do not limit the scope of patent application of the present invention. The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate a specific embodiment of the invention and, together with the general description, serve to explain the principles of the invention.

Reference will now be made in detail to the presently preferred embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

FIG. 1 illustrates a disc image procedure for generating and delivering a disc image corresponding to a desired software configuration. The disc image program utilizes the computerized network system 10 to generate and deliver customized software configurations defined by the ordering customer. The disc image program uses intelligence and granularity when generating the required software configuration. The computerized network system 10 includes an image creator 20 for generating a disk image of a required software configuration, and then transmitting the image to the storage element 30. The storage element 30 is connected to the image server 40 and performs the task of delivering images. This image can be delivered directly to the hard disk 50 during the computer system manufacturing and assembly process. The image can also be delivered to a disc duplicator 52 for copying the image on a computer-readable medium, a ground-based transmitter 54 for broadcasting the image, or a management information system (MIS) 56 Office.

The first step of the disc image delivery process includes entering customer orders into the order registration system 15 to create a bill of materials (BOM). The bill of materials includes the customer's choice of software configuration required for a particular computer system. The material list includes the hardware parameters of the computer system receiving the software configuration, including the BIOS and CMOS settings plus other relevant necessary information. This information is used by the image builder to generate digital images of the required software configuration.

In a specific embodiment, the order registration system 15 is a mini computer. A mini-computer is a multi-processing system that can support four to about two hundred users simultaneously. Mini computers are well known to those skilled in the art. For example, the IBM AS / 400 mini-computer is used as a command registration system 15 in a specific embodiment. In terms of size and power, a mini-computer is between the workstation and the host. Using equivalent input methods as an alternative to using a mini-computer is acceptable, such as using a workstation or 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 receiving 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 that configures the configuration with the operating system and various applications. The computer system description 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 material list generated by the order registration system is applied to the image builder on the interface 17. The interface standard between the mini-computer and the image builder 20 is well known in this technology.

To receive a list of materials that provide image-related information for generating or creating the required software configuration, the image creator 20 is coupled to the command registration system 15 through an interface 17. The intelligence is provided in the steps of the image delivery process, because the image builder 20 sorts the stored images of a database to first determine whether the image of the required configuration has been generated as a previous computer configuration. These images are stored in the mass storage element 30 or more. If the image of the required configuration has not been generated previously, the image builder 20 selects an appropriate baseline image from the storage element 30 and then decides which additional image should be layered on top of the baseline image to obtain the desired final configuration .

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

The actual steps necessary to generate a digital image of a hard disk of a computer system are well known to those skilled in the art. The image creator 20 monitors the data stream loaded on the hard disk 50 of the computer system. As shown in FIG. 1, the disc image delivery process is a linear process, so the image builder 20 can check the baseline image file by file, identify different areas, 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 creator 20 monitors a specific file by a specific name or code when the file is generated.

Where baselines are checked on a file-by-file basis, bit-by-bit comparisons can be performed. In addition to the image creator 20 performing this comparison task, when the image creator 20 decides to change in the registration settings and interrupt settings, another level of wisdom can be obtained, so that the new software configuration can be properly implemented in the computer system Operation. If the required software configuration is not compatible with the hardware of the computer system, Image Builder rejects the BOM as a non-functional configuration.

Full images (baseline and incremental) 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 disk of the computer system (such as the hard disk shown in Figure 1) is currently in the configuration configuration, and all required is an application update, 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 complete image will be installed on the hard disk 50.

The image delivery procedure avoids creating a new baseline for each image to be delivered. Moreover, the image creator 20 includes an editor, for example, it can determine appropriate registration settings, and adds directory information corresponding to the installed application and its file location. The added benefit of the layered information at the top of the baseline is that it enables technical support staff and software engineers to isolate problem areas, debug and correct problems as they arise. Due to the granularity, if the problem occurs after the incremental configuration covers 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 generated, the correct image is installed on a computer system with a known error.

Image Creator 20 is a computer with 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 (pluggable floppy disk), an optical disk drive and a magazine drive. Memory, hard disk, floppy disk, etc. are all types of computer-readable media. The image builder 20 is coupled to a monitor 22, an indicator element 24 and a keyboard 26. The image builder is not limited to any particular type of computer. In a specific embodiment, the image creator 20 is a PC-compatible computer capable of running a version of Microsoft Windows operating system. The construction and operation of such computers are well known in the art.

The monitor 22 allows the information viewed by the computer user to be displayed. The invention is not limited to any particular monitor 22. Such monitors include cathode ray tube (CRT) displays and also flat panel displays such as liquid crystal displays (LCDs). The pointer element 24 allows controlling on-screen pointers provided by a graphical user interface such as a Microsoft Windows version operating system. The invention is not limited to any particular index element 24. Such pointing components include a mouse, trackpad, trackball, and pointing stick. In a specific embodiment, the image creator 20 is a Gateway Inc desktop personal computer, the monitor 22 includes a super VGA CRT display, and the pointer 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.

The image builder 20 is coupled to the mass storage element 30 through an interface 28. Once the image builder 20 defines an image and specifies a corresponding configuration number, the image is stored in the storage element 30. Similarly, when the image creator 20 generates a disc image, in order to establish a baseline to generate an image, the storage element 30 is first checked to find a required configuration or a perfect match of the required configuration. The storage element 30 is not limited to any particular format or structure, as long as it includes a computer-readable medium serving as an interface. The storage element 30 may be a family of hard disk drives, a floppy disk drive (pluggable floppy disk), an optical disk drive, or a cassette drive. As shown in FIG. 1, the storage element 30 used may be inside the image builder 20 or may exist as an independent entity.

After the image builder 20 generates an image of the required software configuration, the image is transferred from the storage element 30 to the image server 40 through the interface 32. The image server 30 is another computer system similar to the image creator 20. The image server 30 is a disc image delivery point. As shown in FIG. 1, the image server 30 may have many interfaces. One illustrated embodiment has an image server coupled to a hard disk 50 via an interface 60. This specific embodiment allows the hard disk 50 to be configured with the image of the required software configuration before being installed on the computer system. In another embodiment shown in the figure, the image server 30 is coupled to the disc duplicator 52 through the interface 61. The disc duplicator 52 duplicates a disc image on a computer-readable medium (such as a floppy disc, a readable CD, or a compressed drive). Other components for copying disc images are acceptable.

In another specific embodiment shown in the figure, in order to wirelessly transmit the disc image to an end user, the image server 40 is coupled to the ground-based transmitter 54 through an interface 62. Based on transmitter 54 operating parameters and transmitter delay performance_，The image can be transmitted to any place in the world. In the location of the ground-based transmitter 54, the image server 40 may be connected to the Internet in any particular manner, and the present invention is not limited thereto and is not shown in FIG. Internet connections are well known in the art.

In a specific embodiment, the image server 40 includes a modem and a corresponding communication driver, which is connected to the Internet via a "dial-up connection" as is well known in the art. In another specific embodiment, the image server 40 includes an Ethernet network or similar hard card connected to a local area network (LAN), which itself is connected via a "direct connection" (known as (Such as the T1 line, etc.) to the Internet. In another specific embodiment, the image server 40 may be connected to the Internet using a cable modem or a satellite Internet connection (as shown by the transmitter 54).

In another embodiment shown in the figure, the image server 40 is coupled to a management information system (MIS) via an interface 63. Management information systems can be used to support business and organizational infrastructures, such systems being well known to those skilled in the art.

Referring to FIG. 2, a logic flow of generating a disc image of a required software configuration is illustrated. Block 200 is the beginning of the logic flow, which represents that a customer order has been received. Block 200 generates a bill of materials (BOM).

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

In block 212, the image builder 20 compares the configuration ID with the configuration history. If the configuration ID corresponds to a previously set configuration image, 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 the storage element 30, block 224 marks the configuration as ready for delivery and notifies the operator of the computer network 10 that the required image is ready. Otherwise, if the image is not found in the storage element 30, the image is generated as a newly created image by the image builder 20 according to block 216. As part of the new creation process, block 230 requires the image builder 20 to process the bill of materials to determine the parameters for creating the image in accordance with the required software configuration and ensure that it is compatible with the customer's hardware, software, and specific requirements. The final result or output of block 230 is an image or "digital image" configured by the required software according to the bill of materials.

FIG. 3 illustrates the structure of a disc image 280 generated by the image creator 20. The image builder 20 creates an image 280 in the software according to the required software configuration, and delivers the image to the storage element 30. The sections of the disc image 280 will be explained in the order shown in FIG. 3. Those skilled in the art can understand other specific embodiments of the image structure.

Section 300 includes BIOS flash features. The next two sections (sections 302 and 304) include the main operating system and main application code or instructions. The hardware characteristics of the computer system receiving the disc image 280 are addressed by the section 306 that handles the CMOS settings. The section 308 includes the main BIOS commands. The section 310 supports LOC information and the section 312 supports the desktop type of the main operating system. parameter.

Section 314 supports, 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 segments contain the identification of the particular image 320, and the last segment contains the identification of the client 322. The identification number allows future reference to the generated images, which helps with troubleshooting issues in software configuration, and also adds incremental images to previously delivered images to update existing applications.

FIG. 4 illustrates an exemplary embodiment of an identification scheme 380 of a disc image structure. Image recognition is a tree structure with a configuration identification number. The tree structure also includes a lower identification number corresponding to the main file and a lower identification number corresponding to the editing dynamic file (EDF).

More specifically, the identification scheme 380 includes identifying a configuration number 380 required to create a desired image. This is the basis of the work of the image builder 20 when generating the required images. Once the configuration ID 380 has been identified, the main file corresponding to the operating system 402 (such as Windows 95) and the required application 404 are layered on top of the basic configuration ID 400 file. The editing dynamic file corresponds to the registration setting 406, the operating system initialization file 408, and the application EDF file 410.

The image creation software delivery process has been described above. This procedure generates the image ordered by the customer in the software before placing the image on the hard disk or other storage means for the customer. Once the image is generated, it is easy to change or increment the baseline image without redefining the baseline. Adding incremental images 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 performing major work by redefining the baseline. This allows for easy updates and allows technical support to function effectively.

Referring to FIG. 5, a specific embodiment of a hibernation program 500 according to the present invention is shown. When the computer system is up and running 510, the hibernation program 500 starts. In this state, all components of the computer system may be activated and immediately operational. When the computer system enters the hibernation state, a computer memory representative and computer component content 520 may be generated. Once the computer is restarted, the hibernation representative can be loaded into memory from hard drive 530. This is extremely beneficial when the hibernation representative is loading quickly. This can produce a very fast computer system startup, putting it into the state it was in before it went to sleep.

In a specific embodiment of the present invention, the operating system of the computer system controls the hibernation program 500 of the present invention. In this way, the operating system can determine when the computer system should go to sleep. In a specific embodiment of the present invention, the hibernation procedure 500 may be implemented according to the advanced configuration and power interface (ACPI) specifications. ACPI specifications include S0 to S5 states, among which S0 is on, S1 to S3 are sleep states, S4 are soft off states, and S5 are off states. With the basic input / output system (BIOS) of the computer system, the discernable table can define what each state represents for individual components. The operating system of a computer system can determine when to transfer a component or the entire system from one state to another.

Referring to FIG. 6, there is shown a specific embodiment of retrieving the quick start procedure 600 for software installation. The procedure starts with the configuration of the hardware system 610. The hardware system is similar to the manufactured unit, thereby adapting the quick start procedure of the present invention to the manufactured unit. The hardware system is placed in hibernation state 620. Putting the hardware system into hibernation includes generating computer memory images and component contents. In a specific embodiment of the present invention, the hardware system may be placed in the S4 sleep state of the ACPI specification.

When the hardware system is put into hibernation, the contents of the hibernation file can be retrieved (at 630). The retrieved hibernation file content can be incorporated into software installed at the manufacturing unit (at 640). In this mode, the software installed in the manufactured unit includes codes or instructions, which include the contents of hibernation files. In a specific embodiment of the present invention, the captured hibernation status file may be incorporated into the disc image of the present invention, as explained and displayed with reference to FIGS. 1 to 4. However, it should be understood that the content of the retrieved hibernation file 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 program 700 that uses the quick start program according to the present invention. The procedure can be initiated by configuring the initial settings of the manufactured unit to a sleep state (at 710). In a specific embodiment of the present invention, the motherboard BIOS can be set and configured to sleep. Software with hibernation 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 with the content of the hibernation file by using 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 content of the hibernation file. It should be understood that the captured hibernation file content can be incorporated into the software and installed in different ways, which is well known in the art without departing from the field and essence of the present invention.

After receiving the software with the hibernation file content, the manufactured unit can operate according to the hibernation behavior state (730). This is extremely advantageous because the manufactured unit can be quickly restarted during software installation. By reducing the downtime of the manufacturing process during the restart of the manufactured unit, more efficient software installation will result.

In a specific embodiment of the present invention, according to the procedure 700 of the present invention, the first power-on procedure after manufacture can take less time. For example, a manufactured unit can be configured to operate in a sleep behavior state during the first power-up sequence. For example, the hard disk of the unit can be set to a sleep state in advance. Therefore, if the unit has been purchased and first started by the customer, the user can benefit from the quick startup procedure of the purchased unit. It is extremely advantageous because it can provide customers with a pleasant out of the box experience.

From the foregoing description, Xianxin can understand the system and method of the present invention, and its many accompanying advantages. It is also believed that, without departing from the scope and spirit of the invention, and without sacrificing all its substantial advantages, various changes can be made in form, structure, and component configuration. The form described before is only one illustrative embodiment. The scope of the following patent applications is intended to cover such variations.

<p>10. . .Computerized network system</p><p>15. . .Order registration system</p><p>17. . .interface</p><p>20. . .Image builder</p><p>twenty two. . .Monitor</p><p>twenty four. . .Indicator element</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 drive</p><p>52. . .Disc duplicator</p><p>54. . .Ground-based launcher</p><p>56. . .Management Information System</p><p>61. . .interface</p><p>62. . .interface</p><p>63. . .interface</p><p>64. . .interface</p>

Those skilled in the art can more easily understand the many advantages of the present invention with reference to the accompanying drawings. Among them: the block diagram of FIG. 1 is an exemplary system for generating and delivering a disc image corresponding to the required software configuration; the specific embodiment of FIG. The logical flow of generating the disc image with the required software configuration; Figure 3 is a block diagram of an exemplary structure of a disc image; Figure 4 is an exemplary embodiment of a disc image structure identification scheme; and Figure 5 illustrates A specific embodiment of the hibernation program according to the present invention; FIG. 6 illustrates a specific embodiment of the quick start program for software installation according to the present invention; FIG. 7 is a quick start program for installing software according to the present invention Specific embodiment.