Well, the point is the "d:\images".
"d:" is the drive letter assigned to a partition by your current OS.
I can only guess that you have a XP system with just one big partition on the internal hard disk (that has drive letter C: ) and the USB stick with one partition that gets "D:".
When grub4dos (or any other bootmanager for that matters) boots there are no drive letters, but only drives (numbered from 0) and partitions on them (as well numbered from 0).
Normally your internal hard drive will be (hd0) in grub4dos, but since you are going to boot from the USB stick, the stick will become first drive (hd0), and your internal hard drive will become (hd1).
The first partition on first disk is (hd0,0).
Thus, \images directory on USB stick will become (hd0,0)/images
So you can do:
color black/cyan yellow/cyan
timeout 30
default 0
title dosfloppy.gz (grub4dos) 0
root (hd0,0)
map --mem /images/dosfloppy.img.gz (fd0)
map --hook
root (fd0)
chainloader (fd0)/IO.SYS
title dosfloppy (grub4dos) 0
root (hd0,0)
map --mem /images/dosfloppy.img (fd0)
map --hook
root (fd0)
chainloader (fd0)/IO.SYS
title unhook memory
map --unhook
title myfloppy.gz (grub4dos) 1
root (hd0,0)
map --mem /images/myfloppy.img.gz (fd0)
map --hook
root (fd0)
chainloader (fd0)+1
title myfloppy (grub4dos) 1
root (hd0,0)
map --mem /images/myfloppy.img (fd0)
map --hook
root (fd0)
chainloader (fd0)+1
title myfloppy.gz (memdisk) 2
root (hd0,0)
kernel /images/memdisk.gz
initrd /images/myfloppy.img.gz
title myfloppy (memdisk) 2
root (hd0,0)
kernel /images/memdisk.gz
initrd /images/myfloppy.img
You can substitute the
root (hd0,0)
with something like:
find --set-root /images/myfloppy.img
Basically the sequence is as follows:
1) the disk booted by BIOS is current "root"
2) the entries "root (hd0,0)" or "find --set-root /images/myfloppy.img" can be omitted ONLY if you never loop back through grub4dos from a booted .img, the idea is to make sure that you can set correctly root, no matter what you booted from/attempted before.
3) once "root" has been established, the floppy image is mapped in memory to first floppy disk (fd0)
4) memory mapping is hooked, i.e. it is "set" definitely
5) root is established on the mapped floppy
6) either the system file or bootsector oon the floppy is chainloaded
When using memdisk steps 3 to 6 are replaced by "kernel /images/memdisk.gz" and "initrd /images/myfloppy.img.gz" as they are performed "internally" by memdisk.
What I often advise is to experiment with command line, press "c" when booted to grub4dos to access it.
Example type:
find (
and press the TAB key, you will see a list of available devices, like hd0 hd1 cd rd
press h and press the TAB key again
press 0 and press the TAB key again
press 0)/ and press the TAB key again
press ENTER
(you'll see a list of directories and files on (hd0,0) )
You can also manually type any of the above listed menu.lst entries, pressing ENTER every line, in order to see the "feedback" grub4dos gives.
Once you have entered all the lines in an entry, type
boot
and press ENTER
to actually boot (the "boot" command is implied as last command in a menu.lst entry, but must be given explicitely from command line)
Read around for the various commands available and experiment a bit....
jaclaz
,
