| Andreas Klemm on Thu, 28 Nov 2002 17:55:14 +0100 (CET)(envelope-from owner-apsfilter-help@apsfilter.org) |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| Re: Timeout problem printing pdf files from Windows via Smaba |
On Wed, Nov 27, 2002 at 09:22:05PM +0000, John Matthews wrote: > Hi, > > Apologies for apparently mis-leading you and wasting your time. It was > never my intention. Just because I post to a mailing list for help, does > not stop me continuing to investigate the problem that I am having. I will > re-cap so that everything is clear: > > 1. The original problem was when printing a pdf from a windows machine via > samba to an HP Laserjet 1100 connected via the parallel port. The print > driver on the windows machine was the HP 1100 as supplied by Windows XP. > This was set to print to the print queue on the Linux machine that > apsfilter was operating on. understood... > 2. Thanks to your advice I managed to produce the debug output for > apsfilter. I don't know how to emulate sending the data from the windows > machine via samba so used the Linux command line (as instructed by > yourself). From the output and a little web research, I determined that > the acrobat reader installation was causing a broken pipe error. Now > pdftops does the ps conversion and the apsfilter debug seems to be free > from errors. understood... > 3. I don't know how things work when printing via samba from the windows > machine to the printer on the Linux machine. However in the configuration > mentioned in (1) above, everything works apart from pdf files which > timeout. Reading further elsewhere made me suspect that: > (i) The windows machine should be made to print using a ps driver if > printing via the apsfilter or Windows knows how to print PDF files .. no need to install additional drivers. Only if you want to print PS files, then you need additional driver ... > (ii) The windows machine should be made to print using the > HP1100 windows driver if printing via a raw queue (ie: no apsfilter on the > queue). Yes this is the normal way ... You simply hit print within acrobat reader and this application prints to a windows (samba) network printer, that's it. > (what I have been doing is printing to an apsfilter enabled queue while > using the Windows RAW print driver - I suspect that this is bad... but > please correct me if apsfilter should cope with this). Yes ... this is indeed a bad thing. Simply don't do this ... It doesn't make sense .... You simply overshot and did too much .... > When testing from the Linux command line, I was verifying that apsfilter > was not at fault (and I succeeded in this verification). If you want to get debugging output when printing from windows remotely to a samba / apsfilter printer, then simply "hack in" set -x in /usr/local/share/apsfilter/bin/apsfilter below the line #! /usr/local/bin/bash Then you'll find the usual debugging output under /var/spool/lpd/<queue>/*.err (from memory, certainly some paths are different on your machine, but it gives you an idea where to search ... After debugging, please remove set -x > I have been away from the machine for a few days and need to test > configuration (i) listed above. I suspect that pdf files will print OK now > that I have a better understanding of how to configure my system. I will > confirm tomorrow. > > Many thanks and apologies for the confusion, No problem, thanks. Andreas /// -- Andreas Klemm /\/\/\/\/\/\/\/\/\/\/\ http://www.64bits.de < Powered by FreeBSD > http://www.apsfilter.org/ \ www.FreeBSD.org / http://people.FreeBSD.ORG/~andreas \/\/\/\/\/\/\/\/\/\/