sambul12
Distinguished Member
Could you guys clarify how EasyBCD "Insert MBR" feature works?
I've an HD with 4 partitions with Win7, WinXP, Win2008 Server and Ubuntu installed respectively. I assume, OS installers placed MBR separately on each partition, so all 4 MBRs are there. Is that correct? Or each subsequent install erased previous OS MBR at the beginning of the whole drive?
Now, when I install EasyBCD, and select a default partition to boot from, and added other boot partitions to the boot menu, what next? Should I insert manually the MBR of the default boot OS with EasyBCD? What will happen with other MBRs? Anything at all will remain on each partition to show its bootable, or everything boot related will be stored on default boot partition in the Boot Store?
What's the difference btw EasyBCD and Plop in that sense? Plop won't change any boot records on any partition at all? EasyBCD is a great program, I really enjoy it, but what are the advantages of using it and messing up with boot records instead of using Plop only? For example, if I want to boot in a Virtual Machine guest from a physical bootable host partition, changed with EasyBCD to non-default bootable, how I can do that? Am I correct, that partition will have no MBR and can't boot on its own in a VM? Can I fix it without affecting the host's existing boot order?
I've an HD with 4 partitions with Win7, WinXP, Win2008 Server and Ubuntu installed respectively. I assume, OS installers placed MBR separately on each partition, so all 4 MBRs are there. Is that correct? Or each subsequent install erased previous OS MBR at the beginning of the whole drive?
Now, when I install EasyBCD, and select a default partition to boot from, and added other boot partitions to the boot menu, what next? Should I insert manually the MBR of the default boot OS with EasyBCD? What will happen with other MBRs? Anything at all will remain on each partition to show its bootable, or everything boot related will be stored on default boot partition in the Boot Store?
What's the difference btw EasyBCD and Plop in that sense? Plop won't change any boot records on any partition at all? EasyBCD is a great program, I really enjoy it, but what are the advantages of using it and messing up with boot records instead of using Plop only? For example, if I want to boot in a Virtual Machine guest from a physical bootable host partition, changed with EasyBCD to non-default bootable, how I can do that? Am I correct, that partition will have no MBR and can't boot on its own in a VM? Can I fix it without affecting the host's existing boot order?
Last edited: