After a dual-boot install, Vista no longer boots
 

I installed opensuse 11 from a burned DVD. I have two hard drives: one 40GB drive with two ntfs partitions /dev/sda1 (with Vista install) and /dev/sda2, and another 8GB drive with the Suse installation and swap partition.
For some reason, when I choose to boot Vista from the GRUB menu, it just gets stuck at a black console screen with
How do I fix this?

Try changing it to "rootnoverify (hd0,0)"

Thank you! It works perfectly. Although I have to wonder why openSUSE 11 automatically configures the Vista boot entry with hd1 for rootnoverify.

Most distros have trouble with multiple disks - just bad (installer) design.

So apparently, this is an issue with the new Vista bootloader. The generated line from Yast "rootnoverify (hd1,0)" works only for Windows versions below Vista. For vista you have to change it to hd0. I think this should be made a sticky, since I think many people will be running into these issues.

http://forums.opensuse.org/install-b...-opensuse.html

Nope - that wouldn't have worked with any version of windoze.
Don't try and generalize from one specific case. There are plenty of nuances in how the loaders (including Vista) work.

i have the same problem with my Windows xp. i can not boot it. i did the same thing as with previous distros of suse.. this is my menu.lst:

# Modified by YaST2. Last modification on Sat Jun 28 01:18:36 BST 2008
default 0
timeout 5
gfxmenu (hd0,1)/boot/message
##YaST - activate

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

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title windows
rootnoverify (hd0,1)
kernel /boot/vmlinuz-2.6.25.5-1.1-default root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD321KJ_S0ZEJ1MP802507-part1 showopts ide=nodma apm=off acpi=off noresume edd=off x11failsafe vga=0x31a
initrd /boot/initrd-2.6.25.5-1.1-default

title aaaa

but at boot loader for my windows entry i have:

optional kernel command line parameter: showopts ide=nodma apm=off acpi=off noresume edd=off x11failsafe
kernel image: /boot/vmlinuz-2.6.25.5-1.1-default
initial ram disk: /boot/initrd-2.6.25.5-1.1-default
root device: /dev/sda1
vga mode: 0x31a

any ideas how to fix it???
thanks in advance

Report a bug to the developers.

Did you alter menu.lst ???
Let's see the output from "fdisk -l" (as root/sudo, whatever).

i didnt alter the menu.lst.

linux-5cru:~ # fdisk -l

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe294e294

Device Boot Start End Blocks Id System
/dev/sda1 1 19122 153597433+ 7 HPFS/NTFS
/dev/sda2 * 19123 38301 154055317+ 83 Linux
/dev/sda3 38302 38913 4915890 82 Linux swap / Solaris

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd7a757b2

Device Boot Start End Blocks Id System
/dev/sdb1 1 38914 312568832 7 HPFS/NTFS


i have 2 hard drives:
1- have windows + linux + swap
2 - ntfs.

That is what is confusing your boot loader is having the second hard drive in the ntfs format. Your boot loader has to guess which partition is windows. stasik change your windows entry to rootnoverify (hd0,0)

That appears to be a screwed up recovery option (despite it being titled windows) - ignore it for now. Create a new stanza like this

Larry Webb & syg00, thank you very much. that did the trick. thanks again!!!

Happy to help - you might as well go back and fix the titles. Make the other one "failsafe", and the fix-it one "Windoze" (or somesuch :p).