Dual Boot Suse 11and Windows

Hi All
Been trying to get Suse 11 to dual boot with windows but keep having a problem. Grub has Windows (which is a on a second HD as a dual boot Vista and XPPro) listed ,when I choose windows it just goes to a page that says something like root notify or something (sorry I didnt make a note )and just hangs with a cursor )
Tried booting into windows with Super grub disc and get error 13.
Since I have dual booted with Mandriva ,PCLinux ,Ubuntu ,Mint with no problem with the same set up : Suse 11 main drive and windows dual boot second drive.
I have installed Suse 11 before like this and all was OK .
Can some one please tell me where I’m going wrong.
Thanks
Steve

Can you give us the output of the next commands
Fdisk -l(L) lower case
cat /boot/grub/menu.lst
you have to run booth commands as su
dobby9

Hi dobby9
Just re installed Suse 11 KDE 4 and the windows boot gives this text:

root noverify (hd0,1)
chainloader (hd1,0)=1

fdisk -l :

Disk /dev/sda: 80.0 GB, 80060424192 bytes
255 heads, 63 sectors/track, 9733 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000a32c7

Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sda2 * 263 2873 20972857+ 83 Linux
/dev/sda3 2874 9733 55102950 83 Linux

Disk /dev/sdb: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000eb87a

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 4462 35840983+ 7 HPFS/NTFS
/dev/sdb2 4463 9726 42281984 7 HPFS/NTFS

cat/boot/grub/menu.lst :

Modified by YaST2. Last modification on Thu Sep 25 12:13:18 UTC 2008

default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,1)/boot/message
##YaST - activate

###Don’t change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.0 - 2.6.25.5-1.1
root (hd0,1)
kernel /boot/vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_SAMSUNG_SP0812NS00MJ10Y609042-part2 resume=/dev/sda1 splash=silent showopts vga=0x31a
initrd /boot/initrd-2.6.25.5-1.1-pae

###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – openSUSE 11.0 - 2.6.25.5-1.1
root (hd0,1)
kernel /boot/vmlinuz-2.6.25.5-1.1-pae root=/dev/disk/by-id/scsi-SATA_SAMSUNG_SP0812NS00MJ10Y609042-part2 showopts ide=nodma apm=off acpi=off noresumenosmp noapic maxcpus=0 edd=off x11failsafe vga=0x31a
initrd /boot/initrd-2.6.25.5-1.1-pae

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

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

I am not a Linux Guru neither am I a Windows expert
But as far as I know windows will only boot from the first
drive.
So in linux words from SDA and not from SDB
dobby9

Hi dobby9

Widows boots from the second hard drive with all the other distros I have used including Suse. I dont know why it wont now.

Try changing this:

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

to this:

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

Hi swerdna

Thanks a lot that did the trick :slight_smile:

Cheers
Steve

You’re welcome.
Looks like vista was installed after xp on the drive when it was the primary drive, then it looks like it was swapped over to be the secondary drive. Vista when it’s installed invades the bootloader of xp on the first partition. So the upshot of everything was that the dual booting for windows (with choices of xp and vista) ended up on partition 1 of drive 2. In grub speak that’s (hd1,0) – hence the change.

dobby9 was almost right in that xp would only boot from partition 1 of drive 1. But vista is smarter than xp.

Hi swerdna

Dont know whats happening there I have installed gallons of different distros and grub works fine . Just had this problem this time with Suse.
To be honest I keep Vista aand Xppro an a second drive and its very rare that I venture in there at all …very rare !
This Box is my second box and it is an older nforce 2 machine and I find Suse 11 KDE 4.1 runs real fast on there.
Thanks again
regards from pom
Steve

It’s not your error. It’s an oversight on the part of the Suse developers. It came to a head with the entry of vista into the arena. The devs had the setup of menu.lst marginally incorrect for windows from the get go which didn’t matter for 2000/xp. For vista it has to be spot on correct and I suppose it will take a while for it to be noticed and fixed.

Hi
…for information
have recently installed Suse 11 on an HP Pavillion Laptop 9500 series (9576EA)
the laptop had vista home premium installed from new

after installing Suse couldn’t get Vista to come out of its coma

changing
rootnoverify (hd1,5)
chainloader (hd1,0)+1

to
rootnoverify (hd0,1)
chainloader (hd0,1)+1

fixed the problem

Interesting. Which drive and partition did you put Suse on?