Dual boot

English Install/Boot/Login
1

I have a dual boot PC with 11.0 & XP
The XP HD is in 2 partitions. a 1.1gb boot and a 75GB winXP partition.
When I loaded Suses and did updates, and I am running GRUB boot loader, it says when I boot to WinXP, NTLDR is not present. When I access the hd, I can see NTLDR there. Any idea how to resolve this?? Many Thanks!

2

Grub has probably just got confused about your windows partitions. Have a look at /boot/grub/menu.lst, and make sure the windows entry corresponds to the correct windows (boot) partition.

If you need futher help, provide the output of

cat /boot/grub/menu.lst
fdisk -l (so we can see partition layout)

3 
title openSUSE 11.0 - 2.6.25.11-0.1
    root (hd0,0)
    kernel /vmlinuz-2.6.25.11-0.1-pae root=/dev/system/root resume=/dev/system/swap splash=silent  showopts vga=0x31a
    initrd /initrd-2.6.25.11-0.1-pae

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.0 - 2.6.25.11-0.1
    root (hd0,0)
    kernel /vmlinuz-2.6.25.11-0.1-pae root=/dev/system/root showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x31a
    initrd /initrd-2.6.25.11-0.1-pae

###Don't change this comment - YaST2 identifier: Original name: windows###
title WindowsXP
    rootnoverify (hd0,0)
    chainloader (hd1,0)+1

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
    rootnoverify (hd0,0)
    chainloader (fd0)+1

boot path for XP seems to be good, but still get the NTLDR error…

4

We need to see the the partition table(s) as requested previously. And now also the grub device map. So, as root, do:

fdisk -l
cat /boot/grub/device.map

Finally, in your computer bios, which disk is configured as the first boot disk (this is not the order the bios see the disks, this is the boot sequence)?

5

Looks like this happened: You installed Suse on a second hard drive with the bios set to boot to the second hard drive. If that’s not right then ignore the rest. If it’s right then this happened:
Suse’s redirect to windows is correct and when it gets there windows takes over. But when windows was installed it was then drive zero and now it’s drive 1 because Suse is now drive zero. So windows gets confused (and rightly so). So to un-confuse windows you have to change this:

###Don’t change this comment - YaST2 identifier: Original name: windows###
title WindowsXP
rootnoverify (hd0,0)
chainloader (hd1,0)+1

to this:

###Don’t change this comment - YaST2 identifier: Original name: windows###
title WindowsXP
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader (hd1,0)+1

There are special permissions on the file menu.lst. You must be root to edit it.