Hi,
On Tue, Aug 07, 2001 at 10:17:26PM +0200, Guido Socher wrote:
> Has anybody seen the following problem with the net backend
> in sane 1.0.5?
Not me.
> The xscanimage program crashes because it tries to write
> data to a closed connection.
As far as I see only the data connection is closed,
Jochen Eisinger wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi!
>
> Does network scanning work with scanimage and/or xsane?
>
> Here it works also with xscanimage...
I did some tests with xsane, sane-umax and sane-pnm.
No problems with network scanning when I am using sane-b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Does network scanning work with scanimage and/or xsane?
Here it works also with xscanimage...
regards
- -- jochen
[Guido Socher]
> Has anybody seen the following problem with the net backend
> in sane 1.0.5?
>
> The xscanimage program crashes
Has anybody seen the following problem with the net backend
in sane 1.0.5?
The xscanimage program crashes because it tries to write
data to a closed connection.
The connection is closed in the sane_read() function in
net.c because it executes this code:
if (s->bytes_remaining == (size_t) - 1)
Hi,
> [snapscan] add_device(/dev/usbscanner)
> [snapscan] mini_inquiry
> [snapscan] mini_inquiry: sanei_scsi_cmd command failed: Error during device
> I/O [snapscan] add_device: mini_inquiry failed with Error during device
> I/O. [snapscan] sane_snapscan_get_devices (0xb380, 0)
I didn't real
Am Dienstag, 7. August 2001 19:37 schrieb Jed S. Baer:
> Greetings folks.
>
> Regretably, there isn't much to go on here, unless sharing an IRQ with
> my SB-Live is what's causing the lockup.
>
> System is an ABIT KA7 mobo, running RH7.1, custom kernel.
Kernel version ?
> The attached file is a
Hi,
I have just started using Sane and was very happy to see my old UC840
is supported. Unfortunately, I can't get it to work properly :(
When I attempt to preview using xsane, it finishes the first pass ok and
then displays an error "Failed to start scanner: device busy".
Below is the output w
Oliver Neukum wrote:
>
> Am Dienstag, 7. August 2001 19:37 schrieb Jed S. Baer:
> > Greetings folks.
> >
> > Regretably, there isn't much to go on here, unless sharing an IRQ with
> > my SB-Live is what's causing the lockup.
> >
> > System is an ABIT KA7 mobo, running RH7.1, custom kernel.
>
> K
This is a multi-part message in MIME format.
--BC42531231CF0F798C93FAA8
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Greetings folks.
Regretably, there isn't much to go on here, unless sharing an IRQ with
my SB-Live is what's causing the lockup.
System i
--- Oliver Schwartz
> wrote:
>Hi,
>
>> Then I start xsane, which looks for devices and then informs me that it
>> found none.(I am root)
>
>Make sure that /dev/scanner does *not* exist. Also check that
>/dev/usbscanner is listed in snapscan.conf. If this doesn't help, run
>'export SANE_DEBUG_SN
Hi,
I'm pleased to announce that version 0.8 of the HP OfficeJet Linux driver
(hpoj) is now available at http://hpoj.sourceforge.net.
Major changes include the following:
- A completely new low-level I/O driver, with new USB support and greatly
improved parallel-port support for both the MLC a
On Wednesday 25 July 2001 20:40, Simon Munton wrote:
> Hi Roger,
>
> It looks like the Blackwidow scanner has had its SCSI vendor and product ID
> changed. You can get the artec backend to 'pretend' that a scanner it finds
> has a different vendor/product ID - see the sane-artec man page. Basically
Thanks for your suggestion, but I think scanner.c 0.4.5 (included in
kernel 2.4.7) is up to date. Which version of scanner.c do you refer to?
Did I overlook a new version on David Nelson's web site?
Stephan
--
Bill Slade wrote:
>
> Dear Stephan,
> Updating scanner.o to the latest versio
13 matches
Mail list logo
