we will see the name of the
> option in the log. Then one can adapt the config file to match the
> option name and call a scan-script.
>
> Am 02.11.2017 um 21:49 schrieb Adam Lloyd:
> > Sorry about that.
> >
> > pi@raspberrypi:~ $ export SANE_CONFIG_DIR=/etc/scanbd
> >
we will see the name of the
> option in the log. Then one can adapt the config file to match the
> option name and call a scan-script.
>
> Am 02.11.2017 um 21:49 schrieb Adam Lloyd:
> > Sorry about that.
> >
> > pi@raspberrypi:~ $ export SANE_CONFIG_DIR=/etc/scanbd
&
:001:004
Thanks again for your assistance!
Adam.
On Sun, Nov 5, 2017 at 6:31 PM, Wilhelm Meier <
wilhelm.wm.me...@googlemail.com> wrote:
> Please provide the log of scanbd from the beginning on - until the point
> where it starts repeating the same messages.
>
> Am 05.11.2017 um
Hello,
I recently moved an old scanner to a raspberry pi to see if I could get it
to work on alternative platform. A google search revealed that SANE has
"good" support for my particular scanner. After a few attempts I managed to
get Xsane working on a raspberry pi 3 running with stretch. I was
gt;
>
> Am 02.11.2017 um 16:19 schrieb Adam Lloyd:
> > Hello,
> >
> > I recently moved an old scanner to a raspberry pi to see if I could get
> > it to work on alternative platform. A google search revealed that SANE
> > has "good" support for my
*.tif.pdf cat output "compiled.pdf"
gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.4 -dPDFSETTINGS=/ebook
-dNOPAUSE -dQUIET -dBATCH -sOutputFile="$FILE_NAME.pdf" compiled.pdf
cp $FILE_NAME.pdf $OUT_DIR/
rm -rf $TMP_DIR
On Thu, Nov 2, 2017 at 4:49 PM, Wilhelm Meier <
wilh