Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have had a dual boot setup on my computer for some time now. I achieved this by first installing Windows 7, and then installing Ubuntu. Grub is the bootloader and I have had no problems.
I decided I've been working with so many XP machines that I wanted to have an install to play around with (there was getting to be too much overhead on the VMs). I made a third primary partition and installed XP to that.
At this point, only XP would boot (as I expected). I threw in Boot-Repair-Disc and ran the automated fix. This restored the original grub boot menu I had before, and at this point Ubuntu would boot fine, but Windows 7 would not boot when selected. Using the Windows 7 install disc I ran the startup repair, and this got the Windows 7 selection working again. However, I cannot see the XP install anymore Of course it is still there and intact, but running update-grub from Ubuntu didn't find the install, and the Windows 7 startup repair didn't find it during its 'searching for other Windows installations' phase. I even tried to add the menu entry manually to grub.cfg pointing to the partition XP is installed on.
So now I am not sure how to proceed. I wonder if XP needs to be added to the MBR, as it was somehow overwritten by Boot-Repair-Disc? Though I don't understand why or how. I was thinking perhaps I need to use the XP startup repair, followed by the Windows 7 startup repair, followed by Boot-Repair-Disc? I'm really not sure though, and don't want to get myself in any deeper lol so I figured it's about time to call in the cavalry and appeal to the gurus!
Anyone who can help shed some light on the topic, please do! TIA!
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
By default each windows system expect that he is on c drive : or the linux notification the sda1
As you installed windows xp as the last windows system you have to make him believe that he is on sda1 too
You can to this by drive mapping
If you do not know how to do it , post the partitioning of you're drive EQ the result of fdisk -l (L lower case }
Oddly, my XP installation is on the F: drive, and it sees my Windows 7 partition as the C: drive. Doesn't cause any problems since that's the way it installed, but I am pretty sure I will have issues if I try to change it.
I do not know how to do drive mapping lol, you lost me for a second there. Here is the output of the cmd you requested though:
root@hostname:~# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005e098
Device Boot Start End Blocks Id System
/dev/sda1 1 13087 105117696 83 Linux
/dev/sda2 13087 36366 186985472 7 HPFS/NTFS
/dev/sda3 * 36366 46809 83886080 7 HPFS/NTFS
The first partition is Ubuntu, then 7, then XP. After that is about 100GB of unallocated space, which I will probably format to an extended partition (which shouldn't cause any issues I don't think, but if I'm wrong please tell me lol).
windows bootloaders are backward compatible so Windows 7 should have detected the xp install. Don't know why it didn't. If you have windows 7 on sda2 and xp on sda3, maybe sda2 should be marked active/bootable. Try going to the site below and reading the instructions, downloading and running the bootinfoscript from Ubuntu (or any Linux Live CD) and posting the output, a results.txt file. It will contain detailed information on your partitions and boot files.
Looks like XP has plonked it's boot files on sda2.
Try copying/moving boot.ini ntldr and NTDETECT.COM to sda3.
Then boot buntu, run 'os-prober' which should show all three, followed by update-grub to write the correct grub.cfg.
Not strictly true - they are capable are recognising a prior release is installed during the install process. After that it can get ugly.
Without having to reinstall Win7:
- mark the XP partition as hidden.
- boot the Win7 DVD and get into recovery centre and restore the boot environment. Boot it to ensure it loads.
- hide the Win7 partition, unhide XP and do likewise.
- unhide Win7, fix grub - os-prober should find both now as both will have valid loader code for the appropriate system; Win7 via the BCD, XP via ntldr.
Looks nice in theory, but I've never installed Windoze systems "out of order" when I've needed dual boot.
I tried marking the 7 partition as active (I assume sda2=2nd partition and sda3=3rd partition, etc.), but that didnt seem to affect anything.
I copied the three files you listed to the 3rd partition / sda3 / the XP partition, and ran os-prober; this is the output:
/dev/sda2:Windows 7 (loader):Windows:chain
/dev/sda3:Microsoft Windows XP Professional:Windows1:chain
Followed by update-grub:
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.6
Found initrd image: /boot/initrd.img-3.2.6
Found linux image: /boot/vmlinuz-2.6.32-21-generic
Found initrd image: /boot/initrd.img-2.6.32-21-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda2
Found Microsoft Windows XP Professional on /dev/sda3
Could it be!? I think that may have done it! I'm in Linux right now, so let me reboot and check it out. Will post back soon!