METHOD AND SYSTEM FOR AUTOMATICALLY INSTALLING AN INITIAL SOFTWARE CONFIGURATION INCLUDING AN OPERATING SYSTEM MODULE FROM A LIBRARY CONTAINING AT LEAST TWO OPERATING SYSTEM MODULES BASED ON RETRIEVED COMPUTER IDENTIFICATION DATA

[0002] 1. Field of the Invention

[0003] This invention relates to methods and systems for installing software onto a computer, and, in particular embodiments, methods and systems for automatically installing an initial software configuration onto a computer.

[0004] 2. Related Art

[0005] Generally, computer manufacturers sell a number of different types (e.g., desktop, laptop) and models (e.g., Toshiba Equium 7100 Desktop Series, 3200 Series, Tecra 8000 Series laptop, Libretto 110 Series laptop) of computers with different hardware configurations (e.g., different processors, processing speed, amount of RAM, hard disk drive storage, peripheral devices, and the like). Such computers are typically sold with an initial software configuration (including an operating system, device drivers, and software applications) pre-installed on a hard disk drive of the computer. Factory installation of an initial software configuration onto multiple computers usually involves manually installing each software program onto a sample computer as desired. Once the manual installation is completed, the disk image is saved onto a storage medium (e.g., compact disk, hard disk drive of another computer, or the like) as one or more compressed files, which represent all of the properly installed software programs and the properly configured operating environment of the computer. The compressed disk image file(s) is then duplicated onto each computer to be delivered with the initial software configuration. The drawback of this disk imaging method is that it requires the creation of multiple boot disks for the different types, models, and hardware configurations of computers, as well as different operating systems, device drivers, and software applications to be installed onto the computers. For example, different boot disks are required to install Windows® 95, Windows 98, Windows NT, or OS/2 onto different computers. Such use of multiple boot disks makes factory installation of initial software configurations onto multiple computers a cumbersome process. Additionally, a factory worker is often needed to enter the type, model, and hardware configuration of the computer in order to determine which software programs (e.g., device drivers) to install onto the computer. Because such user interaction is required, factory installation of initial software configurations onto multiple computers cannot be an automatic process, and thus, is inefficient. Furthermore, during installation of the initial software configuration onto the computer, an initial boot of the computer as well as one or more reboots of the computer are generally required. In order to keep track of which boot or reboot has been performed, a process flag is typically written to the boot disk. However, such writing to the boot disk involves a risk of infecting the boot disk with a virus.

[0006] It is an object of embodiments of the present invention to provide a method and a system for automatically installing an initial software configuration onto a computer, which obviate for practical purposes, the above mentioned limitations.

[0007] According to an embodiment of the present invention, an installation system includes one or more target computers having different hardware configurations. Each target computer also has a memory and identification data associated with its hardware configuration, such as a unique part number, for indicating the particular hardware configuration of the target computer. To install an initial software configuration onto each of the target computers, a boot storage medium is placed in each of the target computers. Each boot storage medium includes logic and other data for booting each of the different target computers and automatically installing an initial software configuration onto each of the target computers. The identification data associated with the hardware configuration of each target computer is automatically retrieved from the memory of the target computer, and a software bundle is automatically retrieved and transferred from a library of software bundles to the memory of the target computer based on the retrieved identification data. The transferred software bundle is then installed onto the memory of the target computer, preferably the hard disk drive.

[0008] Because each boot storage medium includes logic and other data for booting each of the different target computers and automatically installing an initial software configuration onto each of the target computers, multiple versions of the boot storage media for the different target computers are not required. Instead, a single version of the boot storage medium is required. Additionally, once a target computer is booted from the boot storage medium, the installation process is entirely automatic and requires no user interaction, and thus, is more efficient.

[0009] Other features and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, which illustrate, by way of example, various features of embodiments of the invention.

[0010] A detailed description of embodiments of the invention will be made with reference to the accompanying drawings, wherein like numerals designate corresponding parts in the several figures.

[0011] FIG. 1 illustrates a system for automatically installing an initial software configuration onto a computer in accordance with an embodiment of the present invention.

[0012] FIG. 2 illustrates a system for automatically installing an initial software configuration onto a computer in accordance with an alternative embodiment of the present invention.

[0013] FIGS. 3A-3C are flowcharts illustrating a method for automatically installing an initial software configuration onto a computer in accordance with an embodiment of the present invention.

[0014] As shown in the drawings for purposes of illustration, embodiments of the present invention are directed to a method and a system for automatically installing an initial software configuration or pre-install onto one or more target computers. In preferred embodiments, the target computers are of different types (e.g., desktop, laptop) and models (e.g., Toshiba Equium 7100 Desktop Series, 3200 Series, Tecra 8000 Series laptop, Libretto 110 Series laptop). Accordingly, the target computers have different hardware configurations (e.g., different processors, processing speed, amount of RAM, hard disk drive storage, peripheral devices, and the like), which support different software configurations (e.g., different operating systems, such as Windows® 95, Windows 98, Windows NT, and OS/2; device drivers; and software applications, such as a word processor, a spreadsheet, and the like). Each target computer also has identification data associated with its hardware configuration, such as a unique part number, for indicating the particular type, model, and hardware configuration of the target computer. For example, Part Number PV 1046U-D34J0 represents an Equium 7100 Desktop Series computer with a Pentium® II 400 MHz processor, 64 MB SDRAM, 6.0 GB hard disk drive, 32X CD-ROM drive, and other hardware characteristics.

[0015] To install an initial software configuration onto one or more of the target computers, a boot storage medium, such as a removable floppy disk, is placed in each of the target computers. Each boot storage medium includes logic and other data for booting each of the different types and models of target computers and automatically installing an initial software configuration onto each of the target computers. In other words, the same version of the boot storage medium is placed into all of the target computers, regardless of the hardware configuration of the target computer or the initial software configuration to be installed onto the target computer. Different versions of the boot storage media for installing different initial software configurations (e.g., different operating systems, such as Windows® 95, Windows 98, Windows NT, or OS/2) are not necessary.

[0016] Once a target computer is booted from the boot storage medium, the installation process is entirely automatic and requires no user interaction. The identification data associated with the hardware configuration of each target computer, preferably the unique part number, is automatically retrieved from the memory, preferably the BIOS storage area, of the target computer, and a software bundle is automatically retrieved and transferred from a library of software bundles stored on a library storage medium to the memory of the target computer based on the retrieved identification data. The library storage medium may be a memory, such as a hard disk drive or a compact disk placed in a CD-ROM drive, of a remote installation server connected to the target computers through a network connection. Alternatively, the library storage medium may be a compact disk local to the target computer. The transferred software bundle is then installed onto the memory of the target computer, preferably the hard disk drive. In preferred embodiments, the software bundle includes an operating system, one or more device drivers, and one or more software applications (e.g., a word processor, a spreadsheet, and the like) appropriate for the hardware configuration of the target computer. In alternative embodiments, the device drivers and/or software applications may be omitted from the software bundle.

[0017] FIG. 1 illustrates the operational environment for the installation method and the basic components of the installation system in accordance with an embodiment of the present invention. In preferred embodiments, the installation system 10 includes a communications link 12, such as a local area network (LAN) 12. The installation system 10 also includes one or more target computers 14 and a remote installation server 18, which are interconnected through the LAN 12 in a manner well known to those having skill in the art. In alternative embodiments, the communications link 12 may include any other private, public, or hybrid private/public communications network which transfers data packets among computers in the network.

[0018] In the embodiment illustrated in FIG. 1, the installation system 10 includes a remote installation server 18. The remote installation server 18 includes memory (such as RAM, ROM, and a hard disk drive) and at least one processor. Software bundles, each of which preferably include an operating system, one or more device drivers, and one or more software applications (e.g., a word processor, a spreadsheet, and the like), are transferred from one or more removable storage media 20a(such as a floppy disk, a compact disk, a zip drive, or the like) and stored on the memory of the installation server 18, preferably the hard disk drive.

