JP2003508845A - Computer operating system remote installation method and apparatus - Google Patents

Abstract

  (57) [Summary] The invention includes a method of installing a computer operating system on a computer from a network and configuring the computer for use on that network or another network. The installation routine runs and accepts the built location and the delivery location and queries the environment database at the built location and the delivery location to obtain one or more built-in variables and one or more delivery-specific variables. The installation routine further determines the computer type and installed hardware components, accesses the network using built-in variables, and copies the master installation script from an operating system installation source stored on that network. Further, the installation routine modifies the copied installation script based on the built-in variables and the delivery-specific variables, the detected computer type, and the hardware components, and generates a dedicated installation script. The computer operating system is then automatically installed using this dedicated installation script. The installation process further includes the step of registering the computer with the network in which it will be used, so that it is ready for immediate use at the delivery location.

Description

Detailed Description of the Invention

TECHNICAL FIELD OF THE INVENTION The present invention relates to the remote installation of computer operating systems on networked computers.

[0002] To connect computers to each other by the cable connected to the background network of the present invention has become common in business organizations. As a result, resources such as printers and files can be shared, and functional equipment such as electronic mail, the Internet, and an intranet can be used. The network may be a local area network (LAN), where computer workstations in one physical location, eg a building, are connected to each other and to computers acting as network servers. Network servers typically control security access to the network and regulate resource sharing. One L
There may be more than one network server in the AN, eg, there may be a server for each floor on each floor of the building.

With the advent of inexpensive and high performance communications, it has become possible to connect individual LANs together to form a wide area network (WAN). This interconnection is
It allows large-scale resource sharing and becomes the basis of the Internet. Large organizations can use this technology to form their own intranets, which enables stable organization wide e-mail and file sharing.

In large LANs or WANs with hundreds or thousands of computer workstations and many servers, administration and management of individual computer workstations can be a daunting task. Manual installation on each computer workstation is a labor-intensive and time-consuming task, often taking several hours to complete. During the installation and configuration of a computer operating system, the installer must select the settings, software components to be installed that are compatible with the machine, a wide range of organizational policies, LAN requirements, and end user requirements. What this means is that the configuration of the computers across the WAN is very different and the same LAN
Even the settings of the computer across can be different. Each system administrator must be familiar with different settings for any LAN or WAN they can support. Each setting causes its own support issues and potential conflicts with policies. In response to this,
Many organizations now have broad organizational policies that define software and hardware settings on their respective computer workstations, which seek to create standardized settings to mitigate these support issues.

Currently, computer operating systems can be installed on specific computer workstations from a data store on the network. This can be done with a pre-written script that initiates the installation and configuration options that facilitate automatic installation. However, these scripts are typically only used for standardized installation of operating systems from a LAN with one server.

As mentioned above, in many organizations there is no “standard” computer setting. One user, a set of users, may need to set up a computer with video conferencing capabilities, and another user may need to set up a light weight computer to work outside the office. On the other hand, clerical staff may only need basic computer settings to access network resources. It may be possible to supply a "standard" computer setup and add the necessary hardware components to satisfy the user. However, computer components are almost obsolete as soon as they are released, and operating systems usually do not have the software to support the newest hardware. Therefore, supporting automatic installation of operating systems for various types of computer configurations is highly questionable. In fact, many new computer hardware components are not directly supported by current operating systems. Additional support software provided by the computer component manufacturer must be installed during the installation of the operating system in order for the hardware to operate properly.

[0007] According to a first aspect of the Summary of the Invention The present invention, a method of installing a computer operating system is provided, comprising the following steps. That is, the computer runs an installation routine that accepts user input that defines the delivery location and that detects the computer type. Connect the computer to the operating system installation source contained on the remote computer. Obtain a copy of the master installation script contained on the remote computer. Modify the copied master installation script based on a number of variables associated with delivery location and computer type. Subsequently, a dedicated installation script is used to automatically install the computer operating system.

