🚀 go-pugleaf

      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?

      Along the same lines, we have laser-printing stations and the
   laserwriter drivers are loaded on all of the machines so that a
   user can have their formatting ready - instead of tying up the
   few stations in the lab.  But, the next user (what a curse!  ARG
   "The Next User..."  :^) doesn't know that the Chooser settings 
   have been altered and gets garbage when they print to the linked
   imagewriters.  Anything in this area?  Something that would be
   able to restore Chooser settings after a period of inactivity?

      andrew.  (brennan@hal.hahnemann.edu)


--
   The opinions expressed are not necessarily those of the University of
     North Carolina at Chapel Hill, the Campus Office for Information
        Technology, or the Experimental Bulletin Board Service.
           internet:  bbs.oit.unc.edu or 152.2.22.80