Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!unido!rwthinf!slcdec!hippo!f1.n6000.z2.fidonet.org!p1.f36.n245.z2.fidonet.org!Thomas_Hornschuh
From: Thomas_Hornschuh@p1.f36.n245.z2.fidonet.org (Thomas Hornschuh)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Question on UAE's when running TPW
Message-ID: <233261955@p1.f36.n245.z2.fidonet.org>
Date: 12 Jun 91 21:50:28 GMT
Reply-To: Thomas_Hornschuh%p1.f36.n245.z2@hippo.dfv.rwth-aachen.de (Thomas Hornschuh)
Organization: Thomas Hornschuh, SoftStream Development, FRG
Lines: 20
Comment-To: F0O@f1.n6000.z2.fidonet.org (F0o)

f >    Since when doing program development in TPW, one is likely to get
f > many UAE's(especially when you're first starting out) :-)
f > I was wondering if your other programs are protected from
f > these errors or not.  I wouldn't like to have to exit windows and restart
f > every time I would encounter a UAE, but maybe this is the best way to
f > work?

My personal expierence is:
If windows survives the UAE, you need not terminate your windows session.
Most common reason for a UAE is using an invalid pointer. This causes a general 
protection fault _before_ any damage occurs. 

+-----------+                         Thomas Hornschuh
|           |                     SoftStream Development
|   *       |           Obermarkstr. 72, D-4600 Dortmund 30, FRG
| *   *     |         Tel ++49-231-48 64 60  Fax ++49-231-48 85 98
|   *       |                        FidoNet 2:245/36.1
+-----------+ UseNet: Thomas_Hornschuh%p1.f36.n245.z2@hippo.dfv.rwth-aachen.de