Re: apsfilter V6.0; dvips and pdf problem

[Andreas Klemm <andreas@xxxxxxxxxxxxx>]

Hi !

Just a little remark, Did I tell you already, not to write only 
to me directly, but instead write to the mailing-list as well ??

Its even not necessary to put me on Cc: since I see, if mail
arrives in that mailinglist folder (using procmail +xbuffy).

I'm not running Linux or LPRng and can't help much when it
comes to those systems with sometimes kind of strange behaviour.

At least I don't have these problems with my FreeBSD 4.2 system
which is my personal reference platform with a standard Berkeley
line printer scheduler (lpd). O.k., doesn't help you much, but
thats the infrastructure, I'm using.

But actually I didn't get failure reports from other Linux
Users last recently, where certainly many use LPRng ...
So in my eyes your system seems to be a bit "special" to me.
What did you say, what your Linux distrib "exactly" is ?
And ... is it really apsfilter or SuSE with susefilter, which
they call apsfilter as well :-/

On Tue, Jan 09, 2001 at 03:12:38PM +0100, Bernd Speiser wrote:
> Andreas Klemm wrote:
> 
> >
> > > echem9:[/root] #ls -ld /root
> > > drwx------  12 root     root         1024 Jan  7 02:03 /root/
> >   ^^^^
> >
> > What happens if you change it to 755 ?
> >
> > This could be a valid workaround.
> 
> When I change it to 755 dvi files are indeed printed - however, special-included
> postscript files are still not found, if I give only a relative pathname although
> the directory where the file resides is in the TEXINPUTS
> path. Well, maybe this is indeed a dvips problem.

Remark2: and could you please try not to exceed 70 or so colums,
since reading partly wrapped around lines in an 80 column xterm is
ugly.

> Also acroread seems to work better now, but it produces another error message
> (maybe not related to apsfilter?):
> 
> IF filter 'apsfilter' filter msg - 'Fatal System Error: Raise at top of Exception
> Stack' at 2001-01-09-15:08:56.264 ## A=bs@echem9+176 number=176 process=11178
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> IF filter 'apsfilter' filter msg - '++ return' at 2001-01-09-15:09:00.621 ##
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> A=bs@echem9+176 number=176 process=11178
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Question ... concerning this output and the logs you sent some days
ago ...  Is it LPRng, that puts the whole crap in front of apsfilters
debugging output, making it pretty unreadable ?
Or from what source did you give me the debugging output ???

Its currently not easy recognizeable, if its an acroread error message,
when it appears, etc ...

> Nothing is printed in this case. Any ideas?

What acroread version ?

Could you please enable debugging in apsfilter and try to 
send me the output of one failing print session using
acroread as filter ?
Could you also try to "silence" LPRng, so that it doesn't write
the "&%"&%§$" crap in from of the apsfilter shellscripts debugging
output ? That would make me really glad ;-)

	Andreas ///

-- 
Andreas Klemm                                           Powered by FreeBSD SMP
Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.html
My homepage................................ http://people.FreeBSD.ORG/~andreas
Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/