Hallo and kind regards to all

I am not a native English speaker but I hope you can still understand what I am writing.

I have got a Toshiba Notebook with preinstalled Vista Ultimate with Recovery CD. I then installed Windows XP SP2 as second OS and - as expected - could then only boot to Win XP. I made the necessary steps (with bcdedit and VistaBootPro 3.1.0) to make a dual boot configuration. All went well and is working as expected, no errors what so ever.

I installed then VistaBootPro 3.2.0, run it and got the already here reported message:
"First Backup"
"VistaBootPro has detected that you have not performed a backup of your BCD registry..."
I click on Accept and I am taken to the "BCD/Registry Backup/Restore Center"
Click on "Browse", select dir for backup and enter a filename.
New pop-up
"VistaBootPro error"
"VistaBootPro detected an error while attempting to run the following command:
/export....."
"The operation was completed successfully"
I always got this when starting VBP3.2

I hoped than VBP 3.3.0 would resolve the problem but I have with this version the same troubles. I wonder if I am the only one with this error because since the advent of VBP 3.3.0 nobody here seems to be affected any more.
Please tell me if you still are working on the problem or if I have to live with the Beta-Version 3.1.0.

Thanks for reading this
foreigner

foreigner,

Welcome to PROnetworks and hope you are finding everything that you need. When you get a chance stop by our Introduction Area and tell us a little about yourself.

As for your situation we are aware of this problem and are actively seeking a solution. The only time we have encountered this error is in your same scenario of installing XP after Vista. In order to correct your problem without VBP you need to boot to the Vista DVD and instead of installing look down on the left and you will see System Repair. Click on this and then select Repair Startup.

This will reinstall the Vista boot manager and other startup files. Although, VBP has a Vista Bootloader install option, the reapir cannot be done within Windows due to security.

However, we will keep everyone informed if we can figure out a way to correct this problem without using the method above.

HTH,
Jason

Hi Jason,

Thanks for the reply but I am a bit confused about your advice; perhaps I wasn’t clear enough.

I have really no problems with my two OS or booting to either. I have the dual boot menu with VBP 3.1.0 created and it still works flawless.

When the v3.2.0 was available I deinstalled v3.1.0 and installed the newer Version (and later on v3.3.0).

When I now try to make a BCD backup or want to change the displayed menu text the well-known error messages pop up:

"VistaBootPro detected an error while attempting to run the following command:
/export..... (or /edit.... respectively)"
"The operation was completed successfully"

Of course I have no idea if the backup is actually without errors and can be really used to restore the BCD if required.

I think it is because of this error that VBP does not know that a backup was already made and on each start shows the same message:

"VistaBootPro has detected that you have not performed a backup of your BCD registry..."

Those are my only problems. I could live with the error messages if I could be certain, that the backup is indeed usable.

If so I can patiently wait till you have the problem finally resolved.


Again thanks and regards
foreigner

Foreigner:
You are not alone.
I reported ProNetworks those and another bugs after v3.2 release.
ProNetwroks reported to have worked on them and that everything would be fine in v3.3.
I see that v3.3 has still the same problems.
It even tells me, during VBP 3.3 startup, that Vista is not installed!!!
I wonder what OS I am running then. :-)
I have finally uninstalled VBP.
Carlos


edited by jbullard

solracna,

The above is not a bug with VistaBootPRO. In fact, this is an error with your system and can be corrected; however, we are trying to develop a way for VistaBootPRO to correct this error upon startup of the application.

If you would like, please post a copy of VistaBootPRO -> View Settings -> All and a screenshot of your disk management and I can have these errors taken out in a matter of minutes. It is a very simple fix but requires an extensive knowledge of the BCD Registry.

But just to give you a little background of what VistaBootPRO actually does on startup is this:

1. Checks for required Vista file and if not found on any drive reports that Vista may not be installed (We will reword this because you are not the first to misunderstand what we are trying to convey here). This is actually an error and should not be overlooked.

2. Checks to make sure you have Admin rights and that your BCD Registry is not corrupt or missing. This is one of the errors above that people have been experiencing. Again, this can be fixed.

3. Checks your BCD Registry for missing entries (automatically adds them if found)

4. Rescans BCD Registry twice to ensure no entries or settings were missed.

As you can see it does a lot of work at startup and helps to protect your system.

Also, I am not just saying this but because I have successfully duplicated this error and no matter which method I try to use a backup it will fail on restore. This includes the bcdedit.exe command line interface as well which will not create the file just like VistaBootPRO because there were errors noted with the BCD Registry.

I hope that this gives you a little better understanding of how we go about disseminating between VistaBootPRO errors, System errors, and other errors. We do a lot of work just to try and keep your system as safe as possible and working.

HTH,
Jason

Jason:
Thanks for the extensive explanations.
As a user, my expectation is to be able to use the program and not be baffled by sequental error messages that diminish my trust on VBP.
I hope every "interaction" problem (formerly known as "bug") between VBP and Vista can be solved in VBP 3.4.
VBP has so far caused no harm in my system in spite of the error messages (whatever the root cause may be) and I have nothing to blame.
I currently have uninstalled it and eagerly wait for a problem free new release.
Have a nice day.
Carlos

Carlos,

Thanks for the information and once again I do apologize that you are receiving these errors. I do hope that as you say 3.4 will be able to fix the problems that a couple of users are experiencing but until then we just have to manually fix their systems through command lines and the Vista DVD.

Please keep checking back often as we are always working to better serve the members/users of VistaBootPRO.

Thanks,
Jason

Not really familiar with forums I would like to report the same problem (message) with my single OS system. Can you help to solve this problem? Kind regards, Franklin
The settings are:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale nl-NL
inherit {globalsettings}
default {current}
resumeobject {fdf05f9f-20ed-11dc-afaa-e9d0e176bf21}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 20

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale nl-NL
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {fdf05f9f-20ed-11dc-afaa-e9d0e176bf21}
nx OptIn

Resume from Hibernate
---------------------
identifier {fdf05f9f-20ed-11dc-afaa-e9d0e176bf21}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale nl-NL
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

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

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}

Another problem that might be interesting is that I am not able to run bcdedit.exe (like vistabootpro?). The Program just shows up and disappears immediately. What wrong with my handling this?
Franklin

What you need to do is Start -> Programs -> Right click on Command Prompt and Run As Administrator. Then you can access the bcdedit command line utility. When you open it would mind testing something out for me. Try to run

bcdedit /export "c:\test.bcd"

Let me know what it returns if you wouldn't mind.