Hi,
On Fri, Apr 25, 2003 at 03:04:53PM -0500, Peter Chen wrote:
> I entered SANE_DEBUG_FUJITSU=128 as a shell command (am I doing it right?)
Either do
export SANE_DEBUG_FUJITSU=255
scanimage ...
or
SANE_DEBUG_FUJITSU=255 scanimage ...
At least if you use bash as your shell.
> In my previous
Hi,
On Fri, Apr 25, 2003 at 01:58:39PM -0500, Peter Chen wrote:
> In my application, after sane_start succeeded, I called sane_read, and it
> always returned SANE_STATUS_GOOD, so it just hanged there.
>
> What could be the reason?
You mean it never returns SANE_STATUS_EOF even after all the data
Tim Waugh wrote:
>
> I'm afraid I no longer maintain the ppSCSI patch due to lack of time.
>
Will someone else at Red Hat do it or will the patch be removed from the
Red Hat kernels?
Anyone on the list who wants to overtake the maintainership of this
patch so that parallel scanners stay suppor
--iig7nzZQzi/oiJm2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Apr 20, 2003 at 01:32:35AM +0200, Till Kamppeter wrote:
> Tim, can you perhaps put the patch for kernel 2.4.21 onto your FTP site?=
=20
> Thank you.
I'm a
Hi,
I entered SANE_DEBUG_FUJITSU=128 as a shell command (am I doing it right?)
and then I ran scanimage --duplex=both -d fujitsu:/dev/usb/scanner0 > a.pnm
and it showed me the same error messages, nothing special, besides br-x,
br-y, it only showed:
scanimage: sane_start: Invalid argument.
In my
On Thu, 24 Apr 2003, Peter Chen wrote:
> I tried scanimage with --mode=gray, and it worked fine. But I could not do
> it with --duplex=both. It said:
> scanimage: sane_start: invalid argument. scanadf did not work either.
ok, sounds like a driver problem. the output from setting
SANE_DEBUG_FUJIT
Hi,
In my application, after sane_start succeeded, I called sane_read, and it
always returned SANE_STATUS_GOOD, so it just hanged there.
What could be the reason?
Thanks,
Peter
Hi,
On Fri, Apr 25, 2003 at 11:30:19AM +0200, Karsten Festag wrote:
> in your list you mentioned microtek2 as not supporting i18n. I think that
> isn't true, in microtek2.h the translateable strings are marked with
> SANE_I18N.
You are right, I've only grepped the .c files, not .h. Some others
w
Hi Henning,
in your list you mentioned microtek2 as not supporting i18n. I think that
isn't true, in microtek2.h the translateable strings are marked with SANE_I18N.
Bye
Karsten
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Ho
Hi,
Please reply to the list, not to me pesonally.
On Thu, Apr 24, 2003 at 04:39:45PM -0700, Doug Docherty wrote:
> Yes, that's the problem. The "S" suffix indicates a SCSI scanner. I
> have the USB version, that has, alas, no suffix.
It's not in the list so it's most probably not supported. I
Hi,
On Thu, Apr 24, 2003 at 11:12:00PM +0200, Franz Bakan wrote:
> Everything built fine with one exeption:
> OS/2 runtime-lib doesnt't have rintf()
> (used in Line 1226 of hp5400_internal.c)
rintf is C99, rint is BSD 4.2.
> So I got one undefined symbol _rintf while linking.
>
> replacing rint
Hi,
On Thu, Apr 24, 2003 at 06:07:53PM -0500, Peter Chen wrote:
> I tried scanimage with --mode=gray, and it worked fine. But I could not do
> it with --duplex=both. It said:
> scanimage: sane_start: invalid argument. scanadf did not work either.
Does scanimage --help show the duplex option? Does
Hi,
On Thu, Apr 24, 2003 at 03:43:38PM -0500, Peter Chen wrote:
> I tried to set fi-4120c to Grayscale. I used the following code flow:
>
> status = sane_init(version_code, NULL);
> status = sane_get_devices(&device_list, true);
> ...
> sane_exit();
Some backends
Use the strings 'Lineart', 'Halftone', 'Gray' or 'Color' to set option
scan_mode. As far as I can see, value=3 does not work.
Which function returned SANE_STATUS_INVAL? sane_control_option with
option SANE_NAME_SCAN_MODE? That should only happen when you try
to set mode 'Halftone'.
Oliver
Am Don
14 matches
Mail list logo
