Claus and Ingo's solutions both assume that the message box described by Alex is the system unhandled exception message. I just wanted to mention that this may not be the case. Several development environments impose their own top-level exception handler which displays modal UI instead of or before handing over to the system exception handler.
For example, Delphi apps are particularly fond of displaying "Access Violation" message boxes and tend to continue (and, inevitably, display a storm of further errors) after the user OKs them. If I remember rightly, an unhandled exception in a VB6 app also leads to a modal message box, though I think the process does terminate once this is acknowledged. If this is what's happening in Alex's third-party process, then hooking the system unhandled exception / JIT debugging behaviour won't help, because the process is "catching" the access violation and *ahem* "dealing" with it. -- Ivan Towlson White Carbon =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
