Hey folks, I like the forum. But the reason I'm here is an issue using vista bootpro 3.3. I'm trying to dualboot vista and xp on a new notebook. One hd sliced into 2 primaries - one xp - one vista - and one to share between the two. All on single drive - pata I believe.

I have both os's loaded and bootable. But haven't been able to get the boot menu to actually to work. Example - last os = vista then selecting vista = successful boot. However to get xp partition to work I have to boot to vista then select vistabootpro > system bootloader > unistall vista bootloader (legacy bootloader) > all drives > install bootloader.

Have tried some of the intuitive selections. Like trying to get proper bootloader onto proper drive. No real luck though.

Came across "howto" that indicated I'd missed a step with the managing os's in vistabootpro. However i get an error when trying either diagnosics or manage os's in vistabootpro. I've seen some references to this error in other posts that indicated that newer releases (last post i saw was 3.1 that issue was brought up maybe) were fixing issue. But I haven't seen any resolution since then in the forums.

Ok so the here is the error :

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentNullException: Value cannot be null.
Parameter name: item
at System.Windows.Forms.ListBox.ObjectCollection.AddInternal(Object item)
at System.Windows.Forms.ListBox.ObjectCollection.Add(Object item)
at 4QUXZ7BxjUuiOXgX4wk.OgiG9nBwUiv3boHqO2e.rDCCFkHK4b()
at 4QUXZ7BxjUuiOXgX4wk.OgiG9nBwUiv3boHqO2e.Yo4CGctWon(String )
at 4QUXZ7BxjUuiOXgX4wk.OgiG9nBwUiv3boHqO2e.w5rCrgfsZ8(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
VistaBootPRO
Assembly Version: 3.3.0.0
Win32 Version: 3.3.0.0
CodeBase: file:///C:/Program%20Files/PROnetworks/VistaBootPRO%203.3/VistaBootPRO.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
idllfunc
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/PROnetworks/VistaBootPRO%203.3/idllfunc.DLL
----------------------------------------
BcdProvider
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/PROnetworks/VistaBootPRO%203.3/BcdProvider.DLL
----------------------------------------
enum
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/PROnetworks/VistaBootPRO%203.3/enum.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system>
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

END ERROR:

So anyway - has anybody found a resolution yet. My platform - OEM notebook, one HD. No acronis used - just windows management for setting partitions. Vistabootpro 3.3.

Please post a screenshot of your Disk Management (from either OS) and give a description of what OS is where according to Disk Management.

Also, where are your boot system files for both operating systems? (ntldr, boot.ini, NTDETECT.COM for XP and the folder Boot and bootmgr for Vista).

Thanks for the reply Gav!ty. This dualboot project has been a pain. OEM vista that refused to squish less than 80 gig. I have dumped and reloaded enough times to make it a bonified career. Getting tired of os loading.

Looks like I lost track of where I was at. Xp wound up sitting on a logical drive this time. Could that be the issue?

Ok - for the screen shot - not sure how to. Paste isn't working here.


As for boot files - vista partition has ntdlr,boot.ini,ntdetect.com,boot folder and boot.ini. XP partition has ntdlr, bootmgr and boot.ini.

I'll need instructions on how to screen shot or let me know what info you need from management screen.

Again, thanks in advance.

Grav!ty,

I started browsing this site -hmm 2-3 weeks ago maybe? Somewhere I thought I saw a jump-through-the-hoop-procedure thing to get a screen shot in a post on this forum. But I haven't been able to find the link again.

However, just curiosity, did my mistake about poking xp to that logical drive instead of primary partition cause these issues?

I've multibooted before. Vista as the OEM os on this notebook has the rules set about starting points. Vista OEM notebook > slicing , squishing, redefining - etc > to (with luck) you get a selection of whatever os enviroments you want that work with.

As OEM - new and being vista - oem xp drivers were a challenge. Many do-overs just to be sure..... First vista sacrificial pc. Will another full reload of xp be needed to correct logical os location instead of primary partition? Never tried using disk management to try redefining from logical to primary. Is possible even?

Anyway - Happy Holidays!

Here is a link for you:
How to Post An Image At PROnetworks

Happy Holidays too

Also if you could please post the contents of VistaBootPRO -> View Settings -> ALL

You may also want to try and do the following just to see if it will help.

http://www.pronetworks.org/forum/about89711.html

For the disk management screenshot:



For the vistapro settings :

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {8c384824-6ff0-11db-8455-0016d303c84f}
displayorder {572bcd55-ffa7-11d9-aae2-0007e994107d}
{default}
{e9042df9-37b2-11db-80d7-0011d8c8bb47}
{ntldr}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {572bcd55-ffa7-11d9-aae2-0007e994107d}

Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
recoverysequence {572bcd55-ffa7-11d9-aae2-0007e994107d}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {8c384824-6ff0-11db-8455-0016d303c84f}
nx OptIn

Windows Boot Loader
-------------------
identifier {e9042df9-37b2-11db-80d7-0011d8c8bb47}

Resume from Hibernate
---------------------
identifier {8c384824-6ff0-11db-8455-0016d303c84f}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
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 Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device unknown
path \ntldr
description 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}

