EasyBCD also ships with NeoGrub, a customized build of Grub for Dos, which can be configured by editing C:\NST\menu.lst with the standard GRUB syntax for booting into the needed Linux or BSD partitions.


EasyBCD can chainload the Mac OS X Darwin bootloader in order to boot into OS X on another partition or physical disk. It doesn't require that Darwin be installed to the bootsector of the OS X partition.

• Grub (Legacy)

• New Grub2
• also LILO

             Vista Boot Pro is a tool allowing to make live together several Windows systems
      VistaBootPro allows so to edit Boot Configuration Dates blind (BCD)of  WindowsVista,            containing information on the parameters  of the system.
      VistaBootPRO is a utility designed to provide a user friendly interface for making changes to the Windows Vista boot menu and the Boot Configuration Data store. It is particularly useful when dual booting with “Earlier versions of Windows”. Being able to recover the ability to boot to Windows Vista is another great function that it provides.
     

Anyone who has attempted using the command line based applications; bcdedit.exe and bootsect.exe will appreciate the ease with which VistaBootPRO can be used. VistaBootPRO 3.3 has the ability to disable the driver signing requirements in Windows Vista 64-Bit versions, so that unsigned device drivers can be used for testing purposes.

                                                        Download VISTA BOOT PRO
Other features include changing the name of the Operating Systems shown in the boot menu, adding an Operating System to the boot menu and repairing the Windows Vista boot configuration data. Advanced settings include backing up and exporting your boot loader configuration data and modifying various other details of the boot menu entries including the ability to remove ‘rogue’ BCD entries which sometimes occur with multiple installations of Windows Vista.

               






The Boot Configuration Data (BCD) store contains boot configuration parameters and controls how the operating system is started in Microsoft® Windows Vista™ and Microsoft® Windows Server™ Code Name "Longhorn" operating systems.



These parameters were previously in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile RAM (NVRAM) entries (in Extensible Firmware Interface–based operating systems). You can use the Bcdedit.exe command-line tool to affect the Windows® code which runs in the pre-operating system environment by adding, deleting, editing, and appending entries in the BCD store.



Bcdedit.exe is located in the \Windows\System32 directory of the Windows Vista partition


 


 The Bcdedit.exe command-line tool can be used to add, delete and edit entries in the BCD store which contains objects. Each object is identified by a GUID (Globally Unique Identifier). Every drive or partition on the system will have its own GUID and could be {ntldr} (to describe a drive or partition on which a pre- Windows Vista operating system), {default} (to describe the drive or partition containing the current default operating system), or {current} (to describe the current drive or partition one is booted to), or for example {c34b751a-ff09-11d9- 9e6e-0030482375e7} (to describe another drive or partition on which an operating system has been installed).

Bcdedit.exe is located in the \Windows\System32 directory of the Windows Vista partition and can be accessed only from the Command Prompt which is found on the Windows Vista start menu at Start>All Programs>Accessories




BCD was created to provide an improved mechanism for describing boot configuration data. With the development of new firmware models (for example, the Extensible Firmware Interface (EFI), an extensible and interoperable interface was required to abstract the underlying firmware. This new design provides the foundation for a variety of new features in Windows Vista (for example, the Startup Repair tool and Multi-User Install shortcuts.)