Post the contents of your menu.lst file.In which order did you install the two OS?Are you sure you are using grub4dos and not "legacy GRUB"?How is the disk partitioned/formatted? (I mean which filesystems are used, what is your primary bootloader, etc.)

Post the contents of your menu.lst file.In which order did you install the two OS?Are you sure you are using grub4dos and not "legacy GRUB"?How is the disk partitioned/formatted? (I mean which filesystems are used, what is your primary bootloader, etc.)

I am not at all familiar with the Sabayon distro, but I doubt it uses grub4dos, for what I can see it uses the anaconda setup/install, which AFAIK uses GRUB.

Is your primary bootloader GRUB or grub4dos?

If it is grub4dos you should have in the root of your primary active partition a file "grldr" and a file "menu.lst".If it is GRUB you may find only a file "menu.lst" in one of:root\boot\\boot\grubor a similar path.

This does not help me much:

4)My windows partition is NTFS and my primary boot loader is GRUB

My question was different:

How is the disk partitioned/formatted? (I mean which filesystems are used, what is your primary bootloader, etc.)

(I need to try understanding how your WHOLE disk is set, I need details on ALL partitions on it, need to know WHICH one is your Primary Active partition, etc.)

I am not at all familiar with the Sabayon distro, but I doubt it uses grub4dos, for what I can see it uses the anaconda setup/install, which AFAIK uses GRUB.

Is your primary bootloader GRUB or grub4dos?

If it is grub4dos you should have in the root of your primary active partition a file "grldr" and a file "menu.lst".If it is GRUB you may find only a file "menu.lst" in one of:root\boot\\boot\grubor a similar path.

This does not help me much:

My question was different:

(I need to try understanding how your WHOLE disk is set, I need details on ALL partitions on it, need to know WHICH one is your Primary Active partition, etc.)

Does your machine have a floppy drive?

Or can you burn if needed a bootCD?

jaclaz

I'll check out what kind of bootloader I have when I come back to school today.

I'm not sure about my whole disc,how do you find that out? My primary active is my Windows partition.

Does anyone know where I can find an ISO image of a bootCD (legal please) that fixes my problem?

Yes, but the point is that "ISO images" of bootCD (legal or illegal) are generally not "magic items" that by themselves take control of your PC, find what the problem is and fix it.

The order in which one NEEDS to proceed is:1) find what the problem is2) find the cause of that problem3) find a remedy to the cause of that problem4) use a bootcd or whatever to apply the remedy

Having 4) above does not help much until you also have 1) to 3).

Particularly, it does not exist a "non-linux" "legal" "ISO image" of a bootCD capable of solving the problem, WHATEVER it might be, and since you are saying that you already can boot to Linux, I don't see the point of creating a bootCD to boot something that is the same (or very similar to) what you ALREADY can boot, without even troubling yourself with burning a bootCD.

I was thinking about making you create a grub4dos boot floppy or burn a grub4dos bootCD, but I would like to know how the heck is your drive partitioned and what the heck you have in your menu.lst.

If you are sure that you are into grub4dos when you fail booting, you do not need even a grub4dos floppy/bootCD.

DO NOT, and I mean DO NOT, meaning DO NOT issue any other command, and DEFINITELY NOT the parttype one until you get some instructions from me or some other member, this is tricky business, and doing the wrong thing may worsen the situation.

Yes, but the point is that "ISO images" of bootCD (legal or illegal) are generally not "magic items" that by themselves take control of your PC, find what the problem is and fix it.

The order in which one NEEDS to proceed is:1) find what the problem is2) find the cause of that problem3) find a remedy to the cause of that problem4) use a bootcd or whatever to apply the remedy

Having 4) above does not help much until you also have 1) to 3).

Particularly, it does not exist a "non-linux" "legal" "ISO image" of a bootCD capable of solving the problem, WHATEVER it might be, and since you are saying that you already can boot to Linux, I don't see the point of creating a bootCD to boot something that is the same (or very similar to) what you ALREADY can boot, without even troubling yourself with burning a bootCD.

