EasyBCD does't recognize XP

No, I'm referring to needing to sit down and write the code that does that, then upload a new build you guys can use :smile:

For now, you'll need to manually locate the file and remove the read-only flag.
 
Computer Guru said:
No, I'm referring to needing to sit down and write the code that does that, then upload a new build you guys can use :smile:

For now, you'll need to manually locate the file and remove the read-only flag.
Click to expand...

Thanks a lot.

Last question, where is the file located? That should be all I need to fix this. :smile:

Addendum:

Okay, I'm pretty sure I got it.

I saved a boot.ini via legacy to my C: and F: directories. I rebooted and XP worked, but it froze while booting. I realized I forgot to rename to WinXP folder and in the boot.ini on F drive. I did this, then I got a missing dll error, so I changed to "winxp" on the boot.ini on my C: drive as well - this fixed it.

I had to show hidden folders and files as well as take read only off in order to edit the boot.ini's.

Hopefully I'm able to re-load Windows 7 next time I try..
 
Last edited:
I have the same problem with the WINXP folder name but explorer does not give me the option to rename it. How can I do this??
 
You can't rename it from within XP.

Addendum:

Question: does Windows by default ever use WINXP? I seem to recall there's a particular case where it may.... perhaps when upgrading from 2k or ME?
 
Last edited:
I *know* I've seen it before.... I kinda recall seeing being presented with a dialog and having WINXP as the default, but I'd done so many unorthodox XP installs back in the day, it could be anything.

Basically, if it's in any way official, I'll add it to BootGrabber.


Addendum:


I think it was either a Whistler or Longhorn beta build.
 
Last edited:
Good idea to add it.
It's cropped up so many times that even if it's not of MS origin, it seems to be the regular choice of "self namers", and a predictably obvious one.
 
Wjhall and anyone else with XP installed to \WINXP : as a gesture of goodwill from your friends at NeoSmart, you'll find that the latest EasyBCD beta build (and future releases starting with 2.1) will recognize, detect, and configure your XP ou-of-the-box, no hacks needed or required.

:smile:

Addendum:

EasyBCD beta download: EasyBCD 2.1 Beta Builds - The NeoSmart Forums
 
Last edited:
thanks for all master of easyBCD, now I can boot with two OS again. who have problem like me,
HDD 0, partition 1, FAT32, winXP
HDD 0, partition 2, NTFS, win7

and if I add new entry fro my XP he (easyBCD 2.0.2) say
" easyBCD failed to detect a valid installation of windows
NT-2003 or all mounted driver and was unable to continued "

and the solution is :
EasyBCD beta download: EasyBCD 2.1 Beta Builds - The NeoSmart Forums
 
Hello, I have the same problem: "EasyBCD failed to detect a valid installation of Windows NT-2003 [...]".

My Windows folder is named WINDOWS. It's XP Pro x64.

I have tried with the suggested BootGrabber.exe as well as the newest beta of EasyBCD.

Any advice?
 
WARN: Unable to get volume information for \\?\Volume{f5b28e2a-737b-11e0-becd-80
6e6f6e6963}\
D0,5,4,2,640135028736,0
P1,H:\,39,15032385536,2621186048,Yes,multi(0)disk(0)rdisk(0)partition(1),No,
P2,C:\,7,104857600,68702208,Yes,multi(0)disk(0)rdisk(0)partition(2),Yes,NTFS
P3,F:\,7,322233696256,284977225728,Yes,multi(0)disk(0)rdisk(0)partition(3),No,NT
FS
P0,,15,302761639936,0,Yes,,No,
P4,D:\,7,229360271360,208969809920,No,multi(0)disk(0)rdisk(0)partition(4),No,NTF
S
P0,,5,73400320000,0,No,,No,
P5,E:\,7,73399271424,58699862016,No,multi(0)disk(0)rdisk(0)partition(5),No,NTFS

E:\Program Files (x86)\NeoSmart Technologies\EasyBCD\bin>

###

C: is some kind of a utility partition
D: is a data partition
E: is XP system
F: (appears as C in Win 7) is win 7 system
 
What's drive H?

It has some weird filesystem! It's showing up as Plan9 which makes no sense.
 
I'm not sure. It's not mounted in XP. The computer came with 3 partitions:
- Win 7 system
- 100 MB Utility partition
- 14 GB restore partition (maybe it's this one?)

I've added the data and XP partitions.
 
Hi, I'm also running into the "failed to detect" problem, I have a netbook which came with pre-installed Win 7 Starter and I installed Win XP from an USB key.

I already tried replacing BootGrabber.exe,
I also installed the beta build 146
The Win 7 (partition D) folder is called Windows
The Win XP (partition E) folder is called WINDOWS

here's the BootGrabber output:

Code: 
E:\Program Files\NeoSmart Technologies\EasyBCD\bin>BootGrabber.exe /tlist

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

D0,5,4,2,250059350016,1
P1,G:\,39,13958643712,3106320384,Yes,multi(0)disk(0)rdisk(1)partition(1),No,
P2,F:\,12,4294967296,2853568512,Yes,multi(0)disk(0)rdisk(1)partition(2),No,FAT32

P3,C:\,7,104857600,77398016,Yes,multi(0)disk(0)rdisk(1)partition(3),Yes,NTFS
P0,,15,231698595840,0,Yes,,No,
P4,D:\,7,126438342656,108160606208,No,multi(0)disk(0)rdisk(1)partition(4),No,NTFS
P0,,5,105259204608,0,No,,No,
P5,E:\,7,105258156032,101873971200,No,multi(0)disk(0)rdisk(1)partition(5),No,NTFS
D1,1,1,0,4026531840,-1
P1,U:\,7,4026531328,3270258688,Yes,,Yes,NTFS


E:\Program Files\NeoSmart Technologies\EasyBCD\bin>BootGrabber.exe /bootcfg

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

 Drive 0, Partition 1: No Windows installation found.
 Drive 0, Partition 2: No Windows installation found.
 Drive 0, Partition 3: No Windows installation found.
 Drive 0, Partition 4: Windows Vista+ (Ignored).
 Drive 0, Partition 5: Valid Windows 2k/XP/2k3 (Added).
 Drive 1, Partition 1: No Windows installation found.
Unable to detect correct boot device, quitting.

(the /bootcfg in the earlier version of BootGrabber only told me it's unable to detect the correct boot device and nothing else)
edit - the C: partition contains the boot info, D: is win 7 and F: partition is Android (preinstalled along with Windoze 7) - these 3 were already present. I split D: in 2 and got E:, which I put XP on - Hth.


Thank you in advance for your help and have a nice day.
 
Last edited:
The reason is because it's not detecting a boot device. As you can see from the tlist output above, the disk is being seen as rdisk(1) instead of rdisk(0).

Usually, this is a result of booting from a different disk in the BIOS. Is that the case?
 
Back
Top