Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!rex!samsung!sdd.hp.com!decwrl!shelby!neon!rokicki
From: rokicki@Neon.Stanford.EDU (Tomas G. Rokicki)
Newsgroups: comp.sys.next
Subject: Re: spooled LaserWriter problems
Message-ID: <1990Aug3.234502.21089@Neon.Stanford.EDU>
Date: 3 Aug 90 23:45:02 GMT
References: <26357@usc.edu> <588@grumpy.sarnoff.com> <232@heaven.woodside.ca.us>
Organization: Computer Science Department, Stanford University
Lines: 22

In article <232@heaven.woodside.ca.us> glenn@heaven.UUCP (Glenn Reid) writes:
>In article <588@grumpy.sarnoff.com> puh@sarnoff.com (Patrick Hsieh) writes:
>>I have the NeXT connected to our local Ethernet network and have it set up 
>>to print by spooling to one of our Suns.  It sort of works, in the sense 
>>that sometimes things print OK, and sometimes not.  In particular, I ran 
>>dvips (300 dpi, memory set to 900000) on the emacs manual, and brought it 

The standard Apple LaserWriter doesn't have 900,000 bytes of free VM.
Try setting it to 130,000, or send the attached few lines to see how
much VM you actually have.  Try printing just the first page, too.

If it should happen that the Emacs manual is simply too complex (dvips
will complain of some pages being too complex), you can either try 
another printer (with more VM), or get dvips5.31 from labrea.stanford.edu.
It is set up to compile and go on the NeXT, and it uses somewhat (30%?)
less VM for most bitmapped fonts.

Mail to me for more help as necessary.   -tom

%! Hey, we're PostScript!
/Times-Roman findfont 30 scalefont setfont 144 432 moveto
vmstatus exch sub 40 string cvs show pop showpage