The idea being you can have several operating systems and choose which to boot using the flag.
The MS_DOS MBR is a universal booter in that it loads and runs the partition boot code for the partition whose boot flag is set. If you want to test that your Mint works you can change the boot flag to sda2. There should be no reason to reinstall Mint if the problem is just with the bootloader. For some reason it isn't configured correctly, it seems. I think I would be inclined to reinstall EasyBCD. Please let me know how I could do this better! I'm willing to reinstall Mint if I have to (at this point I can't reinstall Windows, so any solutions I'm hoping will leave Windows be). This point determines where GRUB will be installed. Also, certain anti-virus programs have been known to mess with the contents of the MBR, so installing GRUB in another location will ease the maintenance headache associated with your system. That portion of the hard drive is known as the Master Boot Record (MBR).
Why? Because whenever you reinstall or update Windows 7, its installer will overwrite anything it finds in the portion of the hard drive where critical boot-related programs are installed.
When dual-booting Windows 7 and a Linux distribution on a computer with one hard drive, the best option is to have Windows 7′s boot manager be the primary boot manager.
Installing Ubuntu on the same hard drive throws another boot manager into the mix, so the most important decision you are going to make about this, is which boot manager (Windows 7′s boot manager or Ubuntu’s) do you want to be responsible for primary boot operations? Now that you know what the overall goal is, how do you get from here to there? First, understand that if you have a computer running Windows 7, that Windows 7′s boot manager is responsible for making sure that the system boots.
If you can think of a better way to install Mint alongside Windows 7, please let me know! If I were to install Mint again, should I instead overwrite the Windows 7 MBR? I'm a little hesitant to do that after reading the following from an Ubuntu guide also found on the website: Do you think there's an easy fix for this? If not, it's no big deal - I'm willing to reinstall Mint a second time if I have to as I haven't even been able to boot into my first installation attempt of Mint! So now this finally brings me to my next question. lst files? I checked the EasyBCD website, and I found an interesting tutorial posted in 2011 for installing Ubuntu alongside Windows 7, but I'm not sure if that applies to my Mint configuration: I used EasyBCD v2.1.1 - perhaps the older versions used. Please let me know what I can do next! I have an Asus Aspire 4750G.
Why am I not seeing the correct GRUB 2 boot menu? Why am I seeing a grub command line interface instead? I tried using the “boot” and “kernel” commands, but obviously I don’t know enough to use this command line properly. However, despite making sure I followed every step correctly, when I select the Linux Mint menu item I created in the Windows 7 boot menu, I don't get the correct GRUB 2 menu. If you had done everything correctly according to the tutorial up until that point, selecting Mint in the Windows boot menu should bring you to the GRUB 2 boot menu, and from there you can select Mint and boot into Linux without a problem. Nobody has answered me yet, so wanting an answer faster, I'm turning to the forumsĮssentially the tutorial has you install Mint on other partitions and then use a tool in Windows called EasyBCD to add a menu entry for Mint in the Windows 7 boot menu. If you scroll down to the comments section you can see I left a comment related to this issue as "Jason S".
So I recently tried installing Linux Mint 13 alongside my previous install of Windows 7 by following this fantastic tutorial at :