[sane-devel] Re: scanner not recognised part II

[Paul Frisson]

--Boundary-00=_2HJQAGcNDnjQsX8
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

here is the printed text

Le Samedi 28 F=E9vrier 2004 13:56, Karl Heinz Kremer a =E9crit :
> The backend gets initialized correctly, so you should find debug output
> from the EPSON backend when you set SANE_DEBUG_EPSON. Please try it
> again:
>
> export SANE_DEBUG_EPSON=3D128
> xsane
>
> Does this print anything?

--Boundary-00=_2HJQAGcNDnjQsX8
Content-Type: text/plain;
  charset="iso-8859-1";
  name="sane_debug2"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="sane_debug2"

[sanei_debug] Setting debug level of epson to 128.
[epson] sane_init: sane-backends 1.0.12
[epson] sane_init, ># epson.conf<
[epson] sane_init, >#<
[epson] sane_init, ># here are some examples for how to configure the EPSON backend<
[epson] sane_init, >#<
[epson] sane_init, ># SCSI scanner:<
[epson] sane_init, >scsi EPSON<
[epson] sane_init, >#<
[epson] sane_init, ># Parallel port scanner:<
[epson] sane_init, >#pio 0x278<
[epson] sane_init, >#pio 0x378<
[epson] sane_init, >#pio 0x3BC<
[epson] sane_init, >#<
[epson] sane_init, ># USB scanner - only enable this if you have an EPSON scanner. It could<
[epson] sane_init, >#               otherwise block your non-EPSON scanner from being<
[epson] sane_init, >#               recognized.<
[epson] sane_init, >#           Depending on your distribution, you may need either the<
[epson] sane_init, >#           first or the second entry.<
[epson] sane_init, >#usb /dev/usb/scanner0<
[epson] sane_init, >#usb /dev/usb/scanner0<
[epson] sane_get_devices()

--Boundary-00=_2HJQAGcNDnjQsX8--