Providing disk layout information to an operating system for booting after disk repartitioning

[0002] This invention relates in general to operating system registries, such as the registry provided in the Windows NT® operating system from Microsoft Corporation of Redmond, Wash. More specifically, this invention relates to devices and methods for manipulating an operating system registry to maintain coherency between the registry and disk partitions.

[0003] “Partitioning” refers to a process by which a computer storage device, such as a hard disk, is divided into multiple logical devices. For example, a computer user wishing to run both the Windows NT® and Linux® operating systems from a single hard disk might partition the disk into two logical devices—one for running Windows NT®, and the other for running Linux®.

[0004] The assignee of this invention, PowerQuest Corporation, has developed partitioning software (referred to as “PartitionMagic®”) to assist computer users in the partitioning process described above. Various implementations of this software are described in detail in U.S. Pat. Nos. 5,675,769 and 5,706,472 to Ruff et al., and U.S. Pat. No. 5,930,831 to Marsh et al.

[0005] When running as a Win32 program (i.e., a 32-bit Windowse program) under the Windows NT® operating system, PartitionMagic® can only operate on partitions that have no open files. Since the Windows NT® operating system always has at least some open files running from its own partition, PartitionMagic® cannot operate on the Windows NT® partition when it runs as a Win32 program.

[0006] Accordingly, PartitionMagic® has been designed to also run in the Windows NT® boot mode, where it can operate on all partitions, including the Windows NT® partition. In this mode, the Windows NT® kernel loads first. The kernel then loads any device drivers. A portion of the kernel referred to as the “Session Manager” then executes any programs that require hard disk access before the Windowse user interface is loaded. In addition to PartitionMagic®, such programs include ‘autochk.exe’ (a utility for checking the condition of the hard disk) and ‘autoconv.exe’ (a utility for performing file system conversions), both from Microsoft® Corporation, and ‘autofat.exe’ and ‘autontfs.exe’ (utilities for file defragmentation), both from Executive Software, Inc. Once these programs have executed, the Session Manager generally loads the Windows® user interface to initiate the Windows NT® Win32 mode, although PartitionMagic® reboots instead.

[0007] PartitionMagic® reboots after executing in the Windows NT® boot mode because it typically manipulates the Windows NT® partition itself If PartitionMagic® did not reboot after execution in boot mode, Windows NT® would likely crash when it attempted to load the Windows® user interface from the Windows NT® partition, because it wouldn't be able to find the interface on the newly partitioned hard drive.

[0008] Windows NT® stores disk layout information (e.g., drive letter assignments and information regarding multiple partition volumes, such as stripe sets) in the Windows NT® registry under a key named “HKEY_LOCAL_MACHINE\SYSTEM\DISK\Information”. Changes can be made to this key by PartitionMagic® during the Windows NT® boot mode by making calls to the Windows NT® Registry API (Application Programming Interface). Unfortunately, these changes are discarded before taking effect when PartitionMagic® reboots instead of loading the Windows® user interface.

[0009] While PartitionMagic® typically needs to reboot after executing in the Windows NT® boot mode, it also needs to be able to manipulate the disk layout information key referred to above so that the disk layout information contained in the key is consistent with the information stored in partition tables on the hard disk being partitioned. If the information in the key and the information in the partition tables is not consistent, then Windows NT® makes default drive letter assignments that may not match the user's wishes and needs.

[0010] Accordingly, since the changes to the disk layout information key referred to above are discarded when PartitionMagic® reboots, there is a need in the art for an alternative means and method for manipulating a registry (e.g., the disk layout information key) so, for example, it conforms to the information in the partition tables on a hard disk being partitioned. Such a means and method should be effective despite a reboot.

[0011] In accordance with this invention, data stored in an operating system configuration settings repository (e.g., a Windows registry) that includes one or more repository files is modified by accessing operating system services associated with the repository in a user interface mode of the operating system to store a modified form of the data in the repository. The repository files are then directly edited in a boot mode of the operating system to replace the data with the modified form of the data.

[0012] In another embodiment of this invention, a storage device is repartitioned by making Windows NT calls in a Windows NT Win32 mode to store repartitioning information in a temporary disk layout information registry key. Then, in a Windows NT boot mode, partition tables stored on the storage device are modified to match the repartitioning information, and registry files containing the temporary disk layout information registry key and a primary disk layout information registry key are directly edited to replace the primary disk layout information registry key with the temporary disk layout information registry key.

[0013] In still another embodiment of this invention, a storage device is repartitioned by accessing operating system services in a user interface mode of an operating system to store repartitioning information in an operating system configuration settings repository that comprises one or more repository files. Then, in a boot mode of the operating system, the storage device is repartitioned using the repartitioning information, and the repository files are directly edited to replace partitioning information stored therein with the repartitioning information.

[0014] In yet another embodiment of this invention, an apparatus for modifying data stored in an operating system configuration settings repository that comprises one or more repository files includes a device that accesses operating system services associated with the repository in a user interface mode of the operating system to store a modified form of the data in the repository. Also, another device directly edits the repository files in a boot mode of the operating system to replace the data with the modified form of the data.

[0015] In an additional embodiment of this invention, the apparatus described immediately above is incorporated into an electronic system that includes an input device, an output device, a processor device, and a memory device.

[0016] In a still additional embodiment of this invention, a computer-readable medium has computer program portions embodied therein that modify data stored in an operating system configuration settings repository made up of one or more repository files. The computer program portions include a computer program portion that accesses operating system services associated with the repository in a user interface mode of the operating system to store a modified form of the data in the repository, and a computer program portion that directly edits the repository files in a boot mode of the operating system to replace the data with the modified form of the data.

