=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 29 June 2004 22.45, Eric Tanguy wrote:
> I use this scanner on fedora core 2 with sane-backends-1.0.13-7 and
> xsane-0.92-10. All works fine except when i try to use resolution
> greater than 600 (900 or 1200). In these cases, the result i
--=-Xiaxg9k3fvPLAHu4fHrf
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
I use this scanner on fedora core 2 with sane-backends-1.0.13-7 and
xsane-0.92-10. All works fine except when i try to use resolution
greater than 600 (900 or 1200). In these cases, the result is malforme
Hello Cosmin,
>It's the complete driver. Anything needed to acces the
>scanner is there.
That´s good, that will make it not so difficult. So normally, we
will find all parts what we will need in the sources.
Do you got also some documentation from Mustek?
>Yes, I need help, somebody to talk to.
when you run scanimage with no -d argument, sane will load all the
backends that are listed in the dll.conf file, in an attempt to find your
scanner. you can look for this file in /etc/sane.d or similar, and # out
all the options other than the backend you are using. this should fix the
video i
Hi,
On Mon, Jun 28, 2004 at 06:54:29PM -0700, Peter Mark Guevarra wrote:
> Sorry for this late response..I have tested scanimage with Red Hat 8 and
> Red Hat 9.
> The output in Red Hat 9 is darker compared with that of Red Hat 8 but exactly
> the same settings were used..
Even if you use
Hello Kees,
I do not understand how you can change the version from 0.91 to 0.94
in xsane.rc when you removed the file xsane.rc,
in this case the file is deleted so you can not change anything in the
file!
When the problem still occurs then please do:
rm ~/.sane/xsane/xsane.rc
export XSANE_DEBUG
Hi,
The seg fault problem seems to be caused by an old ~/.gtkrc file with
illegal content: as soon as I remove this file all problems are gone !!
Don't know which line is responsible, but just decided to discard this
file completely to avoid any xsane seg faults as it doesn't seem to be
that i
Hello
I have configured my scanner with sane running in Fedora Core 2.
Whenever i try to run xsane or 'scanimage -L' the system does not find
any scanner attached... until i unplug the usb cable, wait a couple of
seconds and plug it back again. The whole time, the Fedora's hardware
browser DOE
I've got a MSI KT266-Pro2 motherboard with a VIA chipset. I'm wondering if
my hardware is the problem or if there's other things to check. I'm
able to sync a USB Palm device with Jpilot without any problems, but
my scanner generates errors.
I have another machine (an older Toshiba laptop) which
--xYxgRrcmUCOORODc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 29, 2004 at 03:57:40PM +0300, Panos Katergiathis wrote:
> Hello
>=20
> I have configured my scanner with sane running in Fedora Core 2.=20
> Whenever i
Hi,
I have the same problem with xsane 0.94, but although it indeed works
for most users, with some other users the problem doesn't disappear by
just removing the xsane.rc !
For those users where it still crashed we could fix the problem by
changing the version number from 0.91 to 0.94 in xs
11 matches
Mail list logo