Have your tried a system restore point before installing MC3? And did you try the clean uninstall/reinstall that Beag bumped?
Everything you have reported as an error message is referring to documentation - and judging by the "hungapp" at the end, I would say the documents are documenting what you already know - the application is hung (up) - no laughs please. -
snickers are cool.
Also this is from Leo the computer dude so you don't waste your time with "Appcompat.txt": "Appcompat.txt is simply a reporting file used when uploading error reports to Microsoft. You've seen the message asking you if you would like to "report this error to Microsoft"? Appcompat.txt is a file that is uploaded if you say yes.
Appcompat.txt is not the problem. It contains information about the problem. Open it up in notepad, and you'll see what I mean. When you get an error message that references appcompat.txt, it'll usually give you the full path to the file. So click on Start, Run and enter:
notepad C:\DOCUME~1\username\LOCALS~1\Temp\WER7b4e.dir00\appcompat.txt
Where "C:\DOCUME~1\username\LOCALS~1\Temp\WER7b4e.dir00\appcompat.txt" is replaced with the actual information that was presented in the error message. You'll see a lot of technical information that begins with this:
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
Followed by information about the program that was running at the time an error occurred. Note: it's not meant that you understand this. It's meant for the engineers back at Microsoft to use to analyze failures and hopefully provide fixes over time. I point it out here, simply to drive home the point:
Appcompat.txt is not the problem. It contains information about the problem."
But unless you can understand the techie end of it - it probably won't do much good.
post edited by millerbill - 2007/07/06 01:23:38