Grub4dos Guide - Experimenting with Grub4dos

To test installing and using Grub4dos without risking any damage to your current operating system, use a Virtual Machine. With the widespread availability of hardware virtualising software, it's a relatively straightforward process to create a hard disk image for testing.

For those comfortable with command line tools, QEMU is a freeware machine emulator ported to Windows. QEMU does not need to be installed and can be used as a portable application - simply unzip the contents of the download to a location of your choice and run from a command prompt. Alternatively use the GUI version - QEMU Manager.

If enough free hard disk space is available, large image files can be used and the disk image can be partitioned and set up for multibooting.

QEMU Walkthrough - Installing Windows XP

NOTES

The following was tested with QEMU version 0.9.0. File/folder paths in this version of QEMU are separated with a forward slash / (not a backslash \ as used in windows based systems).
If you do not have a Windows XP installation disc, the following walkthrough can be adapted to install DOS/MSDOS; Linux; and Windows 9x/NT/2000/XP (Windows Vista is not compatible with QEMU).
The walkthrough only covers basic QEMU usage - a variety of other features are available, including networking with the host operating system, and other virtual machines.

Creating a Disk Image

qemu-img.exe help output (from command qemu-img.exe -h)

qemu-img version 0.9.0, Copyright (c) 2004-2007 Fabrice Bellard
usage: qemu-img command [command options]
QEMU disk image utility

Command syntax:
  create [-e] [-b base_image] [-f fmt] filename [size]
  commit [-f fmt] filename
  convert [-c] [-e] [-f fmt] filename [-O output_fmt] output_filename
  info [-f fmt] filename

Command parameters:
  'filename' is a disk image filename
  'base_image' is the read-only disk image which is used as base for a copy on
    write image; the copy on write image only stores the modified data
  'fmt' is the disk image format. It is guessed automatically in most cases
  'size' is the disk image size in kilobytes. Optional suffixes 'M' (megabyte)
    and 'G' (gigabyte) are supported
  'output_filename' is the destination disk image filename
  'output_fmt' is the destination format
  '-c' indicates that target image must be compressed (qcow format only)
  '-e' indicates that the target image must be encrypted (qcow format only)

Supported format: qcow2 vvfat vpc bochs dmg cloop vmdk qcow host_device raw

To create a raw disk image, open a command prompt in the same directory as QEMU and use the following syntax qemu-img.exe create [filename] [size].

Where [filename] is the disk image (with path) to create - e.g. C:/test.ima. Relative paths can also be used - e.g. test.ima will create the image file test.ima in the same directory as QEMU, /Images/test.ima will create the image file test.ima in the QEMU subdirectory Images.
Where [size] is the disk image size in kilobytes. Optional suffixes 'M' (megabyte) and 'G' (gigabyte) are supported - e.g. 1024M would create an image file 1024 MB in size.

To create a 3GB image file (XP.ima) at the root of the C: drive - enter the command
qemu-img.exe create C:/XP.ima 3G

Installing the Guest Operating System

qemu.exe help output (from command qemu.exe -h).

QEMU PC emulator version 0.9.0, Copyright (c) 2003-2007 Fabrice Bellard
usage: qemu [options] [disk_image]

'disk_image' is a raw hard image image for IDE hard disk 0

Standard options:
-M machine      select emulated machine (-M ? for list)
-fda/-fdb file  use 'file' as floppy disk 0/1 image
-hda/-hdb file  use 'file' as IDE hard disk 0/1 image
-hdc/-hdd file  use 'file' as IDE hard disk 2/3 image
-cdrom file     use 'file' as IDE cdrom image (cdrom is ide1 master)
-boot [a|c|d|n] boot on floppy (a), hard disk (c), CD-ROM (d), or network (n)
-snapshot       write to temporary files instead of disk image files
-no-quit        disable SDL window close capability
-no-fd-bootchk  disable boot signature checking for floppy disks
-m megs         set virtual RAM size to megs MB [default=128]
-smp n          set the number of CPUs to 'n' [default=1]
-nographic      disable graphical output and redirect serial I/Os to console
-audio-help     print list of audio drivers and their options
-soundhw c1,... enable audio support
                and only specified sound cards (comma separated list)
                use -soundhw ? to get the list of supported cards
                use -soundhw all to enable all of them
-localtime      set the real time clock to local time [default=utc]
-full-screen    start in full screen
-win2k-hack     use it when installing Windows 2000 to avoid a disk full bug
-usb            enable the USB driver (will be the default soon)
-usbdevice name add the host or guest USB device 'name'

Network options:
-net nic[,vlan=n][,macaddr=addr][,model=type]
                create a new Network Interface Card and connect it to VLAN 'n'
-net user[,vlan=n][,hostname=host]
                connect the user mode network stack to VLAN 'n' and send
                hostname 'host' to DHCP clients
-net tap[,vlan=n],ifname=name
                connect the host TAP network interface to VLAN 'n'
-net socket[,vlan=n][,fd=h][,listen=[host]:port][,connect=host:port]
                connect the vlan 'n' to another VLAN using a socket connection
-net socket[,vlan=n][,fd=h][,mcast=maddr:port]
                connect the vlan 'n' to multicast maddr and port
-net none       use it alone to have zero network devices; if no -net option
                is provided, the default is '-net nic -net user'

-tftp prefix    allow tftp access to files starting with prefix [-net user]
-redir [tcp|udp]:host-port:[guest-host]:guest-port
                redirect TCP or UDP connections from host to guest [-net user]

Linux boot specific:
-kernel bzImage use 'bzImage' as kernel image
-append cmdline use 'cmdline' as kernel command line
-initrd file    use 'file' as initial ram disk

