[Idontbyte]

I hope this is the right place to enter the following:

I've used PCs for too many years, but am new to dual booting. I'm running Windows 7 32 bit and obviously not using all available memory. I would like to install Windows 7 64 bit but can't do without a lot of my 32 bit software until I've got 64 bit up and fully running.

I've thought of several ways of doing this
1. imaging C:, installing 64 bit, imaging 64 bit, restoring 32 bit and repeating as I develope 64 bit. I've tried this and got into trouble after a few rounds of the process (not quite sure why).
2. So, I thought of buying a new disk for Win 7 64 bit, and swapping with C: for Win 7 32 bit as required.
3. Then I was told about DualBootpro and thought maybe I could dual boot Win 7 32 and 64 bit (ignoring licensing questions for the time being), so bought a license for DualBootPro.

I've installed DualBootpro and am still looking at the screens and scratching my head!! The thing is I seem to have a few "funnies"

a. The boot information screen reports three (3) OS(s) ???
b. The operating systems screen shows only Windows 7 (but in red).
c. The advanced settings screen comes up with an "Unhandled exception error" and reports the following details (the asterisks *** are mine):
***********************************************************************************************************
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.ComboBox.ObjectCollection.AddInternal(Object item)
at System.Windows.Forms.ComboBox.ObjectCollection.Add(Object item)
at .(String )
at .  (Object , EventArgs )
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.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.5444 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
DualBootPRO
Assembly Version: 1.1.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///C:/Program%20Files/PROnetworks/DualBootPRO/DualBootPRO.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
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.5420 (Win7SP1.050727-5400)
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.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
BcdProvider
Assembly Version: 1.1.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///C:/Program%20Files/PROnetworks/DualBootPRO/BcdProvider.DLL
----------------------------------------
idllfunc
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/PROnetworks/DualBootPRO/idllfunc.DLL
----------------------------------------
AutomaticUpdater
Assembly Version: 2.5.24.0
Win32 Version: 2.5.24.0
CodeBase: file:///C:/Program%20Files/PROnetworks/DualBootPRO/AutomaticUpdater.DLL
----------------------------------------
MyToolBox
Assembly Version: 1.0.2998.32584
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/PROnetworks/DualBootPRO/MyToolBox.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
enum
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/PROnetworks/DualBootPRO/enum.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/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.windows.forms jitDebugging="true" />
</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.
***********************************************************************************************************************************

Any help and suggestions would be much appreciated.

Thanks.

[Grav!ty]

So which operating systems do you have installed now? Both X86 and X64?

In which operating system did you get this unhandled exception?

Please go to the Boot Information page of DualBootPRO, select All at the top of the page and then right click on the page>Select All and copy and paste the information here.

Please post a screenshot of your disk management so that we can see what is going on with your disk configuration.

I run both X86 and X64 very happily side by side on the same disk and don't have any of the issues you seem to be having. I'm sure we can get you sorted out.

[Idontbyte]

I have only one OS installed, namely Windows 7 32-bit (X86), so my problems are with running DualBootPro in this environment.

I do have "Acronis True Image Home 2011" installed which also has the ability to create a boot menu (for itself and Windows), but I don't use this facility, relying on booting from a rescue CD (created by Acronis) if I need to do an OS restore.

Boot Information screen contents follows:
***********************************************************************************************************************************************

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {a6d2e43f-d62c-11de-afc5-c21052454324}
displayorder {a6d2e43d-d62c-11de-afc5-c21052454324}
{current}
{a6d2e441-d62c-11de-afc5-c21052454324}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {a6d2e43d-d62c-11de-afc5-c21052454324}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {a6d2e441-d62c-11de-afc5-c21052454324}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {a6d2e43f-d62c-11de-afc5-c21052454324}
nx OptIn
pae ForceEnable

Windows Boot Loader
-------------------
identifier {a6d2e441-d62c-11de-afc5-c21052454324}

Windows Boot Loader
-------------------
identifier {a6d2e443-d62c-11de-afc5-c21052454324}
device ramdisk=[C:]\Recovery\46c1f89e-c02b-11de-9b30-a36c21a6aa46\Winre.wim,{a6d2e444-d62c-11de-afc5-c21052454324}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\46c1f89e-c02b-11de-9b30-a36c21a6aa46\Winre.wim,{a6d2e444-d62c-11de-afc5-c21052454324}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {a6d2e43f-d62c-11de-afc5-c21052454324}
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

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}
{7ff607e0-4395-11db-b0de-0800200c9a66}

Inherited Settings (20200003)
-----------------------------
identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
custom:250000f3 0
custom:250000f4 1
custom:250000f5 115200

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

Device options
--------------
identifier {a6d2e43e-d62c-11de-afc5-c21052454324}
ramdisksdidevice unknown
ramdisksdipath \Recovery\46c1f89e-c02b-11de-9b30-a36c21a6aa46\boot.sdi

