can't remove 2 useless entries in boot manger

I've read a similar question here (you can skip):
http://ubuntuforums.org/showthread.php?t=829466

and then go through an excellent long article about BCDedit
(you can skip too):
http://technet.microsoft.com/en-us/l.../cc721886.aspx
but only find it useless.
It seems I've got a rare problem...god help me!

My problem is I've tried several times to install Ubuntu but failed.
Resulting in adding two more useless entries in the Windows boot manager, one is Ubuntu (Linux OS), the other is Wingrub (Software to load Linux).

Either of them won't run, and XP and Windows 7 are good.
How could I remove them??????????

I have two hard drive, two system : Windows XP Windows 7
when I use bcdedit to edit Windows Boot Configuration Data, there's no "Ubuntu" or "wingrub",
so I really don't know how to use command-line "bcdedit /delete" or what to delete (which {ID}).

If you know how to deal with this problem, please leave me a message,
for god's sake, I've working on it for 72 hours, it's driving me crazy.
Thank you soooooooooooooo much!
mail me is fine too. [email protected]

 

here is the Boot Configuration Data:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {fa81845e-07b7-11de-8c1a-99c28aeb518d}
displayorder {ntldr}
{current}
toolsdisplayorder {memdiag}
timeout 15

Windows Boot Loader
-------------------
identifier {fa81845c-07b7-11de-8c1a-99c28aeb518d}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\fa81845c-07b7-11de-8c1a-99c28aeb518d\Winre.wim,{fa81845d-07b7-11de-8c1a-99c28aeb518d}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\fa81845c-07b7-11de-8c1a-99c28aeb518d\Winre.wim,{fa81845d-07b7-11de-8c1a-99c28aeb518d}
systemroot \windows
nx OptIn
detecthal Yes
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=E:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {fa818460-07b7-11de-8c1a-99c28aeb518d}
recoveryenabled Yes
osdevice partition=E:
systemroot \Windows
resumeobject {fa81845e-07b7-11de-8c1a-99c28aeb518d}
nx OptIn

Windows Boot Loader
-------------------
identifier {fa818460-07b7-11de-8c1a-99c28aeb518d}
device ramdisk=[E:]\Recovery\fa818460-07b7-11de-8c1a-99c28aeb518d\Winre.wim,{fa818461-07b7-11de-8c1a-99c28aeb518d}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[E:]\Recovery\fa818460-07b7-11de-8c1a-99c28aeb518d\Winre.wim,{fa818461-07b7-11de-8c1a-99c28aeb518d}
systemroot \windows
nx OptIn
detecthal Yes
winpe Yes

Resume from Hibernate
---------------------
identifier {fa81845e-07b7-11de-8c1a-99c28aeb518d}
device partition=E:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=E:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=C:
path \ntldr
description Windows XP

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{7ff607e0-4395-11db-b0de-0800200c9a66}

Inherited Settings (20200003)
-----------------------------
identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
custom:250000f3 0
custom:250000f4 1
custom:250000f5 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {fa81845d-07b7-11de-8c1a-99c28aeb518d}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\fa81845c-07b7-11de-8c1a-99c28aeb518d\boot.sdi

Device options
--------------
identifier {fa818461-07b7-11de-8c1a-99c28aeb518d}
description Ramdisk Options
ramdisksdidevice partition=E:
ramdisksdipath \Recovery\fa818460-07b7-11de-8c1a-99c28aeb518d\boot.sdi

 

Have you tried running MSCONFIG and deleting the unwanted entries from the boot tab ?

 

I had the same exact problem. I tried installing Ubuntu 6 times and it failed in everyone of them. I had six useless entries. I download this and it helped me fix the problem.

Basically, this will let you modify your bootloader. I don't know if it works with XP or 7, but it worked for me in Vista.

 

You can edit it by hand and remove the erroneous entries. Use notepad.

If you haven't already found it look on your C: partition, or whichever is the boot partition for a file called boot.ini, it may be hidden so you may need to alter the folder options via the tools menu in windows explorer (not internet explorer).

Then just open it with notepad and edit it. Press CTRL+S to save it otherwise it'll get saved as a .txt file, you may also wish to check that it's not read only first.

I would advise you do a backup of the file first though, just in case.

 

yes, I did.
It don't show error entries.

 

I've tried several software to solve this problem:
easyBCD VistaBootPro...
none of them worked

 

I solve the problem before your post, but thanks any way.
thank you all for reply, thank you very much.

I edit the boot.ini using notepad, the same way you mentioned.

I didn't use this way first because I believe Windows 7 or Vista develop a totally new way to boot up, using Boot Configuration Data, so it won't change anything if I edit the "boot.ini".

It accured to me when I enter the Windows Xp, I have to choose again, there are 3 options:
1.Windows XP pro
2.Ubuntu
3.WinGrub
just "Windows 7" is disappeared from "Windows Boot Manger".

WinGrub which I installed is a version at 2005 or earlier,
so WinGrub won't do anything to Boot Configuration Data, because he don't even know it!

That means what WinGrub did and the only thing he did is add an entry in boot.ini.

So when I use BCDedit in Windows 7(cmd run as administrator)to view the BCD file, he did show me every thing recorded(I thougt he hide entries that he doesn't recognise or have sth wrong).

Now, probably most of you know what happened.
Let me explain: correct me if I'm wrong please!([email protected])

1.Generally computer load MBR (Master Boot Record), then we choose an Operation System from a list if you have multiple OS, if you choose Windows XP or Vista or Windows 7 then load bootsector to guide the system.
2.In my case, power on, BIOS, MBR, then Windows Boot Manger (using Boot Configuration Data), BCD is in charge of everything I see.
3.BCD load entries that created at earlier version like XP from "boot.ini".

You can close entries using BCDedit, or just edit "boot.ini" adding ";" just before these entries and timeout=0.

4.That means when I first install Ubuntu(Linux), he didn't creat an entry in BCD for me, I have to creat it manually using BCD.