[Ej@Y]

Hello,

Don't know if this is a bug or not... But when I used VistaBootPro 2.1 on Windows Vista beta 2 Build 5384 my XP boot failed. I was running Windows 2003 (C:\) and Windows XP (E:\) with XP's bootmanager located on a third partition (F:\). After installing Windows Vista (C:\), overwriting the 2003 partition, I only could run the Vista version. After downloading VistaBootPro 2.0 and later VistaBootPro 2.1 I manually added a new boot entry, but I always got the message 'ntldr missing' when I choose the new XP option in the Vista bootmanager.

I did this:
- copy ntldr and ntdetect.com to my E: partition (Windows XP)
- run fixboot on e:
- boot.ini edited on e:

but all with no succes. Then I ran bcdedit /enum and that gave me this:

C:\>bcdedit /enum

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {50c73d50-e6b3-11da-bc73-d30cdb1ce216}
displayorder {current}
{99e74315-1582-11db-ab4a-000c6e38dcb2}
{99e74316-1582-11db-ab4a-000c6e38dcb2}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {50c73d50-e6b3-11da-bc73-d30cdb1ce216}
nx OptIn

Windows Legacy OS Loader
------------------------
identifier {99e74315-1582-11db-ab4a-000c6e38dcb2}
device unknown
path \ntldr
description Windows XP Music

IOW : the line device unknown (or somewhat different) had my attention.
after i ran

bcdedit /set {99e74315-1582-11db-ab4a-000c6e38dcb2} device partition=e:

everything was fine... Why doesn't VistaBootPro 2.1 added that bcdedit-entry altough i thoroughly setted the E-partition in VistaBootPro?

Greetings,
Ej@Y

split from the Bug Reporting Thread

[gries818]

Umm downloading 2.0 is the problem. There was a know issue with 2.0 that caused this.... You can check out the fix here (downloading 2.1 alone cannot fix this): http://www.pronetworks.org/forum/viewtopic.php?t=79762

Note: this was before 2.1 was released so don't download the 2.0 Refresh version.

Btw, Welcome to PROnetworks! Head on over to the <a href="http://www.pronetworks.org/forum/viewforum.php?f=32">Introduction Area</a> and introduce yourself.

Thanks for working on this

[jbullard]

Ej@Y,

First of all welcome to PROnetworks and don't foget to head over to the Introduction Area and tell us about yourself.

To answer your question and give you a little of background information Vista has a known issue by changing the drive letters around. When you boot into XP, 2003 you will probably notice that Vista was actually installed, lets say, drive E. But when you boot into Vista, it now shows that it is on drive C. I can't tell right off hand why this is, but it is very confusing for some people. In order to fix your problem, go into VBPro 2.1, go to Manage Entries and add a Legacy OS to drive C. This will most likely fix your problems.

If you remember what drive you actually installed XP on, then use that drive. VBPro only will check to make sure that the drive you are using is physically available. Please let us know if this does not fix the problem.

HTH,
Jason

[kd1966]

Vista drive letters will vary depending on HOW Vista was installed; if Vista was installed by booting the DVD, then Vista will always take C: when you are booted to it, BUT if you install Vista from the DVD from within Windows, then Vista will take whatever the next letter in line is.