Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!ucsd!pacbell.com!pacbell!att!mcdchg!chinet!patrickd
From: patrickd@chinet.chi.il.us (Patrick Deupree)
Newsgroups: comp.windows.ms
Subject: Re: Unrecoverable Application Error
Message-ID: <1990Aug30.141654.2064@chinet.chi.il.us>
Date: 30 Aug 90 14:16:54 GMT
References: <419.26dbf5bd@venus.ycc.yale.edu> <11726@chaph.usc.edu>
Organization: The Whitewater Group, Evanston, IL
Lines: 20

In article <11726@chaph.usc.edu> dchun@aludra.usc.edu (Dale Chun) writes:
>Besides the obvious, does anyone know what an Unrecoverable
>Application Error is and what triggers it? Sometimes it pops up
>immediately and other times, it takes over 2 hours of Windows 3.0 use
>before it appears. Thanks for any input.

Basically, an Unrecoverable Application Error is anything that Windows
doesn't understand.  There is no "set condition" that will cause it to
happen.  With Windows, however, it will usually involve memory referencing/
allocation errors.  Basically, if you have a program that wasn't written
correctly, it might try to reference memory someplace.  Now, if this memory
it tries to reference happens to contain something Windows needs, you'll
get said error. If you're lucky and that application doesn't hit that memory
right off the bat, you can run for a while before it does try to do something
nasty.
-- 
"What's in a name?  That which we call a rose by any other name would smell
 as sweet."             William Shakespeare
Patrick Deupree ->	patrickd@chinet.chi.il.us
			Business Phone: (708) 328-3800