[0008] Preferably, the installation routine operates to obtain additional software associated with the computer type and then install that software using a dedicated installation script.

[0009] Preferably, the installation routine detects the hardware components of the computer, obtains additional software associated with the hardware components to supplement the computer operating system from the remote computer, and then using a dedicated installation script. Works like installing software.

[0010] Preferably, the installation routine operates to detect the computer type and hardware components of the computer by evaluating the computer's BIOS set. Preferably, the installation routine evaluates the computer's BIOS set by comparing it to the well-known BIOS set. The storage device houses a database containing a well-known BIOS set, each of which is associated with one or more hardware variables, which allow the hardware variables to modify the master installation script. Used. Hardware variables are used to modify the master installation script, thereby adding additional software for undetectable hardware components known to be on a computer that has a certain type or hardware component. To install. Hardware variables are used to modify the master installation script, thereby changing the programmable set of computers or hardware components.

To assist system administrators and computer workstations that must be in the physical location where the computer workstation is used, the operating system can be used by the equipment supplier's premises or other such centralized IT / support center. It is desirable to be able to be installed and configured at The installation is preferably capable of being performed in different languages and without a network connection to a LAN or server where computer workstations are used. Further, the computer installed and configured at the first location for use at the second location is as accurate as the computer installed and configured at the third location for use at the second location. It is more desirable to set to.

Computer types and settings are automatically configured to satisfy installations on various computer settings, and also to automate the installation of operating systems that support hardware that obsoletes operating system releases. It would be highly desirable if appropriate additional software could be detected and installed to supplement the operating system.

The present invention provides an installation procedure in which the installation and configuration of each workstation is standardized and repeatable. The present invention further provides an installation procedure, in which the installation process is in principle automated, thereby reducing the amount of time the installer has to spend on each machine and preparing it for delivery. Provided machine. Further, the present invention provides an installation method and system, wherein the computer operating system is a second
May be installed and configured at the first location for use at the second location, the second location not necessarily the same LA as the first location.
It does not have to be in N or WAN. Most advantageously, the present invention provides an installation procedure, which is adaptable to select additional software needed to support non-standard settings without instructing the user. .

Preferably, the installation routine operates to obtain the computer operating system, along with any additional software, from the remote computer and then disconnect the computer from the remote computer. Here, the computer is then rebooted and the computer operating system is installed using a dedicated installation script.
The installation routine may also accept user input defining a built location corresponding to the location of the remote computer. The remote computer contains the operating system.

The data connection to the remote computer may be made via the Internet.

Preferably, the storage device is a computer disk. However, it may be any readable medium capable of storing the aforementioned instructions.

According to a second aspect of the invention, there is provided a system for installing a computer operating system, which is a computer; a network to which the computer is connected; an operating system installation source and additional software, a master installation script. A remote computer containing a file, connected to a network; containing a set of computer executable instructions and a number of files for executing an installation routine according to the first aspect of the invention when running on a computer. A storage device for

According to a third aspect of the invention, there is provided a machine readable program storage device for encoding program instructions and a number of files for performing the method of the first aspect of the invention. There is.

[0019]   Preferably the machine is a general purpose computer.

The installation routine is started by running a computer program contained in the storage device. Preferably, the storage device is a computer disc that is inserted into the drive of the computer. The computer may connect to a remote computer via the internet. Additional software may be placed on the remote computer in a different source to that.

The typical arrangement of the computer hardware used in the remote installation of such a computer operating system in the detailed description the present invention is shown in FIG. The network 10 includes a network server 12 and a network data store 14.
And are connected to the network interface device 16. The network interface device 16 is connected to a computer workstation 18 having a random access disk memory 20. Because it is a brand new machine, random access disk memory 20 does not include a computer operating system.

