🚀 go-pugleaf

rbennett@loki.une.oz.au (Robert Bennetts) writes:

>	Hi...
>
> [question, why an application's UAE appears in shell and kills it instead]

Hi!

Most (well, all, could be said) UAE:s are due to a programming error in
an application.  If such an error hits before an application has properly
started, the Windows still wants to get rid of an offending application.
But it doesn't quite yet know that the improperly initialized startee even
exists, so in a state of confusion it kills the (still active one) starter
process just to be sure.

I've seen it once or twice, too.  It's funny, if you're running any other
applications - in my system IdleWild usually becomes the new 'shell'.

Btw, if you're developing Windows apps and do some 'iterative coding' that
occasionally UAEs like that, you can copy the PROGMAN.EXE into TASKMAN.EXE
(after making a backup copy of the TASKMAN.EXE !!!).  Then you'll get the
Program Manager (and not the Task List) when you press <CTRL>&<ESC> to be
able to start new programs instead of Switching to...

Terveisin: Risto Lankinen
-- 
Risto Lankinen / product specialist ***************************************
Nokia Data Systems, Technology Dept *  2                              3   *
THIS SPACE INTENTIONALLY LEFT BLANK * 2 +1 is PRIME!  Now working on 2 -1 *
replies: risto@yj.data.nokia.fi     ***************************************