I didn't notice this was an old thread.
After using BING and BIBM for many years, I have finally moved away from them for GPT disk systems. I have several comments pertinent to this thread:
1) No one has mentioned how much easier dealing with Windows installers is with GPT disks compared with MBR.
On a GPT system, the Windows installer will only write to the selected install partition, the EFI partition, and the Microsoft Reserved partition. If you install when the MS boot manager is the default boot method, the new Windows system will be added to the MS boot manager. The installed partition can be copied to another location to create a clone and a new entry added to the MS boot manager using your favorite BCD editor. The copying and BCD editing can even be done with BIBM from a flash drive, if you can boot legacy/MBR from your UEFI system easily.
On an MBR system, the Windows installer typically (for us in this forum) will not know the correct situation on all disks as most or all disks have more than four partitions. It will gladly write on any "unused" space. It will also gladly add boot files to other Windows partitions or even just ordinary partitions that contain a Drive:\\Windows folder or maybe even Drive:\\Program Files folder. Both of these are relative disasters, although recoverable(but it is way too much trouble to take ownership of all those \boot files and delete them). I now won't use a Windows installer on an MBR system with EMBRM/BIBM unless there is only one drive plugged in and the Windows installer is given access to all of it. Of course this is a small price to pay for the convenience of BIBM.
2) For a boot manager replacement for GPT/UEFI look at rEFInd. There is a lot of information there. All BIOSes are different, my limited experience is that it is best to leave the MS boot manager at the default EFI\Microsoft\Boot\bootmgfw.efi and use the EFI shell to put rEFInd at another location following http://www.rodsbooks.com/refind/install ... l#efishell
See more at https://wiki.archlinux.org/index.php/Un ... l_Commands
As near as I can tell, no one has figured out how to boot Windows implementations without using the Windows Boot Manager, so you just need rEFInd to choose between WBM and (your favorite linux loader).
3) Given the end of comment #2 above, BIBM for GPT/UEFI would only need to be able to boot GRUB2, SYSLINUX and Windows Boot Manager.
4) If comment #3 is unattainable, it would be great to offer a bibm.efi executable with the current partioning/backup utilities that could be booted directly on UEFI systems.
5) @eldiener re 250Gb systems. I always thought one of the main assets of multibooting was to separate all your program, data and swap files away from the OS. Then all your OSes share programs and data. To install a new OS you just install it and make sure the logical drives with your files are mounted at the correct locations. Of course it helps if you don't use any non-programs that need to be installed rather than just run from wherever they are located(Most/many non-portable Windows programs don't need to be installed). Bye bye anything from Apple, Google, Microsoft....