EasyBCD does't recognize XP

I have WinXP and Win7 installed, but no boot manager. Can you help?

This is what I've done:

Partitioned a RAID-1 BIOS array on a Gigabyte MA770-UD3 as follows:

PRI [C:] NTFS 80GB Windows7
PRI [C:] FAT32 10GB WinXP Pro *
Logical [D:] FAT32 20GB data & DOS pgms
Logical [E:] NTFS 100GB future data
Logical [F:] NTFS 120GB future data
Logical [G:] NTFS 146GB future data

* Originally had tried install of Win98SE. Unsuccessful. Turned this up on the MSI site:
"Because of the limitations of chipset, this MB does not support Win98/ME"
(Same chipset as my board - AMD 770.)

Secondly, installed Windows7 on the 80GB partition.

Thirdly, reformatted that 10GB partition, and installed WindowsXP instead of Win98. O.K.

Tried a "repair" of Windows7, from the original Windows7 DVD, thinking it would now
"see" the WinXP installation on the 2nd primary partition. Unsuccessful.

Reading in "Windows 7 Annoyances", I came up against the problem of editing Boot.ini or
BCDEDIT. Clearly I would not have known what I was doing.

So, I downloaded and ran EasyBCD V2.0.2 from neosmart. It did not run successfully,
giving this, when trying to "Add" the WinXP installation:
"EasyBCD failed to detect a valid installation of Windows NT-2003 on all mounted drives
and was unable to continue."

Following this thread EasyBCD does't recognize XP - The NeoSmart Forums, I performed the
action in Post #2, and downloaded a "different" BootGrabber.exe, though I suspect the
original version in V2.0.2 of EasyCD is just as current. There are minor differences
in their output:


Output with "downloaded" version of BootGrabber.exe file:

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2010 <http://neosmart.net/>



Unable to get volume information for \\?\Volume{edeaa49f-e4a5-11df-b559-806d6172696f}\

Unable to get volume information for \\?\Volume{edeaa49e-e4a5-11df-b559-806d6172696f}\

D0,6,3,4,499999965184,0
P1,,23,83889598464,63829258240,Yes,multi(0)disk(0)rdisk(0)partition(1),No,

P2,C:\,12,10487232000,5980315648,Yes,multi(0)disk(0)rdisk(0)partition(2),Yes,FAT32

P0,,15,405621457920,0,Yes,,No,

P3,D:\,11,20974431744,19708641280,No,multi(0)disk(0)rdisk(0)partition(3),No,FAT32

P0,,5,104864094720,0,No,,No,

P4,E:\,7,104864062464,104759963648,No,multi(0)disk(0)rdisk(0)partition(4),No,NTFS

P0,,5,125830333440,0,No,,No,

P5,F:\,7,125830301184,125736525824,No,multi(0)disk(0)rdisk(0)partition(5),No,NTFS

P0,,5,153952565760,0,No,,No,

P6,G:\,7,153952533504,152415801344,No,multi(0)disk(0)rdisk(0)partition(6),No,NTFS

D1,1,1,0,4009754624,-1
P1,I:\,12,4009722368,2072584192,Yes,,Yes,FAT32




Output with native BootGrabber.exe from V2.0.2:

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2010 <http://neosmart.net/>



Unable to get volume information for \\?\Volume{edeaa49f-e4a5-11df-b559-806d6172696f}\

Unable to get volume information for \\?\Volume{edeaa49e-e4a5-11df-b559-806d6172696f}\

D0,6,3,4,499999965184,0
P1,,23,83889598464,63829258240,Yes,multi(0)disk(0)rdisk(0)partition(1),No,

P2,C:\,12,10487232000,5980372992,Yes,multi(0)disk(0)rdisk(0)partition(2),Yes,FAT32

P0,,15,405621457920,0,Yes,,No,

P3,D:\,11,20974431744,19708641280,No,multi(0)disk(0)rdisk(0)partition(3),No,FAT32

P0,,5,104864094720,0,No,,No,

P4,E:\,7,104864062464,104759963648,No,multi(0)disk(0)rdisk(0)partition(4),No,NTFS

P0,,5,125830333440,0,No,,No,

