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.
I am having some problems duel booting windows and linux.
I am using Linux Fedora Core 4 and Windows XP Pro SP2.
Linux is on an IDE hard drive and Windows is on a serial ata hard drive on the first controller.
I keep getting error 13 when I try to boot into Windows.
Here is my grub.conf file.
default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Fedora Core (2.6.11-1.1369_FC4)
root (hd0,0)
kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.11-1.1369_FC4.img
#title Windows XP Pro
# rootnoverity (sda1,0)
# rootnoverify (hd0,0)
# chainloader +1
I tried some things and just commented them out. So I guess in short my question is, what entries to I use boot Windows on a serial ata hard drive on the first controller, so SATA1.
Look at the device.map file in the /boot/grub directory. I would guess it is something like:
(fd0) /dev/fd0
(hd0) /dev/hda
(hd1) /dev/sda
so:
title Windows XP Pro
rootnoverify (hd1,0)
map (hd1) (hd0)
map (hd0) (hd1)
chainloader +1
The map lines are necessary because windows wants to be the first drive. See grub documentation for additional details. The first hard drive found will be hd0, the next hd1 and so on. Partitions IDs start at 0 i.e. hd0 is hda1.
Welcome to LinuxQuestions. You can find lots of help by searching the web and this website. As a newbie the difficult part is knowing what to search for.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.