Technology, Support, and News Forum

[Cbarnhorst Profile]

On starting VBP in either Vista RC1 x64 5600 or XP Pro x64 I get a message stating "Index and count must refer to a location within the string. Parameter name count."

When I OK this message I get the VBP interface but with a blank text area.

View Settings gets the "Index and count must refer to a location within the string. Parameter name count."

Configure, Advanced, and Manage Entries, result in an Unhandled Exception error with the info that "Value cannot be null" and "Parameter name item."

Asus A8N-SLI Deluxe, AMD64 x2 4400+, 4GB ram, XP Pro x64 and Vista x64 RC1.

Two different boot options screens can appear. One lists XP Pro x64 and some versions of Vista previously on the system plus an aborted Setup Files entry. The other lists four generic names for Windows and Recovered Windows.

[Grav!ty Profile]

Version 2.1 works just fine in both XP X64 and 5600 X64. What you are indicating points to there having been a number of previous installations and recovered installations on that system with invalid entries left in the BCD store

We will need to take a good look at accomodating that sort of scenario in our next version. Thanks for pointing this out.

I am presuming that you are not able to delete the invalid entries using VistaBootPRO because of the error you are getting?

In the mean time I suggest you boot into XP X64 (because you won't get any UAC interference from there), copy bcdedit.exe from the Program Files>PROnetworks>VistaBootPRO folder and paste it into the Windows\system32 folder (it will do no harm there at all), open the command prompt and run the following commands:

CD\ and Enter to take the command prompt to the root of the your XP X64 installation drive

bcdedit /enum alland Enter so that all entries in the BCD are shown

Now open another instance of the command prompt so that you have the first one open to see the GUID entries and the second one to run commands, and again type:

CD\ and Enter

bcdedit /delete {GUID string of item to be deleted} and press Enter for each invalid entry.

Once you have removed the invalid entries you should find that VistaBootPRO will be fully functional again.

[kd1966 Profile YIM]

Before you actually delete those entries, could you possibly post a screenie of the bcdedit.exe output from the command prompt in x64 XP? I'd personally like to see it, as I'm having some issues understanding the explanation. Thanks!

[Cbarnhorst Profile]

Well, here is the whol sad thing.

I don't know how to distinguish which entries need to be deleted. Can you help me with that?

------------------------------------------

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>bcdedit /enum all

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}
{cbd971bf-b7b8-4885-951a-fa03044f5d71}
{7fda6e7e-345c-11db-b6f4-e57ef49587fc}
{24a500f2-12ea-11db-a536-b7db70c06ac2}
{a34a0d26-1302-11db-8617-b8f8359ef694}
toolsdisplayorder {memdiag}
timeout 3

Windows Boot Loader
-------------------
identifier {24a500f2-12ea-11db-a536-b7db70c06ac2}
device partition=N:
path \Windows\system32\winload.exe
description Microsoft Windows Vista x86
locale en-US
inherit {bootloadersettings}
osdevice partition=N:
systemroot \Windows
resumeobject {24a500f3-12ea-11db-a536-b7db70c06ac2}
nx OptIn
custom:47000005 301989892
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 {a34a0d26-1302-11db-8617-b8f8359ef694}
device unknown
path \Windows\system32\winload.exe
description Microsoft Windows Vista x64
locale en-US
inherit {bootloadersettings}
osdevice unknown
systemroot \Windows
resumeobject {a34a0d27-1302-11db-8617-b8f8359ef694}
nx OptIn
custom:47000005 301989892
3

Windows Setup
-------------
identifier {cbd971bf-b7b8-4885-951a-fa03044f5d71}
device partition=C:
path \$WINDOWS.~BT\Windows\system32\winload.exe
description Windows Setup
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \$WINDOWS.~BT\Windows
nx OptOut
detecthal Yes
winpe Yes
custom:47000005 301989892
1

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 {a34a0d27-1302-11db-8617-b8f8359ef694}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filepath \hiberfil.sys
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}

C:\Documents and Settings\Administrator>

[kd1966 Profile YIM]

I believe this one is bad:

Windows Setup
-------------
identifier {cbd971bf-b7b8-4885-951a-fa03044f5d71}
device partition=C:
path \$WINDOWS.~BT\Windows\system32\winload.exe

Note the path..................... that is normally used during setups/installs and does not normally exist afte such OS installs - this occurs with XP as well, but this one is from Vista due to the "winload.exe"


You might want to adjust your "Timeout" settings as well......... to more than 3 seconds

I think this one is bad as well:

Windows Boot Loader
-------------------
identifier {a34a0d26-1302-11db-8617-b8f8359ef694}
device unknown
path \Windows\system32\winload.exe
description Microsoft Windows Vista x64

Note the device (Hard disk location) is unknown, and you have another x64 XP on C:\

Your screen is also showing Vista to be present on the D:\ and N:\ drives........... I'm not sure which one is the valid one at this point.

[Cbarnhorst Profile]

N: is the working Vista x64 RC1 5600 installation.

D: is a formerly working Vista x86 pre-RC1 5536 installation which I don't care about.

N: is on an external SATA drive connected to the mobo via passthrough cabling.

I am ready to move Vista x64 RC1 5600 inboard to the D: drive, but I want to clean this all up first.

Is there short advice on how to remove the two entries you flagged using bcdedit from XP64?

Thank you for all your time!

[jbullard]

Personally I would remove "ALL" the entries and then add them back using VBP. It looks like there are too many rogue entries in there and to actually go through and figure out which one is correct would be a hassle. What you can do, is remove the entries, and then for each Vista entry, just add the drive as C:. Then, for the XP entry, you will need to know exactly where this was installed before you added XP. If it was C:, then I would add it as C: and if that does not work, just keep going down the list until it was actually found on boot.

Jason

[Cbarnhorst Profile]

"Personally I would remove "ALL" the entries and then add them back using VBP."

If you read the initial post you would have seen that VBP is not loading the entries. The interface is blank. How do you propose that I do as you suggest in VBP at this point?

[jbullard]

"Personally I would remove "ALL" the entries and then add them back using VBP."

If you read the initial post you would have seen that VBP is not loading the entries. The interface is blank. How do you propose that I do as you suggest in VBP at this point?

Sorry about that. You will have to use the Command Prompt under Accessories by right clicking and selecting Run As Administrator. Then you will just have to go and type in

bcdedit /delete {GUID} /f /cleanup

For those that don't have a GUID and have {current} or {ntldr} just replace GUID with current or ntldr.

Once they are deleted out of the BCD Store, then open VBP and go to Manage OS Entries and add them. If you still need help let us know.

Jason

**edit** the GUID is the BCD ID that you see when you type in bcdedit /enum ALL. However, only delete the entries that have Windows Boot Loader or Windows Legacy OS Loader above them.

[Cbarnhorst Profile]

I am in XP Pro x64, not Vista.

Does "Add back in" in VBP mean that VBP will detect the XP Pro x64 and Vista RC1 x64 partitions and generate the data? Or do I need to cut and paste from the above entries?