I used the form (hd0,msdos1) instead of (hd0,1) because
1. That is what you get shown if you ls to find the partitions on the drive
2. That is what you get offered with tab autocompletion
3. That is what ubuntu use in their scripts
Well, it is very possible that there is a new "feature".
Last time I tried using the thingy, it had an output similar to this:
grub> chainloader (hd0, <tab>
Possible partitions are:
Partition hd0,1: Filesystem type ext2, Label KARMIC, Last mofication time 2009-12-23 04:02:13 Wednesday, UUID 6d6af125-7087-4frb6-afbc-14ddeeb465b8
Partition hd0,2: Filesystem type ext2, Label JAUNTY, Last mofication time 2009-12-25 04:39:45 Friday, UUID 6d6af125-7087-4frb6-afbc-14ddeeb465b8
Partition hd0,3: Filesystem type ext2, Label INTREPID, Last mofication time 2009-12-25 04:39:45 Friday, UUID 6d6af125-7087-4frb6-afbc-14ddeeb465b8
Partition hd0,5: Filesystem type ext2, Label HARDY, Last mofication time 2009-12-28 10:577:17 Monday, UUID 6d6af125-7087-4frb6-afbc-14ddeeb465b8
Partition hd0,6: Unknown filesystem
grub> chainloader (hd0,2)+1
example taken from:
Still as far as I know, this makes little sense:
However, for now I still want to try to boot from grub2 via grldr not via grub.exe.
You want to boot grub4dos, the suggested way to do so is to use grub.exe, and it works normally. (this means that the problem is ALREADY solved).
Since grldr can normally be booted from the bootsector of the volume (just like NTLDR or BOOTMGR), I see no issues however in theory in installing the grub4dos bootsector to that volume.
An example is given here (link previously posted by steve6375):
So, yes, your entry should be:
menuentry "Test grldr on dev/sda1"
To test if there is an issue with the bootsector, chaniload grub.exe from GRUB2 , and from this grub4dos chainload the partition:
if it re-cycles to grub4dos the bootsector and grldr are OK.
P.S.: JFYI the Owner and Admin of the board found NOT fun "quote pyramids" and in order to avoid them set the board so that this - while still possible - has become more difficult.
The fact that this harasses any member of the board attempting to properly quote a previous post of course seems like seen as "collateral damage".