#UEFI DISK MAP DRIVERS#
#UEFI DISK MAP DRIVER#

What we have been doing on the other thread, had you missed it, was finding out that the BOOTMGR (at least the one form Windows 7) does NOT find a BCD of a grub4dos mapped drive (hard disk drive, i.e. There is NO boot.ini used in grub4dos, maybe you mean menu.lst, but as already said when experimenting is a good thing that you use command line. I recall another thread around here doing just this kind of fooling windows through identical disk signature of image and real device, can't recall. Needless to say, the signatures are exactly the same. What's going wrong? If it could boot from a ramdrive such as memdisk or wimboot (see and previous posts), then why not from grub4dos direct mapping?Īn aside : I had a false start when it booted, but that was because the actual VHD whose image I had dumped into the partition was still attached to the VM. Then I typed 'boot' + enter, but I got bootmgr error :ĭescription : An error occurred while attempting to read the boot configuration data I could not interpret the message after mapping very well. Still not being used to boot.ini, I use the shell to type in and get the following :Īnd the response when I pressed TAB, saying 'the possible partitions are :' or something to that effect. MBR disk 80MB : standard MS MBR, 1 partition, holding bootmgr+BCD gpt3 : FAT partition holding Grub2, Grub4dos files.But the last I checked, GRUB4DOS didn't have GPT knowledge, although that's possibly changed, now.įacing some trouble booting windows from an MBR disk in a GPT partition, after mapping it to (hd2) using Grub4Dos.

So you can use such partitions-as-disk-images right now. This mapping is certainly used by WinVBlock. In GRUB4DOS, you can indeed map a virtual disk from a contiguous range of sectors on a physical disk.

#UEFI DISK MAP DRIVERS#

So does any of the existing drivers like FileDisk, FiraDisk, WinVBlock, etc. Can be useful both for booting and maybe other things.

#UEFI DISK MAP DRIVER#

I think it'll be quite easy to make such a mapping module for boot managers like Grub/Grub4dos, as well as a driver for Windows and perhaps Linux.

It was envisaged that non-GPT-supporting OSes can be booted from such a mapped virtual HDD. Intended to be mounted as a separate virtual device. īasically it means that the GPT partition contains a full MBR disk in it. This is a partitions-inside-a-slice configuration. More details were only obtained from FreeBSD mailing list archive : Mbr | A partition that is sub-partitioned by a Master Boot Record (MBR). Partition containing a legacy MBR | 024DEE41-33E7-11D3-9D69-0008C781F39FĪ better description from the gpart manual : The official GPT specification lists a partition type with a peculiar description :

Uefi disk map