In the present invention, a 32-inch disk or other suitable storage device 22 is used to boot the computer workstation 18. During boot, the installation program contained in computer storage device 22 runs on computer workstation 18. As described in more detail below, when a software controlled installation routine is running, the installer will identify the specific network interface device 16 and build it with a built-in location code, delivery location code, computer workstation 18 You will be prompted to enter a unique identifier for.
Subsequently, the installation routine detects the computer type of computer workstation 18 and its added hardware components. The use of data input by the installer enables the installation routine to connect the computer workstation 18 to the network 10 via the network interface device 16. The installation routine then automatically installs the appropriate computer operating system in random access disk memory 20 of computer workstation 18 from a remote computer operating system installation source contained in network data store 14. As detailed below, the installation routine is adapted to configure the computer operating system based on the delivery location code, the detected computer type, and the hardware component. The built location code indicates where the built process should be performed, while the delivery location code indicates where the built computer workstation should be installed.

An overview of the installation routine will be discussed with reference to the flowchart of FIG.
Inserting the installation disc and switching on the computer workstation, as shown in FIG. 2, prompts the installer at step 100 to enter the build location code and the delivery location code. The environment database of look-up tables stored on the install disk is then made responsive to the built location code and the delivery location code (step 102) to obtain the built location specific variables and the delivery location specific variables, which are step 104. Stored by computer workstation. The installer is further prompted to enter a unique identifier for the computer workstation (step 106).
. The installation routine then scans the computer workstation's BIOS settings at step 107 and installs on the computer workstation, including computer type (including manufacturer and model), and, for example, a PC.
Determine the hardware components such as I-bus. The detected computer type and hardware components are cross-referenced with additional look-up tables contained on the installation disk to determine computer workstation variables in step 107a. Using the built-location specific variables, the installation routine connects the computer workstation to the network at step 108 and accesses the installation account on the server. The master installation script, which is included in the computer operating system installation source of the network data store, is stored in the random access disk memory of the computer workstation in step 110.
Copied in. The copy of the install script is then modified based on the built location and delivery location specific variables, computer workstation variables (step 112) to generate a dedicated install script. The computer operating system is then installed and configured using the operating system installation source setup routine with a dedicated installation script.

The installation and configuration step 114 of FIG. 2 extends to the flowchart of FIG. As shown, the computer operating system installation source is step 20 from the network data store to a random access disk memory (eg, hard disk) of the computer workstation.
Copied at 0. The additional software required by the detected computer type or detected hardware component, such as that defined by computer workstation variables, is copied in step 201 from the network data store. The setup routine then disconnects from the network and restarts the computer workstation in step 202. After restarting the computer workstation, the setup routine installs the computer operating system using a dedicated installation script (step 204). Additional software is then installed in step 205 to supplement the computer operating system. The computer operating system is then configured at step 206 based on the dedicated installation script. Any additional software components identified in the installation script, such as e-mail or office application suits, are now installed from the network data store (step 20).
8). The setup routine further cleans random access disk memory of the computer workstation in step 210 by deleting any unnecessary files. Once the computer workstation has a complete computer operating system prepared for use at the delivery location, the setup routine ends.

FIG. 4 includes the computer hardware arrangement of FIG. 1 and further includes a network 30 and a network server 32 to which the computer workstation 18 is about to be connected. The network 10 is part of the same LAN as the network 30, which is the same W as the network 30 connected by the communication system.
It is part of the AN, ie there is no network connection to the network 30. If a computer workstation 18 is about to be used, the network 1
If there is a connection between 0 and the network 30, then the installation routine registers the computer workstation 18 with the unique identifier in the networks 30 and 32 in which the computer workstation 18 is used. If there is no connection to the network 30 where the computer workstation 18 is to be used, the computer first (fir
st) When started at the delivery location, the registration runs again.