[0019] In one embodiment, each software bundle is stored as one or more compressed disk image files that are capable of automatically installing the software onto a computer and configuring the environment of the computer without any user interaction. The software bundle is packaged by first completely installing each desired software program (e.g., operating system, device driver(s), software application(s)) onto a clean hard disk drive of a computer. The computer is then booted from a boot disk, and the image of the hard disk drive is compressed into one or more disk image files using a compression utility program such as PKZIP™.

[0020] In preferred embodiments, the software bundles are stored in a library on the memory of the installation server 18, preferably the hard disk drive, along with tools (software programs and procedures) for installing the software bundles onto the target computer 14. In one embodiment, the library is arranged into one or more directories on the memory of the installation server 18. Each directory corresponds to a distinct initial software configuration or pre-install for a target computer 14 and includes the software bundle to be installed onto the target computer 14 as well as the tools for installing the software bundle onto the target computer 14. Generally, each pre-install corresponds to a particular type, model, and hardware configuration of a target computer 14. However, it is possible for a single pre-install to correspond to different types and models of target computers 14 with similar hardware configurations. In alternative embodiments, the library of software bundles may be arranged in a different structure on the memory of the installation server 18.

[0021] In preferred embodiments, the installation server 18 also maintains a database in the memory of the installation server 18, preferably the hard disk drive. The database stores information regarding the contents of the library of software bundles, including the organization of directories in the library, certain pre-install definitions, and all other data used in installing an initial software configuration onto each of the target computers 14. In one embodiment, each database record associates a unique part number with a particular type, model, and hardware configuration of a target computer 14. Each database record also identifies the corresponding directory in the library of software bundles, which contains the initial software configuration (i.e., pre-install) for the particular target computer 14 associated with that part number. Each database record further includes a pre-install definition, describing which software programs are included in the pre-install for the particular target computer. 14 and how the software programs will be configured on the target computer 14. The pre-install definition may include a list of the operating system, device driver(s), and/or software application(s) to be installed onto the target computer 14; instructions for partitioning and formatting the hard disk drive of the target computer 14; and settings for configuration of the operating environment of the target computer 14. In alternative embodiments, the pre-install definition may be stored in the library directory which contains the pre-install for the particular target computer 14, rather than in the database. In further alternative embodiments, each database record may include other information regarding the contents of the library of software bundles, such as other identification data associated with the hardware configuration of the target computer 14 (e.g., the model name and number of the target computer 14), characteristics of the software bundles (e.g., the order in which software programs must be installed because certain software programs may require other software programs to exist before they can be installed, dependencies among the software programs), or the like.

[0022] In the embodiment illustrated in FIG. 1, the installation system 10 further includes one or more target computers 14. Each target computer 14 includes memory (such as RAM, ROM, and a hard disk drive) and at least one processor. Each target computer 14 also includes an output device 22, such as a display 22. Each target computer 14 may further include an input device, such as a keyboard, a mouse, or the like, but such input device may be omitted. An initial software configuration, preferably including an operating system, one or more device drivers, and one or more software applications (e.g., a word processor, a spreadsheet, and the like), will be installed onto the memory of the target computer 14.

[0023] To install an initial software configuration or pre-install onto one or more of the target computers 14, a boot storage medium 16, preferably a removable floppy disk, is placed in each of the target computers 14. Each boot storage medium 16 includes instructions or logic for booting all of the different types and models of target computers 14. In other words, the same version of the boot storage medium 16 may be used for all of the target computers 14, regardless of the hardware configuration of the target computer 14 or the initial software configuration to be installed onto the target computer 14. Different versions of the boot storage media 16 for installing different initial software configurations (e.g., different operating systems, such as Windows® 95, Windows 98, Windows NT, OS/2) are not necessary.

[0024] FIGS. 3A-3C are flowcharts illustrating a method for automatically installing an initial software configuration onto a target computer in accordance with an embodiment of the present invention. At step S100, the boot storage medium 16 boots the target computer 14 using a series of batch files and program files. Once the target computer 14 is booted from the boot storage medium 16, the installation process is entirely automatic and requires no user interaction. In preferred embodiments, the boot storage medium 16 includes all of the necessary logic and other data for automatically installing an initial software configuration on the target computer 14.

