Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 trying to make my PC dual boot but have got stuck, may be some here can help me:
I have a PC running Suse 9.1 Professional. The PC has two hardrives:
First IDE channel has a 4GB hardrive (master) with Suse Linux installed and a CD as slave.
Second IDE channel has 40GB harddrive (master) with Windows 2000 Pro installed. nothing as slave on this
IDE channel.
With both hardrives connected, the machine boots up and displaye the GRUB memu if SuSe is chosen all is
fine and Suse starts, however, if I choose Win 2000 from the Grub menu I get this errror:
Error 13 Invalid or unsupported executable format.
the grub script for the Win 2000 menu choice is:
title Win 2000
map(hd0,0)(hd1,0)
map(hd1,0)(hd0,0)
rootnoverify (hd1,0)
chainloader +1
Thinking it was an error in the Win installation I have tried turning off the PC, disconnecting the
ribbon cable from the Linux drive and then re-booting and in this case the PC boots in to Win 2000.
So I am convinced that the installation of Win 2000 on the second hard drive is correct but that the
Grub script is not correct.
What should the correct grub commands be to boot into Win 2000 on the second drive?
This seems OK, although I'm not sure why the boot is needed as what I have says that Grub should automatically add this when executing boot menu selections.
I had the similar problem some time ago, and tried/learned "all" the grub options and command line combinations without success...I'm pretty sure I screwed up winxp boot before that (so I had no chance of repairing it). Anyway, I'm pretty sure you can do without the two "map...." lines, because what 'map' does is shange the order or naming of harddisks/partitions (hd0 means hda, hd1 hdb, second number is number of partition on that hd)...The 2nd map line practically switches back o original (default) partition order
Could you tell me where did you put your bootloader (grub)? MBR, / or /boot?
After the installation of SUSE I applied the patch, to no avail, it kept telling me
hd(0,0)
Chainloader +1
SUSE says that somehow GRUB can not autodetect this LBA and it fails loading. Since I'm a newbie I didn't understand it well but changed (HD C) from AUTO to LBA, and it works as before.
Originally posted by Steve2001 This seems OK, although I'm not sure why the boot is needed as what I have says that Grub should automatically add this when executing boot menu selections.
The boot should be unnecessary if using the grun.conf
Manually entering the commands requires the boot command to initiate.
Both map commands *are* required - they are directives to grub, and refer to separate (physical) entites.
Seen a couple of these posts with "bad" mappings recently - so much for automation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.