Debug/Expert options:
-monitor dev    redirect the monitor to char device 'dev'
-serial dev     redirect the serial port to char device 'dev'
-parallel dev   redirect the parallel port to char device 'dev'
-pidfile file   Write PID to 'file'
-S              freeze CPU at startup (use 'c' to start execution)
-s              wait gdb connection to port 1234
-p port         change gdb connection port
-d item1,...    output log to /tmp/qemu.log (use -d ? for a list of log items)
-hdachs c,h,s[,t]  force hard disk 0 physical geometry and the optional BIOS
                translation (t=none or lba) (usually qemu can guess them)
-L path         set the directory for the BIOS, VGA BIOS and keymaps
-kernel-kqemu   enable KQEMU full virtualization (default is user mode only)
-no-kqemu       disable KQEMU kernel module usage
-std-vga        simulate a standard VGA card with VESA Bochs Extensions
                (default is CL-GD5446 PCI VGA)
-no-acpi        disable ACPI
-no-reboot      exit instead of rebooting
-loadvm file    start right away with a saved state (loadvm in monitor)
-vnc display    start a VNC server on display
-option-rom rom load a file, rom, into the option ROM space

During emulation, the following keys are useful:
ctrl-alt-f      toggle full screen
ctrl-alt-n      switch to virtual console 'n'
ctrl-alt        toggle mouse and keyboard grab

When using -nographic, press 'ctrl-a h' to get some help.

Assuming your CD drive is mounted as "D:", insert the Windows Installation CD into your drive and use the following command to boot from it (change D: to reflect your own CD drive letter if required) -
qemu.exe -L . -m 256 -boot d -cdrom D: -hda C:\XP.ima.

Where -L sets the path to the bios and keymap files (in this case -L . sets the path as the directory from which qemu is being run.
Where -m 256 sets the emulated machines virtual memory as 256MB.
Where -boot d sets the CD as the boot device (-boot a = floppy device; -boot c = hard disk).
Where -cdrom D: sets the cdrom device as the physical device D: (can also use cd image files - e.g. -cdrom C:\XP.iso.
Where -hda C:\XP.ima mounts the disk image file C:\XP.ima.

QEMU should boot from the install CD. The disk image can be partitioned and formatted during the XP installation - QEMU is slow in comparison to some of the other software listed above, so the install may take some time.

Once the operating system has been installed, the Guest OS can be started using the following command -
qemu.exe -L . -m 256 -boot c -hda C:\XP.ima.

Sharing Files With The Guest Operating System

Once the guest operating system has been installed, we will need to find a way to share files with it. There are a number of methods for doing so, some are easier to set up than others.

Mount a CD (or CD Image)

Mounting a physical CD drive was covered earlier - simply use the syntax -cdrom [drive:] (where [drive:] is letter allocated to the device).

Alternatively, create a CD image file (.iso) and mount it using the syntax -cdrom [file] (where [file] is the image filename with path - remember to use a forward slash / for the path). To create an .iso image, download the command line tool mkisofs from here. The following is a simple method of using mkisofs -

Create folder C:\mkisofs and copy mkisofs.exe to it.
Create folder C:\mkisofs\root.
Copy any files you want to include in the .iso image to C:\mkisofs\root.
Open a command prompt in the mkisofs folder, and enter the command -
mkisofs.exe -R -o C:\xp.iso root
where C:\xp.iso is the name (and path) of the image to create, and root is the root directory of the CD.

Now use the command qemu.exe -L . -m 256 -boot c -hda C:\XP.ima -cdrom C:\xp.iso when starting the Guest OS, and all files will be available on the Guest OS CD-ROM drive.

Mount The Guest OS Disk Image

It is possible to mount a disk image on the Host operating system using various tools. To use ImDisk (freeware tool available here), download and install the ImDisk package. Now right click on the image file you want to mount (e.g. C:\XP.ima) and choose option Mount as ImDisk Virtual Disk - this will open a "Mount new virtual disk" window.

As we are mounting a hard disk type image with MBR, we will need to use a file offset. Enter 63 and check Blocks option to mount the first partition on the hard disk image created earlier. You will need to calculate the offset for any other partitions within the image manually. Please note - different disk image formats such as .vmdk might use a different offset value for the first partition.

Select a drive letter (this will be the mount point for the disk image) - the default will be the first available drive. All other options can be left at their default values. When you have finished, click on OK. Open Explorer, the disk should now be mounted as the drive letter selected earlier. If, after installing the operating system, you are prompted to format the disk when accessing it in explorer on the Host OS, then you have used an incorrect offset value for ImDisk.

Mount a Physical Hard Disk

"Hard disks can be used with the syntax: `\\.\PhysicalDriveN' where N is the drive number (0 is the first hard disk).

WARNING: unless you know what you do, it is better to only make READ-ONLY accesses to the hard disk otherwise you may corrupt your host data (use the `-snapshot' command line so that the modifications are written in a temporary file)."

To use the first hard disk (physical disk (hd0) in grub4dos terms), use command
qemu.exe -L . -m 256 -boot c -hda C:\XP.ima -hdb \\.\PhysicalDrive0 when starting the Guest OS. Please note that backslashes (e.g. \\.\PhysicalDrive0) were used in testing, as recommended in qemu-doc.html. Other sources suggest that forward slashes should be used - e.g. //./PhysicalDrive0. It is not possible to mount individual partitions - only the whole of a hard disk.

During testing a USB flash drive was mounted using the command qemu.exe -L . -m 256 -boot c -hda C:\XP.ima -hdb \\.\PhysicalDrive1. The drive was mounted as a local disk on the Guest OS. Files copied to the drive from the Guest OS were not displayed in Explorer on the Host system until the disk was removed and remounted.