Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!ucbvax!agate!WEB.berkeley.edu!laba-1aj
From: laba-1aj@WEB.berkeley.edu
Newsgroups: comp.sys.atari.st
Subject: Printer spooler
Message-ID: <1989Oct24.231605.26688@agate.berkeley.edu>
Date: 24 Oct 89 23:16:05 GMT
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: laba-1aj@WEB.berkeley.edu ()
Organization: Berzerkley Institute
Lines: 15


Is there a printer spooler that operates like the unix printer spooler:
it prints all the files in a directory, sequentially by date/time.  With
a hard disk, this could be a better spooler than one that eats up a chunk
of RAM and doesn't support queueing and de-queueing (via file deletes).


A somewhat related question:  How does GEM feel about TSRs and ACCs opening,
using, closing, and deleting files?  I've read that they should not do such
things.  What about file buffer space: is there a way to increase the number
of files allowed open?

&  John Kawakami
&  laba-1aj@web.berkeley.edu
&  Live each day as if it were your first