Subject: Re: Netatalk and PC printi
From: Yaser K. Doleh (doleh@dijkstra.cba.csuohio.edu)
Date: Fri Nov 04 1994 - 16:19:25 EST
Patrick Harris said in a letter
>
> We have been using netatalk for a couple of months and we have been very
> pleased from the mac side (much much better than the commercial package we
> were using to access NFS volumes), but have come across a problem with
> printing files on the PC side.
>
> The pcs connect to the sun 670 using PC-NFS and we are trying to use pap to
> print to our ethertalked printers (especially our Compaq Pagemarq 20).
> Text print jobs print out fine but postscript jobs are causing errors.
>
> Excerpt of lpd-errs:
>
> ofpap[11755]: starting
> ofpap[11755]: sending to pap
> %%[ Error: undefined; OffendingCommand: ^D ]%%
> %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
> ofpap[11755]: 11756 done
>
The problem is that your PC is putting a ^D character the the begining
of your postscript file. You can solve this problem in one of two ways
1 - Tell your PC not to put the ^D. I know it can be done but I don't
know how.
2 - Modify psf source to accept the file that starts with ^D and strip
it.
I used the second solution because I did not know how to do
the first one and I did not have usefull documentation about
the postscript driver for Windows. Sorry, I don't have a patch
but it's an easy fix. Look for the lines where psf checks
to see if the file is a postscript.
Yaser
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:20:58 EST