jharris1993
Member
Here's a real head-scratcher for you.
Though it's not something that you would want to use every day, there are occasionally times when it would be PRETTY DARN CONVENIENT to be able to edit the listing you see in the "view" window.
In my case, I very frequently install dual-boot configurations on my computers - Win7 and Ubuntu Linux. Of course, neither one plays well with others, (at least Grub/Grub2 tries to play well), which is one of the reasons EasyBCD is so darned convenient.
Also, for asthetic reasons, I prefer the Win7 boot loader menu.
Of course, installing Ubuntu next to Windows clobbers Win7's carefully crafted Master Boot Record. So, prior to installing Ubuntu (while the live CD is running), I save a copy of the Windows MBR to a file, and stash it away I then do the install - which overwrites the MBR - forcing the boot to Ubuntu instead of Windows.
So, I let it do the reboot, let it boot into Ubuntu, and - when everything has settled down - I make another backup copy of the MBR, save it using a different name, and stash that away too. I then take the stashed copy of the original Windows boot loader and put it back where it belongs (copy it back where it belongs is a better way of putting it.)
I then boot back into Windows and fire up my Trusty Ole' Copy of EasyBCD. I create a 2nd boot entry for Ubuntu, and save it.
Here's the nub:
EasyBCD boots a Grub2 install via a carefully crafted "hack" chainloader. It works, but (IMHO) jumps thorugh a few hoops that it really doesn't need to.
The path to the chainloader file is hard-coded as C:\NST\AutoNeoGrub0.mbr
I would then copy my "linux.mbr" file to the same directory. Unfortunately, I cannot ask EasyBCD to use MY file instead of the one IT wants to use. So, I am forced to rename my mbr file to "AutoNeoGrub0.mbr" so that EasyBCD can find it. (Or, manually hack at the BCD Store via the command-line using BCDedit!! :?? )
That being done, selecting the "Ubuntu" entry boots directly into the Grub2 boot loader and gives me the standard - though inelegant - Grub2 boot menu.
This is one situation - I have run into others, just as odd-ball, just as annoying, and requiring the same kind of bait-and-switch hack, or hacking at the BCD store, that I describe here.
Being able to simply go into the listed content of the BCD store and change one or two little things as if using Notepad, would be so convenient that it would not be funny. Of course, I realize that this would be an very advanced option with a significant risk of borking the system ( :S ) - that, perhaps, should be hidden away in a "tools" menu somewhere. Or, like Avira does, require the user to switch to a special "advanced/expert" mode. Or, maybe, require the use of an enabling command-line parameter within the shortcut to EasyBCD. (which would require the user to have enough of a clue to know how to do this. . . .)
So, waddaya think? Idea? Or am I just outta my mind.
Jim (JR)
Addendum:
Hmmmm. . . .
Just saw a reference to the 2.2 beta - allowing you to select the target of a grub2 install - which might be worth investigating. However my suggested feature would be handy too.
Though it's not something that you would want to use every day, there are occasionally times when it would be PRETTY DARN CONVENIENT to be able to edit the listing you see in the "view" window.
In my case, I very frequently install dual-boot configurations on my computers - Win7 and Ubuntu Linux. Of course, neither one plays well with others, (at least Grub/Grub2 tries to play well), which is one of the reasons EasyBCD is so darned convenient.
Also, for asthetic reasons, I prefer the Win7 boot loader menu.
Of course, installing Ubuntu next to Windows clobbers Win7's carefully crafted Master Boot Record. So, prior to installing Ubuntu (while the live CD is running), I save a copy of the Windows MBR to a file, and stash it away I then do the install - which overwrites the MBR - forcing the boot to Ubuntu instead of Windows.
So, I let it do the reboot, let it boot into Ubuntu, and - when everything has settled down - I make another backup copy of the MBR, save it using a different name, and stash that away too. I then take the stashed copy of the original Windows boot loader and put it back where it belongs (copy it back where it belongs is a better way of putting it.)
I then boot back into Windows and fire up my Trusty Ole' Copy of EasyBCD. I create a 2nd boot entry for Ubuntu, and save it.
Here's the nub:
EasyBCD boots a Grub2 install via a carefully crafted "hack" chainloader. It works, but (IMHO) jumps thorugh a few hoops that it really doesn't need to.
The path to the chainloader file is hard-coded as C:\NST\AutoNeoGrub0.mbr
I would then copy my "linux.mbr" file to the same directory. Unfortunately, I cannot ask EasyBCD to use MY file instead of the one IT wants to use. So, I am forced to rename my mbr file to "AutoNeoGrub0.mbr" so that EasyBCD can find it. (Or, manually hack at the BCD Store via the command-line using BCDedit!! :?? )
That being done, selecting the "Ubuntu" entry boots directly into the Grub2 boot loader and gives me the standard - though inelegant - Grub2 boot menu.
This is one situation - I have run into others, just as odd-ball, just as annoying, and requiring the same kind of bait-and-switch hack, or hacking at the BCD store, that I describe here.
Being able to simply go into the listed content of the BCD store and change one or two little things as if using Notepad, would be so convenient that it would not be funny. Of course, I realize that this would be an very advanced option with a significant risk of borking the system ( :S ) - that, perhaps, should be hidden away in a "tools" menu somewhere. Or, like Avira does, require the user to switch to a special "advanced/expert" mode. Or, maybe, require the use of an enabling command-line parameter within the shortcut to EasyBCD. (which would require the user to have enough of a clue to know how to do this. . . .)
So, waddaya think? Idea? Or am I just outta my mind.
Jim (JR)
Addendum:
Hmmmm. . . .
Just saw a reference to the 2.2 beta - allowing you to select the target of a grub2 install - which might be worth investigating. However my suggested feature would be handy too.
Last edited: