[sane-devel] Epson 2400 and transparency scanning geometry

2005-08-30 Thread Olaf Meeuwissen
Hi Bob, Please Cc: sane-devel so your "ordeal" gets archived. bob writes: > On Mon, 2005-08-29 at 09:39 +0900, Olaf Meeuwissen wrote: > >> Hmm, log data looks fine to me. TPU area is reported fine. 48.26 mm >> by 231.14 mm is big enough to scan a strip of 6 negatives (that's what >> the prod

[sane-devel] Epson 2400 and transparency scanning geometry

2005-08-30 Thread bob
On Tue, 2005-08-30 at 12:10 +0900, Olaf Meeuwissen wrote: > Hi Bob, > > Please Cc: sane-devel so your "ordeal" gets archived. Will do. > bob writes: > > On Mon, 2005-08-29 at 09:39 +0900, Olaf Meeuwissen wrote: > > > >> Hmm, log data looks fine to me. TPU area is reported fine. 48.26 mm > >>

[sane-devel] scanning an entire A4 page under commandline

2005-08-30 Thread Aldo
Hi, I am vision impaired and I can only use the console under Gnu/Linux. I've tried to scan, doing: scanimage -v --format tiff >outputfile.tif It works but the scanner only picks a portion of 248x256 pixels at 24-bit, while there is no any option mentionned in the man page to tell scanimage tha

[sane-devel] scanning an entire A4 page under commandline

2005-08-30 Thread m. allan noah
Aldo- the options for paper size and scanning area are provided by the 'backend' which is a driver that talks to the scanner. scanimage is a 'frontend' which talks to you. try scanimage --help, which will tell the frontend to list all the options the backend provides. allan On Tue, 30 Aug 2005

[sane-devel] genesys backend

2005-08-30 Thread Pierre Willenbrock
Hi St?phane VOLTZ schrieb: > Le Lundi 29 Ao?t 2005 20:01, Pierre Willenbrock a ?crit : > ... >>Next i'd like to rewrite genesys_read_ordered_data to be more >>maintainable and able to convert the cis style planar data to "chunky" >>data. >> > > It is indeed a rather complicated fun

[sane-devel] scanning an entire A4 page under commandline

2005-08-30 Thread m. allan noah
forget that you are running debian for a second, and just run: scanimage --help this will make the sane front-end (scanimage) display all the options that the scanner backend (driver) provides. oh- and respond to the whole list, not just to me... allan On Tue, 30 Aug 2005, Osvaldo La Rosa wro

[sane-devel] /proc/bus/usb/001/002 , write permission changes required, is that normal behaviour?

2005-08-30 Thread Rayudu Addagarla
URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050830/1ef1d6fe/attachment.html From an...@pfeiffer.edu Tue Aug 30 20:16:22 2005 From: an...@pfeiffer.edu (m. allan noah) Date: Tue Aug 30 20:16:44 2005 Subject: [sane-devel] /proc/bus/usb/001/002 , write permission cha

[sane-devel] /proc/bus/usb/001/002 , write permission changes required, is that normal behaviour?

2005-08-30 Thread Henning Meier-Geinitz
Hi, On Tue, Aug 30, 2005 at 04:01:52PM -0400, Rayudu Addagarla wrote: > I had to change to have write permissions to other like, > -r--r--rw- 1 root root 57 2005-08-30 12:22 002 > then only as user i can see the device with scanimage -L > > Is this a common behavior? I expect to have only read pe

[sane-devel] /proc/bus/usb/001/002 , write permission changes required, is that normal behaviour?

2005-08-30 Thread Bertrik Sikken
Rayudu Addagarla wrote: > Hello > When i run scanimage -L as user i dont see the devices. > when i run as root i can see the devices. > i set Debug on and i see plustek backend says open failed. > > sane-find-scanner gives that device is libusb:001:002 > The permission on the /proc/bus/usb/001

[sane-devel] Mustek ScanExpress A3 USB

2005-08-30 Thread Henning Meier-Geinitz
Hi, On Thu, Aug 25, 2005 at 08:58:45PM +0100, Jonathan Hipkiss wrote: > I hate to say it but everything works fine in Windows, 24bit colour, > 600dpi full scan OK Ok, I'll try to find out what's the difference between the Windows and the Linux scan. However, this can take some time. Bye, Henn

[sane-devel] /proc/bus/usb/001/002 , write permission changes required, is that normal behaviour?

2005-08-30 Thread Martin Collins
On Tue, 30 Aug 2005 16:01:52 -0400 Rayudu Addagarla wrote: > Is this a common behavior? I expect to have only read perms and does > not require write perms. SANE has to ask the scanner to identify itself, and to be able to tell it to scan. That requires write permission. Martin