GB2336009A

GB2336009A - System for partitioning and formatting computer memory

Info

Publication number: GB2336009A
Application number: GB9900730A
Authority: GB
Inventors: Alan E Beelitz
Original assignee: Dell USA LP
Current assignee: Dell USA LP
Priority date: 1998-01-23
Filing date: 1999-01-13
Publication date: 1999-10-06
Also published as: BR9803211A; JPH11212839A; SG77645A1; ITTO990025A1; KR19990066738A; FR2774786A1; IE980560A1; DE19900668A1; AU8089998A; TW386200B

Abstract

A computer (10 Figure 1) includes a processor (12) and the computer memory (16), which may be a hard disk. The processor is capable of running operating system code, receiving external directives, and accessing the hard disk. In operation, the processor runs a set of operating code for preparing the hard disk, which set includes; instructions for receiving an external directive, 110, from a directive file 110a, or as command line parameters 110b; instructions for determining 116 the characteristics, or configuration, of the hard disk; instructions for creating 120 a partition descriptor from the external directive and/or configuration; and instructions for preparing 122 the hard disk according to the partition descriptor. The characteristics of the disk may include the numbers of disks, heads, and tracks.

Description

2336009 SYSTEM AND METHOD FOR PREPA1UNG A COMPUTER MEMORY

The present disclosure relates generally to computers, and more specifically, to a system and method for partitioning and formatting one or more memory devices in the computer.

When one or more memory devices such as a hard disk are added to a computer system, the memory devices often require specific preparation. Such preparation may include, for example, simultaneously partitioning the hard disk into logical regions so that certain data or programs can be separately stored and formatting the hard disk to make it suitable for a particular operating system. One common situation occurs when a new computer that utilizes a Microsoft DOS or WINDOWS operating system, available from Microsoft Corporation of Redmond, WA, is being manufactured. During the manufacture, one or more hard disks must first be partitioned into one or more partitions, such as a primary partition, in which the computer's operating system anid other application program are stored, a utility partition, in which utility or maintenance-type program, and extended partitions. Similar situations occur when a new hard disk is being added to a computer system or an existing hard disk is being reformatted. For the remaining discussion, the term "preparation" includes both partitioning and appropriate formatting procedures.

Preparing one or more hard disks has many variables associated therewith, allowing a large number of potential configurations of the hard disk(s). These variables may be disk-determined, such as the size and number of hard disks, system-determined, such as supporting "suspend-to disk" operations with pre-reserved spaces or separated storage areas with utility partitions, andlor user-determined, such as a choice of operating systems or multiple partitions. The wide variety of possible configurations can be problematic for computer makers, especially for those who customize each computer for a particular user.

Typically, a person must oversee the process of preparing the one or more hard disks, making many choices based on the above-desciibed variables to produce an optimum configuration. However, it is desired to simplify andfor automate this function to better streamline this process.

In response thereto, provided is a system and method for preparing a computer memory. In one embodiment, the computer includes a processor and the computer memory, which may be a hard disk. The processor is capable of running operating system code, receiving external directives, and accessing the hard disk. In operation, the processor runs a set of operating code for preparing the hard disk. The code set includes instructions for receiving an external directive, instructions for determining a configuration of the hard disk, instructions for creating a partition descriptor from the external directive andfor configuration, and instructions for preparing the hard disk according to the partition descriptor.

In one embodiment, the external directive is received from a directive file, thereby providing instruction for directing the preparing process.

In another embodiment, the external directive is provided at a command line, thereby providing instruction for directing the preparing process.

The invention also covers a program product comprising a computer readable storage medium, instructions recorded on the medium for determining a confliguration a first hard disk, instructions recorded on the medium for receiving a first directive, instructions recorded on the medium for creating a partition descriptor according to the configuration and the directive and instructions recorded on the medium responsive for preparing the first hard disk using the partition descriptor.

A technical advantage achieved is that preparing the computer memory is simplified andlor automated, thus streamlining this process.

Another technical advantage achieved is that the directives can be modified to accommodate the specific configuration of the computer memory.

Another technical advantage achieved is that long series of directives can be placed in a single directive file, thereby simplifying the input thereof.

An example of the present invention will be described with reference to the accompanying drawings, in which:

Fig. 1 is a block diagram of a computer for implementing one embodiment.

Fig. 2 is a layout diagram of a hard disk of the computer of Fig. 1.

Fig. 3 is a flow chart of a routine to be run by the computer of Fig. 1 for preparing the hard disk of Fig. 2.

The following disclosure incorporates by reference the applicant's earlier British Application GB 9826110.0.

Referring to Fig. 1, the reference numeral 10 designates a computer having several components, including a processor 12, a bank of random access memories (RAM) 14a and read only memories (ROM) 14b, one or more hard disks represented by hard disk 16, and a network interface 18. Each component is capable of communication with the processor 12, as graphically represented by a general bus 20. In the present example, the computer 10 is a personal computer running Microsoft DOS and/or WINDOWS. It is understood, however, that the computer 10 and its illustrated components are merely representative of many different types of computers and components well known and understood by those of ordinary skill in the art.

