Ahh, ok..so that's how it works. I was thinking before that maybe it modifies the Vista PBR slightly, so it knows to look for a file called BOOTMGR.HnS, instead of the standard bootmgr. But, I see now that it still looks for the bootmgr file, only the bootmgr file was replaced with grldr, which was renamed to bootmgr, which in turn points to bootmgr.hns, which is actually the real bootmgr.There's no grldr except in the HnS installation folder because the way HnS works is by renaming Vista's bootmgr to bootmgr.hnS (yes that's the real one) and usurping the boot process by putting grub4dos (grldr) in its place (renamed as bootmgr).
That way the normal Vista MBR/IPL looks for its own bootmgr but is fooled into executing a disguised grub. Grub then chains the renamed Vista bootmgr or NTLDR as required having done the necessary hiding/unhiding first.
But, if that's the case, and it calls up the Grub4Dos GRLDR, renamed as BOOTMGR, then shouldn't the BOOTMGR (i.e. the disguised grub loader) be on the C: partition, in his case, since it is "active" and "system"? Because, according to the screenshot posted of his D: partition contents, it exists instead in the root of that partition, which is not "active"...
I would think that what would have to be there (i.e. in the D: partition's root) is the (real) bootmgr, which was renamed to BOOTMGR.HnS. But, it seems the fake BOOTMGR was placed on D: instead.
Could that be part of his problem?