PROnetworks »

Post new topic    Reply to topic
Login to print this topic
Author Message
jbullard
Jason Bullard
PostPosted: Sun Sep 10, 2006 4:00 am Reply with quote

Vice President
Software
 
 


Joined: 06 Jun 2004
Posts: 3233
Location: Utah
Let's go ahead and take kd1966's idea and run through each of these entries first. The first thing you need to do is copy "bcdedit.exe" and "bootsect.exe" from the VBP Program directory to your current System32 directory. Once that is completed, open up command prompt and do the following. I will also add comments so you know what you are doing.

1. Delete this entry (Microsoft Windows Vista x64) and cleanup
bcdedit /delete {a34a0d26-1302-11db-8617-b8f8359ef694} /f /cleanup

2. Delete this entry (Windows Setup) and cleanup
bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71} /f /cleanup

3. Delete this entry (Windows Resume Application) and cleanup
bcdedit /delete {a34a0d27-1302-11db-8617-b8f8359ef694} /f /cleanup

4. Delete this entry (Microsoft Windows Vista x86) and cleanup
bcdedit /delete {24a500f2-12ea-11db-a536-b7db70c06ac2} /f /cleanup

Now you should be left with something like this

Quote:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {7fda6e7f-345c-11db-b6f4-e57ef49587fc}
displayorder {ntldr}
{default}
{7fda6e7e-345c-11db-b6f4-e57ef49587fc}
toolsdisplayorder {memdiag}
timeout 3

Windows Boot Loader
-------------------
identifier {7fda6e7e-345c-11db-b6f4-e57ef49587fc}
device partition=D:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice partition=D:
systemroot \Windows
resumeobject {7fda6e7f-345c-11db-b6f4-e57ef49587fc}
nx OptIn
custom:47000005 301989892
3

Windows Boot Loader
-------------------
identifier {default}
device partition=N:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice partition=N:
systemroot \Windows
resumeobject {ffba5e75-3ad8-11db-9a8d-83936994fbef}
nx OptIn
detecthal Yes
custom:47000005 301989892
3

Resume from Hibernate
---------------------
identifier {24a500f3-12ea-11db-a536-b7db70c06ac2}
device partition=N:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=N:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {7fda6e7f-345c-11db-b6f4-e57ef49587fc}
device partition=D:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=D:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {ffba5e75-3ad8-11db-9a8d-83936994fbef}
device partition=N:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=C:
path \ntldr
description Windows XP Pro x64

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}


Now, you should be able to go into VBP and work. It took me minute to figure out your exact BCD Store problem as it had some very strange info in it. However, you should not have any problems booting to any device now. If you do, then please let us know.

HTH,
Jason
 
Back to top
Cbarnhorst
PostPosted: Sun Sep 10, 2006 10:55 am Reply with quote

PRO Level 4
 
 


Joined: 09 Jun 2004
Posts: 129
Location: Aurora CO USA
Very Good!

I went through the steps provided. The third command resulted in a file not found error (I assume that the boot configuration data store changed due to use), but no matter since it did not affect the outcome.

VBP now works as advertised. I renamed the V64 entry, set the default boot to xp64, and reset the timeout value to 15 secs.

Upon reboot I had the predicted three boot options and the reboot went normally.

Thank you, thank you, thank you!
 
Back to top
kd1966
Kevin Durbin
PostPosted: Sun Sep 10, 2006 11:07 am Reply with quote

Respected Member
of PROnetworks
 
 


Joined: 08 Aug 2005
Posts: 9172
Location: USA - GSO - NC
That's great to hear! Enjoy Vista!
 
Back to top
Back to top
Index >> PROnet Developed Software >> VistaBoot Pro 2.1 does not display data in the interface

Goto page Previous  1, 2

Page 2 of 2

Post new topic   Reply to topic


Tired of the Ads? Registered users have 80% less adverts.