/boot on /dev/hda3
Knoppix 3.1 installed on /dev/hda5
Grub is intalled on MBR (/dev/hda)
Windows is installed on /dev/hda1

I have following entry in my /boot/grub/menu.lst for windows:


title Windows
rootnoverify (hd0,0)
makeactive
chainloader + 1
boot

I see following error message after selecting Windows from grub menue:


rootnoverify (hd0,0)
makeactive
chainloader + 1

Error 1: Filename must be either an absolute pathname or blocklist"

The same system works fine with lilo:

other=/dev/hda1
label=dosfree
table=/dev/hda


Help me please with this. I did read a few documents and articles but it did not help.

Thanks in anticipation.

Not sure if it makes a difference but a I don't think there should be a space between + 1 i.e. chainloader +1

I'm also not familar with boot option. If you want windows to be the default then add to the top of the menu.lst:
default x (where x is the number of the entry starting from 0).

Here is my grub.conf file, it gives me no problems, maybe try a windows entry like the one I have, it has worked with many distributions

title SuSE 8.2
kernel (hd0,0)/vmlinuz root=/dev/hda5 vga=0x31a hdc=ide-scsi hdclun=0 spla\
sh=silent showopts
initrd (hd0,0)/initrd

title Windows 2000
root (hd0,1)
chainloader +1

title Gentoo
root (hd0,0)
kernel /bzImage-2 root=/dev/hda6

As you can see there are only two options in ther windows start up
Check if something like that works, and make sure to point windows to the right partition
Remember that for grub the 1st partition is (hd0,0) and the second is (hd0.1) and so on

You shouldn't put
boot
at the end of the code block in menu.lst, only at grub command line.

Whether this will bugger it though, I don't know.

lugoteehalt:

Actually, I ran update-grub commandwhich created entries for different kernels and all these were succeeded by the "boot" line.

It was only the "redundant" space in "chainloader +1" that created the error. I closely looked at aeruzcar's code and the manual at http://www.linuxjournal.com/article.php?sid=4622 and found out that both of them contain no space between + and 1.

Removing the space solved the problem and now I have written grub into my harddrive's mbr. I think, I won't miss lilo since grub is much easier and more powerful.


I will try out whether that boot is necessary or not and write the results once I am back home.

cheers