A detailed Grub4dos guide is available here. If you are not familiar with Grub4dos usage I recommend that you read this guide - in particular the section on using the map command (here).
Grub4dos will search for and load the configuration file menu.lst if it is present on a supported device. The root device is set as the device from which menu.lst is loaded - this can impact on the paths (for devices and files) used within the configuration file. The method used to install Grub4dos and the location of the Grub4dos loader grldr and/or menu.lst will determine which device is set as root. Having more than one instance of grldr and/or menu.lst (e.g. on different physical devices or partitions) can cause problems if you do not understand how grub4dos works - particularly if using hardcoded paths.
It is possible to use relative paths by using the find --set-root command to search for a unique file - ensure that the file being searched for is not present on multiple devices. See here
For more detail about file paths see here
The configuration file entries used in this guide should work provided that any files searched for using the find --set-root command are present on only one device. Having the same file on multiple devices could result in the wrong file being located - you may need to experiment if this is the case. Grub4dos also includes a command line interface (see here). I recommend using the command line for testing purposes - the working commands can then be added to a configuration file.
The following menu entry has been copied from Walkthrough 1 -
Breaking down these commands line by line, as they would be entered from the command line -
Assuming that the file my_disk.ima is located at the root of device (hd0,0) the following menu entry could also be used -
or if my_disk.ima is located at the root of the same device as the loaded menu.lst file -