For Creating The Image of MBR and Partition Table image from linux to windows

127 views
Skip to first unread message

chirag patel

unread,
Apr 6, 2006, 3:21:12 AM4/6/06
to VG...@googlegroups.com
hi All,
I wants to create the image of windows MBR using dd  ,so if any body have any idea  then reply.


This is Chirag Patel,
Have a nice day

New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.

nilesh vaghela

unread,
Apr 6, 2006, 9:09:07 AM4/6/06
to VG...@googlegroups.com
try this,

http://www.cpqlinux.com/ddbackup.html

Nilesh
--
Nilesh Vaghela

nilesh vaghela

unread,
Apr 6, 2006, 9:11:50 AM4/6/06
to VG...@googlegroups.com
http://wiki.linuxquestions.org/wiki/Dd

nilesh

On 4/6/06, chirag patel <chiragp...@yahoo.com> wrote:



--
Nilesh Vaghela

nilesh vaghela

unread,
Apr 6, 2006, 9:14:50 AM4/6/06
to VG...@googlegroups.com

XP Dual Boot Problems - contribution from a newbie

  • From: "Thiers Botelho" <thiers fosfertil com br>
  • To: fedora-devel-list redhat com
  • Subject: XP Dual Boot Problems - contribution from a newbie
  • Date : Thu, 27 May 2004 15:29:53 -0300
Hi all devels,

I don't consider myself as a developer but, as I have written and 
successfully tested at least _one_ shell script, I think I might loosely 
fit on this category.   :))

Now seriously: regarding JS's call on this thread,


 http://www.redhat.com/archives/fedora-devel-list/2004-May/msg00901.html

and also JA's posting of a preliminary doc on this one,


 http://www.redhat.com/archives/fedora-devel-list/2004-May/msg00908.html

I wish to offer a contribution to the theme, following a different path 

from what's being explored till now. Note that some users might consider 
it more troublesome and  more involved, whereas some other users might 
prefer it due to the additional security it offers.

I have been playing for a time with 'System Rescue CD' which is a live CD 

with recovery tools, published at

        http://sysresccd.org/ .

Using it a few times, and adding a shallow knowledge of shell scripts, 
I've managed to build a set of scripts which work together and allow me to 

make partition backups (ext3, vfat and ntfs have been tested) to another 
HD or smb share (using partimage), plus backups of the MBR and partition 
table using dd and sfdisk .

I've also successfully restored NTFS and VFAT partitions which these 

scripts. In one case I purposely deleted the Windoze boot partition with 
fdisk and then restored it with a partimage backup after manually 
restoring the MBR and partition table.

Summing up all of this: if a doc is being cooked up to advise users on the 

perils of dual booting, I suppose many users would be pleased to find on 
this doc an additional and optional procedure like the following:

        - back up MBR with dd (per script)
        - back up partition table with sfdisk (per script)

        - back up windows partition(s) using partimage (per script)
        - install FC2 with all precautions
        - confirm that FC2 boots
        - see that Windoze boots and sigh in relief . . . OR

        - see that Windoze does not boot and proceed
        - back up FC2 partition(s) using partimage (per script)
        - restore MBR with dd (manually, maybe . . .)
        - restore partition table with sfdisk (manually, maybe . . .)

        - see that Windoze now boots and sigh in relief . . . (at least 
that's what's hoped at this point . . .)
        - see that now FC2 does not boot and proceed
        - if needed, destroy and recreate partitions for FC2 (manually 

with parted - Partition Magic could also be mentioned as an optional tool)
        - restore FC2 partition(s) using partimage (per script)
        - see that FC2 boots and sigh in relief 
        - go do something more interesting


I haven't personally gone thru the whole procedure myself, but judging for 
my experience with parts of it I have no reason to suspect it won't work. 
Of course I might have missed something, but that would require someone 

willing to go thru the whole shebang at once. It might take a few hours 
(mostly for I/O on backup and restore operations), but the setup is 
straightforward if shell scripts are used.

Maybe it will not be 'politically correct' to suggest third-party tools 

such as 'System Rescue CD' to recover from a Fedora-specific problem. 
However I'm suggesting this with a vision of broader 'Open Source' and 
'community' concepts.

Thanx all for your attention.

Thiers


--
Nilesh Vaghela

nilesh vaghela