[0025] At step S110, after the target computer 14 is initially booted, it is determined that the initial booting step has just been performed. During the installation process, the target computer 14 will be rebooted several times. Therefore, a process flag is stored on the memory of the target computer 14 for keeping track of the boot sequence and is used to determine which booting or rebooting step has just been performed. At step S115, the process flag is set to indicate that the initial booting step has been performed. In preferred embodiments, the process flag is stored by writing to the last sector of the hard disk drive of the target computer 14. In alternative embodiments, the process flag may be stored by writing to the boot storage medium 16. However, it is preferable to store the process flag on the memory of the target computer 14, rather than the boot storage medium 16, so that there is no risk of infecting the boot storage medium with any virus.

[0026] Next at step S120, the hardware configuration parameters in the CMOS of the target computer 14 are set. The CMOS parameters are first reset to their default values. The CMOS parameters are then set as required by the particular hardware configuration of the target computer 14. For example, a PCMIA slot may be set to card bus mode to support a particular network adapter installed in the target computer 14.

[0027] At step S125, the target computer 14 is rebooted for a first time. Next at steps S110 and S130, the stored process flag is used to determine that the rebooting for the first time step has just been performed. At step S135, the process flag is then set to indicate that the rebooting for the first time step has been performed. Next at step S140, the target computer attempts to establish a network connection with the installation server 18 through the LAN 12. At step S150, it is verified that such a network connection has been established. In preferred embodiments, identification data associated with the hardware configuration of the target computer 14 is then retrieved from the memory of the target computer 14 at step S160. In one embodiment, the unique part number which indicates the particular type, model, and hardware configuration of the target computer 14 is retrieved from the BIOS storage area of the target computer 14. However, in alternative embodiments, other identification data may be retrieved, such as the model name and number of the target computer 14, or the like.

[0028] After the identification data is retrieved, the database on the installation server 18 is checked to determine which directory in the library of software bundles stored on the memory of the installation server 18 contains the pre-install corresponding to the particular target computer 14 indicated by the retrieved identification data. At step S170, the directory is checked to verify that the files necessary for installing the initial software configuration onto the target computer 14 are stored in that directory on the memory of the installation server 18. If the necessary files are not stored on the memory of the installation server 18, the installation process prematurely terminates and an error message indicating that the installation process failed is displayed on the display 22 of the target computer at step S260.

[0029] Otherwise, if the necessary files are stored on the memory of the installation server 18, the hard disk drive of the target computer 14 is partitioned. In preferred embodiments, instructions for partitioning the hard disk drive of the target computer 14 are retrieved from the memory of the installation server 18. At step S175, all partitioning and formatting information is erased from the hard disk drive of the target computer. Then at step S180, the hard disk drive of the target computer 14 is partitioned in accordance with the instructions. In alternative embodiments, prior to partitioning the hard disk drive of the target computer 14, the size of the hard disk drive is determined because it will control which partitioning scheme or instructions to use in partitioning the hard disk drive. In further alternative embodiments, the drive letter assigned to the CD-ROM drive is determined before the hard disk drive is partitioned because it will affect the number of hard disk drive partitions.

[0030] Next at step S185, after the hard disk drive is partitioned, the target computer 14 is rebooted for a second time. At steps S110 and S130, the stored process flag is again used to determine that the rebooting for the second time step has just been performed. Next at step S200, the target computer attempts to establish a network connection with the installation server 18 through the LAN 12. At step S210, it is verified that such a network connection has been established. In preferred embodiments, instructions for formatting the hard disk drive of the target computer 14 are retrieved from the memory of the installation server 18. Then at step S215, the hard disk drive of the target computer 14 is formatted in accordance with the instructions.

