XP Pro / XP Pro 64 / Vista / the X fruit

#1
I know it is pretty much the same old thing but I have searched and tried and beat my head against a wall for a week. I had a dual boot XP Pro / Vista Ultimate setup which did just fine. After getting a new hd I decided to take it two steps further. I have tried everything, the biggest thing that I hear is install in release order XP / 64 / Vista / the X fruit or the X fruit / Vista. I have never been able to get all three Windows OSes to coexist. XP and 64 do fine together but no matter what I try with XP / 64 installed Vista dies after the first reboot when installing unless it is run on the first slot unformatted and without anything else on that slot. Why can I not have it formatted in order. My other question is do I need to format the X fruit's partition to primary also (as Acronis appears to make possible) or will that just confuse the system.
 
#2
First thank you for the awesome product, I can't wait until it is all in place and I can really put EasyBCD to use, it has already saved me tons of headache.

Okay, I have all three successfully installed and I was able to get BCD restored, but now I can't get into XP / x64.

Here is what I have got:

Code:
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 {62cf43bb-5ceb-11dc-b57b-de5af81f08a3}
displayorder {62cf43bb-5ceb-11dc-b57b-de5af81f08a3}
{c25a7525-5cf2-11dc-b873-0015c50c40fb}
{c25a7526-5cf2-11dc-b873-0015c50c40fb}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 7
Windows Boot Loader
-------------------
identifier {62cf43bb-5ceb-11dc-b57b-de5af81f08a3}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=C:
systemroot \Windows
resumeobject {62cf43bc-5ceb-11dc-b57b-de5af81f08a3}
nx OptIn
Windows Boot Loader
-------------------
identifier {c25a7525-5cf2-11dc-b873-0015c50c40fb}
device partition=D:
path \Windows\system32\winload.exe
description XP Pro Audio
osdevice partition=D:
systemroot \Windows
resumeobject {85b61fb1-5cf4-11dc-8781-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {c25a7526-5cf2-11dc-b873-0015c50c40fb}
device partition=D:
path \Windows\system32\winload.exe
description XP Pro 64
loadoptions DDISABLE_INTEGRITY_CHECKS
bootdebug No
osdevice partition=D:
systemroot \Windows
nx OptIn
pae ForceDisable
sos No
debug No
Simple Version:

Code:
There are a total of 3 entries listed in the Vista Bootloader.
Bootloader Timeout: 7 seconds.
Default OS: Microsoft Windows Vista
Entry #1
Name: Microsoft Windows Vista
BCD ID: {current}
Drive: C:\
Bootloader Path: \Windows\system32\winload.exe
Windows Directory: \Windows
Entry #2
Name: XP Pro Audio
BCD ID: {c25a7525-5cf2-11dc-b873-0015c50c40fb}
Drive: D:\
Bootloader Path: \Windows\system32\winload.exe
Windows Directory: \Windows
Entry #3
Name: XP Pro 64
BCD ID: {c25a7526-5cf2-11dc-b873-0015c50c40fb}
Drive: D:\
Bootloader Path: \Windows\system32\winload.exe
Windows Directory: \Windows
Any help is more than appreciated.
 

mqudsi

Mostly Harmless
Staff member
#3
Hi greyreap, welcome to NeoSmart Technologies.

This sounds more like a Boot.ini misconfiguration than a BCD issue.

Looking at your EasyBCD output, there should be a NTLDR and NTDETECT.COM on drive D: - is that correct?

Normally they would be on C:\, together with the bootmgr and the boot folder...

Where is your boot.ini located? Can you paste the contents here? (please use a [c o d e] box :smile:)
 
#4
Actually, I messed up when I input the OS types into EasyBCD, I added them under Vista/Longhorn rather than XP. After I changed it they were all running great. Again awesome product, now if I can just figure out why X isn't recognizing my drives when asked where to install it, even though they show up in its disk utility. Not an EasyBCD problem I know but I figured I would throw it out there.
 

mqudsi

Mostly Harmless
Staff member
#5
Sounds like a driver problem - what kind of drives are they? SATA? RAID?