Re: Timeout problem printing pdf files from Windows via Smaba

[Andreas Klemm <akl@xxxxxxxxxxxxxxxxxxx>]

On Tue, Nov 26, 2002 at 05:34:42PM +0000, John Matthews wrote:
> Hi,
> 
> After a bit more testing, I believe that the problem is not with apsfilter
> - printing pdf files from command line on the Linux box completes OK. So,
> the problem is with the data that my windows box is sending (or maybe
> still with the way apsfilter is interpreting it).

I don't understand your logic anymore.
You make tests you don't tell me about.
You come to conclusions I can't share because you 
don't tell me the details ...
You ask me what to do but I don't understand the NEW problem,
since from the previous mail everything seems to work o.k. now.

First of all ..... Where is the printer ?
If I understand you right, then its connected to the linux box.
You then use samba to print from windows to the linux printer as
if it were a shared windows printer, but actually its a Unix printer.

If you print stuff from windows, then the windows printer driver
take usually care, that the output of the printjob is already
translated to the printers own native print language ...

The data arrives from apsfilter view of things as DATA.

There are rare cases, where your Linux boxes file command
can't detect exactly that its data.

In this case you should install a 2nd apsfilter printer and
best call him "raw" or something like this, and globally
configure it to print simply raw data .... Another method
would be, to create a printer in printcap "by hand" and
NOT using apsfilter, since Windows already translated the
job to the printers language ...

All that apsfilter then does is something like
cat - (that is read the data stream from <stdin> and
concatenate it to <stdout> which is connected to the
print device (i.e.: /dev/lp0).

Well, when you sent me the 1st debugging output of aps2file
it looked, as if you were printing a PDF file on the linux
machine, not from the Windows printer .... I say this because
from my experience Windows doesn't send the PDF print job
as PDF print data to the samba printer ... it would translate
it to data ... but here apsfilter recognizes a PDF document ...

+ HEADER=/tmp/apsfilter8680/header1
+ dd bs=1k count=16
++ file /tmp/apsfilter8680/header1
+ FILE_TYPE=/tmp/apsfilter8680/header1: PDF document, version 1.3
++ echo PDF document, version 1.3
++ tr A-Z a-z
+ FILE_TYPE=pdf document, version 1.3
+ unpacker=
+ '[' '' ']'
+ cat /tmp/apsfilter8680/header1 -

The solution to this problem with the gs runtime error was,
to remove acroread or acroread4, which possibly produced
wrong PS output. But this was in a sutuation where you printed
locally on the linux machine !!!!


Now you come along with a complete different theme.

> After a bit more testing, I believe that the problem is not with apsfilter
> - printing pdf files from command line on the Linux box completes OK.

A) This was NOT o.k. the 1st debugging output was a local print jon
   initiated from the linux machine from what I see ...
   Printing was o.k. after removing acroread as I described before ...
   So please what are you writing here ????

> So,
> the problem is with the data that my windows box is sending (or maybe
> still with the way apsfilter is interpreting it).

NOW you have a 2nd problem or not (who knows, did I already get
a separate problem description for that ???? )

Well .... apsfilter should treat windows print data as data ...
and do nothing more than doing a "cat -" .... no filtering, nada,
nothing more ....


Please ... write a little more structured, sorted, verbose ...

Currently you descritions are a mess ...

I can't understand them anymore :-/
It wastes my time.


-- 
Andreas Klemm                             /\/\/\/\/\/\/\/\/\/\/\
http://www.64bits.de                     <  Powered by FreeBSD  >
http://www.apsfilter.org/                 \   www.FreeBSD.org  /
http://people.FreeBSD.ORG/~andreas         \/\/\/\/\/\/\/\/\/\/