A more detailed embodiment of the invention is described with reference to FIGS. 4 and 5. In this embodiment, the network 10 is an Ethernet network, Mi
crosoft Windows (registered trademark) NT Server operating system V.4 is provided with the network server 12, 32, and the computer operating system installation source is Microsoft Windows NT workstation. The computer storage device 22 includes an MS-DOS v.6.22 operating system kernel, files necessary to boot the computer workstation 18, installation routines, an environment database, a TCP / IP network driver for each selectable network interface device 16, M housing and
It is an S-DOS format disc. Computer workstation 18
Has a Hewlett-Packard Vectra XM / 4 with 32MB of random access memory
5/166 Personal Computer. The random access disk memory 20 of the computer workstation is a 1.2 GB hard disk drive. The network interface device 16 is a computer workstation 1.
3COM Etherlink 2 3C503 / 16 Ethernet network card installed in 8.

The computer workstation 18 is booted with the computer storage device 22 inserted into the computer's disk drive, the operating system kernel of the computer storage device 22 takes control of the boot routine, and gives the user MS-DOS v.6.22 startup. Step 3 using the menu function to select the network interface device 16 to use from the list of supported network interface devices.
Promote at 00. The TCP / IP network driver corresponding to the network interface device selected from the list is copied to the default filename (step 302) and the installation routine recognizes the type specific to any supported network interface device. Access without. The boot routine then runs the install routine at step 304. The installation routine accepts a built-in location code input (step 305) and a delivery location code input (step 306). The built location code and the delivery location code are cross-referenced in the list of acceptable locations in each step 307, 308, and if the location is not in the list, the list of acceptable locations is in each step 305, 306. Displayed and the installer is prompted to re-enter the code at each step 305, 306. If six incorrect attempts have been made in entering an acceptable location, the installation routine will exit with each step 309a.
, 310a report the error. After entering a valid built location code and a valid delivery location code, the installation routine will
Accepts the input of a unique identifier for a computer workstation that will be used later as a DNS address (step 311). The installation routine
In step 312, the environment database including the built location code and the delivery location code is queried to obtain the built location specific variable and the delivery location specific variable. These variables are associated with the environment and network specific settings for the two locations, as can be seen from Table 1.

[0028]

[Table 1] The built-location specific variables “server” and “share” define the server and network data store that contains the computer operating system installation source. If the built-in location UK is entered, for example, the computer operating system installation source is installed from ID4 of the UK_ID4 server.

Once the build and delivery locations have been set, the installation routine is the computer workstation's BIOS (basic input / output system).
Is accessed in step 312a. This BIOS contains the data in the hardware of the computer workstation (manufacturer, model, memory, hard disk capacity, advanced power management support and settings, etc. such as MPEG, USB, Firewire, parallel and serial interfaces). Other hardware components). An example of data contained in the BIOS of a computer workstation is shown below.

[0030]

[Table 2] The installation routine writes the contents of the BIOS of the computer workstation to the BIOS setting table stored in the installation disk and step 31.
Cross-reference in 2b. The BIOS setting table stores the BIOS code. The BIOS code can be found in the BIOS of each computer workstation from a particular manufacturer, such as the "Hewlett-Packard" identifier in the example above. A subset of entries is stored in a table for each manufacturer that identifies the BIOS code. The BIOS code can be found in each particular computer workstation model supplied by the manufacturer, such as "HP.Kayak.PC.Workstation XA 6/266" in the example above. A unique station type code is stored in a table for each computer workstation model supplied by the manufacturer. The unique station type code is determined by cross referencing the contents of the BIOS with the entries in the table.

The BIOS also contains data on other hardware components such as PCI cards and USB devices that are tied to the bus of a computer workstation. PCI by computer work station BIOS
An example of the data contained on a component is shown below.

[0032]

[Table 3] The BIOS configuration table also contains an entry for each supported component and cross-references each component with a unique component code. Each entry in the BIOS of the computer workstation is cross-referenced with an entry in the BIOS configuration table,
Determine the unique component code.

Using the built-location and delivery-location-specific variables in combination with the TCP / IP driver and its unique identifier, the installation routine logs the computer workstation to the network at step 313. The IP address for that computer is obtained from the server using DHCP (Dynamic Host Configuration Protocol) and the unique identifier is used as the DNS address. The master installation script stored in the network data store along with the computer operating system software source is copied to random access disk memory (step 314). An example of a master install script is shown below.

[Unattended] OemPreinstall = yes OemSkipEula = yes NoWaitAfterTextMode = 1 NoWaitAfterGUIMode = 1 FileSystem = ExtendOEMPartition = 1, nowait ConfirmHardware = no NtUpgrade = no Win31Upgrade = no TargetPath = WINNT OverwriteOemFilesOnUpgrade = no KeyboardLayout = [GUIUnattone] ] Banner = "Glaxo Wellcome, GIS ID4 v3.0 Installation. * Wwindows NT v4.0 Wo
rkstation "Background = gis.bmp [UserData] FullName =" Glaxo Wellcome "OrgName =" Glaxo Wellcome "ComputerName = [Display] ConfigureAtLogon = 0 BitsPerPel = 8 XResolution = 800 YRresolution = 600 VRefresh = 60 AutoConfirm = 1 [Network] InstallProtocols = Glaxo_Protocol_List InstallInternetServer = Glaxo_Internet_List JoinDomain = CreateComputerAccount = [Glaxo_Protocol_List] TC = TCPIP_Parameters [TCPIP_Parameters] MCP = Yes [Glaxo_Internet_List] InstallNETSTP = 0 InstallMOSAIC = 0

The install routine then modifies the copied script based on the built location and delivery location specific variables (step 31.
5) Generate a dedicated installation script. In the above example, the script fields shown in bold are edited by inserting delivery location specific variables and the field names correspond to the row headers of Table 1. The unique identifier is entered as the computer name.

The entry in the dedicated installation script is created including the workstation type code and each component code. These are later used during unattended installations to obtain and install additional operating system components needed to best support the workstation type and installed components.

The computer operating system installation source is then copied from the network data store to a random access disk memory (such as a hard disk) of the computer workstation. Computer workstation variables are used to select additional software, copied from the network data store, required by the detected computer type or detected hardware component.

The installation routine then proceeds to step 316 and accepts input selecting additional software to be installed. The additional software may include drivers for accessing other network protocols, office application suites, email client software. The installation routine ends by running the Windows NT setup routine contained in the computer operating system source in the network store. The Windows NT setup routine is run at step 317 in unattended installation mode with a dedicated installation script to provide answers to the questions normally asked during manual setup. The setup routine proceeds essentially as described in FIG.

Once the operating system is roughly installed, the dedicated installation script then runs the installation routine for additional software. In addition to the hardware drivers needed to supplement the operating system to support a particular hardware component, the additional software may also include the following software: The software is supplied by computer manufacturers specially adapted for computer workstation types such as power management software, help files, maintenance software for specific computer workstation models.

Windows NT does the following: Each computer workstation has its own DNS (Domain Name Service) address, which is registered in the network domain in which the computer workstation is used. It With reference to the embodiment of FIG. 5, the setting step 206 of FIG. 3 is extended to the flowchart of FIG. Prior to the end of the setup routine, the routine reconnects the computer workstation to the network 10 using the newly installed computer operating system (step 412) to bring the computer workstation to the intended network. An attempt is made to connect (step 414). If this is successful, the unique identifier for that computer is registered as the DNS address of the computer workstation, the Windows NT network domain, and the server the computer workstation is to be used in step 416. The computer workstation then disconnects from the network (step 418) and is prepared for delivery to the location where it is to be used. If the attempt is unsuccessful, the installation will fail.