P5,F:\,7,125830301184,125736525824,No,multi(0)disk(0)rdisk(0)partition(5),No,NTFS

P0,,5,153952565760,0,No,,No,

P6,G:\,7,153952533504,152415801344,No,multi(0)disk(0)rdisk(0)partition(6),No,NTFS

D1,1,1,0,4009754624,0
P1,I:\,12,4009722368,2072723456,Yes,,Yes,FAT32


Output of BootGrabber.exe /bootcfg (using native V2.0.2 BootGrabber):

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2010 <http://neosmart.net/>



Unable to get volume information for \\?\Volume{edeaa49f-e4a5-11df-b559-806d6172696f}\

Unable to get volume information for \\?\Volume{edeaa49e-e4a5-11df-b559-806d6172696f}\

Located active partition on drive 0: \ArcName\multi(0)disk(0)rdisk(0)partition(2)

Drive 0, Partition 2: Valid Windows 2k/XP/2k3 (Added).
Drive 0, Partition 3: No Windows installation found.
Drive 0, Partition 4: No Windows installation found.
Drive 0, Partition 5: No Windows installation found.
Drive 0, Partition 6: No Windows installation found.
Located active partition on drive 0: \ArcName\multi(0)disk(0)rdisk(0)partition(2)

Drive 1, Partition 1: No Windows installation found.
Failed to create file to \ArcName\multi(0)disk(0)rdisk(0)partition(2)\Boot.ini. Error code: 0xc0000022.





Boot.ini from the WinXP partition:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimer


Output from bcdedit of the Windows7 partition:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {2c600a6a-d936-11df-9ae6-9efad75921a2}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {2c600a6c-d936-11df-9ae6-9efad75921a2}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {2c600a6a-d936-11df-9ae6-9efad75921a2}
nx OptIn


(Clearly no "Windows Legacy OS Loader".)

