Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
I just installed OpenSuse 10.2 and am having a problem dual booting windows.
I have Windows installed on a SATA drive and OpenSuse 10.2 installed on a IDE drive. During the installation, OpenSuse detected windows and created an entry to boot it. However, when I power up the system and select Windows it displays "chainloader (hd1,0)+1" and hangs. If I modify the BIOS to boot my windows disk it comes up fine. Only the OpenSuse boot loader has problems.
This is the problem in /boot/grub/menu.lst. As root, edit the windows entry in menu.lst to look like this:
title Windows (or whatever you want)
root (hd1,0)
map (hd1.0) (hd0,0)
map (hd0,0) (hd1,0)
makeactive
chainloader +1
Windows will refuse to boot if it isn't on the first partition of the first hard drive (hd0,0). The map lines tells windows a little white lie to make it think it's on (hd0,0).
This is the problem in /boot/grub/menu.lst. As root, edit the windows entry in menu.lst to look like this:
title Windows (or whatever you want)
root (hd1,0)
map (hd1.0) (hd0,0)
map (hd0,0) (hd1,0)
makeactive
chainloader +1
Windows will refuse to boot if it isn't on the first partition of the first hard drive (hd0,0). The map lines tells windows a little white lie to make it think it's on (hd0,0).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.