US20020026571A1 - Dual use master boot record - Google Patents
Dual use master boot record Download PDFInfo
- Publication number
- US20020026571A1 US20020026571A1 US09/960,181 US96018101A US2002026571A1 US 20020026571 A1 US20020026571 A1 US 20020026571A1 US 96018101 A US96018101 A US 96018101A US 2002026571 A1 US2002026571 A1 US 2002026571A1
- Authority
- US
- United States
- Prior art keywords
- code
- computer
- computer readable
- floppy
- drive
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4406—Loading of operating system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
Definitions
- the present invention relates generally to the field of computer storage, and more particularly to high capacity removable media devices which may be accessed and booted, regardless of format configuration, as either a floppy or hard disk.
- HCRM High Capacity Removable Media
- Iomega Corporation's ZIP® drive BIOS configurable as either a hard drive, or a floppy drive.
- HCRM drives are not new to the PC industry, they have traditionally been used as removable hard drives, and therefore the HCRM media is generally partitioned in the same manner as conventional hard disks.
- DOS based operating systems boot from or access partitioned media in a floppy drive.
- This format should be compatible with existing partitioned media so that they can be used without requiring reformatting, or otherwise destroying the data they contain.
- the boot process of IBM compatible computers begins with the BIOS reading the boot sector of the boot drive into memory and executing it. If the required boot record code and/or data structure is missing from the media, the boot process will fail to load the operating system.
- HCRM drives For example, in systems which allow HCRM drives to be configured as either A: (i.e. a floppy) or C: (i.e. a hard disk); with the HCRM drive configured as C: the partitioned media will boot because a Master Boot Record (MBR) and Partition Table are present in the boot sector.
- MLR Master Boot Record
- Partition Table Partition Table
- the reason for the system's failure to boot is due to the fact that operating systems, which are designed to read DOS formatted disks, require different data structures to be present in the boot sector of the disk depending on whether the disk drive is a floppy drive (typically having BIOS drive numbers 0 or 1) or a hard disk drive (typically having BIOS drive number 80h or higher).
- the operating system initially determines how it will access media configured as floppy by scanning each floppy drive (BIOS drive number 0 and 1) and using the BIOS Parameter Block (BPB), to locate the media's root directory, FATs, and data area.
- the operating system will assign a drive letter when the presence of drive 0 (A:) and 1 (B:) is detected.
- media access is determined by the presence of a correct BPB at sector 0; that is, the data contained in drive A: or B: can only be accessed when the BPB is present at sector 0.
- a correct BPB for partitioned media such as a HCRM configured as C:
- the operating system will scan all drives looking for DOS type partitions, as defined in the system type file of the Partition Table, and will only assign a drive letter if a BPB is found in the first sector of each partition.
- the BPB for a hard drive formatted media does not reside in sector 0. Therefore, when attempting to use a partitioned HCRM as A: (i.e. a floppy), the operating system will not be able to access the data on the media.
- the present invention solves the problems discussed above that are associated with accessing and booting a removable partitioned computer storage media, such as a HCRM device, as a floppy.
- a removable partitioned media can be both accessed and booted by the operating system as either a floppy or a hard disk, by replacing the standard MBR with a Dual Use MBR.
- the present invention takes a hard drive formatted media and replaces the contents of the Boot Sector with a new MBR, refered to in this disclosure as “DUMBR” (Dual Use Master Boot Record), that contains new code in accordance with the invention, a Partition Table, and the addition of floppy BPB.
- DUMBR Dual Use Master Boot Record
- the new code first determines the drive number used by the system BIOS for initiating the boot process and saves the result.
- the new code determines if the saved drive number value is 0 (or 00h), indicating that the boot drive is a floppy. If the boot was initiated from a floppy (saved drive number is 0), the new code overwrites the hard disk BPB in RAM with the floppy BPB of DUMBR. The code then jumps to the DBR code in the RAM buffer that has been overwritten with the floppy BPB, and the boot process continues as normal.
- FIG. 1 is a schematic representation of the logical structure of a high capacity medium with a Dual Use Master Boot Record area in accordance with the present invention.
- FIG. 2 is a flow chart representing one embodiment of the present invention.
- FIG. 2 a is a flow chart representing the logic for determining the drive number used by the BIOS for initiating the boot process depicted in FIG. 2.
- Master Boot Record is located in the Boot Sector of a hard drive.
- the MBR contains a Partition Table, a validation signature, and code for locating the active partition of the hard disk and loading and executing the bootstrap loader for the operating system.
- (For Example See Table 1) TABLE 1 (MBR) Byte Field Sample Offset Length Value Meaning 000h 446 Code portion of the Master boot record bytes 1Beh 64 Partition Table (4 16 byte entries) bytes 1Feh 2 55h Validation signature bytes AAh
- DOS Boot Record is found at the beginning of a DOS partition of a media formatted as a hard disk, and in the Boot Sector of a DOS formatted floppy disk.
- the DBR contains a BIOS Parameter Block (BPB) and code to locate and execute an operating system kernel file.
- BPB BIOS Parameter Block
- Fixed or hard disks generally contain a reserved area of at least one sector is used to hold the DBR.
- Boot Sector comprises one or more sectors containing the boot record to be loaded by the BIOS to initiate the boot process.
- the boot sector is the first sector, which is addressable on X86-based PC's as cylinder 0, head 0, sector 1, or LBA 0.
- the first sector contains the MBR, with the remaining sectors being unused.
- Each partition of the hard disk is configured in the same manner as a floppy, with the first sector containing the DBR.
- Boot Track is also called the Reserved Track, and is the first track of a hard drive, or an extended partition. It contains a MBR in the first sector, with all the remaining sectors being unused.
- Hidden Sectors can generally comprise sectors 0-63 in DOS formatted disks, and generally constitutes the area used for the Boot Track on hard disks.
- the specific number of sectors that comprise the Hidden Sectors area is specified in the BIOS Parameter Block (BPB). For floppy disks this area, or number of sectors, is 0. (For Example See Table 3).
- BPB BIOS Parameter Block
- Hidden Sectors area used for boot track on fixed disks. The number of Hidden Sectors ⁇ close oversize bracket ⁇ ⁇ open oversize bracket ⁇ sectors in this area is specified in the hidden sectors filed of the BPB (reference #10). For floppies this area is 0 sectors.
- DOS Boot Record (DBR) Reserved sectors area is used for the DBR There may be additional (1st reserved sector) ⁇ close oversize bracket ⁇ reserved sectors allocated when the media is formatted. The number Additional Hidden Sectors ⁇ open oversize bracket ⁇ of sectors in this area is specified in the reserved sectors filed of the BPB (reference #2) File Allocation Table 0 File Allocation Table 1 Root Directory Data
- Reserved Sectors are those sectors in all DOS formatted disks following the Hidden Sectors area, and is used to contain the DBR. Additional Reserve Sectors may be allocated when the media is formatted. The specific number of Reserved Sectors is identified in the BPB. (For Example See Table 3).
- BIOS Parameter Block is a DOS specific data structure, which describes the format of a fixed or floppy disk.
- Partition Table describes the allocation of storage space on a hard disk (For Example See table 5) TABLE 5 (Partition Table) Byte Field Offset Size Meaning 00h Byte Boot indicator flag. 80h if partition bootable, otherwise 00h 01h Byte Starting head of the partition 02h Word Starting cylinder and sector of partition 04h Byte System type 05h Byte Ending head of partition 06h Word Ending cylinder and sector of partition 08h Dword Prior Sectors 0Ch Dword Total Sector in partition
- DOS means any operating system that reads DOS formatted media, including but not limited to Windows9 2 , Windows 98, OS/2, Novell DOS, and Digital Research DOS.
- the present invention is designed for any operating systems designed to read DOS-formatted media.
- DOS formatted media the MBR is located in the Hidden Sectors area
- the remaining sectors in this first track are generally unused.
- the fundamental problem that occurs when a medium is loaded into a drive with a device number of 0 or 1 (as a floppy) is that the operating system expects to find a floppy BPB in the first sector.
- the same medium is loaded into a hard drive with a device number of 80h or higher, the operating system will expect to find a Partition Table in the Boot Sector of the disk.
- a medium which is formatted with a Partition Table will not be readable from or bootable from a floppy drive with a device number of 0 or 1 because there is no floppy BPB in the Boot Sector.
- BIOS should designate a HCRM media with a floppy number or a hard drive number.
- high capacity removable media had traditionally or generally been treated as hard drives. Accordingly, these hard drive formatted media, when converted to have a floppy number designation for the media and then loaded into a floppy drive device, were not addressable or bootable because the DOS expected to find a floppy BPB in the boot sector.
- BIOS parameter block is required which may be either present in the Boot Sector of the media, or may be loaded into the memory of the computer from a network or from another peripheral memory, for devices which emulate a disk drive.
- the present invention therefore, in one aspect makes a single computer readable medium that is formatted as a hard disk, addressable by the operating system as either a floppy disk drive or a hard disk drive.
- the invention comprises the addition of a computer code in the MBR and a floppy BPB for describing the correct data structure for the medium if the medium, such as a HCRM type media, is inserted in a floppy drive of the computer.
- the computer code determines the drive number from which the system BIOS attempted to boot, and uses this value to determine whether or not to overwrite the BPB of the active partition loaded into RAM during the boot process with the floppy BPB contained as part of the MBR.
- a DOS formatted disk will have the structure described in Table 3.
- a formatted hard disk is basically a collection of floppy like images, called partitions, which are pointed to by the Partition Table located in the MBR, which is contained in the Boot Sector of the hard disk.
- the hard disk format utilizes the first sector of the first track (defined herein as Boot Sector) of the Hidden Sectors area of the DOS format structure to place the MBR, with the remaining sectors remaining unused.
- the hard disk BPB will identify the specific number of sectors that are designated as Hidden Sectors for this purpose (see Table 4, reference 10), and will have the physical drive number field set to 80h and the Reserve Sectors field set to 1.
- the hard disk partitions being a collection of floppy images, will have the same structure as a floppy formatted disk, and therefore will have its BPB indicate 0 for the number of Hidden Sectors, and have the DBR in its Boot Sector, followed by two copies of the FAT (File Allocation Table) and the root directory.
- the hard drive boot process is a super set of the floppy boot process. It begins with the BIOS loading the MBR from the Boot Sector of the hard drive into memory at 0:7C00h, and transferring control. The MBR first relocates itself to 0:600h, to free memory location 0:7C00h for the DBR, then searches the Partition Table for an active partition. If an active partition is found, the MBR loads the DBR, usually from the first sector of the partition, into memory at 0:7C00h, and transfers control.
- a floppy boot begins when the BIOS reads the DBR from the first sector of the floppy into memory at location 0:7C00h, and transfers control.
- the DBR uses the information in the BPB to locate the root directory, and verify that the necessary operating system files are on the disk. If the files are present, the DBR loads the first several sectors of IO.SYS into memory, and transfers control. IO.SYS, completes the job of loading the operating system. If the system files are not in the root directory, the DBR prints an error message indicating that the media is not bootable.
- DOS type partition structure be defined in the Partition Table, and that a proper BPB is in the first sector of that partition. Any non-DOS based partitions in the Partition Table are ignored, and no drive letter will be assigned.
- DOS operating systems will assign a drive letter to any floppy drive that is installed in the system, access to the media is only given if the operating system recognizes the media as having a DOS compatible format. The operating system expects all floppies to have a BPB in their boot sector.
- the BIOS parameter block tells the operating system how large the media is, and where the various areas of the media start and stop.
- the standard DOS MBR code for hard disk formatted media is written to the drive by FDISK.EXE, and always assumes a drive number of 80h.
- the MBR code will find the active partition, but when it attempts to read the DBR, it will read from drive 80h instead of drive 0. This results in the wrong drive being read.
- the BPB still would have a physical drive number filed set to 80h, which also prevents a hard drive DBR from being able to boot as drive 0. Therefore, the present invention solves this problem by replacing the standard DOS MBR with a Dual Use Master Boot Record, referred to previously as DUMBR.
- a standard MBR hard disk format is modified by replacing the code portion of Table 1 with the format shown in Table 6.
- the DUMBR code section contains a modified floppy BPB, and code which is capable of booting as either fixed or floppy.
- the difference between the DUMBR BPB, and a standard floppy BPB is the Reserved Sectors field.
- the DUMBR Reserved Sectors field marks the entire Boot Track, and the first sector of the second track, which is the DBR, as reserved. More accurately, the hidden sectors field in the floppy BPB should be equal to the reserved sectors+the hidden sectors field of the hard drive BPB.
- DUMBR organization includes a jump for jumping over the floppy BIOS parameter block, a system name field, the floppy BIOS parameter block (see Table 4), the code portion for a Dual Use Boot Record, a Partition Table, and a validation signature.
- BPB Bit Offset parameter Table 4
- the Reserved Sectors parameter listed at byte offset 03h is set to a value sufficient to reserve the Boot Track, and that portion of the active partition containing the DBR, including the hard disk BPB and the code portion of the DBR (see Table 2, byte offsets 00Bh and 00Eh), as well as any Reserved Sectors between the DBR and the first copy of the files allocation tables (FAT ⁇ ).
- this Reserved Sectors parameter number is set to 64, i.e., 63+1.
- the Reserved Sectors parameter could simply be set to accommodate a convenient organization on the floppy BPB.
- the first sector of the Boot Track is shown to contain a floppy BPB 20 .
- the floppy BIOS parameter block typically is preceded by a jump instruction to allow the computer to jump directly to MBR code 22 .
- a Partition Table follows in 24 , with the areas comprising 20 , 22 , and 24 making up the first sector, or Boot Sector, of the media.
- the remaining sectors of Boot Track 42 are then listed in the area 26 and are usually empty, not by way of limitation, but simply by convention.
- the Boot Track as previously discussed, comprises the Hidden Sectors region of a DOS formatted disk (see Table 3).
- a DBR located in the Reserved Sectors region of a typical DOS formatted disk (see Table 3), and shown as area 30 .
- the BPB of DBR 30 referenced as 00Bh in Table 2, is a hard disk, or “fixed disk” BPB, shown in area 28 of FIG. 1. This hard disk BPB is preceded by a jump instruction to allow the system to jump over non-executable data in hard disk BPB 28 if the system were to boot as a floppy disk, in accordance with the present invention.
- FAT ⁇ first file allocation table
- FAT ⁇ second, duplicate of the files allocation table
- the root directory is provided in the area 36 , as per convention, followed by data stored in a data area 38 , also as per convention.
- the number of reserved sectors in the BPB is set forth in reference 2; with the number of “hidden sectors” set forth in reference 10.
- the bracketed area 40 shown in FIG. 1 indicates the area specified as “reserved”.
- the reserved sectors field of floppy BPB 20 differs from the reserve sectors field of a standard floppy in that all sectors prior to the first copy of the FAT (usually the entire Boot Track, and the DBR, which is the first sector of the second track) is specified as reserved.
- the bracketed region 42 indicates the area specified as “hidden”; while the bracketed 44 marks the area is specified as “reserved”. It is assumed that there are no reserved sectors after the DOS boot record so that FAT ⁇ begins in the sector following the DBR.
- FIG. 2 there is shown a flow chart for a method for allowing HCRM media with at least one partition to be bootable with both hard and floppy drives of a computer.
- POST Power On Self Test
- INT 19 will attempt to read a Boot Sector from the default boot drive. If the Boot Sector is found, int 19h reads the Boot Sector into RAM at location 0:7C00h and jumps to 0:7C00h transferring control. If no Boot Sector is found on the default boot drive, INT 19 attempts to read the MBR from the drive.
- POST Power On Self Test
- FIG. 2 shows the sequence of events in one particular embodiment of the invention after the system has loaded the Boot Sector of the HCRM media (the contents of bracketed area 42 of FIG. 1, i.e. floppy BPB 20 , MBR 22 , Partition Table 24 ; collectively referred to as “DUMBR”) in 0:7C00h. of RAM.
- the first instruction is a jump instruction at block 52 ; causing a jump over floppy BPB 20 of FIG. 1, to begin execution of the MBR code 22 of FIG. 1.
- the DUMBR code executing out of memory location 0:7C00h, copies 1 sector worth of data (512 bytes)from memory location 0:7C00h to another location in memory (by convention 0:600h) and transfers control to the new copy of itself at the new RAM location so that the DBR of the active partition may be subsequently copied to the computer RAM at address 0:7C00h.
- MBR code 22 depicted in FIG. 1 determines the drive number which the BIOS used for initiating the boot and then saves the result. There are a variety of techniques which may be utilized to accomplished this determination. By way of example, but not by way of limitation, FIG. 2( a ) identifies one way that such a determination can be made.
- step 100 the system sets a count number for the number of attempts to be made in reading the Boot Sector of the media in floppy drive 0 into the RAM buffer.
- INT 13 attempts to read the Boot Sector of the media in floppy drive 0 to the RAM buffer as indicated by block 110 . If INT 13 reports an error, shown by block 112 , the system decrements the count in block 114 and determines if more attempts to boot are to be made in block 116 . If more retries exist the system loops back to block 110 to make another read attempt.
- a set number of retries is provided (such as 10) to allow for INT 13 errors that may result if the media is not properly spun up for example.
- the Boot Sector of the media in the floppy drive is read into RAM and the system moves to the next step, block 118 , and compares in block 120 the entire 512 bytes of the media's Boot Sector now in the RAM buffer to the 512 bytes of code copied into RAM location 0:600h in step 54 of FIG. 2. If the code loaded into the RAM buffer in block 110 is not identical to the code residing in 0:600h, the system flags the boot drive as a floppy, 00h as shown in block 122 . If the code in the RAM buffer is not identical to the code residing in RAM location 0:600h, the boot drive is flagged as a hard drive, 80h as in block 124 .
- boot drive is also flagged as a hard drive if the system continues to receive INT 13 errors and the number of retries is exhausted, as shown in block 116 , thereby indicating that the proper data structure is not present in the media's Boot Sector allowing the system to read the media as a floppy drive. If there is no medium in the floppy drive 0, then the BIOS will report that no medium is in the drive and the drive number will be determined to be 80h.
- the system flags the drive number, and moves to block 58 , where the MBR code initializes a pointer to the first entry in Partition Table 24 of FIG. 1 that was loaded into the RAM.
- the execution then branches to the diamond block 60 and determines whether this entry in the Partition Table is the active partition. If the answer is no, then the execution branches to the diamond block 62 and determines whether all of the Partition Table entries have been examined. If there are more Partition Table entries, then execution branches block 64 and advances the pointer to the next entry in the Partition Table and returns to the diamond block 60 . If there are no more Partition Table entries determined in block 62 , then the execution prints an error message and takes appropriate error recovery action.
- execution branches to the block 70 and reads the DBR of the active partition to the RAM buffer memory at address 0:7C00h.
- the first sector of the active partition will comprise a DOS boot record including a BPB that is correct for a hard disk boot.
- the execution then steps to the diamond block 72 where the system first looks to the drive number that was flagged in either step 122 or 124 , of FIG. 2( a ), which the BIOS used to initiate the boot process.
- the drive number is 0, for a floppy drive designation, then it copies the modified floppy BPB of DUMBR, located in memory at 0:600h, and overwrites the hard disk BPB of the DBR that was loaded in the RAM at 0:7C00h, with the modified floppy BPB that is part of DUMBR.
- the DBR of the active partition now has a BPB with the correct physical drive number, and a Reserve Sectors field for a floppy drive boot. Then the execution goes to the block 76 of FIG. 2 and jumps to the DBR to transfer control and the HCRM media boots as a floppy.
- step in diamond block 72 of FIG. 2 determines that the boot drive number is not 0, but the drive number is 80h, then execution jumps to 0:7C00h and DUMBR transfers control to the DBR in the RAM buffer at address 0:7C00h (see block 76 ) without any overwrite of the hard disk BIOS parameter block having been performed.
- the present invention has been described in the context of a standard organization for disk media where the boot sector is located in the first sector of the first track. It would be obvious to one of ordinary skill in the art to locate the boot sector to other locations on the disk. Accordingly, the present invention is not limited to the boot sector being in a particular location on a disk.
- the Dual Use Master Boot Record of the present invention could be separated from the high capacity medium that is being addressed and/or booted, as noted above. Accordingly, the floppy BPB, the MBR code, and the Partition Table could be stored permanently in another drive in the computer, or could be downloaded from a network, with the only requirement being that the correct BPB be used to describe the media correctly based upon the drive number from which the system BIOS initially attempted to boot.
- the presently disclosed data structure, method, and high capacity computer article of manufacturer support partitioned media in both a floppy drive and a hard drive, but require no code to be added to the BIOS, and require no translation of INT 13h parameters.
- the present invention also removes the need for the operating system vendor to modify the operating system.
- the method, data structure and high capacity computer article of manufacture of the present invention provide a much higher degree of compatibility with existing operating systems compared to the interrupt 13h filtering method.
- the data structure of the present invention can be added to any partitioned media without affecting any of the data stored on the media.
- floppy drive means a computer drive for reading and/or writing to a computer readable medium which is removable from the drive and wherein the operating system in the computer typically will expect to read the BPB and the DBR code in the Boot Sector for the medium.
- a floppy BPB for such a medium will generally have a Hidden Sectors of 0 and a floppy drive number of 0.
- a floppy will not have a Partition Table.
- hard drive is meant a computer drive for reading and/or writing to a computer readable medium which is hard, i.e., not ordinarily removable in the normal course of operation. It expects to find a Partition Table, in the Boot Sector of the medium. Note that the different partitions may be formatted for different operating systems. Typically the hard drive will have a BIOS drive code of 80h or higher, and will be referenced in byte offset 19h in the BPB.
- a hard drive will also have a MBR code for determining from the Partition Table which partition is active, and then going to the head, cylinder, and sector location or logical block address on the medium where the active partition starts and reading the first sector of the active partition into the memory (RAM) of the computer.
- the first sector for the active partition of a bootable disk will contain a DBR which is comprised of the DOS boot record code and the hard disk BPB.
Abstract
Description
- The present invention relates generally to the field of computer storage, and more particularly to high capacity removable media devices which may be accessed and booted, regardless of format configuration, as either a floppy or hard disk.
- The current standard 1.44 megabyte floppy removable media is becoming increasingly inadequate to meet user needs. In response, BIOS vendors have begun offering systems which allow High Capacity Removable Media (HCRM) drives, such as Iomega Corporation's ZIP® drive, to be BIOS configurable as either a hard drive, or a floppy drive. Although HCRM drives are not new to the PC industry, they have traditionally been used as removable hard drives, and therefore the HCRM media is generally partitioned in the same manner as conventional hard disks. One of the problems stemming from the use of HCRM drives as floppies is the inability of DOS based operating systems to boot from or access partitioned media in a floppy drive. Because of the ability to change the configuration of the drive, a single format is needed that will boot, and allow access to the media, regardless of it's current configuration. This format should be compatible with existing partitioned media so that they can be used without requiring reformatting, or otherwise destroying the data they contain.
- The boot process of IBM compatible computers begins with the BIOS reading the boot sector of the boot drive into memory and executing it. If the required boot record code and/or data structure is missing from the media, the boot process will fail to load the operating system. For example, in systems which allow HCRM drives to be configured as either A: (i.e. a floppy) or C: (i.e. a hard disk); with the HCRM drive configured as C: the partitioned media will boot because a Master Boot Record (MBR) and Partition Table are present in the boot sector. However when a HCRM drive containing a partitioned media is configured as A:, where no Partition Table is required, the media will fail to boot. This is because the standard MBR code is designed to boot a hard drive, and always assumes a BIOS drive number of 80h. Conversely, if the user is attempting to boot from a floppy formatted media in a drive configured as C:, the boot will fail because the variable in the BIOS parameter block that tells the DOS Boot Record (DBR) code which BIOS drive number to boot from, will be set to 00h.
- The reason for the system's failure to boot is due to the fact that operating systems, which are designed to read DOS formatted disks, require different data structures to be present in the boot sector of the disk depending on whether the disk drive is a floppy drive (typically having
BIOS drive numbers 0 or 1) or a hard disk drive (typically havingBIOS drive number 80h or higher). The operating system initially determines how it will access media configured as floppy by scanning each floppy drive (BIOS drive number 0 and 1) and using the BIOS Parameter Block (BPB), to locate the media's root directory, FATs, and data area. The operating system will assign a drive letter when the presence of drive 0 (A:) and 1 (B:) is detected. However, media access is determined by the presence of a correct BPB atsector 0; that is, the data contained in drive A: or B: can only be accessed when the BPB is present atsector 0. For partitioned media such as a HCRM configured as C:, the operating system will scan all drives looking for DOS type partitions, as defined in the system type file of the Partition Table, and will only assign a drive letter if a BPB is found in the first sector of each partition. The BPB for a hard drive formatted media does not reside insector 0. Therefore, when attempting to use a partitioned HCRM as A: (i.e. a floppy), the operating system will not be able to access the data on the media. - To support existing HCRM media, a solution is needed that will allow partitioned media to function properly when inserted into a floppy configured HCRM drive. As indicated above, this requires addressing two problems, booting, and access to data. Additionally, for a solution to be viable, it must provide a simple way for existing media to be updated, without compromising the user's data.
- The present invention solves the problems discussed above that are associated with accessing and booting a removable partitioned computer storage media, such as a HCRM device, as a floppy. In accordance with the present invention a removable partitioned media can be both accessed and booted by the operating system as either a floppy or a hard disk, by replacing the standard MBR with a Dual Use MBR. To allow the operating system to locate the BPB where it is expected to reside, which for floppy drives means that a BPB must be located at
sector 0, and for fixed disks a BPB must be present in the first sector of the partition, the present invention takes a hard drive formatted media and replaces the contents of the Boot Sector with a new MBR, refered to in this disclosure as “DUMBR” (Dual Use Master Boot Record), that contains new code in accordance with the invention, a Partition Table, and the addition of floppy BPB. The new code first determines the drive number used by the system BIOS for initiating the boot process and saves the result. Once the DBR of the first active partition is read into RAM, the new code then determines if the saved drive number value is 0 (or 00h), indicating that the boot drive is a floppy. If the boot was initiated from a floppy (saved drive number is 0), the new code overwrites the hard disk BPB in RAM with the floppy BPB of DUMBR. The code then jumps to the DBR code in the RAM buffer that has been overwritten with the floppy BPB, and the boot process continues as normal. - FIG. 1 is a schematic representation of the logical structure of a high capacity medium with a Dual Use Master Boot Record area in accordance with the present invention.
- FIG. 2 is a flow chart representing one embodiment of the present invention.
- FIG. 2a is a flow chart representing the logic for determining the drive number used by the BIOS for initiating the boot process depicted in FIG. 2.
- The following definitions and examples are provided to set forth the context of the present invention.
- Master Boot Record (MBR) is located in the Boot Sector of a hard drive. The MBR contains a Partition Table, a validation signature, and code for locating the active partition of the hard disk and loading and executing the bootstrap loader for the operating system. (For Example See Table 1)
TABLE 1 (MBR) Byte Field Sample Offset Length Value Meaning 000h 446 Code portion of the Master boot record bytes 1Beh 64 Partition Table (4 16 byte entries) bytes 1Feh 2 55h Validation signature bytes AAh - DOS Boot Record (DBR) is found at the beginning of a DOS partition of a media formatted as a hard disk, and in the Boot Sector of a DOS formatted floppy disk. The DBR contains a BIOS Parameter Block (BPB) and code to locate and execute an operating system kernel file. Fixed or hard disks generally contain a reserved area of at least one sector is used to hold the DBR. (For Example See Table 2)
TABLE 2 (DBR) Byte Field Sample Offset Length Value Meaning 000h 3 bytes N/A Jump over the BIOS parameter block 003h 8 bytes N/A System name field 00Bh 51 bytes N/A BIOS parameter block 03Eh 448 N/A Code portion of the DOS boot record bytes 1Feh 2 bytes 55h Validation signature AAh - Boot Sector comprises one or more sectors containing the boot record to be loaded by the BIOS to initiate the boot process. Traditionally, the boot sector is the first sector, which is addressable on X86-based PC's as
cylinder 0,head 0,sector 1, orLBA 0. For “fixed” or hard disks the first sector contains the MBR, with the remaining sectors being unused. Each partition of the hard disk is configured in the same manner as a floppy, with the first sector containing the DBR. - Boot Track is also called the Reserved Track, and is the first track of a hard drive, or an extended partition. It contains a MBR in the first sector, with all the remaining sectors being unused.
- Hidden Sectors can generally comprise sectors 0-63 in DOS formatted disks, and generally constitutes the area used for the Boot Track on hard disks. The specific number of sectors that comprise the Hidden Sectors area is specified in the BIOS Parameter Block (BPB). For floppy disks this area, or number of sectors, is 0. (For Example See Table 3).
TABLE 3 (Logical Structure of a DOS Formatted Disk) Hidden Sectors area used for boot track on fixed disks. The number of Hidden Sectors {close oversize bracket} {open oversize bracket} sectors in this area is specified in the hidden sectors filed of the BPB (reference #10). For floppies this area is 0 sectors. DOS Boot Record (DBR) Reserved sectors area is used for the DBR There may be additional (1st reserved sector) {close oversize bracket} reserved sectors allocated when the media is formatted. The number Additional Hidden Sectors {open oversize bracket} of sectors in this area is specified in the reserved sectors filed of the BPB (reference #2) File Allocation Table 0 File Allocation Table 1 Root Directory Data - Reserved Sectors are those sectors in all DOS formatted disks following the Hidden Sectors area, and is used to contain the DBR. Additional Reserve Sectors may be allocated when the media is formatted. The specific number of Reserved Sectors is identified in the BPB. (For Example See Table 3).
- BIOS Parameter Block (BPB) is a DOS specific data structure, which describes the format of a fixed or floppy disk. (For Example See Table 4)
TABLE 4 (BPB) Reference Byte Field Sample # Offset Length Value Meaning 0 00h Word 200h Number of bytes per sector 1 02h Byte 8 Number of sectors per cluster 2 03h Word 1 Number of reserved sectors, accounts for the DBR sector 3 05h Byte 2 Number of File Allocation Tables 4 06h Word 200h Number of root directory entries 5 08h Word 0 Total number of sectors if less than 65,536 6 0Ah Byte F8h Media descriptor 7 0Bh Word A0h Number of sectors per File Allocation Table 8 0Dh Word 3Fh Number of sectors per track 9 0Fh Word 10h Number of heads 10 11h Dword 3Fh Number of hidden sectors (0 for a floppy) 11 15h Dword 1FE034 Total number of sectors if h word at offset 8 is 0 12 19h Byte 80h Physical drive number (0 for floppy) - Partition Table describes the allocation of storage space on a hard disk (For Example See table 5)
TABLE 5 (Partition Table) Byte Field Offset Size Meaning 00h Byte Boot indicator flag. 80h if partition bootable, otherwise 00h 01h Byte Starting head of the partition 02h Word Starting cylinder and sector of partition 04h Byte System type 05h Byte Ending head of partition 06h Word Ending cylinder and sector of partition 08h Dword Prior Sectors 0Ch Dword Total Sector in partition - DOS means any operating system that reads DOS formatted media, including but not limited to Windows92, Windows 98, OS/2, Novell DOS, and Digital Research DOS.
- The present invention is designed for any operating systems designed to read DOS-formatted media. In DOS formatted media the MBR is located in the Hidden Sectors area The remaining sectors in this first track are generally unused. The fundamental problem that occurs when a medium is loaded into a drive with a device number of 0 or 1 (as a floppy) is that the operating system expects to find a floppy BPB in the first sector. In contrast, when the same medium is loaded into a hard drive with a device number of 80h or higher, the operating system will expect to find a Partition Table in the Boot Sector of the disk. Accordingly, a medium which is formatted with a Partition Table will not be readable from or bootable from a floppy drive with a device number of 0 or 1 because there is no floppy BPB in the Boot Sector.
- It should also be noted that users are now allowed to go into a menu-based set-up program where the user can specify whether the BIOS should designate a HCRM media with a floppy number or a hard drive number. Prior to the availability of this set-up program function, such high capacity removable media had traditionally or generally been treated as hard drives. Accordingly, these hard drive formatted media, when converted to have a floppy number designation for the media and then loaded into a floppy drive device, were not addressable or bootable because the DOS expected to find a floppy BPB in the boot sector.
- If the computer has already booted, or is booting from another device, and it is only desired to be able to address (but not boot from) the removable media (such as HCRM), then a BIOS parameter block is required which may be either present in the Boot Sector of the media, or may be loaded into the memory of the computer from a network or from another peripheral memory, for devices which emulate a disk drive.
- It is generally desirable to not only be able to address the media in either a floppy drive or a hard drive but also to be able to boot from that media. In order to be able to boot from the media in either type of drive, a new Dual Use Master Boot Record in accordance with the invention is provided in the media's Boot.
- The present invention, therefore, in one aspect makes a single computer readable medium that is formatted as a hard disk, addressable by the operating system as either a floppy disk drive or a hard disk drive. The invention comprises the addition of a computer code in the MBR and a floppy BPB for describing the correct data structure for the medium if the medium, such as a HCRM type media, is inserted in a floppy drive of the computer. The computer code determines the drive number from which the system BIOS attempted to boot, and uses this value to determine whether or not to overwrite the BPB of the active partition loaded into RAM during the boot process with the floppy BPB contained as part of the MBR. If the drive number read by the computer code is a 0 (00h), indicating the BIOS initiated the boot process from a floppy drive, the computer code initiates the overwriting of the hard disk BPB with the floppy BPB so the correct data describing the format of the media is available for the DOS boot record code to use for locating and executing the operating system. As noted previously, a DOS formatted disk will have the structure described in Table 3. A formatted hard disk is basically a collection of floppy like images, called partitions, which are pointed to by the Partition Table located in the MBR, which is contained in the Boot Sector of the hard disk. The hard disk format utilizes the first sector of the first track (defined herein as Boot Sector) of the Hidden Sectors area of the DOS format structure to place the MBR, with the remaining sectors remaining unused. The hard disk BPB will identify the specific number of sectors that are designated as Hidden Sectors for this purpose (see Table 4, reference 10), and will have the physical drive number field set to 80h and the Reserve Sectors field set to 1. The hard disk partitions, being a collection of floppy images, will have the same structure as a floppy formatted disk, and therefore will have its BPB indicate 0 for the number of Hidden Sectors, and have the DBR in its Boot Sector, followed by two copies of the FAT (File Allocation Table) and the root directory.
- The hard drive boot process is a super set of the floppy boot process. It begins with the BIOS loading the MBR from the Boot Sector of the hard drive into memory at 0:7C00h, and transferring control. The MBR first relocates itself to 0:600h, to free memory location 0:7C00h for the DBR, then searches the Partition Table for an active partition. If an active partition is found, the MBR loads the DBR, usually from the first sector of the partition, into memory at 0:7C00h, and transfers control. From this point on the boot process is identical to the floppy; wherein a floppy boot begins when the BIOS reads the DBR from the first sector of the floppy into memory at location 0:7C00h, and transfers control. The DBR uses the information in the BPB to locate the root directory, and verify that the necessary operating system files are on the disk. If the files are present, the DBR loads the first several sectors of IO.SYS into memory, and transfers control. IO.SYS, completes the job of loading the operating system. If the system files are not in the root directory, the DBR prints an error message indicating that the media is not bootable.
- Access to fixed disks requires that a DOS type partition structure be defined in the Partition Table, and that a proper BPB is in the first sector of that partition. Any non-DOS based partitions in the Partition Table are ignored, and no drive letter will be assigned. Although DOS operating systems will assign a drive letter to any floppy drive that is installed in the system, access to the media is only given if the operating system recognizes the media as having a DOS compatible format. The operating system expects all floppies to have a BPB in their boot sector. The BIOS parameter block tells the operating system how large the media is, and where the various areas of the media start and stop.
- The standard DOS MBR code for hard disk formatted media is written to the drive by FDISK.EXE, and always assumes a drive number of 80h. When a partitioned media is booted in the A: drive, the MBR code will find the active partition, but when it attempts to read the DBR, it will read from
drive 80h instead ofdrive 0. This results in the wrong drive being read. Assuming the MBR were able to read fromdrive 0, the BPB still would have a physical drive number filed set to 80h, which also prevents a hard drive DBR from being able to boot asdrive 0. Therefore, the present invention solves this problem by replacing the standard DOS MBR with a Dual Use Master Boot Record, referred to previously as DUMBR. In accordance with the DUMBR format, a standard MBR hard disk format is modified by replacing the code portion of Table 1 with the format shown in Table 6. The DUMBR code section contains a modified floppy BPB, and code which is capable of booting as either fixed or floppy. The difference between the DUMBR BPB, and a standard floppy BPB is the Reserved Sectors field. In the simplest case, the DUMBR Reserved Sectors field marks the entire Boot Track, and the first sector of the second track, which is the DBR, as reserved. More accurately, the hidden sectors field in the floppy BPB should be equal to the reserved sectors+the hidden sectors field of the hard drive BPB. A hard disk having DUMBR in the Boot Sector, rather than a standard DOS MBR will still have a hard drive BPB, in the first sector of the partition. Note that to create a DUMBR disk, a standard partitioned media need only have the boot sector replaced with a DUMBR.TABLE 6 (DUMBR) Byte Field Sample Offset Length Value Meaning 000h 3 N/A Jump over the BIOS parameter block bytes 003h 8 N/A System name field bytes 00Bh 51 N/A BIOS parameter block bytes 03Eh 384 bytes N/A Code portion of the Dual Use Boot Record 1BEh 64 N/A Partition Table bytes 1FEh 2 55h AAh Validation signature bytes - Referring to Table 6, DUMBR organization includes a jump for jumping over the floppy BIOS parameter block, a system name field, the floppy BIOS parameter block (see Table 4), the code portion for a Dual Use Boot Record, a Partition Table, and a validation signature.
- Referring to again to Table 4, there is shown an example of BPB. If the byte offsets 11h and 19h are set to 0, the BPB would be configured as a floppy BPB, in accordance with the present invention. The Reserved Sectors parameter listed at byte offset 03h is set to a value sufficient to reserve the Boot Track, and that portion of the active partition containing the DBR, including the hard disk BPB and the code portion of the DBR (see Table 2, byte offsets 00Bh and 00Eh), as well as any Reserved Sectors between the DBR and the first copy of the files allocation tables (FATφ). For example, if there are 63 sectors in the Boot Track, and with the code portion of the DBR, and the hard disk BPB of the DBR being located in the first sector of the next track, this Reserved Sectors parameter number is set to 64, i.e., 63+1. However, note that the Reserved Sectors parameter could simply be set to accommodate a convenient organization on the floppy BPB.
- Referring now to FIG. 1, there is shown the typical layout for a HCRM medium in accordance with the present invention. The first sector of the Boot Track, indicated by
bracket 42, is shown to contain afloppy BPB 20. The floppy BIOS parameter block typically is preceded by a jump instruction to allow the computer to jump directly toMBR code 22. A Partition Table follows in 24, with the areas comprising 20, 22, and 24 making up the first sector, or Boot Sector, of the media. The remaining sectors ofBoot Track 42 are then listed in thearea 26 and are usually empty, not by way of limitation, but simply by convention. The Boot Track, as previously discussed, comprises the Hidden Sectors region of a DOS formatted disk (see Table 3). - In the first sector of the HCRM medium's active partition, designated as44 in FIG. 1, is provided a DBR located in the Reserved Sectors region of a typical DOS formatted disk (see Table 3), and shown as
area 30. The BPB ofDBR 30, referenced as 00Bh in Table 2, is a hard disk, or “fixed disk” BPB, shown inarea 28 of FIG. 1. This hard disk BPB is preceded by a jump instruction to allow the system to jump over non-executable data inhard disk BPB 28 if the system were to boot as a floppy disk, in accordance with the present invention. Following the DBR is a first file allocation table (FAT φ) in thearea 32, with a second, duplicate of the files allocation table (FAT φ), copied into thearea 34 and designated asFAT 1. The root directory is provided in thearea 36, as per convention, followed by data stored in adata area 38, also as per convention. - Referring again to Table 4, the number of reserved sectors in the BPB is set forth in reference 2; with the number of “hidden sectors” set forth in reference 10. In
floppy BPB 20, the bracketedarea 40 shown in FIG. 1, indicates the area specified as “reserved”. The reserved sectors field offloppy BPB 20 differs from the reserve sectors field of a standard floppy in that all sectors prior to the first copy of the FAT (usually the entire Boot Track, and the DBR, which is the first sector of the second track) is specified as reserved. For thehard disk BPB 28, the bracketedregion 42 indicates the area specified as “hidden”; while the bracketed 44 marks the area is specified as “reserved”. It is assumed that there are no reserved sectors after the DOS boot record so that FATφ begins in the sector following the DBR. - Referring now to FIG. 2, there is shown a flow chart for a method for allowing HCRM media with at least one partition to be bootable with both hard and floppy drives of a computer. At the completion of the systems Power On Self Test (POST), INT 19 is called. By convention, INT 19 will attempt to read a Boot Sector from the default boot drive. If the Boot Sector is found, int 19h reads the Boot Sector into RAM at location 0:7C00h and jumps to 0:7C00h transferring control. If no Boot Sector is found on the default boot drive, INT 19 attempts to read the MBR from the drive. The flow chart of FIG. 2 shows the sequence of events in one particular embodiment of the invention after the system has loaded the Boot Sector of the HCRM media (the contents of bracketed
area 42 of FIG. 1, i.e.floppy BPB 20,MBR 22, Partition Table 24; collectively referred to as “DUMBR”) in 0:7C00h. of RAM. Beginning at thestart block 50 in FIG. 2, the first instruction is a jump instruction atblock 52; causing a jump overfloppy BPB 20 of FIG. 1, to begin execution of theMBR code 22 of FIG. 1. Next inblock 54 of FIG. 2, in accordance with convention, the DUMBR code, executing out of memory location 0:7C00h,copies 1 sector worth of data (512 bytes)from memory location 0:7C00h to another location in memory (by convention 0:600h) and transfers control to the new copy of itself at the new RAM location so that the DBR of the active partition may be subsequently copied to the computer RAM at address 0:7C00h. - Next, in
block 56,MBR code 22 depicted in FIG. 1 determines the drive number which the BIOS used for initiating the boot and then saves the result. There are a variety of techniques which may be utilized to accomplished this determination. By way of example, but not by way of limitation, FIG. 2(a) identifies one way that such a determination can be made. - Referring to FIG. 2(a), in
step 100 the system sets a count number for the number of attempts to be made in reading the Boot Sector of the media infloppy drive 0 into the RAM buffer. Next, INT 13 attempts to read the Boot Sector of the media infloppy drive 0 to the RAM buffer as indicated byblock 110. If INT 13 reports an error, shown byblock 112, the system decrements the count inblock 114 and determines if more attempts to boot are to be made inblock 116. If more retries exist the system loops back to block 110 to make another read attempt. Generally, a set number of retries is provided (such as 10) to allow for INT 13 errors that may result if the media is not properly spun up for example. If there is no INT 13 error report, the Boot Sector of the media in the floppy drive is read into RAM and the system moves to the next step, block 118, and compares inblock 120 the entire 512 bytes of the media's Boot Sector now in the RAM buffer to the 512 bytes of code copied into RAM location 0:600h instep 54 of FIG. 2. If the code loaded into the RAM buffer inblock 110 is not identical to the code residing in 0:600h, the system flags the boot drive as a floppy, 00h as shown inblock 122. If the code in the RAM buffer is not identical to the code residing in RAM location 0:600h, the boot drive is flagged as a hard drive, 80h as inblock 124. Note that the boot drive is also flagged as a hard drive if the system continues to receive INT 13 errors and the number of retries is exhausted, as shown inblock 116, thereby indicating that the proper data structure is not present in the media's Boot Sector allowing the system to read the media as a floppy drive. If there is no medium in thefloppy drive 0, then the BIOS will report that no medium is in the drive and the drive number will be determined to be 80h. - Referring again to FIG. 2, once the drive number which the BIOS used to initiate the boot is determined, the system flags the drive number, and moves to block58, where the MBR code initializes a pointer to the first entry in Partition Table 24 of FIG. 1 that was loaded into the RAM. The execution then branches to the
diamond block 60 and determines whether this entry in the Partition Table is the active partition. If the answer is no, then the execution branches to thediamond block 62 and determines whether all of the Partition Table entries have been examined. If there are more Partition Table entries, then execution branches block 64 and advances the pointer to the next entry in the Partition Table and returns to thediamond block 60. If there are no more Partition Table entries determined inblock 62, then the execution prints an error message and takes appropriate error recovery action. - If the computer determines in the
diamond block 60 that the pointer is set to the active partition, then execution branches to theblock 70 and reads the DBR of the active partition to the RAM buffer memory at address 0:7C00h. The first sector of the active partition will comprise a DOS boot record including a BPB that is correct for a hard disk boot. The execution then steps to thediamond block 72 where the system first looks to the drive number that was flagged in either step 122 or 124, of FIG. 2(a), which the BIOS used to initiate the boot process. If the drive number is 0, for a floppy drive designation, then it copies the modified floppy BPB of DUMBR, located in memory at 0:600h, and overwrites the hard disk BPB of the DBR that was loaded in the RAM at 0:7C00h, with the modified floppy BPB that is part of DUMBR. The DBR of the active partition now has a BPB with the correct physical drive number, and a Reserve Sectors field for a floppy drive boot. Then the execution goes to theblock 76 of FIG. 2 and jumps to the DBR to transfer control and the HCRM media boots as a floppy. - Alternatively, if the step in
diamond block 72 of FIG. 2 determines that the boot drive number is not 0, but the drive number is 80h, then execution jumps to 0:7C00h and DUMBR transfers control to the DBR in the RAM buffer at address 0:7C00h (see block 76) without any overwrite of the hard disk BIOS parameter block having been performed. - It should be noted that the present invention has been described in the context of a standard organization for disk media where the boot sector is located in the first sector of the first track. It would be obvious to one of ordinary skill in the art to locate the boot sector to other locations on the disk. Accordingly, the present invention is not limited to the boot sector being in a particular location on a disk.
- It should also be noted that the Dual Use Master Boot Record of the present invention could be separated from the high capacity medium that is being addressed and/or booted, as noted above. Accordingly, the floppy BPB, the MBR code, and the Partition Table could be stored permanently in another drive in the computer, or could be downloaded from a network, with the only requirement being that the correct BPB be used to describe the media correctly based upon the drive number from which the system BIOS initially attempted to boot.
- The presently disclosed data structure, method, and high capacity computer article of manufacturer support partitioned media in both a floppy drive and a hard drive, but require no code to be added to the BIOS, and require no translation of
INT 13h parameters. The present invention also removes the need for the operating system vendor to modify the operating system. The method, data structure and high capacity computer article of manufacture of the present invention provide a much higher degree of compatibility with existing operating systems compared to the interrupt 13h filtering method. The data structure of the present invention can be added to any partitioned media without affecting any of the data stored on the media. - For purposes of the present invention the term “floppy” drive means a computer drive for reading and/or writing to a computer readable medium which is removable from the drive and wherein the operating system in the computer typically will expect to read the BPB and the DBR code in the Boot Sector for the medium. A floppy BPB for such a medium will generally have a Hidden Sectors of 0 and a floppy drive number of 0. A floppy will not have a Partition Table.
- By the term “hard” drive is meant a computer drive for reading and/or writing to a computer readable medium which is hard, i.e., not ordinarily removable in the normal course of operation. It expects to find a Partition Table, in the Boot Sector of the medium. Note that the different partitions may be formatted for different operating systems. Typically the hard drive will have a BIOS drive code of 80h or higher, and will be referenced in byte offset 19h in the BPB. Typically a hard drive will also have a MBR code for determining from the Partition Table which partition is active, and then going to the head, cylinder, and sector location or logical block address on the medium where the active partition starts and reading the first sector of the active partition into the memory (RAM) of the computer. The first sector for the active partition of a bootable disk will contain a DBR which is comprised of the DOS boot record code and the hard disk BPB.
- The foregoing description of a preferred embodiment of the invention has been presented for the purpose of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. The embodiment was chosen and described in order to explain the principles of the invention and its practical application to enable one skilled in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims appended hereto, and their equivalents.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/960,181 US6449716B1 (en) | 1998-09-30 | 2001-09-20 | Dual use master boot record |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/163,359 US6308264B1 (en) | 1998-09-30 | 1998-09-30 | Dual use master boot record |
US09/960,181 US6449716B1 (en) | 1998-09-30 | 2001-09-20 | Dual use master boot record |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/163,359 Continuation US6308264B1 (en) | 1998-09-30 | 1998-09-30 | Dual use master boot record |
Publications (2)
Publication Number | Publication Date |
---|---|
US20020026571A1 true US20020026571A1 (en) | 2002-02-28 |
US6449716B1 US6449716B1 (en) | 2002-09-10 |
Family
ID=22589692
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/163,359 Expired - Lifetime US6308264B1 (en) | 1998-09-30 | 1998-09-30 | Dual use master boot record |
US09/960,181 Expired - Lifetime US6449716B1 (en) | 1998-09-30 | 2001-09-20 | Dual use master boot record |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/163,359 Expired - Lifetime US6308264B1 (en) | 1998-09-30 | 1998-09-30 | Dual use master boot record |
Country Status (5)
Country | Link |
---|---|
US (2) | US6308264B1 (en) |
JP (1) | JP2002526825A (en) |
AU (1) | AU6503199A (en) |
TW (1) | TW446909B (en) |
WO (1) | WO2000019310A2 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030191877A1 (en) * | 2000-05-31 | 2003-10-09 | Zaudtke Stephen M. | Communication interface system for locally analyzing computers |
US20050240821A1 (en) * | 2004-04-09 | 2005-10-27 | Martin Todd R | Hard drive reset cache |
US20060236399A1 (en) * | 2005-04-15 | 2006-10-19 | Samsung Electronics Co., Ltd. | Apparatus and method for restoring master boot record infected with virus |
US20070192581A1 (en) * | 2006-02-10 | 2007-08-16 | Lenovo (Singapore) Pte. Ltd. | Method and apparatus for tracking boot history |
US20080273550A1 (en) * | 2007-05-03 | 2008-11-06 | Dandekar Shree A | Auto-Detecting and Auto-Correcting System State Changes Before Booting Into Operating Systems |
US20080301424A1 (en) * | 2007-05-29 | 2008-12-04 | Barajas Gaston M | Intelligent Boot Services |
US20100153949A1 (en) * | 2008-12-15 | 2010-06-17 | Shara Susannah Vincent | Live streaming media and data communication hub |
US8090937B2 (en) | 2007-11-02 | 2012-01-03 | Dell Products L.P. | System and method for managing booting of an information handling system |
Families Citing this family (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6308264B1 (en) * | 1998-09-30 | 2001-10-23 | Phoenix Technologies Ltd. | Dual use master boot record |
US6493822B1 (en) * | 1999-09-16 | 2002-12-10 | International Business Machines Corporation | Foreign drive determination and drive letter conflict resolution |
EP1085396A1 (en) * | 1999-09-17 | 2001-03-21 | Hewlett-Packard Company | Operation of trusted state in computing platform |
US6751658B1 (en) * | 1999-10-18 | 2004-06-15 | Apple Computer, Inc. | Providing a reliable operating system for clients of a net-booted environment |
EP1498810B1 (en) * | 1999-10-21 | 2018-12-26 | Panasonic Corporation | A semiconductor memory card access apparatus, a computer-readable recording medium, an initialization method, and a semiconductor memory card |
US6931522B1 (en) * | 1999-11-30 | 2005-08-16 | Microsoft Corporation | Method for a computer using the system image on one of the partitions to boot itself to a known state in the event of a failure |
US6629192B1 (en) | 1999-12-30 | 2003-09-30 | Intel Corporation | Method and apparatus for use of a non-volatile storage management system for PC/AT compatible system firmware |
US6594663B2 (en) | 1999-12-30 | 2003-07-15 | Intel Corporation | Method and apparatus for implementing and maintaining a configuration database |
US6785806B1 (en) | 1999-12-30 | 2004-08-31 | Intel Corporation | Bios having macro/effector pairs for hardware initialization |
US6732261B2 (en) | 1999-12-30 | 2004-05-04 | Intel Corporation | Method and apparatus for implementing a register scan process |
US6424975B1 (en) * | 2000-01-07 | 2002-07-23 | Trg Products, Inc. | FAT file system in palm OS computer |
US7668938B1 (en) * | 2000-01-14 | 2010-02-23 | Microsoft Corporation | Method and system for dynamically purposing a computing device |
US8612553B2 (en) * | 2000-01-14 | 2013-12-17 | Microsoft Corporation | Method and system for dynamically purposing a computing device |
US6996706B1 (en) * | 2000-02-19 | 2006-02-07 | Powerquest Corporation | Booting an operating system or running other pre-boot code from a file stored under a different operating system |
GB2376763B (en) | 2001-06-19 | 2004-12-15 | Hewlett Packard Co | Demonstrating integrity of a compartment of a compartmented operating system |
GB0102518D0 (en) * | 2001-01-31 | 2001-03-21 | Hewlett Packard Co | Trusted operating system |
GB0102516D0 (en) * | 2001-01-31 | 2001-03-21 | Hewlett Packard Co | Trusted gateway system |
US6725294B1 (en) * | 2001-02-20 | 2004-04-20 | Lsi Logic Corporation | Installation and access of a device handler for a peripheral device in a computer |
GB2372592B (en) | 2001-02-23 | 2005-03-30 | Hewlett Packard Co | Information system |
GB2372595A (en) | 2001-02-23 | 2002-08-28 | Hewlett Packard Co | Method of and apparatus for ascertaining the status of a data processing environment. |
GB2376764B (en) * | 2001-06-19 | 2004-12-29 | Hewlett Packard Co | Multiple trusted computing environments |
GB2376762A (en) * | 2001-06-19 | 2002-12-24 | Hewlett Packard Co | Renting a computing environment on a trusted computing platform |
GB0114898D0 (en) * | 2001-06-19 | 2001-08-08 | Hewlett Packard Co | Interaction with electronic services and markets |
GB2378013A (en) * | 2001-07-27 | 2003-01-29 | Hewlett Packard Co | Trusted computer platform audit system |
GB2382419B (en) * | 2001-11-22 | 2005-12-14 | Hewlett Packard Co | Apparatus and method for creating a trusted environment |
DE10213802B4 (en) * | 2002-03-27 | 2010-02-18 | Wifag Maschinenfabrik Ag | Method of preserving image information of an imaged printing form |
US7194659B2 (en) * | 2002-12-10 | 2007-03-20 | International Business Machines Corporation | Method and system for detection and correction of entrance into an improper MBR state in a computer system |
JP4704660B2 (en) * | 2002-12-18 | 2011-06-15 | 株式会社日立製作所 | Storage device control device control method, storage device control device, and program |
US20050172111A1 (en) * | 2004-01-30 | 2005-08-04 | Marcak Scott B. | Automatic determination of geometric translation parameters for a disk device |
US7464250B2 (en) * | 2004-03-11 | 2008-12-09 | International Business Machines Corporation | Method to reduce disk access time during predictable loading sequences |
US7305539B2 (en) * | 2004-10-14 | 2007-12-04 | Sandisk Il Ltd. | Adaptive booting from mass storage device |
US8539587B2 (en) | 2005-03-22 | 2013-09-17 | Hewlett-Packard Development Company, L.P. | Methods, devices and data structures for trusted data |
CN100426228C (en) * | 2005-05-20 | 2008-10-15 | 鸿富锦精密工业(深圳)有限公司 | System and method for switching computer start sequence |
KR100750132B1 (en) * | 2005-09-27 | 2007-08-21 | 삼성전자주식회사 | Method and system for booting, updating software automatically and recovering update error, and computer readable medium recording the method |
US7475278B2 (en) * | 2005-11-15 | 2009-01-06 | International Business Machines Corporation | Method, system and computer program product for recovery of formatting in repair of bad sectors in disk drives |
KR101275752B1 (en) | 2005-12-06 | 2013-06-17 | 삼성전자주식회사 | Memory system and booting method thereof |
US8209527B2 (en) | 2006-10-26 | 2012-06-26 | Samsung Electronics Co., Ltd. | Memory system and memory management method including the same |
JP4978224B2 (en) * | 2007-02-08 | 2012-07-18 | カシオ計算機株式会社 | Photoelectric conversion device and display panel having the same |
US7945771B1 (en) * | 2008-07-10 | 2011-05-17 | Cms Products, Inc. | System and method for a software application to determine if the storage device and the operating system is an internal drive or an external drive |
JP5491675B2 (en) | 2011-03-03 | 2014-05-14 | 富士通株式会社 | Information processing apparatus and information processing apparatus control method |
KR101403305B1 (en) * | 2012-08-23 | 2014-06-05 | 한국전자통신연구원 | Method and apparatus for recovering partition using backup boot record |
US10191811B2 (en) * | 2015-08-13 | 2019-01-29 | Quanta Computer Inc. | Dual boot computer system |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2251323B (en) * | 1990-12-31 | 1994-10-12 | Intel Corp | Disk emulation for a non-volatile semiconductor memory |
JPH05289854A (en) | 1992-04-08 | 1993-11-05 | Olympus Optical Co Ltd | Access device for external storage device |
FR2718262B1 (en) * | 1994-03-31 | 1996-05-24 | Sgs Thomson Microelectronics | Modulo addressing buffer memory. |
US5701477A (en) * | 1995-03-30 | 1997-12-23 | Cirrus Logic, Inc. | Method and apparatus for master boot record shadowing |
US5715455A (en) * | 1995-05-18 | 1998-02-03 | International Business Machines Corporation | Apparatus and method for storing file allocation table efficiently in memory |
US5754853A (en) * | 1995-12-15 | 1998-05-19 | Dell Usa, Lp | System for executing utility programs while preserving the state of a native operating system |
US5694600A (en) | 1996-02-09 | 1997-12-02 | Iomega Corporation | Methods and apparatus for booting a computer having a removable media disk drive |
US5764593A (en) * | 1996-12-04 | 1998-06-09 | Keylabs, Inc. | Method and system for the interception and control of the computer boot process |
US5887163A (en) * | 1997-04-04 | 1999-03-23 | Compaq Computer Corporation | Method and apparatus for providing dual booting capabilities to a computer system |
US6308264B1 (en) * | 1998-09-30 | 2001-10-23 | Phoenix Technologies Ltd. | Dual use master boot record |
-
1998
- 1998-09-30 US US09/163,359 patent/US6308264B1/en not_active Expired - Lifetime
-
1999
- 1999-09-30 TW TW088116826A patent/TW446909B/en not_active IP Right Cessation
- 1999-09-30 WO PCT/US1999/022671 patent/WO2000019310A2/en active Application Filing
- 1999-09-30 JP JP2000572750A patent/JP2002526825A/en active Pending
- 1999-09-30 AU AU65031/99A patent/AU6503199A/en not_active Abandoned
-
2001
- 2001-09-20 US US09/960,181 patent/US6449716B1/en not_active Expired - Lifetime
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7082528B2 (en) * | 2000-05-31 | 2006-07-25 | Hewlett-Packard Development Company, L.P. | Enabling emulation of system functions by an external device |
US20030191877A1 (en) * | 2000-05-31 | 2003-10-09 | Zaudtke Stephen M. | Communication interface system for locally analyzing computers |
US20050240821A1 (en) * | 2004-04-09 | 2005-10-27 | Martin Todd R | Hard drive reset cache |
US7340593B2 (en) | 2004-04-09 | 2008-03-04 | Dell Products L.P. | Hard drive reset cache |
US7565523B2 (en) | 2005-04-15 | 2009-07-21 | Samsung Electronics Co., Ltd. | Apparatus and method for restoring master boot record infected with virus |
US20060236399A1 (en) * | 2005-04-15 | 2006-10-19 | Samsung Electronics Co., Ltd. | Apparatus and method for restoring master boot record infected with virus |
US7590834B2 (en) | 2006-02-10 | 2009-09-15 | Lenovo Singapore Pte. Ltd. | Method and apparatus for tracking boot history |
US20070192581A1 (en) * | 2006-02-10 | 2007-08-16 | Lenovo (Singapore) Pte. Ltd. | Method and apparatus for tracking boot history |
US20080273550A1 (en) * | 2007-05-03 | 2008-11-06 | Dandekar Shree A | Auto-Detecting and Auto-Correcting System State Changes Before Booting Into Operating Systems |
US7805598B2 (en) | 2007-05-03 | 2010-09-28 | Dell Products L.P. | Auto-detecting and auto-correcting system state changes before booting into operating systems |
US20080301424A1 (en) * | 2007-05-29 | 2008-12-04 | Barajas Gaston M | Intelligent Boot Services |
US9098448B2 (en) | 2007-05-29 | 2015-08-04 | Dell Products L.P. | Intelligent boot services |
US8090937B2 (en) | 2007-11-02 | 2012-01-03 | Dell Products L.P. | System and method for managing booting of an information handling system |
US20100153949A1 (en) * | 2008-12-15 | 2010-06-17 | Shara Susannah Vincent | Live streaming media and data communication hub |
US8706836B2 (en) * | 2008-12-15 | 2014-04-22 | Shara Susznnah Vincent | Live streaming media and data communication hub |
Also Published As
Publication number | Publication date |
---|---|
AU6503199A (en) | 2000-04-17 |
WO2000019310A2 (en) | 2000-04-06 |
US6308264B1 (en) | 2001-10-23 |
WO2000019310A3 (en) | 2000-06-08 |
US6449716B1 (en) | 2002-09-10 |
JP2002526825A (en) | 2002-08-20 |
TW446909B (en) | 2001-07-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6449716B1 (en) | Dual use master boot record | |
US6304965B1 (en) | Method and device for booting a CD-ROM from a single disk image having multiple emulations | |
US5692190A (en) | Bios emulation of a hard file image as a diskette | |
EP1133730B1 (en) | Method for flashing a read only memory (rom) chip of a host adapter with updated bios code | |
US6996706B1 (en) | Booting an operating system or running other pre-boot code from a file stored under a different operating system | |
US6279109B1 (en) | Computing system and operating method for booting and running a graphical user interface (GUI) with r/w hard drive partition unavailable | |
US5802363A (en) | Bios dynamic emulation of multiple diskettes from a single media | |
US6138179A (en) | System for automatically partitioning and formatting a primary hard disk for installing software in which selection of extended partition size is not related to size of hard disk | |
US5694583A (en) | BIOS emulation parameter preservation across computer bootstrapping | |
US5701477A (en) | Method and apparatus for master boot record shadowing | |
US5136711A (en) | System for multiple access hard disk partitioning | |
US5835760A (en) | Method and arrangement for providing BIOS to a host computer | |
US6993649B2 (en) | Method of altering a computer operating system to boot and run from protected media | |
EP1378830B1 (en) | Operating system selector and data storage drive | |
CA2117845C (en) | Method and computer system for integrating a compression system with an operating system | |
US6415383B1 (en) | Address offset feature for a hard disk drive | |
KR100637983B1 (en) | Computer system and method for preparing a computer-readable medium | |
US7162568B2 (en) | Apparatus and method for flash ROM management | |
KR20000034891A (en) | Computer system and method for accessing a computer-readable medium | |
KR100545654B1 (en) | A method for detecting defectless of file in disk after booting | |
JP2001290606A (en) | Information processor and recording medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: LTOS); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
REMI | Maintenance fee reminder mailed | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
SULP | Surcharge for late payment | ||
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: HIGHBRIDGE PRINCIPAL STRATEGIES, LLC, AS COLLATERA Free format text: GRANT OF SECURITY INTEREST - PATENTS;ASSIGNOR:PHOENIX TECHNOLOGIES LTD.;REEL/FRAME:025406/0604 Effective date: 20101123 |
|
AS | Assignment |
Owner name: PHOENIX TECHNOLOGIES LTD., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RICKEY, ALBERT E.;REEL/FRAME:028802/0232 Effective date: 19981125 |
|
AS | Assignment |
Owner name: MEP PLP, LLC, CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:HIGHBRIDGE PRINCIPAL STRATEGIES, LLC;REEL/FRAME:029291/0354 Effective date: 20121109 |
|
AS | Assignment |
Owner name: PHOENIX TECHNOLOGIES LTD., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MEP PLP, LLC;REEL/FRAME:029307/0590 Effective date: 20121112 |
|
AS | Assignment |
Owner name: CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGEN Free format text: IP SECURITY AGREEMENT - PATENTS;ASSIGNOR:PHOENIX TECHNOLOGIES LTD.;REEL/FRAME:031315/0700 Effective date: 20130927 |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
REFU | Refund |
Free format text: REFUND - PAYMENT OF MAINTENANCE FEE, 12TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: R2553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 12 |