>>>>> "Sam" == Sam MacDonald <smac at visi.com> writes: Sam> Rendering is memory intense, postscript going to a non-postscript Sam> printer will drive you nuts sometimes. Laser printers will go insane Sam> when they don't have enough memory to process a job. Some times they Sam> spit paper out with just one line or many lines of garbage or they just Sam> hang. Sam> But this sounded like a spooler stalling, because it was fixed by Sam> restarting the spooler (cups). Sam> If the print job is coming from a windoze machine. Sam> Be sure the output is set to "Raw" this may not eliminate all stalling Sam> but it should help. Sam> Turn off the printing of any extra pages that divide print jobs. Sam> Delete any temporary files " *.tmp " in the "Temp" directory Sam> (c:\windows\temp or c:\temp). Sam> Don't use the wonderful drag and drop feature on a windows machine to Sam> print, sometimes the application hangs the print job after several pages. Sam> Extend the time-out of the print spooler is another option. Sam> Turn the printer off and on once in a while, nothing like a Sam> cold boot. Thanks, the above are useful. But note that this is NOT just printing from Windoze. In fact, most of the problems occur printing from Linux. I don't understand about the time-out issue. If the time-out were too short, wouldn't I get the jobs failing? That's not what's happening --- the jobs just stop progressing.... Is there any way to tell if the problem's on the spooler side or on the printer side? BTW, I have looked at the WWW CUPS admin tool, and it's totally user-friendly. I.e., it doesn't export any useful information. Seems only to let me choose a driver and specify printer type. Munir seemed to be pointing at something with more functionality.... R _______________________________________________ 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