Referring to Fig. 2, the hard disk 16 includes a master boot record 30, having boot strap code 32 and a master partition table 34. It is understood that the master boot record 30 includes conventional code, such as for booting up the computer 10, which is well known in the art. Associated with the hard disk 16 is a beginning 36 and an end 38, together representing the total memory capacity of each hard disk. Also associated with the hard disk 16 is a capability (not shown), such as whether the hard disk supports BIOS extensions or a particular required bus interface. There may also be additional hard disks (not shown) that have similar or different physical configurations.

Referring to Fig. 3, a method 100 is used to prepare the hard disk 16 of the computer 10. For the sake of example, the method 100 is performed by the processor 12 but may, in the alternative, be performed by another device, such as one connected through the network interface 18. Specific operation examples of the method 100 are also provided below.

At step 110, the processor 12 receives one or more directives. A directive provides guidance and instructions to the method 100 as to how the hard disk 16 should be prepared. The processor 12 may receive the directives by reading a directive file 110a. The directive file 110a is an ASCII text file that contains instructions for the method 100 in the form of a specialized scripting language. The directive file 110a may be provided, for example, through the network interface 18 or through the hard disk 16.

Alternatively, the processor 12 may receive the directives as command line parameters 110b. Cornmand line parameters are commands supplied to the method 100 when the method 100 is invoked.

These directives allow a tiser to specify essentially all aspects of hard disk preparation, including boot record filespecs (e.g., a natne of a file that will contain the master boot record 30, a 16-bit file allocation table CFAT1C partition boot record, andlor a FAT32 partition boot record), file system types (e.g., FAT16 andlor FAT32), partition sizes (e.g. number of megabytes), and so forth. Once the directives are prepared, no further user input is required.

At step 112, the processor 12 checks the received directives to determine if they are consistent. That is, the processor 12 cheeks the syntax of the directives and makes sure that no two directives are conflicting. If the directives are not consistent, at step 114 the processor 12 generates an error message.

At step 116, the processor 12 determines the characteristics of the hard disk 16. Continuing with the DOSIWINDOWS operating system example, the processor 12 may use BIOS calls and extensions to determine the characteristics of the hard disk 16, including such things as the number of actual disks (hard disk 16 represents one or more hard disks), the parameter of each disk, and the capability of each disk. The parameters of each disk may include a number of cylinders, number of heads, and number of tracks. The capability of each disk may include a level of BIOS support.

The processor 12 stores the physical configuration in the RAM 14a.

The method 100 operates sequentially through each disk represented by the hard disk 16. At step 118, the processor 12 determines if a "nexC disk is to be prepared. If so, at step 120 the processor 12 analyzes the characteristics of the disk and the received directives relating to the disk, to create one or more partition descriptors. The analysis can have default, or fall-back descriptors to accommodate preparation details not provided in the received descriptors or not possible with the received descriptors. Other impossibilities may be considered as an error and a user is so notified.

At step 122, the processor 12 prepares the hard disk 16 by processing the previously created partition descriptors. In particular, the processor 12 writes the master boot record 30 by providing the boot strap code 32 and preparing the master partition table 34 according to the partition descriptors created in step 120. The processor 12 also creates one or more partition boot records (not shown) with the appropriate file allocation tables.

Upon completion of step 122, or upon a negative determination at step 118, execution proceeds to step 124 where the processor 12 determines if another disk needs to be prepared. If so, execution returns to step 118 and the next disk is prepared. Otherwise, execution proceeds to step 126 and the processor 12 reports the final logical configuration of the hard disk 16.

For the sake of clarification, described below are several example operations that may be performed by the method 100. It is understood, however, that many different operations are anticipated, and therefore these examples are not intended to limit the claims in any manner.

Example 1 steps 110-112:

steps 116118:

step 120:

step 122:

A directive "prepare hard disk and reserve 32 megabytes" is received. There exists only one hard disk 16 having a capacity of 10 gigabytes. The capacity in the hard disk is sufficiently greater that the desired amount to reserve. A partition descriptor is created to accommodate the received directive. The master boot record 30 and partition boot record are written, reserving the 32 megabytes near the end 38 of the hard disk 16.

Example 2 steps 110-112:

steps 116-118:

step 120:

step 122:

step 118: step 120:

step 122:

Example 3 steps 110-112:

A directive "prepare hard disk and create a utility partition of ten megabytes on the second hard disk7 is received. There exists two hard disks. The first hard disk has a capacity of 2 gigabytes. The capacity in the first hard disk is above a predefined maximum limit for a primary partition. A partition descriptor is created to accommodate the received directive. The master boot record 30 and a boot record for the primary partition are created in the first hard disk. A boot record for an extended partition is also created, the extended partition using the remaining available capacity. A check is performed that the capacity of each partition is greater than a predefined minimum limit. The second hard disk has a capacity of 6 gigabytes. The capacity in the second hard disk is sufficiently greater that the desired amount needed for the utility partition. A partition descriptor is created to accommodate the received directive. The master boot record 30, a primary partition boot record, and a utility partition boot record are written to the second hard disk.

