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 am very new to Linux. Last night I installed Suse Linux 9.1 pro on my computer. This computer had Windows XP on it before.
Everything went well and I am writing this while on SuSe.
But I am getting a problem when I try to boot using windows. When I select Windows on the boot screen it gives me an error.
This is the error:
Error 13: Invalid or unsupported executable format
Upon further investigation I found this is what it means:
This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).
Now, it seems to me that this GRUB doesn't want to boot any sort of Windows. The thing is, this is what came with the program and is the default setup.
I would appreciate it if anybody would be able to tell me how to fix this problem so I can view Windows.
Thanks for your patience and bearing with my newbieness.
I'm not sure if this will help, but I do know that if the xp is using NTFS instead of FAT 32 file system, you cannot dual boot, not with Linux or even windows 9.X.
I made that mistake and spent 2 hours in the phone with MS support to get windows running again with out losing data.
If you using a legal copy of XP, you get 2 free support calls. I'm no M$ fan, but the help I got was impressive.
Originally posted by scottsteibel
I'm not sure if this will help, but I do know that if the xp is using NTFS instead of FAT 32 file system, you cannot dual boot, not with Linux or even windows 9.X.
Oh my God ... hope my dual-boot machines won't
stop working when I read to them that they're not
supposed to be working since they're on ntfs. :}
I have WinXp on NTFS and I dual-boot just fine (sort of, I have my own problems but Windows I can definitely boot by using Grub. And your Grub entry looks just like mine, for Windows. Sorry I can't be of any more help than that.
I was working in the boot loader configuration in Yast and it looks like Windows has disappeared from the menu. When I try to reset the settings to anyway Windows doesn't show up.
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 649 5208808+ b W95 FAT32
Partition 1 does not end on cylinder boundary.
/dev/hda2 * 650 9260 69167857+ 7 HPFS/NTFS
/dev/hda3 9261 9727 3751177+ f W95 Ext'd (LBA)
/dev/hda5 9261 9320 481918+ 82 Linux swap
/dev/hda6 9321 9727 3269196 83 Linux
Ummm ... with my limited knowledge of Grub I'd say
that the output of your grubmenu and the output of
fdisk match ... I can't see why it wouldn't be working,
but then I have no idea what chainloader +1 does...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.