Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by realos
title Windows
rootnoverify (hd0,0)
makeactive
chainloader + 1
boot
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).
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
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.