[0031] At step S220, after the hard disk drive of the target computer 14 has been formatted, the software bundle for the initial software configuration (i.e., pre-install) is retrieved and transferred from the memory of the installation server 18 to the memory of the target computer 14 based on the retrieved identification data. In one embodiment, the software bundle is retrieved and transferred from the library directory on the memory of the installation server 18 which contains the pre-install corresponding to the particular target computer 14 indicated by the retrieved identification data (e.g., unique part number of the target computer 14). At step S225, the transferred software bundle is then installed onto the memory of the target computer 14, and the operating environment of the target computer 14 is configured as required by the software. In one embodiment, the software bundle is stored as one or more compressed disk image files which are transferred to the target computer 14. These compressed files are then decompressed or unzipped at the target computer 14 to install the software bundle onto the target computer 14 and configure the operating environment of the target computer 14.

[0032] The software bundle installed onto the target computer 14 may include device drivers. In one embodiment, peripheral devices associated with or installed in the target computer 14 (e.g., keyboard, mouse, display, modem, CD- or DVD-ROM drive, and the like) are detected, and the device drivers corresponding to such peripheral devices are installed onto the memory of the target computer 14.

[0033] The software bundle may also be configured in accordance with the hardware configuration of the target computer 14. In one embodiment, the initial software configuration or pre-install installed onto the target computer 14 corresponds to multiple target computers 14 which provide different screen resolutions. Accordingly, it is necessary to retrieve the screen resolution provided by the particular target computer 14 from the memory of the target computer 14, preferably the BIOS storage area, and to configure the installed software in accordance with such screen resolution.

[0034] In preferred embodiments, after the initial software configuration is installed onto the target computer 14, a virus scan of the hard disk drive is executed to ensure that no viruses are present. However, in alternative embodiments, the virus scan may be omitted. In preferred embodiments, the memory of the target computer 14 is then checked to ensure that the software was transferred and installed correctly onto the memory of the target computer 14. At step S230, it is determined whether or not the installation process was successful. If it was successful, a banner indicating that the installation process was successful is displayed on the display 22 of the target computer 14 at step S240. However, if it was not successful, an error message indicating that the installation process failed is displayed on the display 22 of the target computer 14 at step S260. In one embodiment, to determine whether or not the installation process was successful, all of the files on the hard disk drive of the target computer 14 are read, and a checksum is calculated. The calculated checksum is compared to a checksum stored on the boot storage medium 16 or on the memory of the installation server 18. If the checksums match, the installation process was successful; if the checksums do not match, the installation process failed.

[0035] During the installation process, if no network connection is established between the installation server 18 and the target computer 14 through the LAN 12, the CD-ROM drive of the target computer 14 is checked for a valid compact disk at steps S190 and S250. If such a compact disk is available, the installation process continues as described above, except that the software bundles are stored on and transferred from the local compact disk, instead of the memory of the installation server 18. If such a compact disk is not available, the installation process prematurely terminates, and an error message indicating that the installation process failed is displayed on the display 22 of the target computer 14 at step S260.

[0036] As described above, the boot storage medium 16 includes all of the necessary logic and other data for automatically installing an initial software configuration on the target computer 14. However, in alternative embodiments, the memory of the installation server 18 may include some of the necessary logic, which can either be executed from the installation server 18 through the LAN 12, or be transferred from the installation server 18 to the target computer 14 and then executed on the target computer 14.

[0037] FIG. 2 illustrates the operational environment for the installation method and the basic components of the installation system in accordance with an alternative embodiment of the present invention. In this embodiment, the installation system 50 includes one or more target computers 14 and corresponding boot storage media 16, as in the embodiment illustrated in FIG. 1. However, this installation system 50 does not include a communication link 12 or an installation server 18. Instead, the operating system and other software programs to be installed onto the target computer 14 are stored on a library storage medium 20blocal to the target computer 14. In one embodiment, the library storage medium 20bis a compact disk.

[0038] In preferred embodiments, the boot storage medium 16 includes all of the necessary logic and other data for automatically installing an initial software configuration on the target computer 14. However, in alternative embodiments, the library storage medium 20bmay include some of the necessary logic, including instructions for booting the target computer 14.

[0039] While the description above refers to particular embodiments of the present invention, it will be understood that many modifications may be made without departing from the spirit thereof. The accompanying claims are intended to cover such modifications as would fall within the true scope and spirit of the present invention.

[0040] The presently disclosed embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims, rather than the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.