Grub does not see windows partition after full Puppy install.
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.
Grub does not see windows partition after full Puppy install.
I am a complete linux beginner! I have done a full install of Puppy 4 on my old HP omnibook laptop (128 RAM)and its absolutely great. I partitioned the HD as follows all according to Puppy instructions:
/dev/hda1 ntfs 3.42 G (windows)
/dev/hda2 ext2 1.46 G (Puppy)
/dev/hda3 linux 128mb (linux swap)
/dev/hda4 Fat 32 502MB.
Grub identifies windows on hda4 instead of hda1 (dont see hda 1) and so I cannot boot into windows. I must have made some error when configuring GRUB. How can I now boot into my windows partition. Grateful for any help.
Which version of windows are you using?
What is on hda4?
If you can boot into Puppy, post the output of fdisk -l (lower-case letter L) and the menu.lst or grub.conf file in /boot/grub directory.
Thanks for replying so promptly. As a complete beginner it took some time to understand your advice but finally got into grub menu 1st and this is what I found. What needs changing? Thanks again.
# Start GRUB global section
#timeout 30
color light-gray/blue black/light-gray
# End GRUB global section
# Other bootable partition config begins
# title Windows (on /dev/hda1)
# rootnoverify (hd0,0)
# makeactive
# chainloader +1
# Other bootable partition config ends
# Linux bootable partition config begins
title Linux (on /dev/hda2)
root (hd0,1)
kernel /boot/vmlinuz root=/dev/hda2 ro vga=normal
# Linux bootable partition config ends
# Other bootable partition config begins
title Windows (on /dev/hda4)
map (hd0,0) (hd0,3)
map (hd0,3) (hd0,0)
rootnoverify (hd0,3)
makeactive
chainloader +1
# Other bootable partition config ends
title Install GRUB to floppy disk (on /dev/fd0)
pause Insert a formatted floppy disk and press enter.
root (hd0,1)
setup (fd0)
pause Press enter to continue.
title Install GRUB to Linux partition (on /dev/hda2)
root (hd0,1)
setup (hd0,1)
pause Press enter to continue.
title - For help press 'c', then type: 'help'
root (hd0)
title - For usage examples, type: 'cat /boot/grub/usage.txt'
root (hd0)
I am using an nlite version of windows XP. It works but is slow hence my reason for trying Puppy which is fantastic.
It is cautious to back up your menu.lst before you change it, in case something gets accidentally messed up.
You need to delete the hashes from in front of these lines
# title Windows (on /dev/hda1)
# rootnoverify (hd0,0)
# makeactive
# chainloader +1
And put hashes in front of these lines (assuming there's nothing on hda4 you need to boot)
title Windows (on /dev/hda4)
map (hd0,0) (hd0,3)
map (hd0,3) (hd0,0)
rootnoverify (hd0,3)
makeactive
chainloader +1
Thanks Honeysuckle. I did it and I now have access to my Windows partition (which frankly I don't think I will use much now).
Puppy works really well on this old laptop. I've just entered a new world!
It is cautious to back up your menu.lst before you change it, in case something gets accidentally messed up.
You need to delete the hashes from in front of these lines
# title Windows (on /dev/hda1)
# rootnoverify (hd0,0)
# makeactive
# chainloader +1
And put hashes in front of these lines (assuming there's nothing on hda4 you need to boot)
title Windows (on /dev/hda4)
map (hd0,0) (hd0,3)
map (hd0,3) (hd0,0)
rootnoverify (hd0,3)
makeactive
chainloader +1
think thats where i usually have the problem lol....however i havent had a problem with puppy 4 univerasl installer.....thanx for that info though honeysuckle
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.