PB connectivity options issues

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi all.

Let me begin this post by saying that I was directed here by a MS contact,
and if this discussion (concerning Magneto) should take place somewhere else,
contact me on how.
"On the assumption that a virus is not involved you should post
details of the problem to the MSDN Platform builder forum..."

Now to the issue. I have installed Magneto (Build 14343), but have problems
with image download and transport to the device/emulator in Platform Builder.
In the "Kernel service map" in "Connectivity Options" the "Download",
"Transport" and "Debugger" drop-down boxes are empty. Clicking on their
"Settings"-buttons I get an unhandled exception dialog. Se bottom of post for
details about the dialog.

I have tried on at least 4 different computers with both WinXP and Win2k.
Anti virus is installed on each of them. I have also tried build 14337. I've
used PB since .NET 4.1 and have never had any issues with it. I have used a
registry monitor and can't se any operations concerning PB connectivity
taking place while adding/changing settings. Are they stored in some kind of
service and then saved later on?

The SDK emulators shows in the "Target Device" drop-box, but selecting them
does not impose settings in the Download, Transport and Debugger settings
(and non can be selected).

In short, I have installed (in following order):
..NET Framework
Magneto AK (Build 14343)
Visual Studio Beta 2, 2.0.50215
Active Sync 4.0
Latest Windows Mobile 5.0 Smartphone SDK

In long:
-------------------------------------------------------------------------------
0) Started with a clean Windows 2000 installation. Version 5.00.2195,
service pack 4.

1) Installed .Net Framework from \Build_14337\MagnetoAK\dotnetfx.exe

2) Ran \Build_14337\MagnetoAK\setup.exe

3) Did "Select the first option, “Custom” (Tools and Windows Mobile 5.0
Adaptation Kit) and follow the instructions to continue the installation
process." and installed into default directories.

4) Continued with installing BetaDEVS. Installation failed and aborted of an
unknown reason. "The process has already exited". Reinstalled BetaDEVS with
the repair option.

5) Installed Visual studio 2005 beta 2 with default settings.

6) Installed activesync 4.

7) Installed Windows Mobile 5.0 Smartphone SDK with default settings.
-------------------------------------------------------------------------------


THE DIALOG brought up by pressing the Settings buttons contains the message
"Object reference not set to an instance on an object" with the following
details:

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

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an
object.
at
CoreConUINet.ConfigureKernelServicesControl.BootstrapSettings_Click(Object
sender, EventArgs e)
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.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/winnt/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
CEServices
Assembly Version: 5.1.0.0
Win32 Version: 5.01.14337
CodeBase:
file:///C:/PROGRA~1/COMMON~1/MICROS~1/Corecon/5.01/bin/CEServices.EXE
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/winnt/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/winnt/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/winnt/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
CoreconControls
Assembly Version: 5.1.0.0
Win32 Version: 5.01.14337
CodeBase:
file:///C:/PROGRA~1/COMMON~1/MICROS~1/Corecon/5.01/bin/CoreconControls.DLL
----------------------------------------
Interop.CcSvcHost
Assembly Version: 5.1.0.0
Win32 Version: 5.01.14337
CodeBase:
file:///C:/PROGRA~1/COMMON~1/MICROS~1/Corecon/5.01/bin/Interop.CcSvcHost.DLL
----------------------------------------
Interop.CcDataStore
Assembly Version: 5.1.0.0
Win32 Version: 5.01.14337
CodeBase:
file:///C:/PROGRA~1/COMMON~1/MICROS~1/Corecon/5.01/bin/Interop.CcDataStore.DLL
----------------------------------------

************** JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (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 machine
rather than being handled by this dialog.
===============================================================================


Please advice.
.

Relevant Pages