Disabling the pesky "xyz program has encountered an error..."
-
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