Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!hplabs!nsc!pyramid!pyrps5.pyramid.com!telam
From: telam@pyrps5.pyramid.com (Thomas Elam)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Utility Please...
Message-ID: <136689@pyramid.pyramid.com>
Date: 6 Dec 90 02:38:44 GMT
References: <9011262158.AA29395@luke.eecs.wsu.edu> <135887@pyramid.pyramid.com> <yorkw.659799005@stable.ecn.purdue.edu> <136223@pyramid.pyramid.com>
Sender: news@pyramid.pyramid.com
Reply-To: telam@pyrps5.pyramid.com (Thomas Elam)
Distribution: usa
Organization: Pyramid Technologies, Mt. View, California.
Lines: 25

In article <136223@pyramid.pyramid.com>, telam@pyrps5.pyramid.com
(Thomas Elam) writes:
|> In article <yorkw.659799005@stable.ecn.purdue.edu>,
|> yorkw@stable.ecn.purdue.edu (Willis F York) writes:
|> |> >Phil Cooper asks:
|> |> >  Question:  Has anyone developed a utility that catches traps and other
|> |> >  exceptions and handles them without guru'ing the machine?  
|> |> 
|> |> >There was GOMF (stood for Get Outa My Face).  Version 1.0
|> |> >was public domain. 
|> |> 
|> |> 
|> |> I can still crash the My 500 in ways Gomf Can't catch. 
|> |> (Well the Programs i Run crash my 500)
|> 
|> There's no way, without a Memory Management Unit, to prevent any type of
|> crash.

Before I get flamed on this, let me make myself clear.  I should have said
"... to prevent all types of crash."
 
I think I also misspelled Perry Kivowits' name (I wrote "Kivowitz").  Sorry,
Perry.

Tom