WinXP Manager C4.8.5.1 Error Message

[Daniel]

I am getting an error message everytime I will try to view the Hardware Info section of WinXP Manger. Here's some info:

'An unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will be shut down immediately.'

And these are the details of 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.NullReferenceException: Object reference not set to an instance of an object.
at WinXP_Manager.myClsHardwareInfo.getCPU(TreeView TreeViewName)
at WinXP_Manager.frmHardwareInfo.initHardware()
at WinXP_Manager.frmHardwareInfo..ctor()
at WinXP_Manager.frmMain.ListBar1_ItemClicked(Object sender, ItemClickedEventArgs e)
at vbAccelerator.Components.ListBarControl.ListBar.On ItemClicked(ItemClickedEventArgs e)
at vbAccelerator.Components.ListBarControl.ListBar.Mo useSelectItem(ListBarItem item, MouseEventArgs e)
at vbAccelerator.Components.ListBarControl.ListBar.On MouseUp(MouseEventArgs e)
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(Mes sage& m)
at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& 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.2032
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
WinXP Manager
Assembly Version: 4.8.5.1
Win32 Version: 4.8.5.1
CodeBase: file:///C:/My%20Software/WinXP%20Manager/WinXP%20Manager.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 7.0.5000.0
Win32 Version: 7.10.6001.4
CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
----------------------------------------
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/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.2032
CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
----------------------------------------
acclListBar
Assembly Version: 1.0.1326.27884
Win32 Version: 1.0.1326.27884
CodeBase: file:///C:/My%20Software/WinXP%20Manager/acclListBar.DLL
----------------------------------------
System.Management
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.2032
CodeBase: file:///c:/windows/assembly/gac/system.management/1.0.5000.0__b03f5f7f11d50a3a/system.management.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.

[Alan]

Have you tried using the JIT debugger? If so what did it say.

[Daniel]

What shall I do to use this JIT Debuger?? And even don't know what it is Alan And then... can you tell me step by step please? so I can try it

[Alan]

Try this link Daniel, it should explain.

[Daniel]

When te error box appear, I click on continue (if I understood well it means to debug the program), but nothing will happen.

[Alan]

This from your post, follow what it says:

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.

[Daniel]

Can you help me with this Alan? I have found this Config file in WinXP Manger dir:

[AddedMRDrive]
Defrag=
Scan Disk=
Backup=
[AddedMRFolder]
ShutDown=
Auto-ShutDown=
Command Prompt=
Logoff=
Restart=
Lock Computer Now=
[OtherSet]
Search invalid Shortcut=True
Search 0-length file=False
Search temporary directory=True
Search invalid folder=False
Search empty folder=False
[Reduce]
Delete System Backup files=False
Delete Backup Driven files=True
Delete Backup DLL files=False
Delete System Help files=False
Force to show all Add/Remove Windows Components=False
[Scanlimit]
AllowScanSysFile=False
AllowScanReadOnlyFile=False
[FileType]
*.tmp:Temporary file=True
*.temp:Temporary file=True
*.??$:Temporary file=True
*.??~:Temporary file=True
*.?~?:Temporary file=True
*.___:Temporary file=True
*.---:Temporary file=True
*.??~:Temporary file=True
*.$$$:Temporary file=True
*.@@@:Temporary file=True
*.^:Temporary file=True
*._dd:Temporary file=True
*.~*:Temporary file=True
~*.*:Temporary file=True
*._mp:Temporary file=True
*.syd:Temporary file=True
*.bak:Backup file=False
*.ftg:Temporary file of help=True
*.fts:Temporary file of help=True
*.gid:Temporary file of help=True
mscreate.dir:Setting temp file=True
twain???.mtx:TWAIN Temporary file=True
*.chk:Recover file for lost cluster=True
chklist.*:Recover file for lost cluster=True
Thumbs.db:Cache thumbnails file=False
*.#Res:Transfered to PC Temp file of Mac Photoshop=True
*.old:Old backup file=True
*.wbk:Backup file of word=True
*.xlk:Backup file of Excel=True
*.cdr_:Backup file of Corel DRAW=True
system.1st:Windows diagnostic Registry file=False
suhdlog.dat:Windows diagnostic file=True
scandisk.log:Scan disk log file=True
file_id.dizescription of Shareware=True
*.err:Error file=True
*.dmp:Memory dump=False

[Alan]

Sorry Daniel, for some reason I missed your post.
Click on this link. it will help you with Just In Time debugging.

[Daniel]

OH don't worry Alan you are helping me alot with these troubleshootings here hehe. Thanks. I will post the results soon.

[Daniel]

Visual Studio
Enabling Just-In-Time Debugging

To enable Just-In-Time debugging

1. From the Tools menu, select Options.
2. In the Options dialog box, select the Debugging folder.
3. In the Debugging folder, select the Just-In-Time page.
4. In the Enable Just-In-Time debugging of these program types box, select the program types (see the table below) you want to debug.
5. Click OK.

But I don't Have Visual Studio!!

[Alan]

Again I screwed up! I totally managed to NOT read your post properly, its been a good week so far Anyway if you are getting scripting errors with XP Manager and you want to look at the Hardware info, you can look at mine instead (see pic below)

Just uninstall the software and re-install, if the script error is still there then read on:
If you allow the Machine Debug Manager (MDM) to run, it can generate script errors.
Launch Msconfig from the Start menu's Run dialog and click on the Startup tab. If MDM is on the list, uncheck it and restart.
Appolgies for sending you on a wild goose chase Daniel but its been a hard week!

[Daniel]

THANKS ALAN you're helping me alot, don't worry hehe. Thanks again. So now I am going to re-install it and will see what happens next; and I will post back

[Daniel]

I am going to remove this winxp manager. Is it a good idea to remove that Machine Debug Manager from startup yet?

[Alan]

Yes, you dont really need it and generates script errors of its own.