> -----Original Message----- > From: Dirk Krause [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 09, 2004 2:26 AM > To: [EMAIL PROTECTED] > Subject: Re: LPRng: SLOW spooling of Word file containing 225 pgs of > scanned docs > > > > I ran into something on Friday that I can't > > sort out. > > > > I have the following setup: > > > > Lanier 2138 RPCS Color Laser > > (same as Ricoh 3800CMF) > > > > Win2k SP4 > > RPCS driver v 2.67 (most current) > > Print via Standard TCP/IP Port > > > > OpenBSD 3.2/LPRng 3.8.21 > > OpenBSD 3.4/LPRng 3.8.26 > > > > Printcap entries (tried Friday) > > for the 2138, which seem to work > > fine for all other print jobs: > > :[EMAIL PROTECTED]:lpd_bounce > > :rm=xxx.xxx.xx.xx:rp=lp > > :lp=xxx.xxx.xx.xx%9100 > > :lp=xxx.xxx.xx.xx%9100:lpd_bounce=true > > > > If I use the above settings, printing > > the Word 2000 file through either > > OpenBSD box takes FOREVER to spool > > the temp file; I can ls the > > /var/spool/lpd/2138 directory > > and watch the file dribble in. > > I tried a 40-page chunk, which > > resulted in a 56MB job, with NO > > improvement in speed. It never > > got to the point where the job > > actually started to print. It was > > taking so long, I knew something > > was amiss and killed the job. > > > > > > I ended up setting up a Standard > > TCP/IP port directly to the Lanier, > > to see if it behaved similarly. > > > > NOT!!! > > > > The job started spitting out as soon as > > I clicked on the Ok button in the > > Word print dialogue. It finished printing > > the 40 pages almost before I got to the > > printer. > > > > My lpd.conf is all defaults on both > > OpenBSD boxes. All other print jobs > > seem to print at full speed. > > > > What gives? > > Hi, > > When creating large/complicated print jobs (i.e. including > bitmap graphics) there may be long time intervalls between > data packets sent from PC to the server, timeouts can happen. > To avoid these timeouts create the entire print job first > before connecting to the print server. In the printer > properties go into the spool settings and turn > "Start spooling after last page is finished" on. The exact > text may vary, I have a german Windows on my PC. > I tried that, and "Print directly to the Printer" with the same results.
> Make sure the format for the queue is literal (binary) so > the print server does not run filters on the print job. > No filtering is being done, and the Print Processor is set to "raw" on the Win2k box. > If these hints do not help we need to find out whether the > problem is related to transfering the print job from the PC > to the server or to sending from server to printer. It's from the Win2k PC to the server; it never finished spooling, so it never went to the printer. Sending it directly to the printer's own lpd, with the PC set to the default of "Start Printing Immediately" did exactly that. The only changes in settings were using raw protocol instead of lpr, and printing to port 9100 instead of the queue. The 2138 has a hard drive, and printed at full speed-no dribbling of the job. Why not just print directly to the printer? Because...the Ricoh/Lanier print server has an annoying tendency to go off into la-la land if multiple users/drivers are talking to it. I can crash it just by sending a PS job to it; within 4 print jobs, the queue is corrupt and the printer has to be reset. Sometimes I had to reformat the hard drive just to force a rebuild of the queue structure. I finally troubleshot it down to a decent solution; use ONLY the RPCS drivers, and use LPRng to feed it the jobs. Now it prints all day, every day. I can use holdall while changing out fuser oil rollers, etc, and noone knows the printer's been down. I call the 2138 "The Chipper"; feed trees in at one end, and stuff comes out the other... > Print the print job to a file, transfer the file to the > print server and try to print using lpr. > > Hope this helps, > > Dirk > > Jim> ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
