Grub4dos Guide - Examples


There is often more than one way to boot an operating system under Grub4dos - there is no "correct" method. This is illustrated in the following examples, in which MSDOS is booted from the first partition on the first hard disk (hd0,0).

Example 1

NOTE(s) - Using the root command will fail if the filesystem is not recognised.

Feedback when inputting the above commands -

grub> chainloader (hd0,0)+1

grub> root (hd0,0)
  Filesystem type is fat, partition type 0xe

grub> boot_

Example 2

Feedback when inputting the above commands -

grub> chainloader (hd0,0)+1

grub> rootnoverify (hd0,0)

grub> boot_

Example 3

Feedback when inputting the above commands -

grub> root (hd0,0)
  Filesystem type is fat, partition type 0xe

grub> chainloader +1

grub> boot_

Example 4

Feedback when inputting the above commands -

grub> find --set-root /io.sys
  (hd0,0)
  Filesystem type is fat, partition type 0xe

grub> chainloader +1

grub> boot_


The command chainloader (hd0,0)+1 can be substituted with chainloader (hd0,0)/io.sys in examples 1 and 2, and the command chainloader +1 can be substituted with chainloader /io.sys in examples 3 and 4. E.g. -

Feedback when inputting the above commands -

grub> find --set-root /io.sys
  (hd0,0)
  Filesystem type is fat, partition type 0xe

grub> chainloader /io.sys
Will boot MS-DOS 7.x from drive=0x80, partition=0x0(hidden sectors=0x3f)

grub> boot_

As previously noted in the guide, booting in this way makes no use of the MBR code, and no use of the bootsector code, as the operating system file is chainloaded directly. This means that, as long as the partition data in the bootsector is intact, grub4dos can recover a system when the booting code is corrupted, or points to another system file.


    PREVIOUS    INDEX    NEXT