🚀 go-pugleaf

Andrew.Brennan@bbs.oit.unc.edu (Andrew Brennan) writes:

>      Here's the problem.  I've recently switched the local lab to
>   System 7 from 6.0.7.  We have come up with a number of different
>   problems - none too terrible, but little problems none the less.

>      One is the memory constraints of a SE with 2.5M - you can get
>   Sys 7 and maybe one or two small applications in there and that 
>   is about all.  Not a problem - except for the user who switched
>   out to Finder w/o leaving their application.  The next user is
>   unable to enter anything.  (makes sense, no?)

>      We're ordering more memory, but this situation is related to
>   at least one or two more problems.  Has anyone written a timeout
>   to kill inactive applications?  Perhaps as a Sys 7 extension?

Of course you should upgrade to at least 4 mb memory to get a better
performance of sys 7.  But the problem really is that the users have to
become familiar with quitting applications when they finish using them
instead of hiding them behind the finder with the 'hide application' under
the 'Mac' menu.
As I manage a small network of Macs at work, I too have run into this problem.
I think that by now I have persuaded everyone to quit the application when
they've finished using the computer, so the next user has full access to
the memory (the Macs are 4 mb), but doesn't have to open the hidden appli-
cation via the 'Mac? menu and then quit it to be able to run the application
he/she wants to use.  This, of course, is seldom a problem on 8 mb Macs, but
then everyone has to be aware of these behind-lurking apps.
However, your idea of a timeout killer for inactive apps seems to be a good
idea.  I, too, would like to know if such a thing exists.

Bjorgvin R. Leifsson
brl@kopasker.is