Set my firmware to boot from legacy (CSM support) and booted Grub4dos from a USB drive.
Using GRUB4DOS 0.4.5c 2016-01-18 and entering the following at the commandline, followed by the [TAB] key...
grub> root (hd1,...returned the following -
Possible partitions are: Partition num: 0, Filesystem type is fat, partition type 0xEE Partition num: 2, Filesystem type is ntfs, partition type 0xEE Partition num: 3, Filesystem type is ntfs, partition type 0xEE Partition num: 4, Filesystem type is ntfs, partition type 0xEE Partition num: 5, Filesystem type is ntfs, partition type 0xEEPartition 1 (grub4dos device (hd1,1)) is a Microsoft Reserved partition (MSR) and is not displayed in the Grub4dos output.
Partitions are numbered sequentially from (hd#,0). As this is a GPT disk, there is no extended partition with logical volumes - consequently there is no jump from (hd#,2) to (hd#,4).
I was able to map a .vhd from (hd1,2) to memory and successfully boot from it using the following commands (please note wonko, that these were entered at the commandline as per your recommendation(s)) -
map --mem (hd1,2)/test.vhd (hd0) map --hook root (hd0,0) chainloader +1 bootI also noticed in the readme for GRUB4DOS 0.4.6a 2018-09-19 that bootlace.com (and bootlace64.com) now support a --gpt switch ("Install the grldr.mbr to the GPT partition type device."). I'm not in a position to test this at the moment - does anyone know how this works. E.g. where is the grub4dos MBR code written on a GPT disk - it would appear to be too large to fit in the MBR only.
GRUB4DOS 0.4.6a 2018-09-19 also contains grldr.pbr - presumably this is partition boot record code? Any information on usage and why/when this might be used instead of grldr.mbr?