I was thinking about making you create a grub4dos boot floppy or burn a grub4dos bootCD, but I would like to know how the heck is your drive partitioned and what the heck you have in your menu.lst.

If you are sure that you are into grub4dos when you fail booting, you do not need even a grub4dos floppy/bootCD.

DO NOT, and I mean DO NOT, meaning DO NOT issue any other command, and DEFINITELY NOT the parttype one until you get some instructions from me or some other member, this is tricky business, and doing the wrong thing may worsen the situation.

jaclaz

Nice! helps me a lot! it has the same problem as I do,my windows partition seems to be (hd0,2) because it's a notebook I confirmed it because it said that the partition is NTFS.

Now I'll follow those instructions in the other thread to see if I successfully boot.

Thanks a lot Jaclaz you are a GENIUS!

(I haven't resolved my problem but I know I will with your amazing advice!)

Here's the result of the geometry command (they were all the same (hd0,0+1+2)

Hi, the problem I have is with Windows XP professional but I thought it better to ask for help here rather than starting a new post since the symptoms are very similar to what Pikachu described before. I have also read this closed post http://www.boot-land...?...=3833&st=40. I seem to be getting the idea of what is going on but since jaclaz has suggested not to rush into using the 'parttype' command I rather wait to read any suggestions from the experts. Here is a summary of the problem and some information I have collected (Thanks in advance for any help provided):

1. When I start my PC, it goes to GNU Grub version 0.95 where I can choose between starting Linux or Windows XP Pro. I only have one physical drive partitioned for Linux and Windows.

2. I can boot Linux but when trying to boot Windows I get the typical black & white screen with the following message:

"We apologize for the inconvenience, but Windows did not start successfully. A recent hardware or software change might have caused this.

If your computer stopped responding, restarted unexpectedly, or was automatically shut down to protect your files and folders, choose Last Known Good Configuration to revert to the most recent settings that worked.

If a previous startup attempt was interrupted due to a power failure or because the Power or Reset button was pressed, or if you aren't sure what caused the problem, choose Start WindowsNormally.

Safe ModeSafe Mode with NetworkingSafe Mode with Command Prompt

Last Known Good Configuration (your most recent settings that worked) Start Windows Normally"

3. Choosing any one of the five options given in the black & white screen won't boot windows and will show for a fraction of a second another screen with:

"A problem has been detected and windows has been shut down to prevent damage to your computer. If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps. Check for viruses on your computer. Remove any newly installed hard drives or hard drive controllers. Check you hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption and then restart your computer.Technical information:xxx STOP: 0X0000007B (0XF7C84640,0XC0000034,0X00000000,0X00000000)"

Restarting the computer and trying to boot windows only takes me back to the blue screen over and over.

4. Back to the GNU grub menu, I pressed 'c' to see the selected command in the boot sequence, which is:

"root (hd0,0) savedefault makeactive chainloader +1"

5. Also in Grub, I have typed the 'root', 'geometry' and 'find' commands with these results:

Options if your HDD is larger than 1TB:
* Move your boot files to a smaller partition at the start of the HDD.
* Format the HDD and allow Windows 7 to create a 100MB boot partition.
* Shrink and move your partitions with GParted.

Options if you have an OEM/Recovery partiion"
* Format the whole HDD with Active@ Kill desk.
* if possible use EasyBCD to relocate the boot files.

Hello.
I had the same problem for 1 hour ago. But i think i did something real STUPID. when i came to grub > i wrote this command. 1) rootnoverify (hd0,2 2) chainloader +1 3) makeactive 4) boot
After that my pc restarted an now i am in a black and white page and this is what it say. Error: Bootmgr is missing Press Ctrl+Alt+Del to restart

