Path: utzoo!attcan!uunet!cs.utexas.edu!asuvax!stjhmc!p12.f56.n114.z1.fidonet.org!Chris.Gehlker
From: Chris.Gehlker@p12.f56.n114.z1.fidonet.org (Chris Gehlker)
Newsgroups: comp.sys.mac.misc
Subject: Re: Alarming Events (was Indispensable INITs...)
Message-ID: <26595.26F0E373@stjhmc.fidonet.org>
Date: 14 Sep 90 13:59:39 GMT
Sender: ufgate@stjhmc.fidonet.org (newsout1.26)
Organization: FidoNet node 1:114/56.12 - AZ MAC UG, Phoenix AZ
Lines: 37

owen@raven.phys.washington.edu (Russell Owen) asks:

> But is it (Alarming Events) really a good program? How buggy is Alarming
> Events?

It's really a useful program.  The only feature that I wish it had is the 
ability
to prioritize To Do Items by some criterion other than time.  As for buggy,
I've been suspicious of it because about the time I installed it, my Mac 
became
subject to freeze ups after long periods of no activity or only serial 
activity.
 I stuck in a couple of inits that came with Norton Utilities at about the 
same
time so I couldn't be sure that Alarming Events was the culprit.  In fact I
first suspected Norton's Disklight cdev because I have identical setups on my
personal II and my company IIci except that I don't use Disklight in the ci.
 The ci just purrs along, all the problems occured on the II.  Well I had 
determined
that trashing Disklight didn't solve the problem and trashing all my init's
did solve the problem.  I was about to test the hypothesis that Alarming 
Events
in incompatible with the II but compatible with the ci when a message here 
suggested
that there were problems with installing Alarming Events under Suitcase.  I
quick check of the ci confirmed that, sure enough, on the ci the Alarming 
Events
DA was installed direcly in the System File while on the II it was in an open
suitcase.  Not installing the DA with suitcase seems to have solved my problem
 
but it's early to draw that conclusion.

 

--  
Uucp: ...{gatech,ames,rutgers}!ncar!asuvax!stjhmc!56.12!Chris.Gehlker
Internet: Chris.Gehlker@p12.f56.n114.z1.fidonet.org