[sane-devel] snapscan (agfa 1236s) not working since 1.0.4

a few months ago i upgraded my 1.0.4 version. The agfa 1236s scanner stopped working (hp 4c works well). Till now i have had to use the old version for that model. Broken sane says: $ scanimage snapscan > /tmp/scan.pnm [sanei_debug] Setting debug level of snapscan to 255. [snapscan] sane_snapscan

[sane-devel] xsane issues on Mac OS X

Paul, this may come over as selfish, appologies if it does, but when you get a frontend built that I can use across the network (I have my scanner plugged into my linux box), please let me know so that I can do some testing with you/for you? Either scanimage or xsane will do to be

[sane-devel] snapscan (agfa 1236s) not working since 1.0.4

Hi, > a few months ago i upgraded my 1.0.4 version. The agfa 1236s > scanner stopped working ... > [snapscan] send_diagnostic > [snapscan] snapscan_cmd > [snapscan] send_diagnostic: snapscan_cmd command failed: > Error during device I/O Hm, this looks strange. I'm not aware of any changes in thi

[sane-devel] PLUGINRC madness

On Tue, 9 Apr 2002, Oliver Rauch wrote: > Johan Bengtsson wrote: > > We're running Gimp 1.0.4 & xsane 0.79 and we have two workstations with > > scanners, one with an Umax scanner and the other one with an Epson > > scanner. The problem is that if one first uses the Epson scanner, gimp > > will cr

[sane-devel] 'read more data than announced by backend'

--AQYPrgrEUc/1pSX1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I received this bug report: "I have a Microtek ScanMaker E6. I have sane-backends-1.0.7-6 and related versions installed. I am running kernel

[sane-devel] PLUGINRC madness

Johan Bengtsson wrote: > Well, I'm not the only one using these scanners, they're used by > (potentially) hundreds of users, and they can't be expected to go through > this process to make it work. If a scanner device can't be found the > program should look for another device and update pluginrc

[sane-devel] xsane issues on Mac OS X

Jim George wrote: > Paul, > > this may come over as selfish, appologies if it does, but when you get > a frontend built that I can use across the network (I have my scanner > plugged into my linux box), please let me know so that I can do some > testing with you/for you? but of course: I w

[sane-devel] usb umax 2200 configuration issues II

Hi, I can reproduce your problem. For some reason if the "quality calibration" is set, the scanner hangs. If "quality calibration" is not set, it works. I'll try to find out why. Frank.

[sane-devel] snapscan (agfa 1236s) not working since 1.0.4 --- solved

Oliver Schwartz writes: > As a first test, you could try to disable the send_diagnostic command - it > doesn't seem to work for all models. To do this, open snapscan-scsi.c and find > the function send_diagnostic(). Change the lines i disabled. It works now (i have got 2 of this model). So you

[sane-devel] test backend version 1.0.11 (beta)

Henning Meier-Geinitz, Dienstag, 9. April 2002 23:51: > Hi, > > Version 1.0.11 of the test backend can be dowloaded from > http://www.meier-geinitz.de/sane/test-backend/ . > > Changes: > > - Bugfixes > - different return stati for sane_read() > - man page > - it's beta now > > I would like to inclu

[sane-devel] test backend version 1.0.11 (beta)

Hi, Hi, On Wed, Apr 10, 2002 at 09:10:31PM +0200, mh wrote: > I don't have an idea, how a frontend could present all those crazy options in > a reasonable way :-) I'm not sure, either. I just tried everything the standard allows... > E.g. how could/should a user interface for "Int test option

[sane-devel] SCSI problems with avision backend

Hi, Since the latest update of the avision backend I can't access my Mustek (!) scanner anymore. It took some time to find out that the reason is really the avision backend. Symptoms: I have a Mustek scanner (doesn't matter which one) attached to a SCSI controller. The device file is /dev/sg0, a

[sane-devel] a backend test

Hi Frank, I've tested your tstbackend from 08.04.2001. It showed me nicely some bugs in my microtek2 backend :-). But after correcting some of them, I'm now at the following point: karsten@coyote:~ > tstbackend -d microtek2:/dev/scanner -l 1 2>tst.log tstbackend, Copyright (C) 2002 Frank Zago tst

[sane-devel] a backend test

> In the logfile of the backend I see that the option > tstbackend is complaining about is not active: > > [microtek2] sane_control_option: option 21; action 1 > [microtek2] sane_control_option: option 21 not active > > Therefore sane_control_option fails with SANE_STATUS_INVAL. tstbackend, for so

[sane-devel] "illegal" exporting of symbols

Hi, SANE backends should only export symbols (functions, variables) that are absolutely necessary. Usually these are the sane_* functions of the API and for some backends sanei_backendname_* functions. In the latter case the names must be unique in all backends. Please don't export any other symb

[sane-devel] snapscan (agfa 1236s) not working since 1.0.4 --- solved

Hi, > > As a first test, you could try to disable the send_diagnostic command - > > it doesn't seem to work for all models. To do this, open snapscan-scsi.c > > and find the function send_diagnostic(). Change the lines > > i disabled. > It works now (i have got 2 of this model). Good. I'll chang

[sane-devel] SANE_CAP_ALWAYS_SETTABLE

Hi, Does anybody know what the capability "SANE_CAP_ALWAYS_SETTABLE" means? It's in sane.h but I can't find it in the standard. It's used in qcam.c and v4l.c for every option. Bye, Henning

[sane-devel] SCSI problems with avision backend

Hi > And I guess it's nor mustek-related. Anyone else have this problem? I got some similar problem reports from SnapScan users. They couldn't access their scanner until they removed all other backends from dll.conf. However, noone traced it to the avision backend. Since I don't have a SCSI sca

[sane-devel] a backend test

Frank Zago wrote: > > > In the logfile of the backend I see that the option > > tstbackend is complaining about is not active: > > > > [microtek2] sane_control_option: option 21; action 1 > > [microtek2] sane_control_option: option 21 not active > > > > Therefore sane_control_option fails with SAN