Missing MBR options (solved)

[Mr. Rawnar]

When going through the vlite Unattended installation option, I am missing one thing that could be very valuable for all the dual boot people.

I am working with a dual boot system were Vista is for the games and Linux is for the rest of things I do behind my computer. So, I would like to make a strip-down version of Vista to boost performance and to shorten the boot-time. To check the vlited version I am using virtualbox to check if everything works. But with the virtual machine you can not emulate your specific hardware setup. So I have to install the vlited version on my machine (and properly several times), thus overwriting my MBR which holds GRUB. This means I have to repair my MBR by reinstalling GRUB from a rescue CD every time I check an vlited version. Easer will be the option that the Vista installation will not change the MBR. Does anyone know a way stop the windows installation overwriting the MBR?

Edited October 25, 2008 by Mr. Rawnar

[Mr. Rawnar]

There seem to be some interest in this subject, but a solutions is not jet posted.

So, I have been digging around in the boot.wim and install.wim files to find the software that is used to overwrite the MBR. I found the programs but you still want them after you have installed windows. Or is the boot.win image used for setting up a system to do the installation. Thus removing programs like bootrec, bootsect and fixboot that can change the MBR could also be an option.

Then I looked at the options that can be included in the unattend.xml file. I found nothing that could stop the installation from overwriting the MBR. What I did found is that if you use setup.exe to install windows or wipe clean the partitions during installation will overwrite the MBR. Off course the MBR is changed when the partition table is altered as the partition table is located in the MBR. So, an option will be to do the installation with-out the use of setup.exe or a modified version of it that doesn't effect the MBR.

Can someone help me that has more knowledge on the installation sequence that windows is using to do the installation.

[TranceEnergy]

Why not just create a separate partition for the boot loader? If done correctly, you wont ever have any multi booting issues ever again.

[Mr. Rawnar]

What you are implying is that the overwritten MBR by Vista will execute the bootloader on the active partition.

So, I can just install my GRUB bootloader not on the MBR but on the partition were it is installed and make this partition active. Optionally one can make a separate primary partition were only the bootloader is installed and make this partition active. Resulting in a system were the bootloader is not effected by a re-installation of an OS.

This is a much easier solution then ripping out the tools that overwrite the MBR. But still having an option to not overwrite the MBR during the installation would be something valuable.

Edited October 13, 2008 by Mr. Rawnar

[Mr. Rawnar]

It took me sometime to try the optie explained in the previous reply. It works, but one has to be carefull that the GRUB loader does not change the active partition. When the GRUB settings are automatically generated by your linux distribution, it will probably have the following lines in /boot/grub/menu.lst to load the windows OS.

root(hd0,0)

makeactive

chainloader + 1

boot

This will make the partition were windows is on the active partition, so after windows is booted GRUB will not load. By removing the 'makeactive' line solves the problem. Now I can start doing some serious vliting to make my optimal gaming OS.

[jaclaz]

Good ideas.

Wrong app to implement them.

If you multiboot with Vista, the easiest would be to add grub4dos (which is NOT GRUB) to the Vista BCD, see "method #5":

http://diddy.boot-land.net/grub4dos/Grub4dos.htm

http://diddy.boot-land.net/grub4dos/files/install.htm

http://diddy.boot-land.net/grub4dos/files/...all.htm#method5

jaclaz