FedoraForum.org - Fedora Support Forums and Community
Page 2 of 3 FirstFirst 123 LastLast
Results 16 to 30 of 34
  1. #16
    Mesto Guest
    Quote 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.
    Last edited by Mesto; 3rd August 2005 at 07:38 AM.

  2. #17
    gtr225 Guest
    What I don't get about this dual boot issue is that with the same hw configuration I was able to setup FC and I would get the GRUB menu and choose whether to start with windows or fc. Now when it boots it goes straight to windows after reinstalling FC.

  3. #18
    Brian W Guest
    Thank you so much for these instructions awesomejt. I'm sure this post saved me many hours of time and much frustration. I had been running FC3 on my notebook until my HDD crashed, at which point I bought a larger HDD and decided to dual boot XP and FC3. Your instructions worked perfectly, but I'll note the following tweaks for others who may be interested...

    Step 2: I inserted FC3 Disc 1 instead of the FC4 Recovery Disc. I then chose the recovery option from the menu and followed the on-screen instructions until reaching the command prompt.

    Step 5: The dd command didn't like the dash in the -if argument. So my command in FC3 looked like:

    Code:
    dd if=/dev/hda2 of=fc3boot.bin bs=512 count=1
    Step 6: Moved my fc3boot.bin file to a vfat partition, which I had created during the FC3 installation (Windows XP mapped the vfat drive automatically).

    Step 11: I edited the boot.ini file a little further so that FC3 would be the default and would boot after only 10 seconds rather than 30. It looks like this:

    Code:
    [boot loader]
    timeout=10
    default=c:\fc3boot.bin
    [operating systems]
    c:\fc3boot.bin="Fedora Core 3"
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP" /fastdetect
    For added protection, I set the fc3boot.ini file to be hidden so that I wouldn't inadvertently clobber while it in Windows.

    Thanks again for the great post...

    Brian
    Last edited by Brian W; 15th August 2005 at 04:55 PM.

  4. #19
    mcunca Guest
    Quote 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.
    Hi everyone,

    Kinda same config, basically- amd 64 512 ram, 2 hdd IDE, on primary master Windows Server 2003 and on second one trying to install FC4 64.
    Installing goes smoothly, grub on the first sector of /boot, then reboot, linux rescue, dd, copy fedora.bin onto C:\fedora.bin, edit boot.ini, reboot and Windows is booting ok, as per fedora it tells me something weird about ntoskrnl.exe missing or corrupt.
    now, on second thougths I realised that I had instructed (during fedora installation) grub to boot Windows by default, and that might be an issue.
    Can somebody confirm?
    more than that, if i open fedora.bin in notepad , at the end of the file it says something like:GRUB Geom Hard Disk Read Error » ´Í¬< uôÃ
    TIA

    PS. I'll try to reconfiguer grub to boot only Fedora to see if that is the resolution and I'll come with some feedback. Meanwhile I'd appreciate some ideas...
    Thanks again!

  5. #20
    mcunca Guest
    it's gettin' more and more frustrating, I am not being able to make it work. I tried installing grub on the mbr but in this way Windows freaks out... Actually that's why I want to use nt loader. But now I am out of ideas...
    I'd appreciate any advice
    Thanks

  6. #21
    Brian W Guest
    Hey mcunca... It sounds like you had a problem in the boot.ini file and then compounded that by installing GRUB on the MBR.

    You might try this...

    Insert your Windows XP Installation CD and choose the recovery mode option. I don't recall the exact steps for this (it's been a while) but your goal is to reach a Windows command prompt. Once there, type:

    Code:
    FDISK /MBR
    That should enable you to boot XP. Then, follow the instructions posted by awesomejt. When you (re)install GRUB on the first sector of your /boot partition, keep in mind that GRUB does not need to know anything about Windows.

    Hope this helps. Keep us posted...

    Brian

  7. #22
    mcunca Guest
    Thanks Brian,
    Yep I think it was a windows/mbr issue because after a little more reserch, I realised that the windows boot partition was on the first HDD on an extended parition - duh. I reconfigured
    all (install windows on a primary partition) then reinstall fedora core 4 did all the stuff and finally I can dual boot using the nt loader nice and smoothly.
    Thanks for your support,

    M

  8. #23
    Join Date
    Oct 2005
    Location
    Surbiton, UK
    Posts
    57
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Great post - thank you
    Exactly my problem, simple steps did exactly what you said they would - problem solved

  9. #24
    BlackNinjaVirus Guest

    Easiest way for me to dual boot XP-FC4

    In 3 easy steps:

    1. I installed Windows XP, with 2 half partitions, and Windows is on the last half.
    2. Installed Fedora on the first half of the partition.
    3. Installed GRUB on MBR (master boot record).

    GRUB Menu displays:
    Windows XP
    Fedora Core 4

    That is all!!


    EDIT: P.S. GRUB is better developed than NT Loader. GRUB reads all, NT loader reads Windows NT only.
    Last edited by BlackNinjaVirus; 24th October 2005 at 11:48 PM.

  10. #25
    mio-fc Guest
    Anyway to convert to this option without reinstallling both windows and Fedora ?

    I am currently operating with grub on sda only (the normal setup) and both installation are brand new (still missing some small stuff on both) so I do not want to reinstall...

  11. #26
    BlackNinjaVirus Guest
    Quote Originally Posted by mio-fc
    Anyway to convert to this option without reinstallling both windows and Fedora ?

    I am currently operating with grub on sda only (the normal setup) and both installation are brand new (still missing some small stuff on both) so I do not want to reinstall...
    More info please?

  12. #27
    mio-fc Guest
    Sorry... Dell D610 Laptop 1 SATA harddisk. First installed Win XP then FC4 with GRUB as bootlloader.

    SDA1 fat16 System partition from dell 94 mb
    SDA2 ntfs Win XP 26 Gb
    SDA3 FAT32 1,2 GB
    SDA 4 Extended LVM
    SDA5 ext3 /boot
    SDA6 LVM /

    I was wondering if I could re-instate ntloader and point to FC4 from the boot.ini

  13. #28
    BlackNinjaVirus Guest
    I'm not an expert in NT loader, since I use GRUB now.
    But I remember in my ealrier days of dual boot, I had to reinstall Windows for the NT Loader to be installed. [Unless somebody here knows how to install it off of the Windows CD]

    And then create a pointer to FC4 from the boot.ini [using the .BIN file from beginning of this Thread]

  14. #29
    marq Guest
    1) Put in your windows CD and boot to it.
    2) When asked what you want to do go ahead and enter the recovery console.
    3) Login to your system
    4) Once prompted with a cursor type fixmbr (yes) fixboot (yes) (not exactly like that just saying you'll want to answer yes to each commands question)
    5) Boot into windows just to be sure it works *
    6) Grab your Fedora Core recovery disk (or download the iso and burn it)
    7) Boot to it and install grub on the mbr of the hard drive _without_ the ntloader

    * I ran into a weird problem trying this the other day but I think I actually fdisk /mbr in dos before attempting the steps above. Anyways the problem was that when I attempted to boot back into windows it was missing ntoskernel.dll or something. Checked the %SYSTEMROOT%\system32 folder and there it was... Not sure why that funky error happened but I think it had something to do with how fdisk /mbr works... Just don't use it and use the fixmbr and fixboot from the windows recovery console and you should be good.

    EDITED: I noticed that I said the final two steps could be skipped, but that was not true, if you fix your MBR you need to reinstall grub on a drive without the MBR and remake the *.bin file!
    Last edited by marq; 27th October 2005 at 05:48 AM.

  15. #30
    BlackNinjaVirus Guest
    Yes, I remember using FIXMBR and FIXBOOT, because of using Windows Vistas (which messed up my system) and the NTLoader was reinstated.

    Thanks, marq.

Page 2 of 3 FirstFirst 123 LastLast

Similar Threads

  1. dual monitor resolution issue
    By Cryp in forum Using Fedora
    Replies: 2
    Last Post: 20th September 2009, 05:00 PM
  2. FC5 Dual Head ATI Radeon 7500 Resolution Issue
    By zerovice in forum EOL (End Of Life) Versions
    Replies: 11
    Last Post: 12th July 2006, 03:21 PM
  3. boot-up issue involving screen resolution
    By axaf in forum Using Fedora
    Replies: 1
    Last Post: 23rd August 2005, 04:35 PM
  4. Another dual boot issue
    By pills_PMD in forum Installation, Upgrades and Live Media
    Replies: 0
    Last Post: 5th February 2005, 08:09 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •