Booting WIN XP via grub: Invalid or unsupported executable format
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.
Booting WIN XP via grub: Invalid or unsupported executable format
Hello and want to extend my appreciation in advance. I checked the other thread re: Vista but that solution and many permutations teszted are not working so I will explain my setup:
Dell Laptop E1505 with WindowsXP.
successful install of fd8 on 60BG fujitsu usb drive.
When I try to boot WindowsXP I receive the above Error 13.
#fdisk -l
/dev/sdb1 1 6 de dell util
/dev/sdb2 12 6693 7 HPFS/NTFS
/dev/sdb3 6694 8939 7 HPFS/NTFS
/dev/sdb4 8940 9545 db CPM/CTOS
/dev/sda1 1 25 83 Linux
/dev/sda2 26 7296 8e Linux LVM
Disk /dev/dm-0 57.6 GB (I believe is laptop c drive)
... Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1 20.8 GB (laptop d: drive) Disk /dev/dm-1 doesn't contain a valid partition table
Error 13....(when trying to boot Windows only) All Linux/Xen boot fine.
I suspect the above fdisk output:
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1 doesn't contain a valid partition table
is the issue?? Need bigtime help with this one.
Note: Originally, during installation of fd8 I moved the bootloader back to the laptop HD. This worked [only] once??? ie I was able to boot WindowsXP so I reinstalled fd8 and moved boot loader back to usb but lost ability to boot XP. I would not care but have thousands of $ of software and development installed and very poor hence move to Linux.
Last edited by 5n0wCr@5h; 06-29-2008 at 10:24 AM.
Reason: clarifying post
If you have not changed anything since fdisk -l above try to edit the bottom windows entry in your grub.conf file. Remove the entry rootnoverify (hd0,1) and see if your windows will boot.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
Well, from your menu.lst I'd guess a simple answer: put these two lines back in
Code:
map (hd0) (hd1)
map (hd1) (hd0)
i.e. uncomment them. Last time I looked, Windows insisted to be installed on the first partition of the first disk (= /dev/sda1). In your setup linux is there...
Last edited by JZL240I-U; 07-02-2008 at 01:28 AM.
Reason: added missing "(" in the line map (hd1) hd0)
Windows (being brain-dead) needs to be on the first (BIOS boot) disk. I prefer to leave it that way for convenience - Linux is flexible enough to handle any setup. Some of the installers are a bit limited, but that's the fault of the particular distro devs, *not* Linux itself.
With your arrangement you need to con Windows into thinking it actually is on the first disk - hence the "map" directives; that's grub doing the "fudging" for you. The makeactive is really not needed but does no harm as Windows also expect the boot/active flag to be on.
Thanks @JZL240I-U; fixed above.
Nope, that's the Windoze disk - when in doubt, trust the (working) config. If Linux successfully boots from a root(hd0,0), the other disk must be hd1. Simple.
And yes, I did see the device.map. And nope, I can't explain it any better without playing around on the box itself.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.