For a lot of us who dual/tri/quad boot our machines we use GRUB as our Boot Loader. Sometimes the sequence that GRUB boots our machines is not what we want.

I have a machine that dual-boots Windows/MEPIS. I have a Windows network setup and need to have Windows boot instead of MEPIS on a reboot/power failure etc...

Under ROOT privileges:

Open Text editor (eg. KWrite)
Open /boot/grub/menu.lst

You will then see something close to this...

[INDENT]title MEPIS at sdb2, newest kernel
root (hd1,1)
kernel /boot/vmlinuz root=/dev/sdb2 nomce quiet vga=791
boot

title MEPIS at sdb2, older kernel
root (hd1,1)
kernel /boot/vmlinuz.old root=/dev/sdb2 nomce quiet vga=791
boot

title MEPIS at sdb2, kernel 2.6.15-27-desktop64-smp
root (hd1,1)
kernel /boot/vmlinuz-2.6.15-27-desktop64-smp root=/dev/sdb2 nomce quiet vga=791
boot

title Windows at sda1
rootnoverify (hd0,0)
chainloader +1

title Windows at sda5
rootnoverify (hd0,2)
chainloader +1

title MEMTEST
kernel /boot/memtest86+.bin[/INDENT]


Keep the three lines together and move them where you need them. In my case it was this:
[INDENT]
gfxmenu /boot/grub/message

title Windows at sda1
rootnoverify (hd0,0)
chainloader +1

title MEPIS at sdb2, newest kernel
root (hd1,1)
kernel /boot/vmlinuz root=/dev/sdb2 nomce quiet vga=791
boot

title MEPIS at sdb2, older kernel
root (hd1,1)
kernel /boot/vmlinuz.old root=/dev/sdb2 nomce quiet vga=791
boot

title MEPIS at sdb2, kernel 2.6.15-27-desktop64-smp
root (hd1,1)
kernel /boot/vmlinuz-2.6.15-27-desktop64-smp root=/dev/sdb2 nomce quiet vga=791
boot



title Windows at sda5
rootnoverify (hd0,2)
chainloader +1

title MEMTEST
kernel /boot/memtest86+.bin[/INDENT]

As with any MBR (master boot record) be careful what you do and make sure to back up before you make any changes.