Method of booting a computer operating system to run from a normally unsupported system device

• US 7,017,039 B2
• Filed: 12/31/2002
• Issued: 03/21/2006
• Est. Priority Date: 12/31/2002
• Status: Active Grant

• Current Assignee: III Holdings 1, LLC
• Original Assignee: John Alan Hensley
• Inventors: Hensley, John Alan
• Primary Examiner(s): Browne, Lynne H.
• Assistant Examiner(s): YANCHUS III, PAUL B
• Application Number:
  US10/334,611
• Publication Number:
  US 20040128495A1
• Time in Patent Office: 1,176 Days
• Field of Search: 713/1, 713/2, 713/100, 714/2, 714/6, 714/36, 714/160
• US Class Current: 713/2
• CPC Class Codes: G06F 9/4406 Loading of operating system

Abstract

A computer operating system (OS) is altered to boot so as to run from a normally unsupported system device (NUSD). The OS kernel is loaded from a natively supported boot device, such as a floppy disk or CD-ROM, and initialized. Device drivers for a NUSD are then loaded from the boot device and initialized. A bootswap device driver is also loaded and initialized. The bootswap device driver is operative to alter an OS data structure such that the NUSD is recognized as a system device. Upon completion of the boot sequence, the OS runs from the NUSD as a system drive. A method of preparing the boot media and configuring the NUSD is presented.

Claims

1. A method of booting a computer operating system to run from a disk drive device that is not normally supported as a boot or system device by the computer ROMBIOS, comprising:

loading and initializing an operating system kernel from a natively supported boot device;

after loading said operating system kernel, loading and initializing a device driver for a normally unsupported system device (NUSD);

after loading said operating system kernel, loading and initializing a bootswap device driver operative to alter at least one operating system data structure other than changing a drive designator such that said NUSD is recognized by the operating system as a system device; and

running said operating system from said NUSD.

2. The method of claim 1 wherein said operating system data structure is built by said operating system kernel in system memory.

3. The method of claim 2 further comprising loading disk identification information for said NUSD.

4. The method of claim 3 wherein said bootswap device driver alters said in-memory data structure to include said disk identification information.

5. The method of claim 1 wherein said NUSD includes operating system executable and configuration files.

6. The method of claim 5, wherein operating system files on said natively supported boot device and said NUSD are backup copies of a primary operating system that do not require a license separate from that for said primary operating system.

7. A method of computer disaster recovery, comprising:

prior to loss of use of a computer system drive,

copying original operating system executable and configuration files to a normally unsupported system device (NUSD); and

creating a bootable medium for a device natively supported as a boot device, said medium including a bootswap device driver operative to update an operating system in-memory data structure, other than changing a drive designator, to recognize said NUSD as a system device; and

following loss of use of said system drive,

loading and initializing an operating system kernel from said medium; and

after loading said operating system kernel, upon loading and initializing said bootswap device driver, completing the boot sequence and running said operating system from said NUSD.

8. The method of claim 7 further comprising updating said operating system executable and configuration files on said NUSD to mark as boot drivers those device drivers necessary to access said NUSD.

9. The method of claim 7 further comprising updating said operating system configuration files on said NUSD to include disk identification information for said NUSD.

10. The method of claim 7 wherein said bootswap device driver on said bootable medium is a boot driver.

11. The method of claim 7 wherein said bootable medium is a CD-ROM disk.

12. The method of claim 11 wherein said CD-ROM conforms to the El Torito specification.

13. The method of claim 7 wherein creating a bootable medium comprises:

copying a plurality of files minimally necessary to initiate a boot sequence to a subdirectory hierarchy of a system drive; and

copying said files from said subdirectory hierarchy to said bootable medium.

14. The method of claim 13 wherein said plurality of files are selected from the group including operating system bootstrap files, operating system kernel boot files, boot drivers, a bootswap device driver, test scripts and configuration information.

15. The method of claim 13 further comprising testing said plurality of files prior to copying said files to said bootable medium.

16. The method of claim 15 wherein said testing comprises:

rebooting the computer from said plurality of files; and

executing at least one test script prior to copying said files to said bootable medium.

17. A method of computer disaster recovery, comprising:

prior to loss of use of a computer system drive,

copying operating system executable and configuration files to a normally unsupported system device (NUSD);

storing disk identification information for said NUSD in said operating system configuration files on said NUSD;

copying to said NUSD a bootswap device driver operative to retrieve said disk identification information and update an operating system in-memory data structure, other than changing a drive designator, to recognize said NUSD as a system device;

altering said operating system files to mark device drivers for said NUSD and said bootswap device driver as boot drivers; and

copying a subset of operating system executable and configuration files from said NUSD to a disk natively supported by said computer as a boot device; and

following loss of use of said system drive,

loading and initializing an operating system kernel from said disk natively supported by said computer as a boot device;

after loading said operating system kernel, loading and initializing said bootswap device driver; and

running said computer from said NUSD.

18. A bootable computer readable medium including operating system files operative to cause a computer to perform the following steps during booting:

loading and initializing an operating system kernel;

after loading said operating system kernel, loading and initializing device drivers for a normally unsupported system device (NUSD);

after loading said operating system kernel, loading and initializing a bootswap device driver operative to alter at least one operating system data structure, other than changing a drive designator, such that said NUSD is recognized by said operating system as a system device; and

running said operating system from said NUSD.

19. The protected medium of claim 18 wherein said operating system files are a backup copy of the primary operating system of said computer.

20. The protected medium of claim 19 wherein said backup operating system files have been altered to load device drivers for said NUSD and said bootswap device driver during a boot sequence.

21. A method of booting a computer operating system to run from a disk drive device that is not natively supported as a boot device by a computer, comprising:

loading and initializing a device driver for a normally unsupported system device (NUSD) from a natively supported boot device;

loading configuration information from a natively supported boot device;

loading and initializing a protected-mode operating system kernel from a natively supported boot device, said kernel operative to alter an in-memory data structure based on said configuration information, such that said NUSD is recognized by said operating system as a system device; and

using said device driver to run said operating system from said NUSD.

22. The method of claim 21 wherein said configuration information includes identification information for said NUSD.

23. The method of claim 21 wherein said protected-mode device driver, said configuration information, and said protected-mode operating system kernel are loaded from the same natively supported boot device.