Yeah, sure, I agree with you.
[IT, systems] It's just something I do sometimes, pick up like that for fun,
and (sometimes) assume people know more / know enough to 'read between the lines'.
Not saying they can't, saying they have also a whole lot of info which doesn't necessarily
pertain to the asked subject.
Thus if I start something, I'll assume people will have bits of info regarding the topic at hand.
Possibly I do a good bit of searching before, so the amount of info can become
difficult to piece together. All the more to explain.
For instance, here I assumed someone would know what I mean by grub4dos Winvblock patch.
For me there aren't 42 codes that link Grub4dos and WinVBlock when mentioning mapping to memory.
Am I right in thinking
map --mem /images/XP.img (hd0)
map --mem (rd)+4 (0x55)
write (0x55) #GRUB4DOS\x00v=1\x00XP.img\x00\x80\x00
gives info to the WinVBlock driver?
Am I right in thinking it gives the info to enable XP seeing the image?
This is based on an image (XP.img).
If I want to give a (md) (mapped as (hdxx))
a drive letter in the OS (XP), how do I do that?