Hi,

I installed Windows XP on C and Vista on D. Because Windows XP got corrupted, I reinstalled it. Ater this, the computer booted automatically to Windows XP. I restored Vista with the install DVD. After this, the computer booted automatically to Windows Vista.
Then I got the excellent idea to use VistoBootPro 3.1 :-)
When going to 'Manage OS entries' and clicking 'diagnose', I run into a crash with a message like: index and number have to refer to a location within the characteristic set. Parameter name: count.

---> Who can help me?

The stack trace (in Dutch):
System.ArgumentOutOfRangeException: Index en aantal moeten naar een locatie binnen de tekenreeks verwijzen.
Parameternaam: count
bij System.String.Remove(Int32 startIndex, Int32 count)
bij PROnetworks_100001.BCD.FileParse3..ctor()
bij VistaBootPRO.VistaBootPRO.AYQxiUkWP7uBmB8OMZcSmv4jUh(Object , EventArgs )
bij System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bij System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
bij System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bij System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
bij System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
bij System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
bij System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
bij System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
bij System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bij System.Windows.Forms.Control.WndProc(Message& m)
bij System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bij System.Windows.Forms.ToolStrip.WndProc(Message& m)
bij System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

i'm having the same problem..

Hello to both of you and Welcome to PROnetworks! Please be patient as our team members get on top of this. Enjoy the site!

rene@pronetworks and dannyplomp,

This error has been identified and has been fixed in the upcoming VistaBootPRO release. For now, we can help you get your BCD Registry correct if you can provide us with some screenshots and some other stuff.

1. Copy and paste the contents of VistaBootPRO -> View Settings -> All
2. A screenshot of disk management (VistaBootPRO -> Tools -> Disk Management)

This will help us provide you an alternative method to the Run Diagnostics option which is currently unavailable to you.

Thanks,
Jason

Tnx 4 the quick response.. sure i can


Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale nl-NL
inherit {globalsettings}
default {default}
resumeobject {d77eeb85-afc0-11db-bb6a-c46c557f71ce}
displayorder {default}
{ntldr}
timeout 30

Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \windows\system32\winload.exe
description Microsoft Windows Vista
osdevice partition=C:
systemroot \Windows

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=D:
path \ntldr
description Microsoft Windows XP

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}



TNX 4 THE HELP

rene@pronetworks and dannyplomp,

Please see the following that I just whipped up for everyone. It will fix the problems that you are experiencing. I have tested it numerous times on different machines.

http://www.pronetworks.org/forum/viewtopic.php?t=89711&highlight=

If you still have any questions please let us know.

Thanks,
Jason