Hi,
> Ok, I did some testing with my BenQ 5150C.
>
> My first try was in 300dpi color mode (because this was default).
> There are no color stripes anymore. However, the scanned area was
> not very wide. Although the full available range
> ((0,0)x(216.0,297.0)mm^2) was selected in xscanimage. The
Hi,
> I do not understand how automated firmware upload should work
> if there is more than one scanner connected which use the same
> backend but which need different firmware files.
For the snapscan backend that's currently not possible, as there is
only a single firmware file entry in snapsca
abel deuring wrote:
> I don't want to open a discussion about licenses, but IMHO Sane's
> exception to the GPL encourages cases like this one. I think it
> would be more reasonable to put sane-backends under the LGPL, which
Good luck in getting every copyright holder (which includes every
patch
Hi,
On 2006-01-09 16:23, Johannes Meixner wrote:
> > The keyword refers to the previous `:model', is optional,
> > and applicable for devices with :interface "USB" only,
> > and should be used only once per model.
> > Example: `:usbid "0x1234" "0x4321"'
>
> "Should" is o.k. but please do not stri
Hi,
On 2006-01-09 14:36, Johannes Meixner wrote:
> But my question is:
> Can the backend automatically determine the right firmware file
> for a particular model?
Yes and no :-)
I'm talking about gt68xx scanners but I guess it's similar for others.
For the gt68xx scanners there is usually one sp
Volker Kuhlmann wrote:
> Hello Henning,
>>Just to make one thing clear: Vuescan is NOT a SANE frontend. I.e. it
>>does not use any SANE backend. It's a completely independent program
>>with independent scanner drivers.
>
>>It just happens to use a part of the internal low level SANE code
>>(sanei
Hello,
On Jan 8 17:00 Henning Meier-Geinitz wrote (shortened):
> The format of the SANE description files (.desc) has been changed to
> allow the addition of USB vendor and product ids to each model entry.
Great!
> The keyword refers to the previous `:model', is optional,
> and applicable for
Dear SANE Developers,
On Sun, 8 Jan 2006, Henning Meier-Geinitz wrote:
>> OK, I'd like to try. Should I contact the manufacturer for protocol
>> details or maybe someone has these already?
They pretend they're not authorized to give this information and it is
kept in secret by hardware manufact
Hello,
On Dec 28 13:09 Henning Meier-Geinitz wrote (shortened):
> The idea behind this change is that .conf.in files can be preprocessed
> the same way as already done for the manual pages (e.g. sane-epson.man
> -> sane-epson.5). This allows us to use configure variables like
> @DATADIR@ in the c
On Sun, Jan 08, 2006 at 01:53:45PM +0100, Henning Meier-Geinitz wrote:
> Hi,
Hi,
> On 2006-01-07 05:15, Aurelien Jarno wrote:
> > -#if defined(__linux__) || defined (HAVE_SYS_HW_H)
> > +#if defined(__GLIBC__) || defined (HAVE_SYS_HW_H)
>
> But this means that Linux without glibc won' work, which
Hi,
the search engine (http://www.sane-project.org/cgi-bin/driver.pl) now
supports search for usb-ids as well.
You can either fill in the IDs in the form (you can also leave out
either the vendor or the product ID), or invoke the script directly:
driver.pl?p=4002
will search for usb devices wit
Hello Henning,
thanks much for your thoughts!
> > 3) xsane is a GUI around sane,
>
> It's a frontend, not really "gui around sane".
>
> >but not a scanning application either,
>
> Come on.
Let's not argue about semantics. While I don't doubt that xsane is a
good program for pushing slider
12 matches
Mail list logo
