🚀 go-pugleaf

The fleshy one known as Michael MacDonald (mike@REMOVETHIStorfree.net)
did smite their keyboard thus:

>	Greetings,
>
>	I'm having printing difficulties in a 30-seat GIS lab.  The print
>jobs being spooled are huge ArcView printouts (postscript files) of about
>3-8 megabytes in size.  These files are clogging our network and printers,
>as they seem to sit in the spooler and cause errors.  Our configuration is

Try doing some simple maps without image or raster data and see if
that works. Even a layout with just some text on it to see if it's
reading the postscript _at all_. In Arc/INFO at least, the default is
to compress rasters in postscript, and this causes our old (slow)
printers to spend 12-24 hours at a time un-compressing images before
printing them. I don't know how to turn raster compression off in
ArcView though.

(the files will be *huge*, but perversely, print in a fraction of the
time)

>30 machines P-166s 64mb memory, printers are 2 HP desk jets, 1 Lexmark 5700 
>inkjet, and 1 large Lexmark printer (this printer even takes a while to 
>process these immense images once spooled).

3-8 Mb is not big at all.  :o)

(especially if it's just being copied from the desktop machine to the
print spool)

Is your spooler set up to pretend that the Lexmarks etc are really
postscript printers? Try sending your plots to a real postscript
printer and see if that works.

>	There are also blue screens of death associated with these printouts

If it's on the desktop, this suggests that the desktop box and the
spooler are not being nice to each other.

>- Also, we are experiencing SEGMENT VIOLATION errors, which normally are 

And getting personal about it...

Antti
--
"It's the worst feeling in the world to love a song and then
discover that what they're singing about is lame" - Kristin Hersh