Link to home
Start Free TrialLog in
Avatar of stefarg
stefarg

asked on

Disabling Program Error Dialog

Hey All,

I am running a program on Windows 2000 that crashes periodically and displays a "Program Error" Dialogue stating

"decoder.exe has generated errors and will be closed by windows.
You will need to restart start the program
An error is being created"

and then waits for the used to click "OK".  However, I don't want the program to wait for the user to click "OK" or even to display the dialog, I just want the program to crash and continue on as if the "OK" button was clicked.

>>>> PLEASE NOTE (IMPORTANT):
I have tried setting the value of "ErrorMode" in the registry ([HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows]) to 2 i.e. no popups but this did not seem to work.
<<<<

Can someone please help me with this problem, it is urgent!
Thanks,
Stef
SOLUTION
Avatar of Zaheer Iqbal
Zaheer Iqbal
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of stefarg
stefarg

ASKER

Thanks for replying!

What I am trying to do is to allow the program to move on to the next line in a batch file i.e. the program should terminate (even with an error code) and then continue.  Each line in the batch file runs the program with different arguments and I don't mind if it crashes as long as it continues to the next line.  It is not practical to press the "OK" button on the dialog because there are 1000s of lines in the batch file to run different configurations.

I had a similar problem to this on another computer but changing the registry as explained above solved the problem, but unfortunately no for this computer.

Any other ideas?

Could it be something to do with disabling event logging?
Avatar of stefarg

ASKER

OK, problem solved.

I had disabled the error prompts but the Dr. Watson tools seemed to be causing problems with logging, so I disabled it by modifying the registry key "Auto" in
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug] to 0.

Also, I don't know if it made any difference or even if it was a good idea (I needed to get it working so I tried it) but I also disabled
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\CrashControl] "LogEvent".

Thanks for the comments, I'm gonna split the points, with the majority of the points going to Longbow because he (or she) posted some potential solutions, while the other comment was just a question.  However I'm giving some points just for replying :D
Thanks again.
Avatar of stefarg

ASKER

P.S. I didn't delete this question because I think the comments posted and the solution to the problem may prove valuable to others in the future
I am "He". Happy it works for you.