MDX Configurator Crashes

**creaseguard** · 09-27-2009, 01:47 AM

I'm getting a crash on startup of the MDX configurator.

When I initially installed the software and the FB drivers, I could not get the updater to run. I did an uninstall then reinstall and same thing. I did an uninstall, delete directory, remove updater from the startup folder then cleaned the registry, rebooted and reinstalled, rebooted and same thing, crash on startup.

I can't seem to save a copy of the crash dump. Any ideas? Works fine on my desktop but CarPc is a no go. Running XP Pro.

Jay

**creaseguard** · 09-27-2009, 10:08 AM

Just an update to the Fushion Brain Gurus that will eventually read this thread.

Here is what I'm seeing on the error signature:

Error Type: clr20r3
P1: fcc uber mdx configurator.exe
P2: 1.0.0.275
P3: 4a36005d
P4: system.drawing
P5: 2.0.0.0
P6: 4889dec2
P7: 7af
P8: 6c
P9: system.argumentexception

I'm no coder so I googled the error type and found a couple links:

http://www.caublestoneink.com/dev/20...clr20r3-error/

http://channel9.msdn.com/forums/Tech...tType-clr20r3/

http://mymce.wordpress.com/2009/07/1...-media-center/

This seems it might be a .NET framework issue.

I am going to try and uninstall and reinstall 2.0 as that seems to be associated with this error.

Jay

**creaseguard** · 09-27-2009, 02:36 PM

Ok, did a complete windows reinstall and the configurator works now but the Control Center crashes on startup.

So damn frustrating why one that worked before doesn't work now and vice versa....but it works perfect on my desktop that's an older computer.

Any ideas...anyone?

Jay

**creaseguard** · 09-27-2009, 02:54 PM

An uninstall and reinstall of the MDX software seems to have done the trick, both working now.

Man what a nightmare. Stupid winblows blows sometimes.

Jay

**creaseguard** · 09-27-2009, 04:57 PM

Ok, the configurator error has appeared again. I believe it to be a conflict between the FB and MJS's XM USB module and/or his Audio switcher.

Is there anyone running any combo of these units?

Jay

**PaulF** · 09-27-2009, 05:00 PM

Well that error looks like a bug in MDX. It's giving an error with something that uses the System.Drawing class, meaning that there is a problem with some kind of image in it. I doubt it's a hardware conflict.

2k1Toaster is probably the only one that can really help.

**creaseguard** · 09-27-2009, 05:15 PM

I thought the same thing looking at the error but it didn't pop back up until I installed MJS gadgets. I probably mispoke when I said it was hardware, I suspect it's more like something in the two softwares that are clashing. I suspect when I install the software for the XM and HD radios is when it's occuring. It's probably overwriting some file that MDX is looking for a specific instance of.

I suspect I will have to do another windows reinstall to get a good working MDX config again as it looks like just uninstalling the MJS stuff and uninstalling the MDX stuff with a MDX reinstall does not fix the issue.

Jay

**PaulF** · 09-27-2009, 07:46 PM

Uninstall all .net framework packages on your computer and reinstall them. Look on the microsoft site for .net framework 1.0, 2.0, and 3.0.

One of the installers could be screwing with the .net framework installation/

**creaseguard** · 09-27-2009, 10:54 PM

I'm pretty sure it's a dotnet 2.0 issue going on, I just don't know what's happening.

I did a fresh windows install again and have gotten back to the point where I want to install Sat Amp 4. I'd like to install Sat Amp 4 without touching the Dot Net framework at all.

I posted a message over on Mitch's forum to see if we can figure out what's going on.

Jay

**creaseguard** · 09-27-2009, 11:04 PM

Ok, I tried one more thing and so far so good. Instead of running the SatAmp4 setup program, I just ran the .msi installer and that seems to have NOT repeated the issue.

I'm a happy camper for now. Only took the ENTIRE day to work this out. I hope the front end setup isn't this bad.

Jay