Back again
well I found out that the tmpfile is writeable and the commands issued by the
script are like the following:
cat - | sed "s/[(]%%.*%%[)].*flush//g" |
gs -q -sDEVICE=bjc600 -r360x360 -sPAPERSIZE=a4
-dNOPAUSE -dSAFER -sOutputFile=/tmp/printtmp.2qRNaU
-dBitsPerPixel=8 - >/dev/null 2>&1 ; cat /tmp/printtmp.2qRNaU ; rm
/tmp/printtmp.2qRNaU
If I try to issue the command
gs -q -sDEVICE=bjc600 -r360x360 -sPAPERSIZE=a4
-dNOPAUSE -dSAFER -sOutputFile=<my file>
-dBitsPerPixel=8
everything works fine.
My problem is, I don't understand the "cat - | ..." part from the first
script. I think it sort of "feeds" the file into gs, but I don't know.
(I can't figure out any other part of the script where the file-to-print get's
into the script.
On Sam, 18 M�r 2000, Brian T. Schellenberger wrote:
> [...]
> Second, this is just a stab in the dark, but when the tempfile remains
> do you have proper permissions to write to it?
>
> Finally, since you found the script & everything, I'd take a gander at
> the actual ghostcript input and output.
>
> You see that "eval" command at the end? Well, there is presumably
> where the problem is.
>
> Add some lines to the script, like this:
>
> echo mpage_cmd: $mpage_cmd
> echo gs command: gs -q -sDEVICE=$GSDEVICE \
> -r$RESOLUTION \
> -sPAPERSIZE=$PAPERSIZE \
> -dNOPAUSE \
> -dSAFER \
> -sOutputFile=$TMPFILE \
> $COLOR \
> $EXTRA_GS_OPTIONS -
>
> This will tell you what the spooler is actually trying to *do* to print
> the text. Then you can try the commands yourself and see if you get
> some coherent error messages and go from there.
>
>
>
> On Sat, 18 Mar 2000, you wrote:
> | Hello around there,
> |
> | I recently set up a mandrake 7 box and it seems it is impossible to print
> | anything but plain ascii.
> | I used printtool to set up my canon bjc-4000 (using the suggested driver). I am
> | not able to print the ps-testpage (or any other ps-file), but ascii works fine.
> | After tracking down the bug I ended up in
> | '/usr/lib/rhs/rhs-printfilters/ps-to-printer.fpi' . It seems it creates a
> | tmpfile (mktemp-command from line 45), which never gets any input. (I deleted
> | the command 'rm $TMPFILE' from line 131 and the file which remained had size 0
> | bytes.)
> |
> | So, any idea out there?
> |
> | THXIA Sascha Kiedrowski
> --
> I am "Brian, the man from babble-on" (Brian T. Schellenberger).
> I can be reached at [EMAIL PROTECTED] .
> I support http://www.eff.org & http://www.programming-freedom.org .
> I boycott amazon.com. See http://www.gnu.org/philosophy/amazon.html .
--
***************************************************
Oberdorfstra�e 54
69124 Heidelberg
Tel.: 06221/789853
Mobil: 0171/540 24 84
[EMAIL PROTECTED]
***************************************************
