Disabling the pesky "xyz program has encountered an error..."
-
1. Press [Windows][Break] to display the System Properties dialog box. 2. Select the Advanced tab and click the Error Reporting button. 3. When you see the Error Reporting dialog box, select the Disable Error Reporting option. (If you don’t want to see any type of error message, clear the But Notify Me When Critical Errors Occur check box.) 4. Click OK twice — once to close the Error Reporting dialog box and once to close the System Properties dialog box. [^] I think this is what you are talking about; I had the same annoying problem.
Blog link to be reinstated at a later date.
Dude (or Dudette, hard to tell) - you rock. :-D Thanks! [edit] My Paranoid Hubby? Is this a new user name? Didn't think to look at the profile... :doh: [/edit]
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
modified on Monday, September 1, 2008 6:07 PM
-
Oh, wow, this is great! [hurriedly grabs his long list of enhancement requests]
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
Dude (or Dudette, hard to tell) - you rock. :-D Thanks! [edit] My Paranoid Hubby? Is this a new user name? Didn't think to look at the profile... :doh: [/edit]
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
modified on Monday, September 1, 2008 6:07 PM
Dudette
Gary Kirkham Forever Forgiven and Alive in the Spirit "Truly, truly, I say to you, he who hears My word, and believes Him who sent Me, has eternal life, and does not come into judgment, but has passed out of death into life. Me blog, You read
-
Dudette
Gary Kirkham Forever Forgiven and Alive in the Spirit "Truly, truly, I say to you, he who hears My word, and believes Him who sent Me, has eternal life, and does not come into judgment, but has passed out of death into life. Me blog, You read
:doh: I didn't realize it was [name changed to protect the innocent] until I looked at the profile...
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
modified on Monday, September 1, 2008 6:14 PM
-
:doh: I didn't realize it was [name changed to protect the innocent] until I looked at the profile...
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
modified on Monday, September 1, 2008 6:14 PM
shhh, I thought she was incognito
Gary Kirkham Forever Forgiven and Alive in the Spirit "Truly, truly, I say to you, he who hears My word, and believes Him who sent Me, has eternal life, and does not come into judgment, but has passed out of death into life. Me blog, You read
-
shhh, I thought she was incognito
Gary Kirkham Forever Forgiven and Alive in the Spirit "Truly, truly, I say to you, he who hears My word, and believes Him who sent Me, has eternal life, and does not come into judgment, but has passed out of death into life. Me blog, You read
:suss: Kinda hard to be incognito when you give your name in your user profile... :-D
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
-
I don't know if there's some registry setting for this or not. Couldn't turn up anything on Google, so I thought I'd turn to more intelligent sources. There are times when a program meets with an untimely demise. When it crashes, life in Windows comes to somewhat of a halt until you press the OK button on this dialog box which tells you what you already knew - your program is AFU. Sometimes, however, you just want the darned thing to die - without any user interaction required. This dialog prevents Windows from shutting down, among other things, so it can be a bit of a PITA. Does anyone know any clever little tricks to tell Windows not to display this stupid GPF dialog box?
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Wrap a try catch around your application run method?
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingway -
:suss: Kinda hard to be incognito when you give your name in your user profile... :-D
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
I only agreed to change my user name and remove by blog link. We would have to renegotiate for that. I've had a few people wonder until they read the bio. I wanted to leave that so common users still knew who I was.
Blog link to be reinstated at a later date.
-
Wrap a try catch around your application run method?
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingwaydoes that always work ? I read a bit about minidump's recently and they CAN be intercepted/handled programatically (rather than the standard 'report to MS'), but I though it was more involved than that (unless Im off on a tangent) [modified] - yes, I do know that exceptions != minidumps .. people may interested in this http://www.naughter.com/exceptionlogger.html[^] from PJ Naughter, which can trap both. 'g'
modified on Monday, September 1, 2008 10:16 PM
-
1. Press [Windows][Break] to display the System Properties dialog box. 2. Select the Advanced tab and click the Error Reporting button. 3. When you see the Error Reporting dialog box, select the Disable Error Reporting option. (If you don’t want to see any type of error message, clear the But Notify Me When Critical Errors Occur check box.) 4. Click OK twice — once to close the Error Reporting dialog box and once to close the System Properties dialog box. [^] I think this is what you are talking about; I had the same annoying problem.
Blog link to be reinstated at a later date.
-
Wrap a try catch around your application run method?
Need a C# Consultant? I'm available.
Happiness in intelligent people is the rarest thing I know. -- Ernest Hemingwayhahahahaha! LOL! sorry that was all that came to mind.
-
I don't know if there's some registry setting for this or not. Couldn't turn up anything on Google, so I thought I'd turn to more intelligent sources. There are times when a program meets with an untimely demise. When it crashes, life in Windows comes to somewhat of a halt until you press the OK button on this dialog box which tells you what you already knew - your program is AFU. Sometimes, however, you just want the darned thing to die - without any user interaction required. This dialog prevents Windows from shutting down, among other things, so it can be a bit of a PITA. Does anyone know any clever little tricks to tell Windows not to display this stupid GPF dialog box?
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
How about the AppDomain.UnhandledException Event? http://msdn.microsoft.com/en-us/library/system.appdomain.unhandledexception.aspx[^]
-
1. Press [Windows][Break] to display the System Properties dialog box. 2. Select the Advanced tab and click the Error Reporting button. 3. When you see the Error Reporting dialog box, select the Disable Error Reporting option. (If you don’t want to see any type of error message, clear the But Notify Me When Critical Errors Occur check box.) 4. Click OK twice — once to close the Error Reporting dialog box and once to close the System Properties dialog box. [^] I think this is what you are talking about; I had the same annoying problem.
Blog link to be reinstated at a later date.
I too would like to disable the 'report close - yes no' notification when applications crash, but these instructions do not fix the issue. What this does is disables whe dialog where it asks you to notify microsoft of the error; you still get the halt dialog reporting the fatal error. What I would like is for the application to exit silently with no dialogs at all, which is proving much more difficult. My latest attempt was to add handlers for microsoft's own exception mechanism, which picks up access violations and hardware related reports as well as program errors, but even this does not cover everything.
-
I only agreed to change my user name and remove by blog link. We would have to renegotiate for that. I've had a few people wonder until they read the bio. I wanted to leave that so common users still knew who I was.
Blog link to be reinstated at a later date.
My Paranoid Hubby wrote:
I wanted to leave that so common users still knew who I was.
hehehe, well... I changed my name, but left the profile exactly the same. Most folks caught on, but a few did actually get confused. And a few forgot after a few months. Strange how much a name becomes the person, but then... this is the internet, all we really have are names. Change the name and it is like putting on glasses to become Clark Kent.... :-D
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
-
I don't know if there's some registry setting for this or not. Couldn't turn up anything on Google, so I thought I'd turn to more intelligent sources. There are times when a program meets with an untimely demise. When it crashes, life in Windows comes to somewhat of a halt until you press the OK button on this dialog box which tells you what you already knew - your program is AFU. Sometimes, however, you just want the darned thing to die - without any user interaction required. This dialog prevents Windows from shutting down, among other things, so it can be a bit of a PITA. Does anyone know any clever little tricks to tell Windows not to display this stupid GPF dialog box?
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
Not sure what language your program is written in, but I ran into the same type of problem when writing a windows service. What I did was to write a method that handles the AppDomain.CurrentDomain.UnhandledException event. That way if an exception occurs that you are not currently handling, it will allow to exit your code gracefully.
-
I too would like to disable the 'report close - yes no' notification when applications crash, but these instructions do not fix the issue. What this does is disables whe dialog where it asks you to notify microsoft of the error; you still get the halt dialog reporting the fatal error. What I would like is for the application to exit silently with no dialogs at all, which is proving much more difficult. My latest attempt was to add handlers for microsoft's own exception mechanism, which picks up access violations and hardware related reports as well as program errors, but even this does not cover everything.
I haven't tried it myself, but I would think the following product (still in beta) might do the trick since if one can substitute a custom dialog, one ought to be able to squelch the custom dialog. I'd be interested in knowing if it works! http://www.automatedqa.com/products/aqtrace/index.asp[^] Regards, R
-
I only agreed to change my user name and remove by blog link. We would have to renegotiate for that. I've had a few people wonder until they read the bio. I wanted to leave that so common users still knew who I was.
Blog link to be reinstated at a later date.
I was wondering where you went. Glad you're still around. I still miss the daily holidays. :-D
Cheetah. Ferret. Gonads. What more can I say? - Pete O'Hanlon
-
I don't know if there's some registry setting for this or not. Couldn't turn up anything on Google, so I thought I'd turn to more intelligent sources. There are times when a program meets with an untimely demise. When it crashes, life in Windows comes to somewhat of a halt until you press the OK button on this dialog box which tells you what you already knew - your program is AFU. Sometimes, however, you just want the darned thing to die - without any user interaction required. This dialog prevents Windows from shutting down, among other things, so it can be a bit of a PITA. Does anyone know any clever little tricks to tell Windows not to display this stupid GPF dialog box?
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
This one bit me in the ass just recently. Our product consists of a UI application and a number of services. The services run the actual hardware. The UI and the services communicate using TCP/IP sockets, since some of the services can run on separate boxes. The UI crashed. While the Dr. Watson dialog is open, the UI process and its socket connections are 'held' in a constant state. As a result, our services didn't realize the UI had gone down, and continued to merrily operate the equipment (a large printing press). As soon as you clicked the Dr. Watson dialog button, the services were notified of the UI disconnect and shut things down. The WTF in all this: the operators submitted an issue to the bug data base, complaining that the UI stopped responding and the big red STOP button didn't work :doh: :doh: :doh: :doh: :doh:.
Software Zen:
delete this; -
My Paranoid Hubby wrote:
I wanted to leave that so common users still knew who I was.
hehehe, well... I changed my name, but left the profile exactly the same. Most folks caught on, but a few did actually get confused. And a few forgot after a few months. Strange how much a name becomes the person, but then... this is the internet, all we really have are names. Change the name and it is like putting on glasses to become Clark Kent.... :-D
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
El Corazon wrote:
Most folks caught on, but a few did actually get confused.
Or took it as evidence that you were "confused"... :-\
----
You're right. These facts that you've laid out totally contradict the wild ramblings that I pulled off the back of cornflakes packets.
-
I don't know if there's some registry setting for this or not. Couldn't turn up anything on Google, so I thought I'd turn to more intelligent sources. There are times when a program meets with an untimely demise. When it crashes, life in Windows comes to somewhat of a halt until you press the OK button on this dialog box which tells you what you already knew - your program is AFU. Sometimes, however, you just want the darned thing to die - without any user interaction required. This dialog prevents Windows from shutting down, among other things, so it can be a bit of a PITA. Does anyone know any clever little tricks to tell Windows not to display this stupid GPF dialog box?
Christopher Duncan Author of The Career Programmer and Unite the Tribes www.PracticalUSA.com
You don't state if you want a program you are writing to just die, or "any old" program that might encounter a "fatal" error. If any program, then you already have a solution given. If you are writing the program, you can trap this and just terminate your program. In the main program you need an error handler for Application.ThreadException. Of course if your program has multiple threads things get messier and I won't even try to address those.
Charles Wolfe C. Wolfe Software Engineering