>.< Grub Wont Load My Xp Home

Nooooooooooooo!
I reinstalled suse and it's still doing the same thing!
[/b]

You know what to report: post menu.lst, outcome of "uname -a"

Can you boot into Windows or Linux?

Could you choose the default kernel? Do you have a dual-processor computer? Could you avoid xen?

You know what to report: post menu.lst, outcome of "uname -a"

Can you boot into Windows or Linux?

Could you choose the default kernel? Do you have a dual-processor computer? Could you avoid xen?
[/b]

I can only boot linux but i cant boot xp.
When i boot i pick the first option
My comp isn't dual or 64. Its a 32. As for xen, i dont think i use it. As far as i know its a viltrual machine. (for emulating?) If this is the case then i dont think i have any use for it right now.

Linux Omoicane 2.6.16.13-4-default #1 Wed May 3 04:53:23 UTC 2006 i686 athlon i386 GNU/Linux


---------------menu.lst--------------------
# Modified by YaST2. Last modification on Wed Sep 6 17:25:08 AST 2006
color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd1,6)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux 10.1
root (hd1,6)
kernel /boot/vmlinuz root=/dev/hdb7 vga=0x317 resume=/dev/hdb5 splash
=silent showopts
initrd /boot/initrd

###Don't change this comment - YaST2 identifier: Original name: XEN (/dev/hdb
6)###
title XEN (/dev/hdb6)
kernel (hd1,5)/boot/xen.gz
module (hd1,5)/boot/vmlinuz-xen root=/dev/hdb6 vga=0x317 resume=/dev/h
db5 splash=silent showopts
module (hd1,5)/boot/initrd-xen

###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
chainloader (hd0,0)+1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux 10.1
root (hd1,6)
kernel /boot/vmlinuz root=/dev/hdb7 vga=normal showopts ide=nodma apm=off
acpi=off noresume nosmp noapic maxcpus=0 edd=off 3
initrd /boot/initrd
~
~
~
~
~
~
~
~
~
/boot/grub/menu.lst lines 1-27/27 (END)
---------------------menu.lst-------------------------

Ok, this menu.lst looks slightly better than the first one. All seems correct. For information reasons, I suggest you replace all "silent"-s with "verbose".

Now, what happens when you try to boot into Windows? How do you do it?

How do you know that you have a functional Windows installation?

One other way to check things is to jump over grub. Put the SUSE installation CD, start installation, then abort when possible (the HD will not be written on). In the screens that will come, choose "Boot installed system" Then select partition /dev/hda1. You shall have Windows running.

Can you re-install windows without much trouble (say, spending 1 day)?

Once you login into SUSE as root, try to mount and see whether the partition has readable contents:

mount -t ntfs -r /dev/hda1 /mnt

or similar. Then go to /mnt. There, read only, don't try to write anything on /mnt

There is a slight chance that you are trying to boot the wrong Windows partition. Try to modify the chainloader (hd0,0)+1 into
chainloader (hd0,1)+1. Then install the boot loader through Yast, as you know it.

Now, what happens when you try to boot into Windows? How do you do it?
How do you know that you have a functional Windows installation?

One other way to check things is to jump over grub. Put the SUSE installation CD, start installation, then abort when possible (the HD will not be written on). In the screens that will come, choose "Boot installed system" Then select partition /dev/hda1. You shall have Windows running.

Can you re-install windows without much trouble (say, spending 1 day)?

Once you login into SUSE as root, try to mount and see whether the partition has readable contents:

mount -t ntfs -r /dev/hda1 /mnt

or similar. Then go to /mnt. There, read only, don't try to write anything on /mnt

There is a slight chance that you are trying to boot the wrong Windows partition. Try to modify the chainloader (hd0,0)+1 into
chainloader (hd0,1)+1. Then install the boot loader through Yast, as you know it.
[/b]

I know windows works because i've had it for like 5 months now. That was the only thing on the computer. Then I installed Vista to try it out. Its all nice-looking but it hugs WAAY too much power. After that i erased vista and installed suse (like 4 am yesterday). Then later when i tried to boot windows to watch some bleach all i got was "chainloader (hd0,0)+1". I can go into the partition and read files. I opened pictures and tested wine... notepad was the only thing i could get it to run... Ill try to "jump over grub" now. Btw thanks for the help

Boot up your XP install disk, go into the recovery console, logon as administrator and run fixmbr (reboot). That should get you back into windows. Now try to reinstall grub. Boot up the SuSE install CD #1. At the first installation screen you can, choose 'other', then 'boot installed system'. Once SuSE loads, go into yast, system, bootloader, and then 'other', select 'new proposal'. This will reinstall Grub.

Boot up your XP install disk, go into the recovery console, logon as administrator and run fixmbr (reboot). That should get you back into windows. Now try to reinstall grub. Boot up the SuSE install CD #1. At the first installation screen you can, choose 'other', then 'boot installed system'. Once SuSE loads, go into yast, system, bootloader, and then 'other', select 'new proposal'. This will reinstall Grub.
[/b]

harryc:

explain to me please. Doesn't the reinstallation of GRUB take care of MBR? Why shall pirokosan run fixmbr? Does fixmbr do something else besides restoring MBR?

Also, if you know, please clarify. I am of the opinion that a PC has one MBR. But I have seen other opinions. What do you think?

Thanks.

explain to me please. Doesn't the reinstallation of GRUB take care of MBR?
[/b]

TTBOMK, when you install Grub it adds a pointer (to itself) in the MBR already present on the disk or partition, but it does not 'replace' it. Grub lives in stage one (and 1.5) of the mbr, but does not touch the stage 2 (partition table). Fixmbr however does repair the master boot record on the disk you run it on. I have seen cases where fixmbr (and a subsequent reinstall of Grub) will allow Grub to work properly. It's always worth a shot, not guaranteed to work. As a side note, if someone has a better knowledge of the mbr and Grub relationship I am interested in learning more. Please speak up.

Meh, i don't have a windows cd that can fix the mbr except for the vista dvd. I tried that but i cant run fixmbr from the recovery console (i dont think the fixmbr.exe is in there). I tried the gui but all it does is diskchk. The windowsXP install cd i have is the one that comes with emachies. (It's only a restore cd, meaning it just wipes disk and reinstalls only). Isn't there a boot disk with fixmbr i can download off the net?

http://www.bootdisk.com/bootdisk.htm

Take a look at the XP Quick Boot Diskette

last time i had this problem i found my xp pro side of my hard drive was hidden and not active, resulting in suse being the only o.s that would boot. i had to boot from my partition magic cd to set the xp pro side active then reboot the pc to find everything was fine
dont know if this is of any use to anyone