Rendering is memory intense, postscript going to a non-postscript printer will drive you nuts sometimes. Laser printers will go insane when they don't have enough memory to process a job. Some times they spit paper out with just one line or many lines of garbage or they just hang. But this sounded like a spooler stalling, because it was fixed by restarting the spooler (cups). If the print job is coming from a windoze machine. Be sure the output is set to "Raw" this may not eliminate all stalling but it should help. Turn off the printing of any extra pages that divide print jobs. Delete any temporary files " *.tmp " in the "Temp" directory (c:\windows\temp or c:\temp). Don't use the wonderful drag and drop feature on a windows machine to print, sometimes the application hangs the print job after several pages. Extend the time-out of the print spooler is another option. Turn the printer off and on once in a while, nothing like a cold boot. Sam. Munir Nassar wrote: >On Mon, 17 Nov 2003, Ian Stoner wrote: > > > >>more. I assumed it was a problem with the interaction between CUPS and >>SAMBA, but maybe the problem is actually the driver? >> >> > >heh... sounds to me like the printer is stopping to render > >add RAM, use a better PPD(hint: MacOSX ppds work great) or dont send large >jobs. > > > _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list