Originally Posted by awesomejt
I'm writing this because I ran into an issue regarding dual booting XP Pro and FC4. I found the solution and want to warn others so they can make the adjustments accordingly if they experience issues also.
Ok, let's start with my specs:
Athlon 64 3800, socket 939
2 GB PC3200 RAM (4x512)
Primary SATA drive: 250 GB Western Digital drive -- XP Pro 64-bit edition
Secondary SATA drive: 200 GB Seagate Barracuda drive -- reserved for FC4
IDE 0: Pioneer 16x DL DVDRW
IDE 1: DVD/CDRW combo
Ok, enough boasting. :-)
Installation and Issue:
I installed Windows XP Pro 64-bit ed. first (like normal). Works fine --except I had to get some beta 64-bit drivers from Gigabyte. Now, I run the x86-64 install of FC4 -- it sees both disks and I choose to install on my second SATA drive (200GB Seagate). Install process goes smoothly -- I use the default grub setup like normal and pick and shoose my favorite package groups and away I go. I go to reboot the box after what appeared to be a successful install only to be booted directly back into Windows -- no grub menu asking which OS to choose or anything -- just Windows.
Resolution:
I found several posts about this same type of setup causing issues all the way back to the RedHat 5 days all the way up to FC3. There seems to be some debate as to weather grub installed on the MBR of the primary boot drive is a good thing these days (forces use of grub, which might cause problems if Windows needs to be reinstalled -- which I do once a year due to bit-rot). So, I used the old fashioned method:
1. I re-installed FC4 and used the "Advanced" settings for Grub -- and told grub to "only install grub on first sector" of the linux harddrive instead of the MBR of the first harddrive. Ok, go through the rest of install as normal.
2. Reboot system at end of installation process, but put in "recovery disc" in order to force booting into your newly setup Linux system. I opted to enable network connectivity during the recovery setup (I don't have a floppy or a FAT32 common partition, so I will FTP my boot image somewhere else).
3. chroot /mnt/sysimage (set the installed linux system as your base context/environment)
4. Figure out where grub is installed -- df (grub *should* be installed at /boot -- so whatever device has /boot is where grub is locaated -- mine was /dev/sdb1 .
5. dd -if=/dev/sdb1 of=fc4boot.bin bs=512 count=1
(if = input device -- device where grub is installed
of= output file -- name it whaever you want)
6. Move the "bin" file just created to a location that will be accessable to your windows system -- that can be a floppy disk, FAT partition, or FTP location.
7. Remove recovery disc, reboot system (type "exit" until system reboots)
8. Allow system to boot into Windows.
9. Retrieve that "bin" file created while in Linux -- I called mine fc4boot.bin and downloaded it from a common FTP location. I put the file in my root c:\.
10. Backup boot.ini file before making changes or live dangerously.
11. Edit c:\boot.ini file -- add following line to the end of the file:
c:\path\to\thatfile.bin="Fedora Core 4"
Example, my line looks like:
c:\fc4boot.bin="Fedora Core 4"
12. Save boot.ini
13. Reboot system, you should have a choice to load Windows XP or Fedora Core 4.
14. Just for grins, choose Fedora Core 4 and make sure system boots as normal.
15. Reboot again, verify Windows still boots fine (which it should).
This works for me. It uses the Windows supplied bootloader. If you reload Windows, just backup your boot.ini and "bin" file before doing so. This should avoid the whole "reinstalling Windows killed my grub" problem in the future.
Enjoy.
I love you i have 4 of the same size hardrives but i wanted to try Fedora, installed and no go! linux couldnt write to ntfs partitions so i was at a loss but now i have another solution very excited woooooooooot!!
i say we should sticky this post.


Reply With Quote