unread,
Apr 6, 2006, 9:31:14 AM4/6/06
to VG...@googlegroups.com
http://hacks.oreilly.com/pub/h/2337



HACK
#94
Hack the Windows NT/2000/XP Boot Loader
Customize what and how you boot using the BOOT.INI file.
[Discuss (14) | Link to this hack]

The BOOT.INI file was introduced with Windows NT and lives on through Windows 2000, XP, and 2003 as a means to provide preboot reference to where the operating system is located and control over which operating system will be used. It allows users to select the DOS environment or the Windows NT environment (which does not support many of the applications and direct hardware access that DOS does). BOOT.INI can also be modified to support the addition of another drive that has an operating system installed (perhaps unknown to the operating system on the first/original disk drive), giving you multiboot support to a non-Microsoft OS.

BOOT.INI is a plain-text file (equivalent to DOS's IO.SYS and MSDOS.SYS) that resides in the root directory of your boot disk and is read by the NTLDR program when the system is starting up. It is saved with Read-only, System, and Hidden attributes, requiring you to remove these attributes before reading or modifying the file.

BOOT.INI Contents

The contents of a typical BOOT.INI file are shown below. The parameters in the file are few—essentially specifying the time that the boot loader waits for user input before processing the default selection, the default operating system to boot if there is no user selection, and a list of possible operating systems and the disk parameters indicating where the operating systems are stored.

[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows 

XP Professional" 
/fastdetect

In this example, only one operating system is presented, Windows XP, and the computer will wait for three seconds after the menu appears before loading the default operating system. Windows XP is installed in partition 1 on the first physical disk, rdisk(0), on an ATA or SCSI device that is recognized by the system BIOS (the multi(0) parameter).

The following sample shows the [operating systems] section of a BOOT.INI file on a computer with two operating systems, Microsoft Windows XP and Microsoft Windows 2000. It has two boot entries, one for each operating system.

[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows 

XP Professional" 
/fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 
Professional" 
/fastdetect

These entries reveal that Windows XP and 2000 are installed on two different partitions of the same physical disk drive. The operating system location information uses the Advanced Risk Computing (ARC) naming convention for the physical and logical information about the disk and partition where the operating system resides. ARC paths use the formats described in the following sections.

Editing BOOT.INI with a Text Editor

BOOT.INI starts out with System, Read-only, and Hidden file attributes. To find the file in Explorer or at a command prompt, you need to remove at least the Hidden attribute. To edit the file, you need to remove the Read-only attribute. You can remove all of the attributes at a command prompt with the following steps:

  1. Open a command prompt window through StartRun, type in CMD, and then click OK.

  2. Change to the root directory of the boot disk and remove the attributes (System, Hidden, Read-only):

    X:\Foo>C:
    C:\Bar>cd \
    C:\>
attrib -s -h -r boot.ini

With the attributes removed, you can use EDIT, Notepad, or a similar text editor to view and make changes to the file. NTLDR can use the BOOT.INI file with any attributes set, but to protect the file when done editing, restore the attributes at a command prompt with the following steps:

  1. Open a command prompt window through StartRun, type in CMD, and then click OK.

  2. Change to the root directory of the boot disk and restore the attributes:

X:\Foo>C:
C:\Bar>cd \
C:\>
attrib +s +h +r boot.ini

ARC Disk and Partition Syntax for BIOS Drives

The BOOT.INI syntax discussed is used for all controllers that provide BIOS INT-13 support for ATA and SCSI disks. provides details about these parameters.

Table 0. BOOT.INI syntax for IDE devices

Parameter

Description

multi(0)

The drive controller number, typically 0.

disk(0)

Always 0; not used with IDE drives

rdisk(0)

The physical hard disk attached to drive controller. For ATA controllers, this number is typically between 0 and 3. For SCSI controllers, this number is typically between 0 and 7, or 0 and 15, depending on the adapter type.

partition(0)

The partition number.

ARC Disk and Partition Syntax for Non-BIOS Drives

The following syntax tells Windows that the startup device is attached to a SCSI host controller that does not support BIOS INT-13 disk access and that bootup requires the NTBOOTDD.SYS device driver. SCSI host adapters built into servers, many of which support a variety of RAID and disaster recovery functions, avoid using the BIOS for disk access and must use either a custom disk access driver or the boot driver of Windows to support all of the features available in the special hardware. describes the syntax used in BOOT.INI for SCSI devices.

Table 0. BOOT.INI syntax for SCSI devices

Parameter

Description

scsi(0)

The drive controller, typically 0.

disk(0)

The SCSI disk drive device number, between 0 and 7, or 0 and 15, depending on the host adapter.

rdisk(0)

The SCSI logical unit, typically 0.

partition(0)

The partition number the operating system resides on.

You can use this syntax to specify which SCSI disk to boot from by following these steps:

  1. Take a disk drive with an operating system already installed.

  2. Install it as the second disk drive in a system that has another NT-based operating system installed on its disk drive.

  3. Modify the BOOT.INI file on the first drive and adjust all of the lines containing selections of which operating system to boot.

The unmodified BOOT.INI on both drives may initially read as follows:

[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP 

Professional"

After installing the second drive, the BOOT.INI file on the first drive should be modified to look like:

[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP on 1st Drive" 
multi(0)disk(0)rdisk(1)partition(1)\WINNT="Microsoft Windows 2000 on 2nd Drive"

Add the second operating system choice, "Microsoft Windows 2000 on 2nd Drive" and indicate that it resides on the first partition, partition(1), of the second disk, rdisk(1).

Then modify the BOOT.INI file on the second drive to look like:

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(1)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINNT="Microsoft Windows 2000 on 2nd Drive"

This provides the operating system location reference for the operating system on the second drive.

TIP

Remember to make backups of these files before you change them so you can restore them if you make a mistake. You can copy the original file back into the text-based Recovery Console, which you can access by running Windows setup and choosing to recover an existing installation.

Booting Linux

You can boot Linux from BOOT.INI with a little trickery. The first step is to install a Linux bootloader, such as GRUB or LILO, onto your Linux partition. So, supposing your Linux root partition is /dev/hda6, you'd set up the GRUB bootloader with these commands:

# grub
   
GNU GRUB  version 0.95  (640K lower / 3072K upper memory)
   

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]
   
grub> 
root (hd0,  <TAB>
 Possible partitions are:
   Partition num: 0,  Filesystem type unknown, partition type 0x7
   Partition num: 2,  Filesystem type is fat, partition type 0xc
   Partition num: 4,  Filesystem type unknown, partition type 0x82

   Partition num: 5,  Filesystem type is ext2fs, partition type 0x83
   
grub> root (hd0,5)
 Filesystem type is ext2fs, partition type 0x83
   
grub> 
setup (hd0,5)
 Checking if "/boot/grub/stage1" exists... yes
 Checking if "/boot/grub/stage2" exists... yes
 Checking if "/boot/grub/e2fs_stage1_5" exists... yes
 Running "embed /boot/grub/e2fs_stage1_5 (hd0,5)"... failed (this is not fatal)

 Running "embed /boot/grub/e2fs_stage1_5 (hd0,5)"... failed (this is not fatal)
 Running "install /boot/grub/stage1 (hd0,5) /boot/grub/stage2 p /boot/grub/menu
.lst "... succeeded
Done.

   
grub> quit

TIP

Note that GRUB uses a different numbering scheme than the rest of Linux. Linux numbers partitions starting at 1, but GRUB starts at 0. So /dev/hda6 is (hd0,5) in GRUB.

After you set up the bootloader, you need to grab it and save it into a file with the dd command:

# dd if=/dev/hda6 of=grub.bin bs=512 count=1

Now you need to copy grub.bin over to the root of your boot partition, typically the Windows C: drive. If your Windows C: drive is formatted as NTFS, you probably won't be able to write grub.bin to it from Linux, so you'll need to use a FAT-32 partition, a floppy disk, a directory on another computer, or some other means to transfer it over.

Boot back into Windows, edit your BOOT.INI as directed earlier in this hack, and add the following line to the [operating systems] section:

c:\grub.bin="Linux"

If you reinstall your Linux boot loader, you'll need to use dd to extract the boot loader and copy it to your C: drive again. The advantage of using GRUB instead of LILO is that GRUB does not need to be reinstalled each time you install a new kernel (simply edit the GRUB configuration file, usually /boot/grub/menu.lst).

Booting DOS or Windows 9x-Me

Configuring the BOOT.INI file to allow you to boot to DOS or Windows 95-Me is done automatically by the setup program if, when you install Windows NT-2003 including XP, you choose to leave your current filesystem intact (it must be a FAT-16 or FAT-32 partition) and install the new operating system in a different directory or on a different disk drive (which could be NTFS).

If you want to add DOS/95/98/Me to an existing NT-2003 installation, it is easier to do so by adding a second hard drive setup with a FAT-16 or FAT-32 filesystem and modifying the BOOT.INI file to provide the option to boot to the second drive. The steps in a nutshell are:

  1. Disconnect the first hard drive that contains Windows NT-2003.

  2. Connect the drive you want to use for DOS-Me as the first/only hard drive.

  3. Install DOS or Windows 95-Me.

  4. Reconfigure the hard drives so that the Windows NT-2003 drive is the first/"Master" drive and the DOS-Me drive is the second/"Slave" drive.

  5. Boot into Windows NT-2003.

  6. Modify the BOOT.INI file on the second drive to look like:

    [boot loader]
    timeout=5
    default=multi(0)disk(0)rdisk(1)partition(1)\WINNT
    [operating systems]
    multi(0)disk(0)rdisk(1)partition(1)\WINNT="Microsoft Windows 2000"

    d:\="Windows 98"

The line containing d:\="Windows 98" provides the boot-time option and operating system location reference for the operating system on the second drive.
Comment on this hack
You must be logged in to the O'Reilly Network to post a comment.

Showing messages 1 through 13 of 13.

  • Grub booting XP on one disk, Linux on another
    2005-09-17 20:51:40  Greenstreet [Reply | View]

    I was able to get Grub to work on my system but I
    needed a trick to do it. I ran into a problem on my first attempt: On my system XP is already on hda. I loaded Linux on hdb and created the /boot partition as the first partition on hdb (hdb1). (This is a small partition entirely within the 1024 cylinder limit.) I loaded Grub on this partition, then did the dd trick to copy the boot sector of hdb1 to a file that I placed on c:\ (on hda2) and set up my boot.ini accordingly. It didn't work - it just types "GRUB" in the upper-left corner.

    I got an idea for a solution after reading http://www.linuxjournal.com/article/4622, which describes how to create a Grub boot floppy. I was finally able to get my Linux installation to boot from hdb1 with the Grub boot floppy.

    I happen to have a small FAT32 partition on my first drive (hda5, which I created a long time ago with Partition Magic), so I used the "Grub boot floppy" technique to make hda5 a "Grub boot partition". I then did the dd trick for hda5, and copied that boot sector file to c:\. Now I can selectively boot to XP on hda2, or to the grub boot partition on hda5. Just add menu.lst to hda5 and we have a complete working solution. Once control is with Grub the problems with the second drive go away.
    • Grub booting XP on one disk, Linux on another
      2005-10-23 06:47:58  keithglos [Reply | View]

      I recently copied a disk image to a stand alone hard disk. Used for the first time a boot live Linux. I found the dd command would only write from head 0 track 1 sector 1, this should have been head 0 track 0 sector 1 for the PC bios to find it. If this is normal (OK for writing to floppy) it would explain some of the difficulties here. I added bs=32256 (512x63) and skip=1, and hand copied the mbr from the file to the correct location, which then worked.
      • Grub booting XP on one disk, Linux on another
        2005-10-23 07:15:41  keithglos [Reply | View]

        Sorry, I meant write TO head 0,track 0, sector1.
  • XP copy doesn't boot
    2005-08-14 01:59:28  mzarathustra [Reply | View]

    XP is freezing on the shaded blue "windows XP" screen...

    Here's what I did:

    I have a Dell dimension, which has XP installed (on an IDE Drive). I got a new SATA drive.

    First I unplugged the old drive and tried to install window$ on the new one. Gonk. requires a driver disk from the manufacturer, and I don't have a floppy drive in the machine right now. Boo hiss. (if Steinberg and Sibelius would support Linux I wouldn't have this problem -- but I digress)

    So I split up the drive and put SuSE 9.1 on the upper partitions (swap on 3, / on 4)... it installed without driver disk, though the installer couldn't quite seem to talk to the video card (SVGA, I mean, come on!) which made partitioning an interesting experience.

    Then I rebooted XP by plugging the old drive in, and copied over the files to partition 1 using Wester Digital's Data Lifeguard. (I know how egocentric M$ operating systems are -- they are happier being on partition 1)

    Unplugged the old drive, and after some experimentation got grub and the new Boot.ini set to reasonable values, at least as well as I could form browsing the internet.

    So now Linux boots fine. But when I try XP, I get the black background initial window with the animated "thermometer," then it switches to the fancy blue "XP" window, then there is some disk activity and it freezes. An updated version of the "blue screen!"

    I'm thinking it might be the 'pagefile.sys' which I might delete to forced windoze to reconstruct (I assume it's some sort of swap file).

    Another painful (but typical M$ alternative) would be to install XP on the new partition, then copy the files again, to convince the installer to do whatever magic trick it needs to.

    Any ideas? It seems like what I am attempting is a rare sequence of events. Most people don't seem to assume a copy will work without actually installing windows on the partition -- which would be a bit silly if it weren't for micro$oft's retarded os-centrism.

    thanks,

    -= miles =-


  • TWO DRIVES WORKING
    2005-07-23 17:13:43  paisley [Reply | View]

    OK I have this working with two drives using the Windows XP boot loader - WindowsXP on hda2 and Linux on hdc1.

    Here is my setup:

    /dev/hda1 DOS (Fat16)
    /dev/hda2 WindowsXP (NTFS)
    /dev/hda3 Data (NTFS)


    /dev/hdc1 Linux-boot ext2
    /dev/hdc2 Linux-swap
    /dev/hdc3 Linux-root reiserfs
    /dev/hdc4 Windows2003Svr (NTFS)


    I originally had the Windows boot loader installed on /dev/hda MBR. I also had the Grub boot loader installed on /dev/hdc MBR. Both environments booted separately using the Laptop BIOS boot device selection options. However, just like the previous postings I couldn't get the Windows boot loader booting Linux on the second drive.

    This is because Grub stage1 (512 byte MBR code) hard codes the location of Stage2 in drive and block list format. You must obtain this information to create a suitable stage1 binary for the Windows boot loader. (I'm referring to the C:\linux.bin)

    The easiest way to create a suitable Grub stage 1 is to install it on the MBR of the Windows drive temporarily, copy it and then restore the Windows boot loader.

    Here are the steps to do just that (you will need to modify to suit your partition setup):

    ***Please be careful as Grub partitions are indexed from 0 (hd0,0) and Linux indexed from 1 (/dev/hda1)!!!

    1. Establish a way to boot each environment separately (I am using a Laptop so I use the BIOS for this, but you could use boot disks, CDROM, USB etc). Also back up ALL your boot records using dd. e.g "dd if=/dev/hda bs=512 count=1 of=/mnt/usb/backup/hda", "dd if=/dev/hda1 bs=512 count=1 of=/mnt/usb/backup/hda1" .... and so on

    2. a) Boot into Linux or a Linux boot CD and setup Grub onto /dev/hda MBR
    #grub
    grub> root (hd0,0)
    grub> find /boot/grub/stage1
    grub> setup (hd0)

    ***Do NOT install Grub onto a partition (hd0,0) especially the Windows partition as this will erase the NTLDR. Install onto the MBR (hd0) as this is easily restored in step 4.

    2. b) Setup Grub to run from the new location (from Windows):
    Edit /boot/grub/grub.conf and update the splashimage location or you will get a blank/distorted screen
    i.e. splashimage=(hd1,0)/grub/splash.xpm.gz
    Edit any other references such as root(hd1,0), initrd that will also need to change

    ***In theory you could now reboot and get Grub to boot both OS's however the aim is to get Windows boot loader to do that so we will continue...

    3. Copy the Grub stage 1 onto some sort of removable media
    #dd if=/dev/hda bs=512 count=1 of=/mnt/usb/linux.bin

    4. Restore the Windows boot loader.
    -Boot WindowsXP Install CD and select repair option
    -Select the Windows platform in the recovery console and enter admin password
    -Type fixmbr

    5. Reboot into WindowsXP
    -Copy the image stored on the removable media to the C:\ drive
    -Modify the boot.ini as per article above:
    C:\linux.bin="Linux"

    6. Reboot and use the Windows Boot Loader to boot either Linux or Windows on separate physical disks!!!


    • TWO DRIVES WORKING
      2006-04-06 04:31:00  Degash [Reply | View]

      i want the first step to take.Do i have to instor xp and then the next drive after.or i have to make one master and the order one slave.pls help
  • It does not work with 2 drives
    2005-05-09 05:29:57  Dr_Cobalt-60 [Reply | View]

    This hack maybe works when all systems are located on one single drive (hda*). However, when I tried to use it with WIN-XP on (hdc1) and Linux on (hdd3), I failed.
    This is not a complete failure - I have a floppy with GRUB, and it can boot both systems with "chainload +1", so I am sure that all bootsectors are OK. However, when I use "dd if=/dev/hdd3 of=/mnt/win-XP-c/linux.bin bs=512 count=1" and thereafter try to boot through this sector, all I get is a lone "GRUB" in the upper left corner. The system just hangs, there is no reaction even to Ctrl-Alt-Delete, and in frustration I push the power switch.

    If anybody has some idea of what is wrong< it will be appreciated.

    BNK
    • It does not work with 2 drives
      2006-01-03 06:16:24  MickKi [Reply | View]

      Using the Grub boot floppy you bypass the Linux disk boot sector (MBR). Your error is indicative of Grub stalling because it cannot find its grub.conf file/partition. This error is often related to not having mounted the /boot partition when installing/configuring Grub at the beginning. Boot into Linux using the Grub floppy, then make sure that /boot is mounted and reinstall Grub in the Linux drive MBR. If you would rather not install the Linux bootloader in the hdd MBR, then you can install it in the hdd3 partition. Repeat previous steps with dd and your Linux should be chainloaded from ntldr.

      There's another reason why Grub may stall. It could potentially be probing the hardware for a floppy device. In that case, just add this: # grub --no-floppy, when installing Grub.

      Good luck! :-)
      --
      MickKi
    • It does not work with 2 drives
      2005-05-24 21:32:37  sengwai [Reply | View]

      Similar case for me.

      I have 2 SATA hard disk, the first one, I install with Windows XP, and it boot nicely. Then I installed Fedora 4 Test Release to the second SATA hard disk (sdb1)

      I did the "dd if=/dev/sdb1 of=bootsect.lnx bs=512 count=1" and put it into floppy then boot into Windows, copy the bootsect.lnx to the C:

      After reboot, select boot into the Fedora and see only GRUB and a cursor blinking at the top left corner of the screen.

      I thought that it may be due to the LBA problems, I set the second hard disk to LBA, and it still doesn't work.

      I therefore rule out is hardware issue, and it is definately configuration/setup issue in GRUB.

      I struggling with this problem for a week +.

      Anyone can help?
      • Possible solution
        2005-05-29 20:11:54  sengwai [Reply | View]

        I have give up using the Windows boot.ini to boot into the linux. Not sure is it because my hard disk too big (160GB), resulting the geometry problems.

        I have try another way, and it works for me.

        I have swap the connection point of Sata 1 (Windows XP) to Sata 2 (Fedora) and Sata 2 to Sata 1. Then I reinstall the Fedora, and install the boot loader into the MBR. (This should not affect the MBR of Windows XP in Sata 2)

        Then I reboot the system, it finally able to boot into the Fedora.

        Then login as root, edit the grub.conf (for Windows XP):

        title Windows XP
        rootnoverify (hd1,0)
        map (hd1) (hd0)
        map (hd0) (hd1)
        chainloader +1

        Then I reboot the system and from the grub menu, I able to select Windows XP and boot in without any problems.

        Hope this give an alternative.

        • Re: Possible solution
          2006-02-12 23:10:14  zorro2006 [Reply | View]

          Hi,

          I have two hard disks, a 20 GB IDE Drive with Fedora Core 4 Linux, and a SATA HDD with Windows XP on it. I needed a solution to allow me to boot XP without having to change the boot options in my BIOS Setup. This simple method works without any problems. Finally I'm able to boot XP from GRUB without any hitches. Hope this feedback helps others.

          Thanks a lot!




        • Possible solution
          2005-11-05 18:52:44  LarsHansen [Reply | View]

          I had exactly the same problem and you solution worked beautifully for me.

          Thanks a lot,
          Lars
    • It does not work with 2 drives
      2005-05-24 09:56:49  kbclancy [Reply | View]

      same issue here, did you find a fix???

Reply all
Reply to author
Forward
0 new messages