[sane-devel] Epson Perfection 1660 Photo
Yesterday I upgraded to sane 1.0.12 and xsane 0.92. Experienced seg faults when invoking xsane. I commented out "epson" in dll.conf and added "epkowa". This forced sane to use the Epson Kowa backend libsane-epkowa. Seg faults ceased. The Epson Kowa backend to sane works great. You might try and see if they will allow it to be distributed with sane. It is GPL or an approved variant I believe. Running RH 8.0 with Kernal 2.4.18-17.8.0 and gcc 3.2.2 to compile all source (sane, xsane and Epson Kowa source). Regards, Terry Boldt
[sane-devel] Epson Perfection 1660 Photo
Sending this message to the mailing list as you requested. I am requesting that any resoultion to the problem or discussion of the p= rolem=20 be 'cc' to me since I do not subscribe to the sane mailing list. If you=20 insist I will subscribe, but would rather not since my mail box is gettin= g=20 full already and I am trying to keep the input managable. Please do overlook the question on the "copy" function after the xsane de= bug=20 output and the gdb back trace output. I am far from an expert on these matters, but from the xsane output and t= he=20 gdb backtrace output, it would appear that the problem is in xsane. But t= hat=20 is my guess based on ignorance of the issue. On Friday 10 October 2003 21:11, you wrote: > Try to delete the file ~/.sane/xsane/EPSON:.drc and > give it > another try. No effect whatsoever. It is the presence of the 'xsane.rc' file that is=20 causing the problems. This file causes a seg fault if I attempt to use th= e=20 Epson Perfection 1660 Photo scanner with the libsane-epson backend. I can= use=20 the HP laserJet 1220 scanner no problems whatsoever.=20 It is only after the message box displays that it is scaning for devices.= It=20 then displays both scanners for me to choose from. If I choose the HP=20 LaserJet 1220, it continues no problem. If I choose the "Epson GT-8300=20 Flatbed scanner [Epson:/dev/usb/scanner0]" option, then it seg faults wh= en=20 xsane.rc is present. ran export XSANE_DEBUG=3D128 xsane > /tmp/xsane.log 2>&1 The output is below: -- [xsane] Setting debug level to 128 [xsane] This is xsane version 0.92 [xsane] created ipc_pipefd for inter progress communication [xsane] Setting xsane translation table with localedir:=20 /usr/local/share/locale [xsane] xsane_interface [xsane] xsane_init [xsane] xsane_back_gtk_make_path [xsane] path =3D "/home/terry/.sane/xsane/xsane-style.rc" [xsane] xsane_back_gtk_make_path [xsane] path =3D "/usr/local/share/sane/xsane/xsane-style.rc" [xsane] loading /usr/local/share/sane/xsane/xsane-style.rc [xsane] xsane_pref_restore [xsane] xsane_back_gtk_make_path [xsane] path =3D "/home/terry/.sane/xsane/xsane.rc" [xsane] preferences_restore [xsane] xsane_rc_io_w_init [xsane] xsane_rc_io_w_set_dir [xsane] xsane_rc_io_w_flush [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_flush [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_skip_ws [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_string: decoding xsane-version [xsane] reading preferences value for xsane-version [xsane] xsane_rc_pref_string [xsane] xsane_rc_io_skip_ws [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_string: decoding 0.92 [xsane] xsane_rc_pref_string: decoding string =3D 0.92 [xsane] xsane_rc_io_w_free [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_skip_ws [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_string: decoding tmp-path [xsane] reading preferences value for tmp-path [xsane] xsane_rc_pref_string [xsane] xsane_rc_io_skip_ws [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_string: decoding /tmp/ [xsane] xsane_rc_pref_string: decoding string =3D /tmp/ [xsane] xsane_rc_io_w_free [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_skip_ws [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_space [xsane] xsane_rc_io_w_string: decoding working-dire
[sane-devel] Epson Perfection 1660 Photo
solution (dpi): 80 [epson] resolution (dpi): 90 [epson] resolution (dpi): 100 [epson] resolution (dpi): 120 [epson] resolution (dpi): 133 [epson] resolution (dpi): 144 [epson] resolution (dpi): 150 [epson] resolution (dpi): 160 [epson] resolution (dpi): 175 [epson] resolution (dpi): 180 [epson] resolution (dpi): 200 [epson] resolution (dpi): 216 [epson] resolution (dpi): 240 [epson] resolution (dpi): 266 [epson] resolution (dpi): 300 [epson] resolution (dpi): 320 [epson] resolution (dpi): 350 [epson] resolution (dpi): 360 [epson] resolution (dpi): 400 [epson] resolution (dpi): 480 [epson] resolution (dpi): 600 [epson] resolution (dpi): 720 [epson] resolution (dpi): 800 [epson] resolution (dpi): 900 [epson] resolution (dpi): 1200 [epson] resolution (dpi): 1600 [epson] resolution (dpi): 1800 [epson] resolution (dpi): 2400 [epson] resolution (dpi): 3200 [epson] maximum scan area: x 27200 y 37440 [epson] fbf tlx 0.00 tly 0.00 brx 215.84 bry 297.179993 [mm] [epson] send buf, size =3D 2 [epson] buf[0] 1b . [epson] buf[1] 44 D [epson] receive buf, expected =3D 1, got =3D 1 [epson] buf[0] 06 . [epson] send buf, size =3D 1 [epson] buf[0] 10 . [epson] receive buf, expected =3D 1, got =3D 1 [epson] buf[0] 06 . [epson] Max. supported color depth =3D 16 [epson] request_focus_position() [epson] send buf, size =3D 2 [epson] buf[0] 1b . [epson] buf[1] 71 q [epson] receive buf, expected =3D 4, got =3D 4 [epson] buf[0] 02 . [epson] buf[1] 12 . [epson] buf[2] 02 . [epson] buf[3] 00 . [epson] receive buf, expected =3D 2, got =3D 2 [epson] buf[0] 00 . [epson] buf[1] 40 @ [epson] Focus position =3D 0x40 [epson] Enabling 'Set Focus' support [epson] send buf, size =3D 2 [epson] buf[0] 1b . [epson] buf[1] 66 f [epson] receive buf, expected =3D 4, got =3D 4 [epson] buf[0] 02 . [epson] buf[1] 12 . [epson] buf[2] 2a * [epson] buf[3] 00 . [epson] code 02 [epson] status 12 [epson] count 42 [epson] receive buf, expected =3D 42, got =3D 42 [epson] buf[0] 05 . [epson] buf[1] 00 . [epson] buf[2] 00 . [epson] buf[3] 00 . [epson] buf[4] 00 . [epson] buf[5] 00 . [epson] buf[6] 80 . [epson] buf[7] c0 . [epson] buf[8] 17 . [epson] buf[9] c0 . [epson] buf[10] 71 q [epson] buf[11] 00 . [epson] buf[12] 00 . [epson] buf[13] 00 . [epson] buf[14] 00 . [epson] buf[15] 00 . [epson] buf[16] 00 . [epson] buf[17] 00 . [epson] buf[18] 00 . [epson] buf[19] 00 . [epson] buf[20] 00 . [epson] buf[21] 00 . [epson] buf[22] 00 . [epson] buf[23] 00 . [epson] buf[24] 00 . [epson] buf[25] 00 . [epson] buf[26] 47 G [epson] buf[27] 54 T [epson] buf[28] 2d - [epson] buf[29] 38 8 [epson] buf[30] 33 3 [epson] buf[31] 30 0 [epson] buf[32] 30 0 [epson] buf[33] 20 =20 [epson] buf[34] 20 =20 [epson] buf[35] 20 =20 [epson] buf[36] 20 =20 [epson] buf[37] 20 =20 [epson] buf[38] 20 =20 [epson] buf[39] 20 =20 [epson] buf[40] 20 =20 [epson] buf[41] 20 =20 [epson] TPU detected [epson] tpu tlx 0.00 tly 0.00 brx 48.259995 bry 231.13 [mm] [epson] sane_get_devices() [epson] sane_open(/dev/usb/scanner0) -= > > I will try to CC all relevant emails to you, but I cannot promise that > I will always remember. The list archives are online, so even if you I have subscribed to the sane developers list now, so I can now follow th= ere.=20 That will make it easier for you to not have to cc me. Thanks. Terry Boldt
[sane-devel] Visioneer Onetouch 4400 USB (Visioneer/Primax Primascan Colorado 2600u, Memorex 6142u)
Not too sure if how similar the Visioneer 4400 is to the 8000 series scan= ners,=20 but a backend (supposedly) exists for 8000 series, at least some of them.= I=20 have the source for the 8000 series backend and am expecting an 8920 in t= he=20 mail within the next month. At that time I was expecting that I would hav= e to=20 work on the source that I have to adapt it to the 8920. If the 4400 is=20 similar, then we can combine our efforts. I will be connecting via USB 2.= 0. If you think the source I have will be helpul, I can send it to you. Terry On Wednesday 03 December 2003 09:57, Keith Watson wrote: > Well, no-one else has stepped forward to say they are working on this > device, so it looks like if I want a backend for it then... I'm it! :o) > > I suspect it may share the same chipset as some other devices which peo= ple > are working on (see below) so I might not have as much to do as I'd tho= ught > (hope springs eternal...). > > I've been in touch with the Visioneer technical department and not had = any > luck so far but have started an e-mail conversation with one of their > technical bods (who seems quite interested) so one for the back burner.= ;o) > > On Sun, 30 Nov 2003 13:15:15 +0100 > > "Jaeger, Gerhard" wrote: > > I'm pretty shure, that the Visioneer 4400 does not contain a LM983x A= SIC. > > I checked some logs in spring this year, and there it turned out to b= e a > > GeneSysLogic based device, at least containing a GL 640 bridge. The > > ASIC is unknown to me, probably one of those E... ones - maybe Steven > > Ellis knows more... > > Thanks for the feedback and info Gerhard. Now all I've got to find out= is > what ASIC means. :o) (an Epson site I've just Googled says it means > "Application-Specific Integrated Circuit") > > The general opinion seems to be that the Visioneer Onetouch 4400 USB > (V1T4400U for short) is also retailed as; > - Visioneer Primascan Colorado 2600u > - Primax Primascan Colorado 2600u > - Memorex 6142u > > Anyone working on any of these? > > My output for /proc/bus/usb/devices and sane-find-scanner -v -v is > identical to that mentioned on the unsupported scanner web page. Which > also suggests that the USB Descriptor looks similar to the; > - Genius Colorpage Vivid III (USB) > and > - Pacific Image Electronics (PIE) Primefilm 1800u > > I know that Alexander Feldman is working on the Primefilm 1800u (hi Ale= x, > if you're reading this, I may be in touch real soon now :o) ) and someo= ne > said at the end of June this year that they were considering writing a > backend for the Genius Colorpage. So they might be lines worth pursuing= =2E > > There is some speculation about whether the device uses the E1, E3 or E= 5 > chipset. Can anyone point me to a place where I can read up on what th= e > significance of E1, E3 and E5 is? > > Are there any good places to read up on scanner hardware technology in > general so I've got at least some idea what's going on? > > Is the next step to get hold of something called a USB snooper? (I've g= ot > some links but recommendations are welcome). I'd appreciate a pointer t= o > some info on how this is used. > > Right, I've got a whole load of stuff off the SANE web site which I nee= d to > read and the SANE docs directory to dig around in. > > BRB! :o) > > Keith
[sane-devel] Latest iscan-1.52-1 rpm for RH8.0
I have compiled and installed the Epkowa iscan using gcc 3.2 with no prob= lem,=20 if you desire I can send you the compiled iscan. iscan works with sane - it is a sane frontend the same as xsane is a sane= =20 frontend - so iscan works with sane, but not xsane since they are essenti= ally=20 the same thing. Let me know if you desire the compiled iscan front end and/or the compile= d=20 epkowa sane backend. Terry On Saturday 20 December 2003 05:04, Gene Heskett wrote: > Greets; > > Does anyone know if this can be installed by forcing successfully? > > I have never been able to build the tarball due to errors in the gui > causeing the compiler (gcc-3.2) to bail out. However, at that point, > the stuff that works with sane has been built, and a make install > will put them in. > > But I've never seen the iscan front end and would like to compare it. > So the question is, can the compiled versions of sane and xsane be > made to work with iscan rpms, and if so, how to do it?
[sane-devel] Latest iscan-1.52-1 rpm for RH8.0
On Saturday 20 December 2003 23:02, you wrote: > On Saturday 20 December 2003 16:04, Terry Boldt wrote: > >I have compiled and installed the Epkowa iscan using gcc 3.2 with no > > problem, if you desire I can send you the compiled iscan. > > > >iscan works with sane - it is a sane frontend the same as xsane is a > > sane frontend - so iscan works with sane, but not xsane since they > > are essentially the same thing. > > > >Let me know if you desire the compiled iscan front end and/or the > > compiled epkowa sane backend. > > Humm, something must have changed in the way of dependencies here. it > built without incident, and installed, but in August, the last time I > tried to do 1.5.2 from tarball, right after it was released, the > compiler spit it out. This time it completed. > > However that means I should have a GT-6800 backend, but if I uncomment > epkowa in /usr/local/etc/sane.d/sane.dll, it isn't showing up in the I have the perfection 1660 Photo, but the epkowa backend should work for = the=20 GT-6800 if the epkowa web page lists it. You will have to add the line=20 epkowa to the file=20 /usr/local/etc/sane.d/dll.conf iscan and xsane should then find the scanner. Anything past that and you = are=20 getting out of my depth. Sorry. Hope this helps. Terry > xsane choice window yet, all I'm seeing is the plustek backend (its > an epson 1250u). Is there something else I need to do? Running > iscan from the cli gets me a "failed to send message to scanner" > advisory window, but no more. > > Thanks for any other suggestions you can make Terry.
[sane-devel] EPSON PERFECTION 1670 scanner
On Thursday 15 April 2004 11:40, Hubert Figuiere wrote: > On Sat, 2004-04-10 at 18:55, remi.malatray wrote: > > Is there any chance we can get it to work with negatives with sane ? > > xsane can scan negatives, but I personnally have been disappointed with > the results, even with a Nikon Coolscan III > Negative scanning seems to be one of the weakness of XSane. > > If I'm wrong, please correct me. > > Hub I find vuescan to be superior to xsane for scanning negatives with the Ep= son=20 1660 (I think the 1670 is essentially the same thing). The mechanics are = much=20 easier. Defining the scan areas is easy. Terry
