Windows 7 + Fedora16 startup Item

Not long ago, a classmate installed a windows 7 + Fedora16 Dual System on his computer. As a result, he didn't want to use Fedora16, so he formatted the disk of Fedora16 on windows. After the restart, neither Windows7 nor Fedora16 can be entered. The interface has been parked at the place entered by grub. Simply enter winPE, and PE re-installs the C drive, but it is installed on the ghost. After the installation, the restart result still cannot enter Windows 7,

Not long ago, a classmate installed a Windows 7 + Fedora 16 Dual System on his computer in the lab. As a result, he didn't want to use Fedora 16, so he simply formatted the disk of Fedora 16 on windows. After the restart, neither Windows 7 nor Fedora 16 can be entered. The interface has been parked at the place entered by grub. Simply enter winPE, and PE re-installs the C drive, but it is installed on the ghost. After the installation, the restart result still cannot enter Windows 7 or grub boot. Later, I went directly to PE and used the repair startup Item software to rewrite MBR. Now I can enter Windows 7 and automatically rewrite the input table after entering Windows 7, driver. The following is an explanation of the entire process.

The MBR has a partition table (64 bytes) and a boot program (446 bytes). grub is installed on this 446 byte. Grub has powerful functions. grub supports multi-system startup and control transfer. It is not enough to store all the light points. There are two phases in loading Boot Loader (grub here): Stage1 and Stage2. In the Stage1 stage, the Program on the Boot Loader is loaded, that is, grub is loaded, but no Loader-related configuration files are installed here. In the Stage2 stage, the configuration file is read through gurb, such as/boot/grub/menu. lst or grubcon. fig: the configuration file provides a lot of information. A more intuitive information is the system selection menu during startup (detailed configuration file will be introduced again ). This can be understood as the problem above. After Linux is deleted, grub in Stage1 is loaded, but the configuration file will not be loaded during the Stage2 process. Therefore, grub's system boot function and control transfer function cannot be used.

So why cannot I restore the boot after ghost is installed? At the beginning, ghost clones the data on the hard disk, that is, it re-writes the image file to the C drive on Windows 7, and the Boot Loader of drive C is rewritten. However, MBR does not belong to any operating system, and there is no write capacity for MBR. Therefore, the Boot Loader on the MBR is still the original grub program, and the configuration file under Fedora 16 will still be read.

The last step is to repair the MBR after entering the PE. The explanation here is to rewrite the MBR, but it will certainly not be grub anymore. It is a windows boot program.