Outside organisat to supply and configure the workstation
Where the ion is contracted, it is not possible to connect to the network where the computer workstation is to be used. To overcome this, a remote built site code associated with the external configuration-specific network is used for the built location code (REM in Table 1). Figure 5
In step 315 of step 315, when the copied script is modified, the location-specific variables associated with the remote built-site code are used for both built-location and delivery-location-specific variables.
The entered delivery location code is stored for later use. When an attempt is made to connect a computer workstation to a network domain or to a server on which the computer workstation is to be used (step 414), the connection is actually a remote build that can terminate the setup routine. Made to the site network. When the computer workstation is delivered to the delivery location by an external configuration, the computer operating system settings are updated based on the stored delivery location code. The unique identifier of the computer workstation is then registered at the delivery location, in the Windows NT network domain, and at the server where the computer workstation is to be used, in accordance with steps 414-418 of FIG. 6 described above.

In the above embodiment, the network interface device type of the computer workstation is input by the installer, but automatically detecting the network interface device from the BIOS in the same way as for other hardware components. Is possible with new PCI type devices.

In addition to installing operating system supplements and hardware components and software necessary to support a particular computer workstation type, once they are identified based on the BIOS, the BIOS Further software changes can be made based on the settings of or for hardware components.
For example, the BIOS software itself may be outdated and may not support the Year 2000 problem. Since the BIOS software version is stored in the BIOS, this is detected and the BIOS software is consequently updated or patched.

Furthermore, the default settings of some hardware components are known to conflict with others (such as network interface devices and modems) by trying to use the same address or interrupt. . The installation routine can be set to identify these conflicts and resolve them. Knowledge of what standard hardware components a type of computer workstation has, and / or
Rely on the knowledge to detect hardware components from the BIOS.

Furthermore, most modems typically cannot be detected, but the installation routines have the knowledge that some computer workstation types have modems by default, and the operating system and additional software can And with the knowledge that software for access to e-mail, remote access, etc. must be installed and configured to satisfy this.

The additional software is typically expected to reside with the operating system source on a remote computer, but instead of a different source on the same network or on a network as accessible as possible via the Internet or an Intranet. May be placed in.

While the above description has been concerned with specific computers and hardware types,
It will be apparent to the reader that the present invention is applicable to any PC-compatible computer system based on, for example, Intel Chip Architecture or AMD PC Chip Architecture.

[Brief description of drawings]

FIG. 1 is a schematic diagram of a typical computer hardware arrangement used for remote installation of a computer operating system according to the present invention.

FIG. 2 is a flow chart outlining a typical installation routine in accordance with the present invention.

FIG. 3 is a flow chart that extends certain steps of the installation routine described in FIG.

FIG. 4 is an expanded schematic diagram of the hardware arrangement shown in FIG. 2, including an end-use network in which workstations are to be used.

FIG. 5 is a flowchart showing a more detailed example of an installation routine according to the present invention.

FIG. 6 is a flowchart expanding the specific steps of the installation routine described in FIG.

[Procedure amendment]

[Submission date] April 16, 2002 (2002.16)

[Procedure Amendment 1]

[Document name to be amended] Statement

[Name of item to be amended] Claims

[Correction method] Change

[Contents of correction]

[Claims]

─────────────────────────────────────────────────── ─── Continued front page    (81) Designated countries EP (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, I T, LU, MC, NL, PT, SE), OA (BF, BJ , CF, CG, CI, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG), AP (GH, GM, K E, LS, MW, MZ, SD, SL, SZ, TZ, UG , ZW), EA (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), AE, AG, AL, AM, AT, AU, AZ, BA, BB, BG, BR, BY, BZ, C A, CH, CN, CR, CU, CZ, DE, DK, DM , DZ, EE, ES, FI, GB, GD, GE, GH, GM, HR, HU, ID, IL, IN, IS, JP, K E, KG, KP, KR, KZ, LC, LK, LR, LS , LT, LU, LV, MA, MD, MG, MK, MN, MW, MX, MZ, NO, NZ, PL, PT, RO, R U, SD, SE, SG, SI, SK, SL, TJ, TM , TR, TT, TZ, UA, UG, US, UZ, VN, YU, ZA, ZW (72) Inventor Steven, Blair, Kinrou             Lisa, North Carolina, United States             Reach, triangle, park, pee. Oh             -. Box, 13398, Five, Moore,             Drive, inside the GlaxoSmithKline (72) Inventor Andrew, David, Patterson             Cumbria, Alberton, UK,             North, Lonsdale, Road, Glaxo             Within Smith Kline (72) Inventor Daniel, James, Pratt             Lisa, North Carolina, United States             Reach, triangle, park, pee. Oh             -. Box, 13398, Five, Moore,             Drive, inside the GlaxoSmithKline (72) Inventor Thomas, Dwayne, Powell             Lisa, North Carolina, United States             Reach, triangle, park, pee. Oh             -. Box, 13398, Five, Moore,             Drive, inside the GlaxoSmithKline F term (reference) 5B076 AA04 AB07 AB10 AB20 BB06                       BB17