Device options
--------------
identifier {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
description Ramdisk Device Options
ramdisksdidevice unknown
ramdisksdipath \boot\boot.sdi

Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \boot\boot.sdi


End settings paste.

jbuulard:
I followed the steps in this link - http://www.pronetworks.org/forum/about89711.html

Diagnosits does now run. However it completes and immediately sends me to manage os's the fails out with this message :

Start error messaage -

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentNullException: Value cannot be null.
Parameter name: item
at System.Windows.Forms.ListBox.ObjectCollection.AddInternal(Object item)
at System.Windows.Forms.ListBox.ObjectCollection.Add(Object item)
at 4QUXZ7BxjUuiOXgX4wk.OgiG9nBwUiv3boHqO2e.rDCCFkHK4b()
at 4QUXZ7BxjUuiOXgX4wk.OgiG9nBwUiv3boHqO2e.Yo4CGctWon(String )
at 4QUXZ7BxjUuiOXgX4wk.OgiG9nBwUiv3boHqO2e.w5rCrgfsZ8(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///D:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
VistaBootPRO
Assembly Version: 3.3.0.0
Win32 Version: 3.3.0.0
CodeBase: file:///D:/Program%20Files/PROnetworks/VistaBootPRO%203.3/VistaBootPRO.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///D:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///D:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///D:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
idllfunc
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Program%20Files/PROnetworks/VistaBootPRO%203.3/idllfunc.DLL
----------------------------------------
BcdProvider
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Program%20Files/PROnetworks/VistaBootPRO%203.3/BcdProvider.DLL
----------------------------------------
enum
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Program%20Files/PROnetworks/VistaBootPRO%203.3/enum.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///D:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system>
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


End error message.

It looks the same to me as what I started with. The dos bcdedit command completed ok and the diagnositic tab in vistapro thought it had done good too. But it still hangs at managing os's.

Hopefully that'll give yall a clue as to what needs to be done get it right. If anybody needs more info please just say the word. And thanks again folks.

Okay. Here are a couple of things that you need to do.

First open command prompt in Administrator Mode (Start -> All Programs -> Accessories -> Command Prompt -> Right click 'Run As Administrator'

Second, get rid of rogue entries:

bcdedit /delete {e9042df9-37b2-11db-80d7-0011d8c8bb47} /f /cleanup

bcdedit /delete {572bcd55-ffa7-11d9-aae2-0007e994107d} /f /cleanup

That will cleanup those entries that go no where since nothing is configured for them and allow Manage OS Entries to work properly.

I will keep looking into the XP booting problem.

Score another for the home team! Yes the os management tab runs now. Don't know what it'll do but I'll keep you posted.

Thanks a bunch everyone again. Oh and to jbullard - thank you again.

Xp entry is red. That what you meant about working on xp booting problem then eh? Saw the red thing somewhere - forum or guide maybe. Not sure but that's not good is it?