Do not use Grub as Bootloader.
Vista will not start.
Lilo Bootloader will load Vista.
that simply is not true. when i still had vista many months ago grub loaded it fine.
For those who come across this thread, I endorse thestig’s comment.
You can boot vista with Grub. Any problems, just ask & help will come.
I have had a recent issue with getting Vista to boot however as usual Grub nor OpenSuse had nothing to do with it. Often times simply asking for help and allowing the very helpful people here to assist you resolves these types of issues very quickly. Rather than just saying something doesn’t work. OR perhaps reading the first thread that is stickied on this category of the forum would help you understand why you don’t know what you are talking about.
Of Course it was a user error.
When you are installing and things don’t go the way it schould go. You have a problem.
You don’t have any connection with the internet.
You have a death peace of hardware.
My experience is that none of the installations with Grub worked.
That only the installation with Lilo worked.
It is just my experience. But don’t shoot the
messenger. (please)
Hallo!
Habe vor 2 tagen linux suse 11 installiert. 
Auf meiner ersten sata Festplatte habe ich win. xp.
Auf der zweiten sata Platte ist jetzt neu suse drauf.
Der bootloader wird ja automatisch in eine der Partitionen der linux platte aufgespielt. so habe ich es auch belassen.
Mein Problem mit Grub ist nun folgendes:
Wenn bei der Auswahl im Grub-Menü beim hochfahren des Rechners nicht Suse sondern Windows ausgewählt wird kommt folgender Hinweis:
rootnoverify (hd 0,0)
chainloader(hd0,0)+1
und natürlich fährt windows nicht hoch. Der einzige weg ist im bios über die erste hd zu booten, aber das ist auf dauer ja keine lösung. :\
Ach ja… linux wird gut hochgefahren… aber bin ja noch kein linux profi und brauche ab und zu noch die windows hd. 
wär cool wenn jemand da eine lösung hätte! thx 
Ok, i forgot that i m posting on an international platform rotfl! so now again in english…
2 days ago, i installed suse 11.0 on my pc. thats the first time ever that i m dealing with linux.
On my first sata HD i got win. xp installed.
On my second sata HD i just installed suse 11.0.
The bootloader was installed on one of the partitions of my second HD (the root or the boot partition). I didnt change that.
My problem with Grub is now the following:
When starting the computer and choosing in the Grub-Menü to boot windows and not suse, it shows me the following message:
rootnoverify (hd 0,0)
chainloader(hd0,0)+1
and windows is not booting. the only solution i can find is to boot in the bios picking the first HD, but that doesnt really satisfies me tbh.
btw… linux is booting without any problem… but as i am a beginner in linux, the windows hd will still be needed a lot.
thats why i would be very thankful if somebody could help me out.
@Linoob, a few questions to get some info for the experienced folk who usually come on line in a few hours:
Which windows version is installed?
Did you alter the way the computer boots by using the bios bootloader menu (F2 key or similar), or by making permanent changes in the bios? Or did you allow it to boot the way it booted originally when vista was the only installation?
Please show us your partitioning by opening a console window and entering su to become the root user, then entering this command:
fdisk -l
(letter l not integer 1). Use the mouse to copy/paste the whole results/dialogue back here.
Show us the contents of the Grub config file (menu.lst) lkocated at /boot/grub/menu.lst. You can expose it with this command in a console and copy/paste it back here (still as root user / su to root first):
cat /boot/grub/menu.lst
First i gonna answer the 2 initial questions as they are easy to answer.
- I m using the windows XP media center edition
(i know that this thread is about vista but couldnt find a better thread to post this question in)
- Bios settings were not changed at all
First it shows all the 4 usb-devices, then the first hd (windows), then the second hd (suse), then the dvd-drive, when booting manually with bios via F11. If i dont pick the F11 menu to chose my windows hd, it boots with the bootloader automatically.
I will answer the other questions as soon as possible, needing some time to get this done though. 
Finally I managed to get the other informations:
- about fdisk -l
Platte /dev/sda: 250.0 GByte, 250059350016 Byte
255 Köpfe, 63 Sektoren/Spuren, 30401 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Disk identifier: 0x9d3f9d3f
Gerät boot. Anfang Ende Blöcke Id System
/dev/sda1 * 1 30400 244187968+ 7 HPFS/NTFS
Platte /dev/sdb: 500.1 GByte, 500107862016 Byte
255 Köpfe, 63 Sektoren/Spuren, 60801 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Disk identifier: 0x426de7fc
Gerät boot. Anfang Ende Blöcke Id System
/dev/sdb1 1 101 811251 82 Linux Swap / Solaris
/dev/sdb2 * 102 10801 85947750 83 Linux
/dev/sdb3 10802 60801 401625000 83 Linux
- about menul lst
Modified by YaST2. Last modification on Mi Nov 12 14:22:12 UTC 2008
default 0
timeout 8
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_ST3500820AS_9QM7DJSQ-part2 resume=/dev/sdb1 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_ST3500820AS_9QM7DJSQ-part2 showopts ide=nodma apm=off acpi=off noresume nosmp 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###
title Windows
rootnoverify (hd0,1)
chainloader (hd1,0)+1
PS: meanwhile i reinstalled the system with the above partitioning. with that new partitioning the lines changed to
rootnoverify (hd0,1)
chainloader (hd1,0)+1
like they are displayed above. (i mention this so that you dont wonder about why those lines changed meanwhile)
Grub sees the windows partition as the first partition on the second drive.
Linux fdisk sees the windows partition as the first partition on the first drive.
Windows probably sees the windows partition as the first partition on the first drive, although I didn’t ask you to check the windows boot.ini code.
And so as usual I get quite confused by the inconsistency and probably windows does too.
So you need to edit the file menu.lst to unconfuse windows. The file menu.lst has special permissions so you edit it with a superuser text editor that you can start with this command in a console if you use Gnome:
gnomesu gedit /boot/grub/menu.lst
or this if you use kde:
kdesu kwrite /boot/grub/menu.lst
So edit the file menu.lst and change these three lines:
title Windows
rootnoverify (hd0,1)
chainloader (hd1,0)+1
to this
title Windows
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader (hd1,0)+1
If that doesn’t work we call the experts
IT WORKED!
thank you so very much for your help, that was so important for me to set up and now … well i will have to read those codes again a few times to understand what you told me to do, but - lol! - so many thanks to you to making it work!
I guess we found the expert already in you
Glad to be able to help – Yast sometimes configurates Grub in puzzling ways – but that’s what we’re here for.
And thanks for the compliment.