Claims (19)

[Claims] 1. A method of installing a computer operating system, the method comprising executing an installation routine configured on a computer to accept user input defining a delivery location and to detect a computer type, the remote computer. Connect the computer to an operating system installation source as housed in the computer, take a copy of the master installation script as housed in the remote computer, and copy the master installation script to the delivery location and the computer. Modifying based on at least one variable associated with the type to generate a dedicated installation script, A method for automatically installing the computer operating system using an application script. 2. The installation routine is configured to read software associated with the computer type from a remote source, and further installs the software associated with the computer type according to the dedicated installation script. The method of claim 1, further comprising installing. 3. The installation routine is configured to detect a hardware component of the computer, further load software associated with the hardware component, and supplement the computer operating system from a remote source. The method of claim 1, wherein the software is installed according to the dedicated installation script. 4.   The method of claim 2, wherein the remote source is a remote computer. 5. The method of claim 2, wherein the remote source is configured to be accessible by the internet. 6. The method of claim 3, wherein the installation routine is configured to detect the hardware component of the computer by evaluating at least one of the computer's BIOS set. 7. The method of claim 1, wherein the installation routine is configured to detect the computer type by evaluating a BIOS set on the computer. 8. The method of claim 6, wherein the installation routine is configured to evaluate at least one of the computer's BIOS set by comparing it to at least one reference BIOS set. 9. A storage device is configured to store a database containing the reference BIOS set, wherein at least one of the individual BIOS sets is associated with at least one of the hardware variables, 9. The method of claim 8, wherein at least one of the hardware variables is configured to modify the master installation script. 10. The method of claim 9, wherein at least one of the hardware variables is configured to modify the master installation script, and further installs software for undetectable hardware components. 11. The at least one of the hardware variables is configured to modify the master installation script, and further modifies at least one of the programmable set of the computer or hardware components. 10 ways. 12. The method of claim 1, wherein the remote computer is configured to be connected to a network. 13. The method of claim 12, wherein the installation routine is initiated by running a computer program stored on a storage device. 14. The method of claim 13, wherein the storage device is a computer disk configured to be inserted into a drive of the computer. 15. The method of claim 1, wherein the computer is connected to the remote computer by the Internet. 16. A computer, a network configured to connect to the computer, and a remote computer configured to connect to the network, the operating system installation source, software, a master installation script file. And a storage device configured to store a set of computer-executable instructions and at least one file for executing an installation routine. 17.   The apparatus of claim 16, wherein the storage device is a computer disk. 18. A computer-implemented article manufacturer for installing a computer operating system, the manifest being computer-executable instructions contained in a computer-readable medium, at a computer, a delivery location. Executing an installation routine configured to accept user input defining a computer and to detect a computer type, connecting the computer to an operating system installation source as contained in a remote computer; Obtain a copy of the master installation script as it will be housed in the computer, and copy the master installation script to the delivery Modifying based on location and at least one variable associated with the computer type, generating a dedicated installation script, and automatically installing the computer operating system with the dedicated installation script; Manufacture including possible instructions. 19.   The manufacture of claim 18, wherein the machine is a general purpose computer.