Tri-boot was fine until I upgraded Leo. XP is dead.

#1
I have been using my machine in triboot fine for months. I have Vista on 1st part, XP on 2nd, Leo on 3rd. I decided to try a newer version of Leo, and simply installed over old one without touching the other drives. After getting that done and getting Vista back going then repairing the boot sequence in EasyBCD XP won't get past the loading screen.The only thing that I could see affecting it was using the Vista dvd to repair the Vista boot after installing Leo(I don't know if that would affect it or not).Everything is on the root and set to active boot.ini, NTLDR, NTDETECT. Here is both my BCD details and the boot.ini info.

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 {e8709fb6-fa5f-11db-be4d-e219ece5282e}
displayorder {e8709fb6-fa5f-11db-be4d-e219ece5282e}
{c25a7545-5cf2-11dc-b873-0015c50c40fb}
{c25a7547-5cf2-11dc-b873-0015c50c40fb}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 7
Windows Boot Loader
-------------------
identifier {e8709fb6-fa5f-11db-be4d-e219ece5282e}
device partition=C:
path \Windows\system32\winload.exe
description Vista Ultimate
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice partition=C:
systemroot \Windows
resumeobject {e8709fb7-fa5f-11db-be4d-e219ece5282e}
nx OptOut
Real-mode Boot Sector
---------------------
identifier {c25a7545-5cf2-11dc-b873-0015c50c40fb}
device partition=C:
path \NTLDR
description XP Pro Audio
Real-mode Boot Sector
---------------------
identifier {c25a7547-5cf2-11dc-b873-0015c50c40fb}
device boot
path \NST\nst_mac.mbr
description Leopard


[boot loader]
timeout=7
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="XP Pro Audio" /fastdetect /NoExecute=OptIn
 

mqudsi

Mostly Harmless
Staff member
#2
Hey grey,

Which "loading screen" are we talking about here?
 

Mak 2.0

Mod...WAFFLES!?!?
Staff member
#4
The Vista DVD would not have a affect on XP like this. If anything it could be the Leo upgrade. But restoring the Vista bootloader would not have done this. Your XP install must have gotten corrupted by some other factor.
 

Mak 2.0

Mod...WAFFLES!?!?
Staff member
#6
Well you could try to repair the install via the XP CD. But without knowing how this happened there is no telling if it can be recovered.

How long did you let it sit on the XP loading for?
 

Mak 2.0

Mod...WAFFLES!?!?
Staff member
#8
At best i can say try to repair it vi the XP CD. If it works then great. To get the Vista bootloader back jsut use the Vista DVD again. But if it doesnt then the Leo upgrade corrupted something. I have used teh Vista DVD over 20 times at one point during my Quad Boot process and never did it corrupt my XP install.
 

mqudsi

Mostly Harmless
Staff member
#9
Yep, unfortunately Mak is right.

If you're seeing the loading screen, then the bootloaders have all done their job, everything is configured correctly, and it's an XP-only issue. :frowning:
 
#10
Well, I got it working. I don't exactly know how (which concerns me), but none the less I got it working. I think somehow the partition was corrupted a bit. I ran check disk a couple of times and hid my Leo and shared partitions then it suddenly worked again. Thanks for helping me try to figure it out. I'm just glad I don't have to re-install all my programs.
 

Mak 2.0

Mod...WAFFLES!?!?
Staff member
#11
Congrats on getting it working. I think the hiding of Leo helped. :wink:
 

mqudsi

Mostly Harmless
Staff member
#12
Well, I got it working. I don't exactly know how (which concerns me), but none the less I got it working. I think somehow the partition was corrupted a bit. I ran check disk a couple of times and hid my Leo and shared partitions then it suddenly worked again. Thanks for helping me try to figure it out. I'm just glad I don't have to re-install all my programs.
Good news!

And does Leo still work after this?
 
#13
Hi, the error is usually a sign of your XP drive letter changing, can you confirm your XP drive letter is/was the same before and after the Leopard install.