I have no fully understanding of computer but i know i have changed some places with eachother. I do not have any recovery cd or anythinf. I tried everything that comes upp when i push at ESC but no luck. Please hell me i have not any pc now for 2 days. And i am here with my iphone.
Thanks alot

First of all. Thank you for your time. Before when i restarted i came to grub> promt but after i did that stupid thing the onley place i come to is that bootmgr error.
If nothing can be done. I have lost all my lifes history in pc. I downloade Spyhunter and after it searches it asked me to restart and thats why i am here.
I have windows 7 ultimate 32.
How can i get a bottibls cd. Is there any place i can downloaded or get it ?
Thanks

NO, rest assured, unless that program did some other "destructive" operation, all your data is perfectly OK , only you cannot boot to that PC until you repair it's booting mechanism.

To be very clear, what is now preventing your PC from booting is not the effect of that stupid tool running incorrectly the grub (most probably grub4dos) bootmanager, it is your entering it commands without knowing what you were doing.

Seemingly, BUT it MUST be verified BEFORE doing some other mistake, what you messed up - basically is the active status of a partition.

IF this is the case, the best tool/thing you can try is making a UBCD bootable CD:

Then, after having booted to it, you will need to inspect (following instructions, not "inventing commands" like you did before) the internal hard disk, so that we can understand what happened exactly, and find a way to get back first to the same grub> prompt you had before, and from it, restore the working of the boot part of the OS as it was before.

You will need another PC (with a CD/DVD writer) to download the UBCD .iso file and make a CD (or alternatively have, besides the PC, a USB stick with no data in it).

Alternatively, (and hopefully) a "normal" Windows 7 install CD (not necessarily "ultimate") may do, as well as *any* bootable Linux distro, as it seems like the only "damage" is that you managed to change the active partition.

Even a much simpler USB stick created with (say) RMPREPUSB (with grub4dos) may be enough. <- this is probably the simpler choice, but still you need a PC and a USB stick.

In other words, you need to *somehow* boot to *something*, then we'll see how to fix that issue.

Hei.
If i have understanded you correctly. I go to this site and downoad some boot tool for my windows and then move on.
OR i download some windows 7 program and move on to it ?
You see i am not so smart like you. As you know i wrote my own Code :-)
And i have to come back to this Grub > thing ?
Th aks again for your time my friend.

Yes, basically what happened is that the stupid tool you used has been very badly scripted and assumes that the machine on which it is run has a given partitioning scheme.

Most modern notebooks use a different one, having "OEM recovery partitions" or similar.

In these cases the thing fails, and defaults to a grub> prompt.

From this stage, it is normally possible to revert the previous state (by giving to the grub/grub4dos the "right" commands) but seemingly you accidentally issued some commands that modified the status of the hard disk partitions by marking another partition as active.

In other words:

Original=boot to Windows 7

Modified=boot to grub/grub4dos

Current=NO boot

You need to boot to *something* and since there is no way on earth, in current situation to boot anything from the internal hard disk, you need to supply *something else* from the outside, i.e. boot from an external device/media, which once would have been a good ol' floppy drive, but nowadays is basically either a CD/DVD or a USB stick or hard disk.

There is nothing to "move on".

You need to have an external boot/media device, a set of options have been presented before you, with all due respect if you do not understand this, it would be much better if you call a friend, a relative that has some more experience with PC's or a paid for technician.

It is not "difficult", but if you don' t know how to download a file, and make from it a bootable CD/DVD or have a USB stick, download a program and run it on another PC (or you have not another PC and/or a CD/DVD burner on it and a CD/DVD blank disk and/or a USB stick) there is no sense in going on on this thread.

To use a car comparison, you just posted how your car does not start and you were suggested that it is possible that you have to clean your spark plugs, and pointed to several types of spark plug spanners, but if you do not know even how to open the bonnet/hood of your car it is simply not possible that you will be able to make it start again any soon .

I can instruct you on how to use some specific tool, but you cannot pretend to have a crash course from "knowing nothing" to "advanced PC user" in no time and over a few forum posts.