I've been following your topic there thinking of a way to possibly fix the
issue, sorry you're having so much trouble. The topic and some background info
is here for those that haven't:
http://www.pro-networks.org/forum/about78231.html
Now, what I think the problem is in this, is the edits that you attempted to
make in it previously, changing the first entry to XP and not leaving it as the
default. I don't know if that is what is causing it, but it's my guess. I also
think that the fact that XP is cloned on to the "F:" drive could also be a cause
for the problem, as the cloning to that drive would have taken XP's bootloader
and everything with it. And, now that I'm thinking about it, could be the issue
here. Unfortunately, I don't really know how you can get past that. Possibly,
opening up the boot.ini file and redirecting it to the F: drive properly is what
is needed. The current boot.ini file, which is read when you try to add a legacy
OS, if I understand the bootloader properly, has XP as residing on what is now
Vista. Since it can't find XP, it just reboots. BTW, I'm posting this at
PROnetworks so that the folks there see and can think about this too. Somewhere,
we'll get this fixed for you.
----------
Mark Dietz
PROnetworks <http://www.pro-networks.org>
Bill wrote:
> I have VBPro - it doesn't work - I have been on their forum with no results
>
> these are the two entries I have in VBPro
>
> Entry #1
>
> Name: Windows Vista Beta 2
> BCD ID: {current}
> Boot Drive: C:
> Windows Drive: C:
> System Bootloader: \Windows\system32\winload.exe
> Windows Directory: \Windows
>
> Entry #2
>
> Name: Windows XP Home
> BCD ID: {f7464cbe-0082-11db-814e-00123f6b8acd}
> Boot Drive: F:
> Windows Drive:
> System Bootloader: \ntldr
> Windows Directory:
>
> If I select the second entry on boot up - I get a blank screen.
> It was suggested the problem might be the lack of drive letter (F) after
> ''Windows Drive" in entry 2.
> It was suggested I not use F, but another letter, I tried H - same results.
>
> I was hoping I could get into the bcdedit file and add an F - to see if it
> works.
>
> I have been trying to get this machine to dual boot for two days - (I think
> I drove Chad Harris nuts yesterday) - and have not been able to do so.
>
> C an F are two separate WD Raptor HDs
>
> My stubbornness is starting to take over here - I am looking for a bullet
> for my 45 - I hate it when I can't find my bullet.
>
> You people are the best - I really appreciate all your help in this matter.
>
> Bill
>
>
>
> "HDRDTD" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> An easier way is to download a copy of VistaBoot Pro. It's a fantastic
> utility for managing Vista's multi boot menu.
> http://www.pro-networks.org/vistabootpro/intro.php
>
>
> "Bill" <(E-Mail Removed)> wrote in message
> news:F74FA886-3941-4B84-8CC8-(E-Mail Removed)...
>> Does anybody know how to open bcdedit.exe to view/change its contents. I
>> try
>> to run it and it appears to "fly by" in a - you-can't-see-it manner
>>
>> Bill
>>
>>
>
>
>
Similar Threads
