Unfortunately this is all pretty new to me and I'm trying to make sense of it.
Yep, I expected as much.
Point is that you are *somehow* (the actual *somehow*, i.e. Syslinux/isolinux/pxelinux being essentially Icecube
) one of the two grub4dos "executables".grldr
is *something* that can be chainloaded from:
- grub4dos's own MBR: grldr.mbr
- a partition bootsector
- NTLDR through an entry in BOOT.INI
- another bootloader (like Syslinux/Isolinux/pxelinux )
is *something* else that is at the same time:
- a DOS executable, that can be run from DOS as any other
- a "linux kernel" that can be loaded by ANYTHING that can load a Linux kernel (among which Syslinux/Isolinux/pxelinux , but also GRUB legacy, etc. etc.)
The difference is that grldr
accepts NO "command line parameters", whilst grub.exe
does accept them.
BOTH "executables" read by default a very small "internal", embedded configuration file (or menu.lst) that actually searches for the "real", "external" menu.lst on the available drives.
Right now your setup, by loading grldr, attempts to load a menu.lst in the available drives (which evidently do not comprehend the location where your actual menu.lst is
So, there are TWO possible ways to have it load your menu.lst:
- one - more complex - is to pass to the grub4dos "executable" a command line parameter (and to do this you need to "switch" to using grub.exe instead of grldr)
- the other - easier - is to actually replace the embedded menu.lst with the contents of your currently "external" menu.lst
If you try going back to the links I posted earlier at the light of the above info, matter should become clear.
Mind you that my intervention is *limited* to answer the specific question:
How can I load a menu.lst in a grub4dos loaded from Syslinux through COMBOOT pxechain.com?
and nothing else, i.e. whether the contents of your menu.lst will "work" or not is another thing....