A directive "prepare hard disk using defaults" is received.

1 steps 116-118..

step 120:

step 122:

Example 4 steps 110-112:

steps 116-118:

step 120:

step 122:

There exists only one hard disk 16 having a capacity of 10 gigabytes. The capacity in the hard disk is above a predefined maximum limit for a primary partition. A partition descriptor is created to accommodate the received directive. The master boot record 30 and a boot record for the primary partition are created. A boot record for an extended partition is also created, the extended partition using the remaining available capacity. A cheek is performed that the capacity of each partition is greater than a predefined minimum limit.

A directive "prepare hard disk and don't create an extended partition" is received. There exists one hard disk 16 with a capacity of 2.1 gigabytesSince no additional partition is requested, a single 2.0 gigabyte primary partition will be created. A partition descriptor is created to accommodate the received directive. The master boot record 30 and a boot record for the primary partition are created. The remaining 100 megabytes is left unformatted.

r Example 5 steps 110-112:

steps 116-118:

step 120:

step 122:

Example 6 steps 110-112:

steps 116-118:

step 120:

step 122:

A directive "prepare hard disk and create an extended partition" is received. There exLsts one hard disk 16 with a capacity of 2.1 gigabytes. Since an extended partition is requested, and a minimum partition size is 500 megabytes, a 1.6 gigabyte primary partition will be created and a 500 megabyte extended partition will be created. A partition descriptor is created to accommodate the received directive. The master boot record 30 and two additional boot records are created: one for the primary partition and one for the extended partition.

Two directives: "setup disk as a network server" and "create a 1.6 gigabyte primary partitiod are recei.ed. There exists one hard disk 16 with a capacity of 2.0 gigabytes. Since a network server needs at least one 500 megabyte extended partition, there is not enough disk space to accommodate both directives. The 1.6 gigabyte primary partition is reduced to 1.5 gigabytes. A partition descriptor is created to accommodate the received directive. The master boot record 30 and two additional boot records are created: one for the primary partition and one for the extended partition. The modification is reported.

-g- Example 7 steps 110-112:

A directive "prepare hard disk with a FAT32 partition" is received. There exists one hard disk 16 with a capacity of 1.8 gigabytes. Since a FAT32 partition needs at least 2.0 gigabytes, there is not enough disk space to accommodate both directives. The primary partition is reduced to a 1.8 gigabyte FAT16 partition. A partition descriptor is created to accommodate the received directive. The master boot record 30 and a boot record for the FAT16 primary partition are created.

steps 116-118:

step 120:

step 122:

Although illustrative embodiments have been shown and described, a latitude of modification, change and substitution is intended in the is foregoing disclosure, and in certain instances, some features will be employed without a corresponding use of other features. Furthermore, additional features, such as error handling routines, may be added to the illustrative embodiment without altering the scope of the embodiment. Accordingly, it is appropriate that the appended claims be construed broadly.

Claims

1.

A computer comprising: at least one processor capable of running operating code and receiving external directives; at least one storage accessible by the processor; a set of operating code for preparing the at least one storage; wherein the set includes instructions for determining a configuration of the at least one storage, for receiving at least one external directive, and for preparing the at least one storage in response to the directive.

2. The computer of Claim 1, wherein the at least one directive is received from a file including an additional directive.

3. The computer of Claim 1, wherein the processor receives the at least one directive through a command line.

4. The computer of Claim 1, further comprising a network connection and wherein the at least one directive is received through the network connection.

5. The computer of Claim 1, further comprising a floppy disk and wherein the at least one directive is received through the floppy disk.

6. The computer of any one of the preceding claims wherein the at least one directive defines a partitioning configuration of the at least one storage.

7.

comprising the steps of..

A method for preparing a storage device in a computer, the method receiving a plurality of directives; determining a configuration of the storage device; - 1 1 - comparing the directive with the configuration; and if the comparison of the configuration and directives so allows, creating partition descriptors in response to the directives; and preparing the storage device according to the partition descriptors.

The method of Claim 7, further comprising: if the comparison of the configuration and directives does not allow, 10 creating the partition descriptors in response to the configuration.

8.

9. The method according to Claim 8, in which the method is repeated for a second or further directives and a second or further storage devices.

10. The method of any one of Claims 7 to 9, wherein the directives are received from a file.

11. The method of any one of Claims 7 to 9, wherein the directives are received from an operating system command line.

12. The method of any one of Claims 7 to 9, wherein the computer includes a network connection and wherein the directives are received through the network connection.

13.

The method of any one of Claims 7 to 9, wherein the computer includes a floppy disk and wherein the directives are received through the floppy disk.

14. The method of any one of Claims 7 to 13, wherein the directives 30 define a partitioning configuration of the storage device.

15. An apparatus for preparing a storage device substantially as shown in or as described with respect to any of the accompanying drawings.

16. A method for preparing a storage device substantially as described with respect to the accompanying drawings.