[0017] FIG. 1 is flow diagram showing a method for partitioning a hard drive in accordance with this invention, and

[0018] FIG. 2 is a block diagram showing an electronic system on which the method of FIG. 1 is implemented.

[0019] As shown in FIG. 1, a method 10 for partitioning a hard drive (not shown) in accordance with this invention includes a step 12 in which new disk layout information (i.e., new partition information) is determined in the Win32 mode of Windows NT® (sometimes also referred to as the user-interface mode). In PartitionMagic®, for example, the disk layout information is read from the hard drive, the existing partitions are displayed to a user, and the user enters any changes he or she wishes to make to the partitions. New disk layout information that reflects these changes is then stored in step 12 in a temporary registry key named, for example, “HKEY_LOCAL_MACHINE\SYSTEM\DISK\VirtualInfo”.

[0020] It will be understood by those having skill in the technical field of this invention that the invention is applicable to storage devices other than hard drives, including, for example, stripe sets and RAID (Redundant Array of Independent Disks) devices. It will also be understood that the invention is applicable to operating systems other than Windows NT®, and that the invention is not limited to use in connection with any particular registry keys including, for example, the “HKEY_LOCAL_MACHINE\SYSTEM\DISK\Information” and “HKEY_LOCAL_MACHINE SYSTEM DISK\VirtualInfo” keys. Further, it will be understood that the invention is applicable to Windows®-type registries and any other operating system configuration setting repositories.

[0021] In a step 14, a reboot into the Windows NT® boot mode (also sometimes referred to as the Windows NT® Session Manager mode) is performed in case the Windows NT® partition itself needs to be repartitioned. In this mode, the Windows NT® Session Manager maps drive letter assignments to various storage devices, including the hard drive, by accessing the old disk layout information stored in the “HKEY_LOCAL_MACHINE\SYSTEM\DISK\Information” registry key. The hard drive is then repartitioned to match the new disk layout information stored in the temporary registry key (e.g., the “HKEY_LOCAL_MACHINE\SYSTEM\DISK\VirtualInfo” key). More specifically, in the case of PartitionMagic®, for example, partition tables on the hard drive are manipulated to match the new disk layout information to repartition the hard drive.

[0022] At this stage, because the disk layout information in the partition tables on the hard drive and the actual disk letter assignments made by the Windows NT® Session Manager based upon the old disk layout information in the registry key “HKEY_LOCAL_MACHINE\SYSTEM\DISK\Information” do not coincide with one another, the new disk layout information needs to be entered into the registry key “HKEY_LOCAL_MACHINE\SYSTEM\DISK\Information”, and another reboot needs to be performed so the Windows NT® Session Manager can make disk letter assignments based upon the new disk layout information. Otherwise, as discussed above, Windows NT® may not be able to find the components necessary to boot into Win32 mode, and may crash as a result. Unfortunately, as discussed above, calls made to the Windows NT® Registry API in boot mode to modify the “HKEY_LOCAL_MACHINE\SYSTEM\DISK\Information” registry key won't be implemented if a reboot is performed immediately thereafter.

[0023] Accordingly, in a step 16, the Windows NT® system files containing the “HKEY_LOCAL_MACHINE\SYSTEM” group of keys (i. e., “system” and “system.alt”) are accessed through direct reads and writes by traversing each file through a parsing process until the “VirtualInfo” key is found. This key is then renamed the “Information” key so that the new disk layout information is stored in the “Information” key used by the Windows NT® Session Manager to make drive letter assignments during the boot process. The old “Information” key is also renamed in the process so that only one “Information” key exists in the system files. Those of skill in the technical field of this invention will understand that the file format and parsing process for the system files “system” and “system.alt” are readily available or ascertainable.

[0024] In a step 18, a reboot into Win32 mode is performed so that the repartitioning of the hard drive is fully implemented.

[0025] As shown in FIG. 2, an electronic system 100 that executes the method 10 of FIG. 1 includes an input device 102, an output device 104, a processor device 106, and a memory device 108. The electronic system 100 may be, for example, a PC-compatible computer system running the Windows NT® operating system.

[0026] It will be understood by those having skill in the technical field of this invention that the term “computer-readable medium” as used in the appended claims refers to any medium by which the functionality of a computer program portion may be realized. Such a medium may include, for example, a computer-readable storage medium such as a floppy disk, CD-ROM, DVD-ROM, Jaz® or Zip® disk, hard drive, storage area network, storage array (e.g., a RAID device), or memory device (e.g., a DRAM, SRAM, ROM, or flash EEPROM). A computer-readable medium may also include, for example, a signal carrier, such as a conductor, a carrier wave, or an electromagnetic emission (e.g., a light emission).

[0027] Also, it will be understood that the term “computer program portion” as used in the appended claims refers to any functional descriptive material for use in a computing device. Such material may include, for example, computer code capable of execution, either directly or indirectly, on a computing device. Computer code capable of indirect execution may include, for example, code requiring decryption, decompression, or run-time compilation immediately prior to execution. It will also be understood that the term “computer program portion” as used in the appended claims is not restricted to any particular source code language (e.g., Java® or C/C++) or language type (e.g., sequential or object-oriented), and that different computer program portions described as having different functions may share some code or data in common with one another.

[0028] Although this invention has been described with reference to particular embodiments, the invention is not limited to these described embodiments. For example, while the invention has been described with respect to a method having a series of sequential steps, the invention is not limited to the described sequence of steps, but rather includes within its scope any operable sequence of the described steps. Thus, the invention is limited only by the appended claims, which include within their scope all equivalent devices and methods that operate according to the principles of the invention as described.