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.
Distribution: Red Hat Linux 9, Fedora Core 1, *Fedora Core 2*
Posts: 74
Rep:
Code:
#
# Sample boot menu configuration file
#
# Boot automatically after 30 secs.
timeout 30
# By default, boot the first entry.
default 0
# Fallback to the second entry.
fallback 1
# For booting GNU/Hurd
title GNU/Hurd
root (hd0,0)
kernel /boot/gnumach.gz root=hd0s1
module /boot/serverboot.gz
# For booting GNU/Linux
title GNU/Linux
root (hd1,0)
kernel /vmlinuz root=/dev/hdb1
#initrd /initrd.img
# For booting Mach (getting kernel from floppy)
title Utah Mach4 multiboot
root (hd0,2)
pause Insert the diskette now!!
kernel (fd0)/boot/kernel root=hd0s3
module (fd0)/boot/bootstrap
# For booting FreeBSD or GNU/KFreeBSD
title FreeBSD / GNU/KFreeBSD
root (hd0,2,a)
kernel /boot/loader
# For booting NetBSD or GNU/KNetBSD
title NetBSD / GNU/KNetBSD
root (hd0,2,a)
kernel --type=netbsd /netbsd
# For booting OpenBSD
title OpenBSD
root (hd0,2,a)
kernel --type=netbsd /bsd
# For booting OS/2
title OS/2
root (hd0,1)
makeactive
# chainload OS/2 bootloader from the first sector
chainloader +1
# This is similar to "chainload", but loads a specific file
#chainloader /boot/chain.os2
# For booting Windows NT or Windows95
title Windows NT / Windows 95 boot menu
rootnoverify (hd0,0)
makeactive
chainloader +1
# For loading DOS if Windows NT is installed
# chainload /bootsect.dos
# For installing GRUB into the hard disk
title Install GRUB into the hard disk
root (hd0,0)
setup (hd0)
# Change the colors.
title Change the colors
color light-green/brown blink-red/blue
Heres my menu.lst for grub. BTW i think the problem is grub is not written to the MBR.
basix is correct in saying that so far you have grub in the linux hard drive and if you make the XP boot first, then you have yet to put grub in the XP mbr drive.
But you are right to know there are bios choices.
If you change bios to boot the linux drive first you may not have forced grub to see your new device map file so choosing XP takes you back to the incorrect LINUX partition. error 13 would suggest this. But you mention your linux boots so wt?
Anyhow lets not put grub into your XP drive until we can safely get things working on a floppy first ok?
If you have a floppy drive lets set up grub
mount a formatted floppy and make directories so that its
/mnt/floppy/boot
/mnt/floppy/boot/grub
copy only the stage 1 and 2 files into the floppy grub folder
copy a new menu.lst file into floppy grub folder
###########contents of menu.lst
timeout 5
default 0
fallback 1
title XP is default zero
rootnoverify (hd1,0)
map (hd0) (hd1)
map (hd1) (hd0)
makeactive
chainloader +1
title XP is fallback
rootnoverify (hd0,1)
makeactive
chainloader +1
###########end of file
Setup floppy by opening a terminal and typing su to get root password then type
grub --device-map=/boot/grub/device.map #####to force your device map to be used
prompt changes to grub
root (fd0)
setup (fd0)
should give you some messages and as long as the last line shows succeeded we don't care.
so we have a boot disk that has stage1 in the floppy mbr and a menu list file that will attempt to boot xp one way and then the other without risking your current mbr. Assuming that the fallback kicks in, it means grub did not think XP was on hd1 or your bios is still not set to boot the slave first?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.