Well it's not working, I think that when you put the command rootnoverify you must put the partition where Windows is installed (Sorry my mistake)

Hope this one is the definitive

^yea, look at my previous post (last post on 1st page) I gave that one a shot on my own and it worked. Thanks so much man. I don't know why you guys actually help n00b's out so much, but it's a big help.

I'm glad you made it!. As you have noticed you always learn something new in Linux.

Hope you enjoy Suse, it's a powerful distro.

I am getting the same error as penguin. This must be a big issue with suse.

What does chainloader stand for ?

From the GRUB manual:

— Command: chainloader [--force] file

Load file as a chain-loader. Like any other file loaded by the filesystem code, it can use the blocklist notation to grab the first sector of the current partition with `+1'. If you specify the option --force, then load file forcibly, whether it has a correct signature or not. This is required when you want to load a defective boot loader, such as SCO UnixWare 7.1

Basically it is used to boot the OS that is installed in the first primary partition.

Windows likes to be the "only" OS installed in the system, in the first primary partition, so you have use first the map command so Windows thinks it's installed in the first hard disk and then the chainloader command to let it think that it's booting from the first primary partition.

I just tried the same thing and this is what it is giving me

map (hd0)(hd1)

Error 11: Unrecognized device string

----------------------------
does anyone know what the problem is?




below is my menu.lst file

# Modified by YaST2. Last modification on Fri Mar 10 04:19:44 UTC 2006

color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,1)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
root (hd0,1)
kernel /boot/vmlinuz root=/dev/sda2 vga=0x317 selinux=0 resume=/dev/sda1 splash=silent showopts
initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows XP
map (hd0)(hd1)
map (hd1)(hd0)
rootnoverity (hd1,0)
makeactive
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 10.0
root (hd0,1)
kernel /boot/vmlinuz root=/dev/sda2 vga=normal showopts ide=nodma apm=off acpi=off noresume selinux=0 edd=off 3
initrd /boot/initrd

linux:/boot/grub # fdisk -l

Disk /dev/sda: 37.0 GB, 37019566080 bytes
255 heads, 63 sectors/track, 4500 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 131 1052226 82 Linux swap / Solaris
/dev/sda2 * 132 4500 35093992+ 83 Linux

Disk /dev/sdb: 37.0 GB, 37019566080 bytes
255 heads, 63 sectors/track, 4500 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 4499 36138186 7 HPFS/NTFS

Disk /dev/hdc: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 * 1 14593 117218241 7 HPFS/NTFS

Hi Envision5000, I have a question about the layout of your hard disks?

Where do you have Windows?, is it in /dev/sdb1 or /dev/hdc1?

/dev/sdb1


/dev/hdc1 << this drive is used only for storage

I've reviewed your file menu.lst, and it seems that you have omitted some spaces in the map command. Try again but with this correction:
The rest is good, (hd1,0) for your system is /dev/sdb1

I tried it with the spaces and that does not work either

It does not give an error, but just stops

Well, if that didn't work, then you have to give us more info about your system:

1. Did you change the boot order in the bios?. Also would be helpful if you can post the order of the hard disks in your bios setup.

2. Where did you install GRUB? Did you accept to install it in the MBR?

With this info we'll have more clues.

bios hard drive boot order ( should the below have different names? if yes how do I change them? )

WDC WD360GD-OOFL <first drive
WDC WD360GD-OOFL <second drive both have the same name


Grub is intalled in the boot directory

linux:/ # ls
. .. bin boot dev etc home lib lib64 media mnt opt proc root sbin srv subdomain sys tmp usr var windows
linux:/ # cd boot
linux:/boot # ls
. System.map-2.6.13-15.8-smp boot grub initrd-2.6.13-15.8-smp symvers-2.6.13-15.8-x86_64-smp.gz vmlinuz
.. backup_mbr config-2.6.13-15.8-smp initrd message vmlinux-2.6.13-15.8-smp.gz vmlinuz-2.6.13-15.8-smp
linux:/boot # cd grub
linux:/boot/grub # ls
. device.map e2fs_stage1_5 ffs_stage1_5 jfs_stage1_5 menu.lst.old reiserfs_stage1_5 stage2 ufs2_stage1_5 xfs_stage1_5
.. device.map.old fat_stage1_5 iso9660_stage1_5 menu.lst minix_stage1_5 stage1 stage2.old vstafs_stage1_5
linux:/boot/grub #

when I try to boot into windows xp it gives me on a black screen

Grub loading stage 1.5


and freezes.

Hi Envision5000, the reason I ask about the bios boot order is because it's possible you have changed the hard disks from master to slave, for example if you have installed Windows in the first hard disk (master), and then you have changed this hard disk to be slave. Did you do something like that? Could you explain us how did you install windows and then Linux, in that time did you do some change in hard disks?

A reason that could explain your problem, is that GRUB is not recognizing correctly the order of the hard disks, one more thing could you post the content of the file /boot/grub/device.map:

Finally can you post the content of the file C:\boot.ini, in your Windows system?

Hope with that info we can give you a solution.