If you've stayed with me this long, I appreciate your effort. It has been a long post.
(It's easier to ignore the irrelevant than to need information and not have it.)

I don't think I'll be able to wrap my 67-year-old brain around the vagaries of BCDEDIT.
Does anyone have a "fix" that would get this system dual-booting. I'm exasperated.

Thanks in advance,

- Ralph
 
The problem is with the filesystem. Bootgrabber has a problem with FAT.
Convert it to NTFS and delete/add the XP entry , and the auto-configure should be fine.
 
Thanks, Terry!

Will converting the 2nd Primary partition (WinXP) to NTFS curtail my ability to run the DOS programs on the FAT32 [D:] logical partition?

The need to run DOS programs is what started this whole dual-boot scenario, as I was unable to run them from Windows7, no matter how many hoops I jumped through.

Thanks again,

- Ralph
 
No, they should still work. The filesystem does not matter to most applications, as they go through the OS to access it.
 
Many thanks!

Converting the WinXP partition from Fat32 to NTFS went successfully, and I'm still able to run the DOS pgms on [D:] just as you said.

I still haven't got this dual-booting, though. I'm toggling back & forth between the two Primary Partitions, via a utility on CD. Either O/S will boot successfully, once the active partition is set for that O/S, and the computer rebooted.

I ran EasyBCD from both partitions. While booted into the 1st Primary (Win7), attempting to "add" WinXP returned the familiar "EasyBCD failed to detect a valid installation of Windows NT-2003 on all mounted drives and was unable to continue."

Here's the output from the information area of EasyBCD:

On WinXP partition:

There are a total of 2 entries listed in the bootloader.

Default:
Timeout: 30 seconds
Boot Drive: C:\

Entry #1
Name: Windows 7 Professional (recovered)
BCD ID: {0e83a786-ed2c-11df-a95d-b166b9fe2554}
Device: \Device\HarddiskVolume1
Bootloader Path: \Windows\system32\winload.exe

Entry #2
Name: Microsoft Windows XP
BCD ID: {0e83a78b-ed2c-11df-a95d-b166b9fe2554}
Drive: C:\
Bootloader Path: \NST\ntldr

+++++++++++++++++

Detailed (Debug Mode):

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
displayorder {0e83a786-ed2c-11df-a95d-b166b9fe2554}
{0e83a78b-ed2c-11df-a95d-b166b9fe2554}
timeout 30
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {0e83a786-ed2c-11df-a95d-b166b9fe2554}
device partition=\Device\HarddiskVolume1
path \Windows\system32\winload.exe
description Windows 7 Professional (recovered)
locale en-US
recoverysequence {0e83a787-ed2c-11df-a95d-b166b9fe2554}
recoveryenabled Yes
osdevice partition=\Device\HarddiskVolume1
systemroot \Windows

Real-mode Boot Sector
---------------------
identifier {0e83a78b-ed2c-11df-a95d-b166b9fe2554}
device partition=C:
path \NST\ntldr
description Microsoft Windows XP


==============================================================

On Win7 partition:

There is one entry in the Windows bootloader.

Default: Windows 7
Timeout: 30 seconds
Boot Drive: C:\

Entry #1
Name: Windows 7
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe

++++++++++++++++++

Detailed (Debug Mode):

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {2c600a6b-d936-11df-9ae6-9efad75921a2}
resumeobject {2c600a6a-d936-11df-9ae6-9efad75921a2}
displayorder {2c600a6b-d936-11df-9ae6-9efad75921a2}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Boot Loader
-------------------
identifier {2c600a6b-d936-11df-9ae6-9efad75921a2}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {2c600a6c-d936-11df-9ae6-9efad75921a2}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {2c600a6a-d936-11df-9ae6-9efad75921a2}
nx OptIn


Any thoughts on what I should do next? You guys have been very helpful.

And patient.

- Ralph
 
Yes, it's [C:] that I converted to NTFS. (2nd Primary 10GB Partition.)

The DOS pgms & data are located on [D:], which remains a FAT32 logical drive.

- Ralph

Addendum:

Hi Mahmoud!

Here's the latest output from BootGrabber.exe:

From Win7 partition (partition #1):

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2010 <http://neosmart.net/>

Unable to get volume information for \\?\Volume{f1a853b5-d92d-11df-be51-806e6f6e6963}\
Unable to get volume information for \\?\Volume{f1a853b4-d92d-11df-be51-806e6f6e6963}\
D0,6,3,4,499999965184,0
P1,C:\,7,83889598464,63219191808,Yes,multi(0)disk(0)rdisk(0)partition(1),Yes,NTFS
P2,,23,10487232000,6128066560,Yes,multi(0)disk(0)rdisk(0)partition(2),No,
P0,,15,405621457920,0,Yes,,No,
P3,D:\,11,20974431744,19714998272,No,multi(0)disk(0)rdisk(0)partition(3),No,FAT32
P0,,5,104864094720,0,No,,No,
P4,E:\,7,104864062464,104755777536,No,multi(0)disk(0)rdisk(0)partition(4),No,NTFS
P0,,5,125830333440,0,No,,No,
P5,F:\,7,125830301184,125732339712,No,multi(0)disk(0)rdisk(0)partition(5),No,NTFS
P0,,5,153952565760,0,No,,No,
P6,G:\,7,153952533504,152488456192,No,multi(0)disk(0)rdisk(0)partition(6),No,NTFS


From WinXP partition (partition #2):

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2010 <http://neosmart.net/>

Unable to get volume information for \\?\Volume{edeaa49f-e4a5-11df-b559-806d6172696f}\
Unable to get volume information for \\?\Volume{edeaa49e-e4a5-11df-b559-806d6172696f}\
D0,6,3,4,499999965184,0
P1,,23,83889598464,63232204800,Yes,multi(0)disk(0)rdisk(0)partition(1),No,
P2,C:\,7,10487232000,6130151424,Yes,multi(0)disk(0)rdisk(0)partition(2),Yes,NTFS
P0,,15,405621457920,0,Yes,,No,
P3,D:\,11,20974431744,19715014656,No,multi(0)disk(0)rdisk(0)partition(3),No,FAT32
P0,,5,104864094720,0,No,,No,
P4,E:\,7,104864062464,104759971840,No,multi(0)disk(0)rdisk(0)partition(4),No,NTFS
P0,,5,125830333440,0,No,,No,
P5,F:\,7,125830301184,125736534016,No,multi(0)disk(0)rdisk(0)partition(5),No,NTFS
P0,,5,153952565760,0,No,,No,
P6,G:\,7,153952533504,152492650496,No,multi(0)disk(0)rdisk(0)partition(6),No,NTFS

Is it relevant that I am running the onboard AMD RAID in a RAID-1 configuration?

Hope I'm not bombarding you with too much information,

- Ralph
 
Last edited:
Good Evening!
Sorry if I'm beating a dead horse here, but I had a similar problem to what people have posted above. Except I have one additional issue. I renamed the /WINXP folder to /WINDOWS and used the modified BootGrabber file posted earlier, but now I get the error:
"An error occurred while attempting the specified create operation. Insufficient system resources exist to complete the requested service."

My setup is:
Windows 7 installed first on C drive.
Windows XP installed on D drive.
Used windows 7 install disc to repair, boot into windows 7.
Need to create the boot entry to get the ability to boot into both, so I can go into Windows XP and fix the SATA/AHCI driver issue.


C:\Program Files (x86)\NeoSmart Technologies\EasyBCD\bin>bootgrabber /tlist

BootGrabber utility.
Copyright NeoSmart Technologies 2009-2010 <http://neosmart.net/>

D0,4,4,0,320072933376,0
P1,,7,104857600,75055104,Yes,multi(0)disk(0)rdisk(0)partition(1),Yes,
P2,C:\,7,104752742400,79905746944,Yes,multi(0)disk(0)rdisk(0)partition(2),No,NTF
S
P3,D:\,7,104857600000,100029558784,Yes,multi(0)disk(0)rdisk(0)partition(3),No,NT
FS
P4,E:\,7,110355283968,110250180608,Yes,multi(0)disk(0)rdisk(0)partition(4),No,NT
FS
D1,1,1,0,1500299395072,1
P1,G:\,7,1500298346496,716311904256,Yes,multi(0)disk(0)rdisk(1)partition(1),Yes,
NTFS

C:\Program Files (x86)\NeoSmart Technologies\EasyBCD\bin>
Click to expand...
 
Hello there, I recently installed the XP64 on my windows 7 system, on a different partition. my easyBCD fails to detect a valid installation of xp on all drives, using both automatic and manual. i tried the modified bootgrabber to no avail. how should i proceeD?

EDIT: never mind, it seems repairing the boot files in win7 allowed me to successfully add the xp entry, not sure why though, but not it works. thx anyway
 
Last edited:
i got the same problem too, the easybcd cant detect my xp. i have read this thread and the problem is, i dont even able to rename my WINXP folder to WINDOWS even on win7 side.

any solution for me?

edited : i manage to rename it somehow, it seem my xp has changed my account authority. but now i have other problem, i can't edit boot.ini after change it to WINDOWS from WINXP, i'm quite sure i have to change it back to WINXP right? the error msg is boot.ini is set to read only file.
 
Last edited:
Hmm.. after i changed the BootGrabber.exe i get this when trying to add the winxp entry "the procedure entry point encodepointer could not be located in the dynamic link library kernel32.dll" and after that the "EasyBDC failed to detect a valid installation etc..." before changing the bootgrabber i would only get the "failed to detect a valid installation" error

EDIT: repaired wndows 7 with disc and now im able to boot into win7 without problems, but cannot get into the xp again..
 
Last edited:
Use EasyBCD > Tools > Edit Legacy Entries to locate the correct boot.ini and change Windows back to WinXP.
 
Terry60 said:
Use EasyBCD > Tools > Edit Legacy Entries to locate the correct boot.ini and change Windows back to WinXP.
Click to expand...

i done it and it say boot.ini was read only, then i think i need to change it to be writeable before doing that procedure right? but now im on win7 side, i cant find the boot.ini on C:\ which is my win7 partition, and even i got xp shown on boot menu i still cannot go in xp.

i wonder why, i followed ur instruction to rename winxp to windows and change boot.ini to windows as well, after pass that procedure i rename windows back to winxp but i cannot change boot.ini from windows to winxp anymore.
 
Give yourself the correct permissions to modify boot.ini, as you did with the Windows folder.
 
did you read my post? i cant find boot.ini in w7 side ~_~ as should be no boot.ini on w7 right?
so where is it?

am i over stupid to understand 2 post above mine?
 
Back
Top