Device options
--------------
identifier {a6d2e442-d62c-11de-afc5-c21052454324}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\a6d2e441-d62c-11de-afc5-c21052454324\boot.sdi

Device options
--------------
identifier {a6d2e444-d62c-11de-afc5-c21052454324}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\46c1f89e-c02b-11de-9b30-a36c21a6aa46\boot.sdi

*****************************************************************************************************************************************************

I've also attached a jpg file showing the disk management configuration.

Disk 0 = SATA Drive - O/S (Win 7 X86) + User Data partition (moved from C:) + spare partition (for Win 7 X64?)
Disk 1 = SATA Drive - Main data disk + Acronis Secure Zone (Back up Images of O/S & User Data)
Disk 2 = PATA Drive - Backup of Main Data + User Data Partition (to be sure, to be sure!!)
Disk 3 = PATA Drive - Spare Data Partition + Downloaded Software
***********************************************************************************************************************************************************

Many thanks for all your help. I hope the above is what you require.

Screen Snip of Disk Management

Disk Management Snap.jpg (194.29 KiB) Viewed 522 times

[Grav!ty]

I can see no reason you getting an unhandled exception error. Perhaps it's caused by acronis? Have you used acronis to create your partition system? Windows 7 generally does not play nice with third party partition managers. I think you will find that if you ignore the exception error or just OK out of it, DualBootPRO will function fully.

It would probably be better to install X64 immediately to the right of Windows 7. If you fragment both User Space (G: ) and Spare on C (I: ) you can move the data which is on (G: ) to (I: ) and then use Windows disk management to extend G: to the size you want it and I suggest reformatting it from Windows 7 disk management, in case you used acronis to format it previously. Even if you didn't use acronis, a reformat won't hurt...a quick format is fine. You do not need to set it "Active".

After that it is simply a matter of booting from your Windows 7 X64 DVD selecting "Custom", selecting the drive you want to install on and installing the operating system. Windows 7 X64 will auto create a dual boot menu for you. It's a good idea to rename the Windows 7 item, using the operating systems page of DualBootPRO to something like Windows 7 X86, before you install X64, because Windows 7 will also name itself simply Windows 7. This renaming is not really necessary as you be able to tell which is which by the fact that the most recent OS will be listed at the top of the boot menu and will be the default OS...the one highlighted at the boot menu. You can rename the boot menu entry after installation.

By the way, did you have a failed installation of Windows 7 X86 which made it necessary to reinstall it?

[Idontbyte]

Many thanks for the advice. I'll keep you posted on progress/problems.

My current PC is a "bare bones" system, moved from an ancient DELL Dimension which had grown "like Topsy"! I moved all the disks, etc. and then installed a purchased version of Windows 7 X86. I then used Acronis Plus Pack to restore all other installed software from an image of XP onto Win 7 - amazingly this worked - after a couple of reboots to sort out the odd driver.

Thanks again.

[jbullard]

You are getting the unhandled exception because of these two entires:

[code[
Windows Boot Loader
-------------------
identifier {a6d2e43d-d62c-11de-afc5-c21052454324}

Windows Boot Loader
-------------------
identifier {a6d2e441-d62c-11de-afc5-c21052454324}
[/code]

You will need to manually delete them by doing the following:

1. Open Start Menu -> Accessories -> Command Prompt (Right Click and select Run As Administrator)
2. Type in bcdedit {a6d2e43d-d62c-11de-afc5-c21052454324} /cleanup
3. Type in bcdedit {a6d2e441-d62c-11de-afc5-c21052454324} /cleanup

This will remove these two rogue entries that contain no information but DBP is still trying to process them because they are configured as a boot loader entry.

[Idontbyte]

Many thanks for that.

I actually had to insert /delete between bcdedit and the key value for it to work.

I'm now almost ready to try installing Windows 7 X64.

Regards.

[jbullard]

Glad to hear its working now. Yea, sorry about that /delete thing. As you can see from that post I was having some typing difficulties. I'll just blame the keyboard.

[Idontbyte]

Ok. I've now installed Windows 7 X64 successfully and can dual boot with ease. DualBootPro works very well.

But I now appear to have one immense problem! I try to take ownership of the data partitions in one or the other OS and now cannot take complete ownership of all the folders and files in either OS, such that the programs I try to run all fail for security reasons.

I know this isn't your problem, but have you come across it before and do you know of the solution. Help!!!

Regards.

[Grav!ty]

I'm not quite sure what you are wanting to achieve. Are you installing your programs to a drive other than your OS drive?

Taking ownership of the entire hard drive, and including child objects when taking ownership, in safe mode logged in as Administrator, may work. You could also try turning off user account control.

X 64 I find to have many issues with unsigned drivers being blocked when some programs require drivers to run.