Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!ll-xn!ames!elroy!spacely!eto
From: eto@spacely.Jpl.Nasa.Gov (Edward Olsen)
Newsgroups: comp.sys.mac
Subject: Print Monitor Problem
Message-ID: <6529@elroy.Jpl.Nasa.Gov>
Date: 2 May 88 17:37:38 GMT
Sender: news@elroy.Jpl.Nasa.Gov
Reply-To: eto@spacely.Jpl.Nasa.Gov (Edward Olsen)
Organization: Image Analysis Systems Grp, JPL
Lines: 19

I have encountered a problem with Print Monitor v1.0 which I think the Mac
community should know about.  It became apparent when I used Cricket Draw v1.1
to make some figures.  I found that the system crashed, or the mouse froze up,
or applications (Print Monitor among them) "unexpectedly quit" just after the
postscript output file was generated.

These problems did not occur when I ran the same printout under Finder (not
Multifinder).  I then found that the 10K cricket draw document was generating
a 108K spooled print file!  Since I had configured my Print Monitor application
to use 120K of memory, I was just on the hairy limit.  Once I increased my
Print Monitor partition to 200K, all problems ceased.  The document contained
a small bitmap, some shaded circles and some arcs.  Users of applications which
generate postscript files (not just Cricket Draw users) should be aware of this
problem with Print Monitor.

Until Apple comes out with a fixed version of Multifinder and Print Monitor,
I suggest either increasing the Print Monitor application memory size to
at least 200K, avoid Multifinder entirely, or use another print spooler.
				   Ed Olsen