[sane-devel] scanning via network
Hi, I thought I had merged the fix for the wrong color problem into the latest backend but obviously not :-( Unfortunately I have not much time this week, so: Christoph, could you please re-send my modification to me to make sure I'm not mixing something? Thanks! I'll check what's going on. Karsten Hi, Ive just testet with the todays snapshot. The Lightlid will work, but there is the wrong-color-problem again. I've modified the microtek2.c with the change I got from Karsten 1,5 years ago, and now it works fine, with right colors. Bye, Christoph Am Freitag, 8. Oktober 2004 11:52 schrieb Henning Meier-Geinitz: Hi, On Thu, Oct 07, 2004 at 11:13:05PM +0200, Christoph Knauer wrote: For info: it seems to be a problem with the last build on my system ... using the package before (which I know as good) - ok, all is working fine Using the last builded package - nothing works, only error: Julia2002:~ # scanimage -L scanimage: relocation error: /usr/local/lib/sane/libsane-microtek2.so.1: undefined symbol: sanei_thread_init On the weekend perhaps I've more time to search the solution ... The reason is that you only use a new microtek2 backend. backend/Makefile.in also must be updated. As the latest microtek2 code is now in CVS I recommend using a CVS snapshot. Bye, Henning -- GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261 - alles rund um 11 Internet (ISDN, DSL, und vieles mehr) unter http://www.profiseller.de/shop/christoph-knauer -- GMX ProMail mit bestem Virenschutz http://www.gmx.net/de/go/mail +++ Empfehlung der Redaktion +++ Internet Professionell 10/04 +++
[sane-devel] microtek2 backend users: please test CVS version of backend
Hi, Check what the dwarfs are doing inside your computer :-) I've never seen such an error message. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM Does the same happen after make distclean; ./configure; make? The dwarfs went back to work after make distclean! ;-) Sorry, that should have been my idea. Testing with my scanner (Phantom330CX, Parport) was successful, so I personally have no objections against releasing this code. all the best, Karsten
[sane-devel] microtek2 backend users: please test CVS version of backend
Hi, Henning, thanks for updating the backend. I recently replaced my old microtek parallelport scannner with an Epson 2480 (what a difference!) and I think I will stop working on the microtek2 backend. But finally I would like to commit the changes I collected in the last time so they don't get lost. Henning, I'll send you the current files for the CVS, (I don't think I will need CVS access). They include the changes you made. I tried to test todays CVS version on my old machine with the old scanner and I experienced a compilation problem: make[1]: Wechsel in das Verzeichnis Verzeichnis /home/karsten/tmp/sane-backends/tools gcc -c -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes -pedantic -ansi -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 sane-find-scanner.c sane-find-scanner.c: In function `parse_file': sane-find-scanner.c:973: warning: implicit declaration of function `check_libusb_device' sane-find-scanner.c:974: sizeof applied to an incomplete type [...much more of this...] sane-find-scanner.c:1070: dereferencing pointer to incomplete type sane-find-scanner.c:1073: dereferencing pointer to incomplete type make[1]: *** [sane-find-scanner.o] Fehler 1 make[1]: Verlassen des Verzeichnisses Verzeichnis /home/karsten/tmp/sane-backends/tools make: *** [all-recursive] Fehler 1 Looks like a libusb issue? I don't have libusb installed on the old machine but I ran configure with --disable-libusb so I expected no problems. Compiling on the new machine (which has libusb) works, but the 2.6 Kernel doesn't have ppscsi support so I can't test the backend right now. Regards, Karsten On Sunday 03 October 2004 15:20, Henning Meier-Geinitz wrote: Hi again, Also a work-around to fix scanning on the microtek phantom c6 on big endian platforms has been committed to SANE CVS. Please everyone check if that doesn't break anything. I'm especially interested in reports from users of big endian systems. Here is the bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23274523 Karsten: I've applied both patches as you don't seem to have committed changes to the microtek2 backend for quite some time. If you want to become active again, details on getting CVS access are here: http://www.sane-project.org/cvs.html Bye, Henning
[sane-devel] microtek2 backend users: please test CVS version of backend
--Boundary-00=_/ewYBvyf4+rPVX6 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, On Tuesday 05 October 2004 12:50, Henning Meier-Geinitz wrote: Hi, On Mon, Oct 04, 2004 at 11:52:55PM +0200, Karsten Festag wrote: I recently replaced my old microtek parallelport scannner with an Epson 2480 (what a difference!) and I think I will stop working on the microtek2 backend. But finally I would like to commit the changes I collected in the last time so they don't get lost. Henning, I'll send you the current files for the CVS, (I don't think I will need CVS access). They include the changes you made. One issue: (line 4657): if ( !(md-revision=='2.70') (md-model_flags MD_RII_TWO_BYTES) ) That looks strange. I've removed the quotes around the 2.70 but you should double-check if that works. It's o.k., the quotes were a mistake. I've committed your backend to CVS now. Thanks! What about the microtek2.desc file? Shouldn't at least the version number (currently 0.95) be increased? Why not just use the build number? Is the Microtek Colorpage-EP a newly supported scanner? That one should also show up in our scanner lists. Is it support complete, good, basic or minimal? The Genius ColorPage-EP is a OEM version of the Microtek Scanmaker V300. It has an additional firmware peculiarity I had to handle so that the support is good, like the V300. I attach the updated microtek2.desc file. I called the recent version 0.96, I used the build number only for internal referencing. Could you please change MICROTEK2_MINOR in microtek2.h accordingly? I tried to test todays CVS version on my old machine with the old scanner and I experienced a compilation problem: That was my fault. It's fixed now. I tested again and I get some other errors: gcc -o sane-find-scanner sane-find-scanner.o check-usb-chip.o ../backend/.libs/sane_strstatus.o ../sanei/libsanei.a ../lib/liblib.a -lnsl -lm /usr/lib/libjpeg.so /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. .../sanei/libsanei.a(sanei_scsi.o): In function `lx_mk_devicename': :2491: undefined reference to `rsm_open_device' :2491: undefined reference to `rsm_open_device' .../sanei/libsanei.a(sanei_scsi.o): In function `get_max_buffer_size': :781: undefined reference to `rsm_open_device' .../sanei/libsanei.a(sanei_scsi.o): In function `sanei_scsi_open_extended': :1245: undefined reference to `rsm_open_device' :1245: undefined reference to `rsm_open_device' /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Could not find abbrev number 186. .../sanei/libsanei.a(sanei_config.o): In function `sanei_config_read': sanei_config.o(.text+0x36): undefined reference to `__ctype_b_loc' sanei_config.o(.text+0x51): undefined reference to `__ctype_b_loc' .../sanei/libsanei.a(sanei_config.o): In function `sanei_config_skip_whitespace': sanei_config.o(.text+0xaa): undefined reference to `__ctype_b_loc' .../sanei/libsanei.a(sanei_config.o): In function `sanei_config_get_string': sanei_config.o(.text+0xf3): undefined reference to `__ctype_b_loc' /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. .../sanei/libsanei.a(sanei_usb.o): In function `sanei_usb_open': :720: undefined reference to `rsm_open_device' .../sanei/libsanei.a(sanei_usb.o): In function `sanei_usb_init': :276: undefined reference to `rsm_open_device' /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. /usr/i486-suse-linux/bin/ld: Dwarf Error: Invalid or unhandled FORM value: 14. .../sanei/libsanei.a(sanei_init_debug.o): In function `sanei_init_debug': :81: undefined reference to `__ctype_toupper_loc' collect2: ld returned 1 exit status make[1]: *** [sane-find-scanner] Fehler 1 make[1]: Verlassen des Verzeichnisses Verzeichnis /home/karsten/tmp/sane-backends/tools make: *** [all-recursive] Fehler 1 By the way: Could you change all references (e.g. on your website) to mostang.com to www.sane-project.org? If I didn't forget something, this is done now. Bye, Karsten --Boundary-00=_/ewYBvyf4+rPVX6 Content-Type: text/plain; charset=iso-8859-1; name=microtek2.desc Content
[sane-devel] microtek2 --shadow/highlight
Hi, it might well be that the firmware of the V310 doesn't understand the commands for shadow and highlight operations. The firmwares of the different microtek scanners have different peculiarities and that's why this isn't very easy to handle in the code (microtek has a unique driver for each scanner model :-(). For I don't have much time to spent on the microtek backend I don't really want to invest much work in your problem, sorry. But you are welcome to find your own solution and to commit it via the mailing list. You would have to disable the shadow/highlight options in the function 'init_options' depending on the scanner model. Regards, Karsten On Wednesday 08 September 2004 23:48, Gene Stemple wrote: ScanMaker V310 (parport) works fine both gray color; but if any of the /shadow/midtone/highlight/ options are changed from their defaults (mode=Gray) then scan fails. Both scanimage and xscanimage fail the same way... sane-backends 1.0.13; microtek2 v0.95; Debian distribution. kernel 2.4.18; using modules ppscsi + onscsi. scanimage -d microtek2:/dev/sg1 --mode Gray --resolution 150 \ --no-backtracking=yes --shadow 80 From debug output it appears that process starts normally, i.e. the same as successful scans, and proceeds thru calculate_sane_params and scsi_wait_for_image before infinite Busy loop times out. --- sane_start -- scsi_read_image_status = Busy (forever) until retry count expires. Are shadow..highlight not supported in ScanMaker V310? Is this a known issue in microtek2 backend? If not, what debug dumps would be most helpful for a bug report? ...Gene...
[sane-devel] Epson Perfetion 2480 scanner
Hi, I don't want to promise anything but if you send me the info I'll have a look at it and if I have some leisure time maybe I'll try to code it. Thanks Karsten On Thursday 02 September 2004 23:01, Oliver Schwartz wrote: Hi, New patch attached, diff'ed with -u this time. Scanning works fine, however it seems the scanner locks after the first scan :/ I've applied the patch to CVS. Let me know if there are any problems left. If anyone of you is interested in implementing quality calibration for the 2480 please let me know - I have some infos on how it may be done, but I don't have the scanner so I can't test it. /Oliver
[sane-devel] Epson Perfetion 2480 scanner
--Boundary-00=_dLfNB2omT/ELD2T Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, Negative scanning works fine, only in 2400dpi resolution I see the interlacing effects (see the picture I attached to my first mail, it was scanned with in transparency Mode). I tested the starting of xsane again and at first it worked without problems, but after powercycling the scanner xsane started not before the fourth attempt. I attach the logfiles, recorded with 'export SANE_DEBUG_SNAPSCAN=128'. By the way, is there a way to control the lamp of the scanner? I'd like to switch off the lamp when I'm not using the scanner to increase it's lifetime. I noticed that one time the lamp was off but I can't remember the circumstances. Karsten On Tuesday 31 August 2004 15:17, Julien BLACHE wrote: Julien BLACHE j...@jblache.org wrote: Replying to myself: I need to take a closer look at that tomorrow, I'd like to be able to scan several times in a row without power cycling the scanner :) I guess it may have to do with the scanner id string changing once the firmware is loaded, need to check that. (just wondering why is this string used to indentify the scanner, as it's a USB scanner... I know it's the way SCSI scanners are identified) Everything works absolutely fine with XSane. I tried to scan some negatives and it worked really great; however the resulting image seems to be interlaced. Is it the case ? JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169 --Boundary-00=_dLfNB2omT/ELD2T Content-Type: application/x-tbz; name=xsanelog.tar.bz2 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=xsanelog.tar.bz2 QlpoOTFBWSZTWfPoiDQAHnZ/vfgQAgBYff/6/6fayv/v//AASEIAEECAAQBABAjgC98AAAPkAAAo AAAIcNDJpoaZGhpkZBkZGhkBiaMmgDJkYhjhoZNNDTI0NMjIMjI0MgMTRk0AZMjEMcNDJpoa ZGhpkZBkZGhkBiaMmgDJkYhjhoZNNDTI0NMjIMjI0MgMTRk0AZMjEMIpRE02ppoaNAAGgAGgAaDQ AABkCpIgEAQBCMQTCaaPSCeowJtR6mTTZJ6g0fwP7v2Fdhp9pV6qTHJA7/PytYtCtHn6PPHAzopH QoPK7+6j+U97ld5R0/kp79YaxRHWrUk9ZnCY044sTwV+6jIpSmLI234XT3d6z99JuOZZddtLln9W 6k/g/IfNyaTG7Ro3NrcHLWeJRltYzMWzUGKY1JGklVJw2fe8TyNj5UR7/2rqvbVJK8qlVK3Hhhvt a1rW7icTJ8sxj7N/E3n0FNOy7SJgaJG+b1oqlY2gHdK6SY/ZI9UW9mReKmST4Ion2VnKjCNOh6li YFUmEfDFpy993WvytPVv0x1iN0XxO1nrFtVS8/kXfxjKMWMZMIuvf0WfzrBlSzzpbHxzkmCYsSMv SqXU9TLjomik86j7eFpg03peYdvC66J9T9paP04HAyMA5n5ZYmL4j8mLgxg0Ml3BT2TzUqk61Fvf FKiqljzYZsZraScdJs7JJ4SfqKyycMRV3dKPgxbPHJ01WzUsYyJzO25wMXJZ6dGhVZzFdrzllNHm cD3m3Pc27btw3NlLXaylKuidZpJDczOjR6Wbo2WmS0ss0bSzQvIwqSRjhHEYmDk6HTJm2n82aSG3 CdxkYMHYv9D5na8Xt8NIPo/w56W9bDD4R8TvkWSTjISpBSjvLlLRujkPZByfoMOl8LsFsOVscsl1 mKwPIwk9hSe9KhYpJRUzp67fP5sMCmGvXfhN6mFIfqUbIxEGHJJOjLYFaM5SIQiFmJRhhkGFYBhR hhQZGFdhapKFIoFIrZxQAqjtzBSGccON+f7NO34rGWsk61ELlV0p86rbUuk+5JLTOMojwqJEVSM5 x4y0c2GHnGEYrRVSUqKqJUvW5gVjUspZRWEw3FlsNdySaJeVNxKE5ykPpn5Dj4si5e66111MJUk4 nPkk13QSSr1LpPyjoo+ETodJ9hY1YlJPZwmpLWlYzNil+rIl4oxVMZ2uvSfjJJ0gklKRJUrtRZCx QSxRLUSoGlJ6qrRY3U7Oyq3ceBzO6ZssC85yd7dlOUMlvhpYpOy+xzP8anbA8UM46qjWYyVI5WcM JLY42J1dNJqqYRi5lWjnqzbbYn7nztc44U2FVH1TXXBjSsrPrwwzlr1g7ScNDn6TKGvdpyaOEo91 dmL0KmVaTY5fiOFGtTtwj7uS+22kwouaR2RdhdeNE8cEzxw35Rrkq+WpbW/or1TVJpidt4xRmoom aSt2gTbPKNqymhZbtMJg069Z0mqVhzOcxPImXp1m6auBGRlgWdJjNxZ1aTFDcQ5VvljSMovOMqXC Uj8yI6fvPatH41PkUUoyWWntfKYsDGSWsLMbF1Lknzy6+dpiHaTmS7o7iYrpPjbNlw3z/p/ZTlq+ ej7RSP0/Qn/j+hgMPkqqW0PnzM2D5IJoXcCGtBYGzTGXsGDPCAWuB3jves4WYUJX/pwSRDySHwlC B/uZyPZFyUgUWKk9595gVKFHxpdhKtYxSpPrShYXSzJKkYF5LpJT1vgxXWkhnKWZp9NVVVVV SlKYEsmYcTsw/e6SVpKrI1SHzFIn7qmRLWSTZhP0GaGTq4LFQSRst+KSRdEOUJCZH8Widhm8FOaG kWgzm+f0pJ0E+ufpEonuSiapykIalxPz4Oi0kh9eL3Ud47yWSJT9ROmbacEzyg+BwQkSio8oywQf io930yNJHEotHGkkKkKNZLk/5k7bOsjOxUQotT0yKiqUVaQmyzenKZt80O+QyaSTRgiUu1LncTr8 nODUYkwucyp1hsvJZS8VJJjIm6SbSYHsYHt721HD0I0e5TDR+CyyXwsuU8IsYG6Ft67G6TQPBnjJ DBj8VSpRSpRFEk3Dw9sk1T1u47l4Ou9TZs1m05OBadXUsmpd+PbccVBUHiuklntM2smradaTJ6FJ Z1VClMlR8rBympicIyVJDUssNpPRZMp8UHMxXes7Z0MJMVRJ6ZwOfgVHqGZR4JOfg8JUZETSXl0l 5E3qSyVJIXeZ4SSGrc7WrhSbNXTMyjNSTUqSRRnoh6nbdxkf8Jy0kcikR1dSaPVB4pDem50UYrNJ wnHB2egybkYb+yyaztszOKpYZRQqIunBHCVFCV5YmpSNJNzgDOOk3xOTJE+OrKDmoNVPQbnn3yPk KPqKPOeMNzznjdMDhhMMUnhVJOpmaksjDKnwurQx+Mpu3ps7p+1bTsZPMyZxJHBhBi1TgutPNNrG KxhlUsqKplaSVEVBagWSSQtJUgs7I7SIS7E+aLYl1QoyuWVIjhIli6kC8hSUSdZrLyODxfTlIntc TKBubF3nHGndJ2QswSXMZwPXTGDtZbIVZP66O6QwVIznlNJMLHvML2mVPVJZO9ZxsaNPg747dnvu sRZJtJdjJiJCYyOkmwLTtmBZFqkpSlUSlEqiWYqlSVpI5pJSJR9S0xMeyTxkR9wcmrZvZzmfI7jd PdQ0NJMpNAZGMO1UiLlSrMHdhVM355ZumLtOkkP7GEhDvLiiITulkKZycU9DBMip5Mb8zBNUkQom kkKCcGT5Yo8tDKaG5pF1SWYOsmq/SVwkqbSzFLFVEosxmeK0kuMETFPE2KYrSzE6B/kRNU0wcF19 GRZDpL6LCmMnBhBhJdmaSZtygo0kqZzdJwfGT0fgDGbOjfG+TlFKedJqTGTGlUqhRQopVKopSlKk lIUkj7yvwMHyuHRzMpLKLJDxsejeq08FI3hUH5gSTw1LSJUmXH+v3fxBpmDBfSywg34I3BSfMtFo 6Kle0fxYJ5bCeFEskilsP8XckU4UJDz6Ig0A --Boundary-00=_dLfNB2omT/ELD2T--
[sane-devel] Epson Perfetion 2480 scanner
Hi, of course you are right, the case in snapscan-scsi.c was in fact in my modified files but somehow it didn't make into the diff I sent. I don't have locks after the first scan, but if I start Xsane for the first time I get 2 or 3 I/O errors and have to restart Xsane. After a certain time (I guess when the lamp is warmed up?) it works like expected. Regards and thanks for your work! Karsten On Monday 30 August 2004 16:04, Julien BLACHE wrote: Karsten Festag karsten.fes...@gmx.de wrote: Hi, I also have an Epson2480 and after your suggestions I made the modifications in the attached diff file. Scanning works fine, I can scan the whole glass Your patch is missing an important bit; in snapscan-scsi.c::download_firmware(), you need to add a case for the PERFECTION2480, otherwise the firmware won't load properly (enters an infinite loop). New patch attached, diff'ed with -u this time. Scanning works fine, however it seems the scanner locks after the first scan :/ JB.
[sane-devel] Microtek Scanmaker X6 and Lightlid35
Hi Christoph,
I'm having a bad conscience because you asked me this half a year ago...
sorry.
please try the following modification:
in microtek2.c around line 5330 you'll find the following piece of code:
if ( ms-lightlid35 )
{
md-status.flamp = ~MD_FLAMP_ON;
md-status.tlamp |= MD_TLAMP_ON;
}
please comment out the second line so it looks like
if ( ms-lightlid35 )
{
md-status.flamp = ~MD_FLAMP_ON;
/*md-status.tlamp |= MD_TLAMP_ON; */
}
and recompile sane-backends. In theory this second line would switch on only
the transparency lamp but maybe it also controls the flatbed lamp.
Please let me know about the results!
Karsten
On Monday 26 April 2004 20:46, Christoph Knauer wrote:
Hi,
I'm using the above hardware to scan my negatives. When I click on using
lightlid the scanner-lamp should be switched of, but before scanning the
scanner makes an init and switches the lamp allways on.
the scanner is not directly on the xsane-machine, but over ethernet.
Isn't it possible to use this funktion with this scanner, or is it a bug?
workstation:
suse 9.0
kde 3.2.2
xsane 0.92 (self-build)
sane 1.0.14 (suse)
server:
suse 8.2
sane 1.0.14
Thanks,
Christoph
[sane-devel] Re: microtek slimscan C6 USB (black scans!)
In Xsane try disabling the advanced option backend calibration. If this option checkbox isn't visible it has to be enabled in the microtek2.conf. file (see manpage). Regards Karsten Rebuilt the 2.6.3 with microtek loaded in the kernel. SANE finds the scanner, the scanner appears to do its thing, but the images scanned are all black. I did a dump of the file scanimage scanned and it was mainly zeros. xsane produces similar results. Any ideas of what I should do next? Thanks. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- +++ NEU bei GMX und erstmalig in Deutschland: TÜV-geprüfter Virenschutz +++ 100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz
[sane-devel] Re: Microtek ScanMaker 8700
Hi John, [I'm forwarding this mail to the SANE-devel mailing list, maybe we get some comments from there] well, hope never dies... But to be honest, I personally don't have the possibility to do this. Someone who owns this device and has the motivation to do some programming and testing may do this, of course. There is a chance that IEE1394 via SBP can use the microtek2 backend (The SBP-2 driver will install a virtual SCSI controller, and from there on the device can be accesses by any application that supports SCSI devices. To get a IEEE-1394 scanner working, you load three modules: ieee1394, ohci1394 (or whatever driver your system requires for your controller) and sbp2, quotation of Karl-Heinz Kremer) Is there someone out there who might test if the backend responds to a Microtek IEE1394 Scanner?? Best regards Karsten On Monday 16 February 2004 17:33, you wrote: Hi Is there any hope of a backend for my Microtek ScanMaker 8700, which is connected via IEEE1394? I'm not a programmer, just a magazine editor trying to keep working! Thanks John
[sane-devel] Re: [Fwd: Re: TWAIN-SANE for microtek slimscan c6 usb]
Hi, I must admit that I have not planned to convert the microtek2 backend for using threads. And I doubt if this is the solution because under linux the microtek2 - USB- scanners only work with a special kernel module (microtek.o). This module makes the USB-scanner appear as a SCSI device to the backend (the backend only knows SCSI). As far as I know there is no such a module in OS X. A possible solution might be to include the translating code into the microtek2 backend and use libusb. I don't have the time to do this now and I have no USB scanner for testing available but you are welcome to try to do this work. The kernel module for Linux was written by John Fremlin v...@penguinpowered.com and Oliver Neukum oliver.neu...@lrz.uni-muenchen.de Maybe they can help you more than I can. Sorry for the bad news. Best regards Karsten On Saturday 14 February 2004 03:03, you wrote: Hello, I wrote to Mattias Ellert concerning the microtek2 backend (for slimscan C6 USB) and Mac OS X and he suggested I contact to you to find out if there is a time line for converting the backends to use threads instead of forks for microtek2 Also I was wondering if this backend should work from a Mac booted into Yellowdog linux 3.0.1. The backend is included as part of the Yellowdog distribution. I recently tried this on my eMac using GIMP but Xsane indicated it couldn't find any devices. Thanks in Advance, - John From: Mattias Ellert mattias.ell...@tsl.uu.se Date: 2004/02/05 Thu AM 02:53:33 EST To: jrlann...@cox.net CC: karsten.fes...@gmx.de Subject: Re: TWAIN-SANE for microtek slimscan c6 usb jrlann...@cox.net wrote: Mr. Ellert, I am wondering if the Microtek Slimscan C6 USB is supported under Panther (10.3.2) using the TWAIN-SANE Interface? The SANE backend does exist for this scanner. However, I have noticed some caveats for USB scanners (and USB Scanners with SCSI circuitry in particular). Almost all the backends that exist can be complied on MacOS X (except for the parallel port ones). Some of them does not work however. The most common reason why it won't work is that the combination of USB and fork does not work on MacOS X because the forked child process does not inherit the access rights to the USB pipes opened by the parent process. If you have installed the sane libraries and the scanimage command from the command line does not work this is probably the reason why it doesn't work, since looking at the code for the backend you are using (microtek2) shows that it does indeed use a fork call on MacOS X. This can be fixed by using a thread instead of a forked child process. The process of converting the backends to use threads instead of forks is an ongoing effort. The backend you are using has not yet been converted. If you are interested in the time plan for this to happen you should contact the maintainer of the backend at karsten.fes...@gmx.de. The UMAX backend was recently successfully converted in this way. Mattias -- mattias.ell...@tsl.uu.se tel: +46 18 471 32 58 http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13
[sane-devel] Re: Micortek SANE USB Config
Hi Race, i'm afraid you will not be able to use the USB interface with this scanner and SANE under OSX. The microtek2 backend was written for SCSI scanners and the way some of the Microtek USB scanners work under Linux is a special kernel module called 'microtek.o' which makes the USB scanner appear as a SCSI device. I don't know if there is a similar possibility in OSX and I don't have the possibilitiy to include libusb support to the microtek2 backend because I don't have an USB scanner available and I have not enough leisure time left for such kind of project. But maybe someone else would like to do this? Best regards Karsten On Tuesday 27 January 2004 23:58, you wrote: I have installed all the appropriate software to utilize your SANE Microtek backend with my Scanmaker V6USL but I am having a hell of a time configuring it to work at all. I want to use the USB interface. I am on on OSX X.3.2 and have installed TWAIN-SANE-Interface.pkg v0.4 sane-backends.pkg 1.0.13-cvs 2004-01-25 libusb.pkg 0.1.8 beta 2004-01-25 When Running sane-find-scanner I receive: Race:~ race$ sane-find-scanner # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. found USB scanner (vendor=0x05da, product=0x00a3) at libusb:002:002-05da-00a3-ff-03 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Scanners connected to the parallel port or other proprietary ports can't be # detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. Race:~ race$ The Config. File microtek2.config is set to: # See sane-microtek2(5) for a description of the options option dump 1 option strip-height 14.0 option no-backtrack-option on option lightlid-35 on option toggle-lamp on option lineart-autoadjust on option backend-calibration on #option colorbalance-adjust on scsi * * Scanner Can you please advise. Race
[sane-devel] problems with microtek X6 scanner in TMA mode
Hi Joachim, I hope I found the bug. It is in the function 'attach'. There are several calls like status = scsi_read_attributes(md-info[MD_SOURCE_ADF], md-name, MD_SOURCE_ADF); They all must have the first parameter md-info[0] so that they look like: status = scsi_read_attributes(md-info[0], md-name, MD_SOURCE_ADF); Are you able to check if this is the solution to the problem by recompiling SANE with this modification? (The best thing is to use the source rpm provided by SUSE and modify them.) Karsten On Sunday 21 December 2003 20:00, you wrote: Am Samstag, 20. Dezember 2003 17:23 schrieben Sie: Hi Joachim, thanks for the logfiles, it looks like the backend uses the wrong values, I'll have to check this. Do you remember which SANE version the TMA used to work with before? Hi Karsten, I'm not 100% shure, but I think that it worked up to at least SuSE 7.3. I'n the beginning (around 1998/99) there were some problems with the microtek firmware (at least V 1.6 was required) but then everything worked o.k. Yours
[sane-devel] Re: Question about Microtek scanner 3830
Hi, On Thu, Aug 07, 2003 at 07:07:01PM +0200, Karsten Festag wrote: The 3830 type is not yet supported as far as I know. The newer microtek scanners are mostly very different from the ones supported by the microtek2 backend. Hopefully some owner of such a scanner will try to write a SANE backend in the future. Maybe it's similar to the 3800, which is reported to use a SQ 08 chip? Anyway, I'll add that scanner to our lists. I guess I can also add it to the kernel scanner driver as it doesn't look like a SCSI-over-USB scanner? Maybe, but I wouldn't guarantee for nothing: At least there are scanners which both are named 'Slimscan C3' but have different model-IDs and different calibration procedures :-( But I think you are right, these are probably not SCSI-over-USB scanners. Though I don't know about the ones with additional Firewire interface. Isn't the firewire protocol somehow related to SCSI? Karsten
[sane-devel] Re: Question about Microtek scanner 3830
Hi, sorry for the late answer, I was lucky having a bit of holidays :-) The 3830 type is not yet supported as far as I know. The newer microtek scanners are mostly very different from the ones supported by the microtek2 backend. Hopefully some owner of such a scanner will try to write a SANE backend in the future. best regards, Karsten On Wednesday 02 July 2003 05:37, Guo, Min wrote: Dear sir: Glad to write to you! I encountered a problem when set up my USB Microtek scanner 3830 in linux 2.5.73. I found there are CONFIG_USB_MICROTEK in the kernel source ,so I built in and run the following command, but when I run scanimage ,it still failed. So could you please take a look at the following information and tell me whether it is caused by the incorrect driver? Whether sane supports the scanner now? Thank you very much! The product info is [root@mguoserver RedHat]# cat /proc/bus/usb/devices T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1 P: Vendor=05da ProdID=30d4 Rev= 1.00 S: Product=USB Scanner C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=3ms ./sane-find-scanner -v # Note that sane-find-scanner will find any scanner that is connected # to a SCSI bus and some scanners that are connected to the Universal # Serial Bus (USB) depending on your OS. It will even find scanners # that are not supported at all by SANE. It won't find a scanner that # is connected to a parallel or proprietary port. sane-find-scanner: searching for SCSI scanners: sane-find-scanner: checking /dev/scanner... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg0... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg1... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg2... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg3... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg4... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg5... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg6... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg7... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg8... failed to open (Invalid argument) sane-find-scanner: checking /dev/sg9... failed to open (Invalid argument) sane-find-scanner: checking /dev/sga... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgb... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgc... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgd... failed to open (Invalid argument) sane-find-scanner: checking /dev/sge... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgf... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgg... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgh... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgi... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgj... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgk... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgl... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgm... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgn... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgo... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgp... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgq... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgr... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgs... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgt... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgu... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgv... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgw... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgx... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgy... failed to open (Invalid argument) sane-find-scanner: checking /dev/sgz... failed to open (Invalid
[sane-devel] Re: Microtek SlimScan C6 on Mac OS X
Hi Dave, unfortunately I have no experiences with OS X and SANE. But I will cc this mail to the SANE mailing list, hopefully someone can tell you some more details. But I'm not sure if you can get your scanner to work out of the box because there needs to be a piece of software that translates the USB signals to SCSI commands that are used in the scanner software (backend). In Linux there is a kernel module (microtek.c); I don't know if there is something similar under OS X. ( SANE experts, please comment on this...) regards, Karsten On Saturday 05 July 2003 03:24, you wrote: Mr. Festag - I am not a developer, so I don't understand most of what I read on the SANE web site, but I am trying to use a Microtek SlimScan C6 (USB) on a Macintosh running OS X 10.2.6. I can scan in Classic mode, but I would prefer to scan in OS X. Are you aware of any user-friendly front end that will do this? If there's an application I can run through the UNIX terminal, I suppose I could do that as well. Thank you, - Dave Hudson -- Dave and Wendy Hudson dwhud...@headsail.net www.dwhudson.net
[sane-devel] negative-scan
Hi, that sounds like a problem with my backend :-( I'll have to check the code for the lamp control, but I'm afraid I can't do this before August. Regarding the negativ-preview: I think this might be a frontend feature for xsane and the other frontends (..requesting comments..) Karsten On Saturday 28 June 2003 17:57, Christoph Knauer wrote: Hi, i've a litle problem with scanning negatives on an microtek scanmaker x6 / phantom 636 with lightlid35 when i set the option using lightlit or toggle lamp. with toggle the lamp the scannerlam goes out, but when i push the button scan, it goes on again, and setting use lightlid35 seems to do nothing. btw. why there is no negativ-format to set for preview? greetings, christoph ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Microtek SlimScan C3, output always a black image
Hi Jose, ok, I think I found and solved the problem. I put the changed code on my homepage www.karstenfestag.gmxhome.de, it's the latest version. You will have to remove the SUSE packages and compile SANE from the sources if you want to use that. But I think you can try to exchange only the library file so you don't have to uninstall the SUSE package and compile SANE by yourself: for this you have to find the file 'libsane-microtek2.so.1.0.9'; I think it is in /usr/lib/sane or /usr/local/lib/sane. This file is linked to libsane-microtek2.so.1 and libsane-microtek2.so Please remove the links (all these things are to be done as root) and replace the libsane-microtek2.so.1.0.9 file with the one I attached to this mail (don't forget to unpack (bunzip) the attached file :-) ) The re-create the links: ln libsane-microtek2.so.1.0.9 libsane-microtek2.so.1 ln libsane-microtek2.so.1.0.9 libsane-microtek2.so ( of course to be typed in the directory where the libsane-microtek2.so.1.0.9 file is) Have luck! Karsten [ this is a copied mail for the list without attachment ]
[sane-devel] Microtek SlimScan C6 on Mac OS X 10.1.5 (sane-microtek2)
Hi, though I'm the maintainer of the microtek2 backend I cannot help you much with the SCSI-over-USB stuff. But Oliver Neukum oliver.neu...@lrz.uni-muenchen.de has done the linux 'microtek' kernel module and I think he can give you some useful hints if you ask him. Regards, Karsten On Friday 06 June 2003 18:53, Henning Meier-Geinitz wrote: Hi, On Fri, Jun 06, 2003 at 09:24:59AM -0700, David Alan Hjelle wrote: I've been trying to get my Microtek SlimScan C6 working on my Macintosh running Mac OS X 10.1.5. [...] So, I did some research. Apparently, the microtek2 backend only supports USB kernel extensions and not libusb? What would it take to modify the code so that it would work? All these scanners are SCSI. The SCSI protocoll is only transported over the USB in case of USB devices. So they use a kernel SCSI-over-USB driver (called microtek). So you either need to port this Linux driver to MacOS X or do the SCSI-over-USB logic in the backend itsself. Maybe the maintainer can tell you more about how complicated this may be. Userland SCSI-over-USB is used at least in the ma1509 and the avison backends. Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Announcing Scanner-HOWTO at tldp.org
[] Hello, I've parsed it a bit, and I must say that you're painting the picture darker than it really is for parallel port scanners. Parallel port scanners listed in SANE do work. No need to frighten people. I'm a bit skeptic about favouring ECP mode. It may be wise for printers, but I think it is useless for scanners, unless you use some patch that bring DMA reads. From a quick grep in SANE docs, EPP or ECP/EPP seems to be the recommended setting. Just a remark: The Microtek2 parport scanners (they use the onscsi parport chip) do not work in ECP or ECP/EPP mode (data corruption occurs). EPP is here the only option to get good results. Regards, Karsten
[sane-devel] Microtek SlimScan C3, output always a black image
Hi Jose, please look into your BIOS and make sure the parport mode is set to EPP, not ECP! I heard several times that this is the cause for stretched or shifted image lines. By the way: switching off the backend calibration has a negative side effect: you will probably see fine vertical stripes on your scanned images. Normally the backend calibration gets rid of it, but it looks like we have to find the bug in the calibration code so that it works with your scanner. Please tell me if we shall do some work in this direction - I'll need some testing work on your side to achieve this. Could you please tell me what error message appears if you use the '-y20' option to generate a logfile? Karsten On Thursday 29 May 2003 04:13, Jose Sanchez wrote: Hi Karsten, thanks for the help, and sorry for the late answer. until now I didn't find strange things in the logfile. But what error message gives the -y20 option (though this shouldn't be connected to the dark image failure)? Please try what happens when you (in xsane or xscanimage) turn off the advanced option 'calibration by backend'. Do you see that the scanning illumination is on during the scan? well I turn off the advance option you tell me and finally I am able to see the image, although sometimes the image is acquire incorrectly, I mean, it is cut and streched in some parts. I rescan the image several times until the image is acquire correclty. Do you have any idea how should I correct that error. Thanks Jose ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Internationalization and localization status
Hi Henning, in your list you mentioned microtek2 as not supporting i18n. I think that isn't true, in microtek2.h the translateable strings are marked with SANE_I18N. Bye Karsten -- +++ GMX - Mail, Messaging more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
[sane-devel] Microtek Slimscan C3 USB
Hi Josh, Henning is guessing right so please follow his advice. The C3's were buil= t in=20 different variations so I haven' yet a report if your particular model wo= rks=20 out of the box. But I think the chances are good because other C3's work=20 well. Please do your setup in these steps: -make the microtek kernel module recognize your scanner like Henning said= =2E -run sane-find-scanner; your scanner has to be reported, otherwise there = is=20 something wrong with your USB- or SCSI generic configuration -try your favourite scan program (most people prefer xsane) -in any case please make a logfile as described in the manpage sane-micro= tek2=20 and send it to me. If you have problems I can see some details in the=20 logfile. Bye Karsten On Friday 04 April 2003 10:37, Henning Meier-Geinitz wrote: Hi, On Fri, Apr 04, 2003 at 12:02:08AM -0500, Josh Gladden wrote: I'm new to the list and have recently installed Linux on my system. = I have a Slimscan C3 USB scanner. I see that SANE supports the C3 PARPORT, but nothing about USB. Is there a way to redirect to the US= B port? The microtek2 maintainer may have more details for that issue. Anyway I'm guessing a bit: Have a look at the manpage (sane-microtek2). The USB scanners are supported by the microtec kernel module. So if that scanner uses a SCSI-over-USB protocol it may work if you get it detected by the microtek driver. You'll need to add the vendor product ids to drivers/usb/microtek.c. At least your scanner doesn't seem to be mentioned there. Please show us the output of cat /proc/bus/usb/devices when your scanner is plugged in. You may need to run mount -t usbdevfs /proc/bus/usb /proc/bus/usb if that file isn't there. Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] wrong colors
Nice to hear! The if-statement was a workaround for a buggy firmware of a= =20 scanner of your type, so it seems that this was a unique failure of that=20 single device (or your scanner is unique not having this firmware bug ;-) Anyway I think I should add an config option in the next release for this= =20 case. Happy scanning! Karsten Saturday 01 March 2003 00:09, Christoph Knauer wrote: Hi Karsten, is this file only the source for libsane-microtek2? Could i compile th= e backend on another mashine, and copy only the microtek2-files on my scanning system? I tried it in this way, after changing as you wrote. It seems to work :-) Bye, Christoph Am Die, 2003-02-25 um 22.48 schrieb Karsten Festag: Hi Christoph, I checked your logfiles and I have an idea where the problem might be= =2E If my theory is correct, all pictures with an even number of pixels in w= idth are correct and all with an odd width have wrong colors. In the statu= s line of xsane you see the dimensions if the scan also in pixels, you could use this to check my theory. To (hopefully) solve this problem we will have to make a little modification to the source code and then to recompile SANE. If you li= ke to try this: here is the change you could make: in the file 'microtek2.c' in the 'sane-backends/backend' directory of= the sources please find the function 'check_inquiry'. There are the follo= wing lines: case 0x91: *model_string =3D ScanMaker X6 / Phantom 636; /* The X6 indicates a data format of segregated data in TMA mode */ /* but actually transfers as chunky data */ md-model_flags |=3D MD_DATA_FORMAT_WRONG; if ( md-revision =3D=3D 1.00 ) md-model_flags |=3D MD_OFFSET_2; break; Please comment out the if-statement so that it looks like: case 0x91: *model_string =3D ScanMaker X6 / Phantom 636; /* The X6 indicates a data format of segregated data in TMA mode */ /* but actually transfers as chunky data */ md-model_flags |=3D MD_DATA_FORMAT_WRONG; /* if ( md-revision =3D=3D 1.00 ) md-model_flags |=3D MD_OFFSET_2; */ break; If you have some more questions ore comments - please ask, I hope I c= an answer sooner than this time. Could be a problem with wrong group /dev/sg0 (the scanner) belongs = to? I've a look, and /dev/sg0 was root.cdrecording (i think, k3bsetup changed it), but my cd-devices are sr0 and sr1, and they're working= =2E That should be no problem. Otherwise you wouldn't be able to scan as normal user, only as root. Bye Karsten
[sane-devel] MicroTek Scanmaker 4800
just an idea: The SM3800 (which is also unsupported) is based on the SCAN 08 chip and h= as (vendor =3D0x05da, product =3D 0x30ce) A little info is on: http://www.sq.com.tw/products/spec/scan08Spec.PDF Karsten On Thursday 27 February 2003 11:31, Henning Meier-Geinitz wrote: Hi, Does anyone knows what chip is used by the MicroTek Scanmaker 4800? Looks like it's not supported yet. Someone asked on usenet for that scanner and provided the following output of /proc/bus/usb/devices: T: Bus=3D01 Lev=3D01 Prnt=3D01 Port=3D00 Cnt=3D01 Dev#=3D 2 Spd=3D12 = MxCh=3D 0 D: Ver=3D 1.10 Cls=3Dff(vend.) Sub=3Dff Prot=3Dff MxPS=3D 8 #Cfgs=3D = 1 P: Vendor=3D05da ProdID=3D30cf Rev=3D 1.00 S: Product=3DScanMaker 4800 C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D100mA I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3Dff(vend.) Sub=3Dff Prot=3Dff Driv= er=3D(none) E: Ad=3D81(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms E: Ad=3D02(O) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms E: Ad=3D83(I) Atr=3D03(Int.) MxPS=3D 1 Ivl=3D3ms Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] wrong colors
Hi Christoph, I checked your logfiles and I have an idea where the problem might be. If= my=20 theory is correct, all pictures with an even number of pixels in width ar= e=20 correct and all with an odd width have wrong colors. In the status line o= f=20 xsane you see the dimensions if the scan also in pixels, you could use th= is=20 to check my theory.=20 To (hopefully) solve this problem we will have to make a little modificat= ion=20 to the source code and then to recompile SANE. If you like to try this: h= ere=20 is the change you could make: in the file 'microtek2.c' in the 'sane-backends/backend' directory of the= =20 sources please find the function 'check_inquiry'. There are the following= =20 lines: case 0x91: *model_string =3D ScanMaker X6 / Phantom 636; /* The X6 indicates a data format of segregated data in TMA mod= e */ /* but actually transfers as chunky data */ md-model_flags |=3D MD_DATA_FORMAT_WRONG; if ( md-revision =3D=3D 1.00 ) md-model_flags |=3D MD_OFFSET_2; break; Please comment out the if-statement so that it looks like: case 0x91: *model_string =3D ScanMaker X6 / Phantom 636; /* The X6 indicates a data format of segregated data in TMA mod= e */ /* but actually transfers as chunky data */ md-model_flags |=3D MD_DATA_FORMAT_WRONG; /* if ( md-revision =3D=3D 1.00 ) md-model_flags |=3D MD_OFFSET_2; */ break; If you have some more questions ore comments - please ask, I hope I can a= nswer=20 sooner than this time. Could be a problem with wrong group /dev/sg0 (the scanner) belongs to? I've a look, and /dev/sg0 was root.cdrecording (i think, k3bsetup changed it), but my cd-devices are sr0 and sr1, and they're working. That should be no problem. Otherwise you wouldn't be able to scan as norm= al=20 user, only as root. Bye=20 Karsten
[sane-devel] wrong colors
Hi Christoph, Is it a SCSI or USB (or parport?) scannner, if SCSI: what adapter card ? What SANE version do you use? could you please send me a logfile (look into the sane-microtek2 manpage = for=20 instructions how to do that)? I'm not sure, it might be a data transfer problem but as well a bug in th= e=20 software. There are no wrong placed pixels in the image, only the colors = are=20 swappped? Bye Karsten On Friday 07 February 2003 12:14, Christoph Knauer wrote: Hi, I've changed my scanner (from Microtek sm IIx to sm x6). Mostly it work= s fine, but sometimes scanning gives wrong colors. Sometimes the scan itself, sometimes the preview is with wrong colors. I tried it out, but i didn't find any conditions when it happens or not. Any idea? (sorry about my horrible english) So long, Christoph ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] New snapshots available: sane 1.0.10-pre2
Hi, good to hear the stripes are gone. As for the two other issues: can you=20 reproduce this in any way or could you describe under which circumstances= the=20 segfault and the wrong slider moving occur? Regards, Karsten On Sunday 19 January 2003 15:41, Vaclav Cermak wrote: On Sat, 18 Jan 2003, Henning Meier-Geinitz wrote: Hi, new version works good with microtek X12USL, both two problems, which= I had vith previous versions, (vertical stripes and strange purple area i= n scanned images) are perfectly solved. But I saw one segfault with xscanimage and one times it tried to move scanning ruler? in scanner outside working area. Regards Disnel Hi everyone, There are new snapshots of ssane-backends and sane-frontends avilable at http://www.mostang.com/sane/ . The most important changes since pre1 in sane-backends are the fix (?= ) of the Linux on Sparc64 SCSI issue and some compatibility issues for Mac OS X. Further more there have been fixes for the gt68xx, leo, microtek2, and mustek_pp backends. sane-frontends contains a fix concerning installation. make install failed, if $sanedatadir wasn't already there. Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] microtek2 backend
On Thursday 16 January 2003 23:11, Henning Meier-Geinitz wrote: Hi, On Thu, Jan 16, 2003 at 06:18:22PM +0100, Karsten Festag wrote: I made a bugfix for the X12USL (solved problems 600dpi), one for lin= eart mode with a 6400XL and one for Scanmaker 5 (crashes at sendgamma). It= 's in version 20030115 on my homepage. Henning, could you please add thi= s to CVS? Ok, it's in CVS now. Any reason why you don't get CVS write acces? I didn't ask for ;-)=20 (also 'cause I have no experiences with CVS until now and don't want to b= reak=20 someting. But I hope I can manage to learn that.) Nice weekend! Karsten Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] microtek2 backend
Hi, I made a bugfix for the X12USL (solved problems 600dpi), one for lineart= mode=20 with a 6400XL and one for Scanmaker 5 (crashes at sendgamma). It's in ver= sion=20 20030115 on my homepage. Henning, could you please add this to CVS? Karsten
[sane-devel] microtek2 backend
Hi, I tested the translations of the microtek2 backend with the snapshot from= =20 09.01.03 and xsane 0.90. It works correctly. Thanks Henning for correctin= g my=20 mistakes (I somehow didn't realize that the translations are now in one=20 file.) As for the option names,=20 #define M_NAME_QUALITY_SCANquality_scan is corrected to #define M_NAME_QUALITY_SCANquality-scan and #define M_NAME_FAST_SCAN fast_scan to #define M_NAME_FAST_SCAN fast-scan I added another bugfix and have the new files on my homepage. I also woul= d=20 like the new microtek2.conf there to be put to CVS. It has some more opti= ons=20 enabled by default that seem to work reliable. Bye Karsten On Thursday 09 January 2003 02:00, Henning Meier-Geinitz wrote: Hi, On Thu, Jan 09, 2003 at 01:01:54AM +0100, Karsten Festag wrote: I have made some modifications to the microtek2 backend: [Todo List] - microtek2.c (scsi_read_control_bits): Make sure to pass a size_= t* to sanei_scsi_cmd(). -done. Ok. -added german language support (microtek2.de.po) The translations are now done in one file per language (sane-backends.de.po in this case). Also the charset is UTF-8 now. I have merged the files in CVS. Please check if that works correctly. You'll need XSane 0.90 and remove the old microtek2.mo files from your system. I guess you can't access the CVS server, so have a look at http://www.meier-geinitz.de/sane/snapshots/ . -impoved support for Scanmaker X12USL -alpha support for Scanmaker 9800XL -some bugfixes Ok, microtek2.h and microtek2.c (microtek2_20030109) are applied to CVS. By the way, check microtek2.h, SANE option names are not allowed to conatin a _. The option name must consist of lower-case ASCII letters (a--z), digits (0-- 9), or the dash character (-) only. The first character must be a lower-case ASCII character (i.e., not a digit or a dash). The files are downloadable via http://karstenfestag.gmxhome.de/software/list.html microtek2.desc: error 403: Forbidden! Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Re: modules/microtek
Hi Moby, the Scanmaker 5700 is not yet supported by SANE. But there may be a chanc= e to=20 get it to work via the firewire interface. I have no experiences with thi= s,=20 but I think there is a kernel module which makes a firewire device appear= ing=20 as a generic SCSI device (/dev/sg). Then you should be able to detect= the=20 scanner with sane-find-scanner and if we are lucky the scanner uses comma= nds=20 similar to the microtek2 scanners.=20 Perhaps somebody in the SANE mailing list can give some hints concerning = the=20 firewire setup? If sane-find-scanner detects your scanner please follow the instructions = in=20 the manpage and send me a logfile. Regards, Karsten On Thursday 02 January 2003 17:44, you wrote: I am running Red Hat 8.0 with a 2.4.19-opp18 kernel. I have a Microtek Scanmaker 5700. I can't detect it from the USB or from the PCMCIA slot where I have a Belkin F5U512 firewire card. I have installed the sane backend package. Could you tell me how to get Sane to detect the scanner or suggest some modules to load. Regards, moby __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
[sane-devel] Microtek LightLid 35
Though I have no feedback concerning the X6 with Lightlid35 it should wor= k=20 (but please don't shoot me if not. In this case I will try to make it wor= k).=20 Please read the manpage for information about the appropreate=20 backend-options. Karsten On Wednesday 04 December 2002 15:30, Christoph Knauer wrote: Hello, is the LightLid35 Option with a Microtek Scanmaker X6 usable with sane = / xsane? Christoph ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Sane and microtek2 hangs on large scans
Hi Gerald, Abel forwarded your logfiles to me, thanks. I think you should try the=20 no-backtracking option: Please remove the # from the line=20 # option no-backtrack-option on in your microtek2.conf file. This file usually resides in=20 /usr/local/etc/sane.d or /etc/sane.d depending on your distribution. You = have=20 to be root to edit this file. now please try scanimage with the option --no-backtracking=3Dyes, for exa= mple:=20 scanimage --no-backtracking=3Dyes --resolution 300 -l 10 -t 10 -x 200 -y = 210=20 scan.pnm If you like to use xscanimage or xsane then you find the appropriate opti= on in=20 the special options menu. Have luck!=20 Karsten On Wednesday 25 September 2002 10:38, Edenyard wrote: On Mon, 23 Sep 2002 19:47:53 +0200, abel deuring wrote: Can you run another test with SANE_DEBUG_SANEI_SCSI=3D255 and SANE_DEBUG_MICROTEK2=3D255 ? The debug output perhaps gives us a bett= er clue about the problem. As Henning already wrote, you don't need to set these variables in /etc/profile, but you can set them on the command line. Very many thanks for both the prompt response and also the useful clues here! I carried out your instructions, both for a 75 DPI scan (which worked) and a 150 DPI scan (which failed). The 75 DPI scan produced a log file 348346 bytes long, whereas the 150 DPI scan only produced one of 74816 bytes. I've looked through both of these files, but to be honest, I have no real idea what I'm looking for. I'm sure I'd be very unpopular if I tried to send these files to the list, so what do you suggest that I do with them? Thanks in advance! Gerald. ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Re: Questions about Microtek scanners (specifically USB 2.0 and Firew ire scanners)
Hello Eric, unfortunately I have no information about work in progress for these Microtek scanners. Microtek didn't release much information about the internals of their scanners, so I can't say if the new models are more or less similar to the SCSI-based devices which are operated by the microtek and microtek2 backends. Maybe the times have chaged and / or Microtek releases some detailed technical data if somebody wants to use some more of their scanners. Some time ago I was in contact with Michael Papet mpa...@microtek.com from Microtek, but unfortunately he wasn't able to provide helpful technical data. And you may have a look at http://sourceforge.net/projects/sm3600. This is a backend for newer USB scanners from microtek. I would suppose that these are technically more similar to the Firewire ones, perhaps you get some more information there. I cc'd this mail to the SANE-mailing list, maybe a reader of the list has some comments on this? Regards, Karsten Am Freitag, 26. Juli 2002 19:38 schrieben Sie: Hello: I was wondering if you could tell me if any work is taking place surrounding enabling any of the Firewire (IEEE-1394) scanners from Microtek to function through any of the SANE backends. I saw no mention of these scanners under either the microtek or the microtek2 backends. We are interested in potentially utilizing Microtek scanners but are constrained to operate under a Linux based system and having access is obviously a concern. I appreciate any info you can give me on this. Thanks, Eric Jackson Xerox Corporation
[sane-devel] Microtek Scanmaker 4800
Hi, I suppose this one belongs to the same family as the Scanmaker 3600. There is a project for these scanners at http://sourceforge.net/projects/sm3600. As I have no further information about the status of this project you should have a look there. wish you success! Karsten On Monday, 10. June 2002 23:49, you wrote: It's a USB scanner, 2400x1200 optical res., 8.5x11.7 scan area. CCD. Microtek part number 1108-03-520058 Product info at http://www.microtekusa.com/sm4800.html Brent On Mon, Jun 10, 2002 at 08:44:21PM +0200, Karsten Festag wrote: Hi, please tell us some details about the scanner: Interface, resolution, CCD or CIS, A4 or A3. Microtek sells equivalent scanners under different names in different countries so it's sometimes difficult to tell if it's supported or not. Karsten On Monday, 10. June 2002 18:26, you wrote: I just recently acquired a Microtek Scanmaker 4800. Has anyone gotten one of these to work under sane? I did some preliminary searching, but turned nothing up. Any help would be appreciated. Brent
[sane-devel] Microtek ScanMaker 636 at Advance Hostadapter
Hi Nicolas, in the moment I have two suspicions: 1) I included a command which sets the timer for the automatic switch-off for the lamp. Maybe the firmware of your scanner doesn't support this command. To test this issue it is neccesary either to use an old sane version (1.0.4 or older) or (better) to compile from slightly modified sources. 2) The failing command is the first that doesn't only read data from the scanner but sends data to the scanner. If that's the problem then it is probably scsi-related. A test for this might be to push the toggle lamp button in the advanced options in xsane. But you have to enable this button in the configuration file microtec2.conf (probably located in /usr/local/etc/sane.d). There has to be the line option toggle-lamp on If pressing the button doesn't freeze the scanner then probably the above suspicion is right. If it also freezes - well then it might be a scsi issue but I would do also the first test. If you like to compile a modified source that doesn't send the Timer command you have to remove the following lines from the function sane_start in microtek2.c: md-status.aloff |= 128; md-status.timeremain = 10; Please tell me about your results! Best wishes Karsten On Sunday, 9. June 2002 09:56, you wrote: Hi! Sorry, it took me a while to answer been busy the last week. can you tell me what version of SANE you used with the old setup that was working and what SANE version you are using now? Furthermore it would be good to see a logfile. Please look into the manpage sane-microtek2 for instructions how to create this. Maybe the firmware of your scanner doesn't understand a command that is used in newer backend versions (there are a lot of nasty issues with the firmware of different scanners :-( ) Now I'm using sane version 1.0.7. The working version was 1.0.1. The logfile scan.log is attached to this email. The logfile sout.pnm was empty however. BTW, the command scanimage -l0 -t0 -x100 -y20 2scan.log sout.pnm never returns and cannot be aborted using Ctrl-C... Thanks for your help already! I have a SCSI scanner Microtek ScanMaker 636 on an Advance 2911U hostadapter (using module atp870u). This scanner has been working with an older version and an onboard SCSI controllen without any problems. Now (Kernel 2.4.18, SuSE Linux 8.0, xsane-0.83) I cannot get it working. (A ZIP drive on this hostadapter is working properly.) The scanner is terminated correctly. Yast2 identifies the scanner at /dev/sg15 correctly. But when trying to scan with xsane (or the Yast2 Testscan function) the scanner software hangs. The green led at the scanner turns off und even the ZIP drive doesn't work any more The hostadapter is dead I get the following output an the error console: May 25 18:43:55 lianli kernel: Vendor: IOMEGAModel: ZIP 100 Rev: E.08 May 25 18:43:55 lianli kernel: Type: Direct-Access ANSI SCSI revision: 02 May 25 18:43:55 lianli kernel: Vendor: Model: scanner V636A4 Rev: 1.00 May 25 18:43:55 lianli kernel: Type: Scanner ANSI SCSI revision: 02 May 25 18:43:55 lianli kernel: Attached scsi removable disk sda at scsi1, channel 0, id 5, lun 0 May 25 18:43:56 lianli kernel: SCSI device sda: 196608 512-byte hdwr sectors (101 MB) May 25 18:43:56 lianli kernel: sda: Write Protect is off May 25 18:45:14 lianli kernel: scsi : aborting command due to timeout : pid 3756, scsi1, channel 0, id 6, lun 0 0x2a 00 81 00 00 00 00 00 09 00 May 25 18:45:14 lianli kernel: r3b=20 May 25 18:45:14 lianli kernel: May 25 18:46:14 lianli kernel: que cdb= 2a 0 81 0 0 0 0 0 9 0 last_lenu= 9 scsi : aborting command due to timeout : pid 3756, scsi1, channel 0, id 6, lun 0 0x2a 00 81 00 00 00 00 00 09 00 May 25 18:46:14 lianli kernel: r3b=20 May 25 18:46:14 lianli kernel: May 25 18:46:14 lianli kernel: que cdb= 2a 0 81 0 0 0 0 0 9 0 last_lenu= 9 SCSI host 1 abort (pid 3756) timed out - resetting May 25 18:46:14 lianli kernel: SCSI bus is being reset for host 1 channel 0. May 25 18:46:14 lianli kernel: SCSI host 1 channel 0 reset (pid 3756) timed out - trying harder May 25 18:46:14 lianli kernel: SCSI bus is being reset for host 1 channel 0. Concerning my IDE CDROM drives I have the following settings (but even without ide-scsi the problem shows up): /etc/modules.conf: alias scsi_hostadapter atp870u alias scsi_hostadapter2 ide-scsi ... alias char-major-21 sg ... options ide-cd ignore='hdc hdd' pre-install sg modprobe ide-scsi Any ideas? Thanks for your help already!!!
[sane-devel] Microtek Scanmaker 4800
Hi, please tell us some details about the scanner: Interface, resolution, CCD or CIS, A4 or A3. Microtek sells equivalent scanners under different names in different countries so it's sometimes difficult to tell if it's supported or not. Karsten On Monday, 10. June 2002 18:26, you wrote: I just recently acquired a Microtek Scanmaker 4800. Has anyone gotten one of these to work under sane? I did some preliminary searching, but turned nothing up. Any help would be appreciated. Brent
[sane-devel] Scanning Lineart/Halftone with MICROTEK Scanmak
Joachim Backes wrote: Hi, Karsten, On 16-May-2002 Karsten Festag wrote: Hi Joachim, the function that finds the scanning area and calculates the dashed rectangle is included only in xsane if I'm not wrong. That's why in xscanimage you have to draw the scanning area by hand. I don't know the way xsane calculates the scanning area but it might be an issue of the contrast between the sheet of paper and the background of your scanner lid. Maybe a black paper as background does the trick? The cover of the scanner IS black! Hmm, in this case the black paper probably won't help ;-) Anyway, I think Oliver Rauch should make a statement if it could be a xsane problem. I think it isn't backend-related because the preview-image seems to be correct. There were some reports of garbled xsane lineart scans earlier, perhaps Oliver Rauch knows something about this? I tested this with my scanner: If you scan into a file or for a fax or for photocopy then the pictures are o.k. as well as the preview. Only the viewer makes problems. Is this the same at you? Almost. Additionally, when scanning into the viewer, not only the viewer picture itself is blurred or shaked, but the file's contents too when saving the picture to some file. Same as above - looks like an xsane issue only for the xsane viewer mode. Oliver, do you agree? Karsten Regards Joachim Backes -- Joachim Backes bac...@rhrk.uni-kl.de | Univ. of Kaiserslautern Computer Center, High Performance Computing | Phone: +49-631-205-2438 D-67653 Kaiserslautern, PO Box 3049, Germany | Fax: +49-631-205-3056 -+ WWW: http://hlrwm.rhrk.uni-kl.de/home/staff/backes.html Regards, Karsten Joachim Backes wrote: On 06-May-2002 Karsten Festag wrote: Hi Joachim, I will investigate this, but as I have no time in the moment it will be not before next week. Does the same problems occur with xscanimage? Hi, Karsten, using xscanimage: 1. When using pre-view with xscanimage, then the dashed preview rectangle totally misses after prescan. I have to draw it myself. 2. The shake-effect together with xscanimage using lineart or halftone is heavily reduced (there is a little effect: letters have a small black-pixeled wreath which lets letters to be blurred). No problem when scanning in gray or colored mode. Regards Joachim Backes -- Joachim Backes bac...@rhrk.uni-kl.de | Univ. of Kaiserslautern Computer Center, High Performance Computing | Phone: +49-631-205-2438 D-67653 Kaiserslautern, PO Box 3049, Germany | Fax: +49-631-205-3056 -+ WWW: http://hlrwm.rhrk.uni-kl.de/home/staff/backes.html regards, Karsten Joachim Backes schrieb: Hi, having problems with Microtek ScanMaker 96000 xl. Environment: Linux RedHat 7.2 Kernel 2.4.18 xsane-0.86 sane-front/backend-1.0.7 1. The preview: When previewing a A4 Page with normal text on my ScanMaker 9600xl (A3 scanner), then after previewing, the dashed frame painted around the read page is not correct: horizontally, the frame correctly stops at the right margin of the A$ page, but the lower margin does not stop at the bottom of the A4 page, but at the bottom of the Scanners A3 pane. That means, the preview frame contains the rectangle u,v,w,x and not u,v,y,z u v +-+---+ | | | | | | A3 Pane | | | | | | | | | | A4 sheet | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +-+ | |yz
[sane-devel] microtek2: maintainer has new email address
Hi all, my email address will change to karsten.fes...@gmx.de The homepage http://home.t-online.de/home/karsten.festag will be available for some time but I will move it to http://karstenfestag.gmxhome.de in the next weeks/months For SANE-1.0.8: Should I rewrite the files which contain these data or could somebody with CVS access do this directly? Regards Karsten
[sane-devel] Scanning Lineart/Halftone with MICROTEK Scanmaker
Hi Joachim, the function that finds the scanning area and calculates the dashed rectangle is included only in xsane if I'm not wrong. That's why in xscanimage you have to draw the scanning area by hand. I don't know the way xsane calculates the scanning area but it might be an issue of the contrast between the sheet of paper and the background of your scanner lid. Maybe a black paper as background does the trick? There were some reports of garbled xsane lineart scans earlier, perhaps Oliver Rauch knows something about this? I tested this with my scanner: If you scan into a file or for a fax or for photocopy then the pictures are o.k. as well as the preview. Only the viewer makes problems. Is this the same at you? Regards, Karsten Joachim Backes wrote: On 06-May-2002 Karsten Festag wrote: Hi Joachim, I will investigate this, but as I have no time in the moment it will be not before next week. Does the same problems occur with xscanimage? Hi, Karsten, using xscanimage: 1. When using pre-view with xscanimage, then the dashed preview rectangle totally misses after prescan. I have to draw it myself. 2. The shake-effect together with xscanimage using lineart or halftone is heavily reduced (there is a little effect: letters have a small black-pixeled wreath which lets letters to be blurred). No problem when scanning in gray or colored mode. Regards Joachim Backes -- Joachim Backes bac...@rhrk.uni-kl.de | Univ. of Kaiserslautern Computer Center, High Performance Computing | Phone: +49-631-205-2438 D-67653 Kaiserslautern, PO Box 3049, Germany | Fax: +49-631-205-3056 -+ WWW: http://hlrwm.rhrk.uni-kl.de/home/staff/backes.html regards, Karsten Joachim Backes schrieb: Hi, having problems with Microtek ScanMaker 96000 xl. Environment: Linux RedHat 7.2 Kernel 2.4.18 xsane-0.86 sane-front/backend-1.0.7 1. The preview: When previewing a A4 Page with normal text on my ScanMaker 9600xl (A3 scanner), then after previewing, the dashed frame painted around the read page is not correct: horizontally, the frame correctly stops at the right margin of the A$ page, but the lower margin does not stop at the bottom of the A4 page, but at the bottom of the Scanners A3 pane. That means, the preview frame contains the rectangle u,v,w,x and not u,v,y,z u v +-+---+ | | | | | | A3 Pane | | | | | | | | | | A4 sheet | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +-+ | |yz | | . | | . | | . | | . | | . | | . | +-+---+ w x 2. Having problems when scanning in LineArt or Halftone mode: in the scan, a lot of horizontal pixel lines are shifted against each other, so you have a shaked not readable picture. Scanning in Grayscale/Color mode is OK. Regards Joachim Backes -- Joachim Backes bac...@rhrk.uni-kl.de | Univ. of Kaiserslautern Computer Center, High Performance Computing | Phone: +49-631-205-2438 D-67653 Kaiserslautern, PO Box 3049, Germany | Fax: +49-631-205-3056 -+-- -- WWW: http://hlrwm.rhrk.uni-kl.de/home/staff/backes.html ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Problems with Microtek Scanmaker-III, Solaris 8, sgen driver, xsane
Hi Craig, The 'scsi * * scanner' line is for autodetecting every scanner on the scsi subsystem. It is not neccessary if you specify the device file and I don't know if the autodetection works on Solaris. Hope that helps, otherwise please follow Henning's suggestions. Karsten Craig Dewick schrieb: On Mon, 8 Apr 2002, Karsten Festag wrote: Hi Craig, do you have an entry like /dev/scsi/scanner/c6t6d0 in the microtek.conf file? Yes. I modified microtek.conf and dll.conf in /usr/local/etc/sane.d. The first file looks like this: # Uncomment following line to disable real calibration routines... #norealcal # Uncomment following line to disable clever precalibration routines... #noprecal # Using norealcal will revert backend to pre-0.11.0 calibration code. scsi * * Scanner /dev/scsi/scanner/c6t6d0 The line starting with 'scsi' was uncommented by default. I modified the second line so it lists the correct device handle in /dev to use. In dll.conf, I commented out all backend instances except 'microtek' as suggested in one of the postings to the list which I found in the archives. Note that if I run xscanimage using the exact same command-line device identifier (microtek:/dev/scsi/scanner/c6t6d0) the very same message is returned. Regards, Craig. -- Craig Dewick. Send email to cdew...@sunshack.org Point your web client at www.sunshack.org or www.sunshack.net to access my archive of Sun technical information and links to other places. For info about Sun Ripened Kernels, go to www.sunrk.com.au or www.sun-surplus.com
[sane-devel] SCSI Microtek x6EL probs
Hi Michael, Michael Honeyfield schrieb: hello all I am having huge probs getting this scanner to work with sane. it works under windows but thats not were i want it to work. I have followed the insructions in the man pages and docs on the web. I had a brief look at the previous threads for this list and didnt find much that helped me. below is what i hav done so far $ cat /proc/scsi/scsi Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor:Model: scanner 636EL Rev: 1.5 Type: Scanner ANSI SCSI revision: 02 ( i noticed that under vendor there is a blank, i read that in this case you need to add the device, /dev/sg0, to the backend config file is that right?) Yes, that's right, at least until SANE-1.0.6. $ ./sane-find-scanner sane-find-scanner: found scanner scanner 636EL 1.50 at device /dev/sg0 (looks good to me) Yes, to me also :-) $ ./scanimage -L No scanners identified..blah blah (not so good) exactly. Please try to specify the device: scanimage -d microtek2:/dev/sg0 out.pnm should theoretically scan to the file out.pnm. Important: what version of SANE you are using? (I don't know what Mandrake uses) I can make more detailed investigations if you send me a logfile (see manpage sane-microtek2 for instructions how to do that). Regards, Karsten I have also created a group called scanner and made the permissions for the device. lsmod is happy with my scsi modules. I have also added to the ld.so.conf file the path for the sane libs. now have i missed anything or am i just plan stupid. I cannt figure it out, i am hoping that there is some one out there that might have a clue. Also these are standard mandrake 8.1 rpms from their dc. Many thanks Michael -- If linux doesnt have the solution, then you have the wrong problem. ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] C undefined operations in sane-backends-1.0.7-beta1
Hi, I'll split bit = ++bit % 8; in the two lines bit = ++bit; bit %= 8; in microtek2.c Henning, could you do this for me in CVS? Thanks Karsten Tim Waugh schrieb: On Wed, Jan 23, 2002 at 09:43:35PM +0100, Henning Meier-Geinitz wrote: This is with gcc-3.x? I don't get them with gcc 2.95.4. Yes. They are for things like: bit = ++bit % 8; which are indeed undefined. Because it's not clear if bit should be incremented and then the right side assigned to it or vice versa? Or what's the excat problem? Yes, that's right. There is only one sequence point in 'bit = ++bit % 8;', at the end, and so the operations can happen in any order. There are two assignments to 'bit': the '=' operation and the '++' operation. Tim. */
[sane-devel] Re: New test version of microtek2 backend
Argh! Looks like I was very unconcentrated while writing my previous mail :-( Some major 'bugfixes': 1) the URL of my homepage is http://home.t-online.de/home/karsten.festag and therefore the readme is http://home.t-online.de/home/karsten.festag/software/readme 2) for thesting the X12USL you should not only disable the 'no-backtracking' option but also enable the option 'backend-calibration'. A scanimage command thus may look like: scanimage --no-backtracking=no --backend-calibration=yes -l0 -t0 -x100 -y20 2scan.log sout.pnm Regards, Karsten Karsten Festag wrote: Hi folks I made a whole lot of changes to the microtek2 backend (see http://me/home/karsten.festag/software/readme). Especially ADF users should test if the frontend gets now SANE_STATUS_NO_DOCS rather than an I/O error in case of an empty ADF. And X12 users should give that version a try. Please use the following microtek2.conf file: option dump 2 option strip-height 14 # option lightlid-35 on option lineart-autoadjust on option toggle-lamp on option no-backtrack-option on option backend-calibration on # option colorbalance-adjust on scsi * * Scanner # or # /dev/sgx # where sgx is your scanner device In you frontend please --disable-- the option 'no-backtracking' ; if you use scanimage: scanimage --no-backtracking=no ... does the trick. Regards Karsten Festag
[sane-devel] New test version of microtek2 backend
Hi folks I made a whole lot of changes to the microtek2 backend (see http://me/home/karsten.festag/software/readme). Especially ADF users should test if the frontend gets now SANE_STATUS_NO_DOCS rather than an I/O error in case of an empty ADF. And X12 users should give that version a try. Please use the following microtek2.conf file: option dump 2 option strip-height 14 # option lightlid-35 on option lineart-autoadjust on option toggle-lamp on option no-backtrack-option on option backend-calibration on # option colorbalance-adjust on scsi * * Scanner # or # /dev/sgx # where sgx is your scanner device In you frontend please --disable-- the option 'no-backtracking' ; if you use scanimage: scanimage --no-backtracking=no ... does the trick. Regards Karsten Festag
[sane-devel] microtek2 backend bug?
I will have a look at the code, though I haven't got an ADF. But I hope I will find someone who tests this when I'm ready. Regards, Karsten Tim Waugh wrote: In https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=56917 a bug in the microtek2 backend is detailed. It is alleged that it doesn't return SANE_STATUS_NO_DOCS when it should, but instead just returns an I/O error. Does anyone know what would be involved in fixing that? Thanks, Tim. */ Part 1.2Type: application/pgp-signature
[sane-devel] is buying parallel port to usb converter for ibm ideascan worth while?
Hi again parv wrote: in message 1006759554.3c01ee82d5...@webmail.t-online.de, wrote Karsten Festag thusly... Hi, hi there, parv schrieb: is buying parallel port to usb converter for ibm ideascan worth while? ... I'm not sure if the trich with the USB-converter will work. There is a special kernel module for microtek USB scanners but I suppose it has at least to be modified for working with an converter. kernel module for scanner, eh? is this module for linux or (free|net|open)bsd? i am using freebsd 4.4-stable at the moment. The module (called microtek) is for Linux. I don't know if it's possible to use it for freebsd. The module was made by Oliver Neukum oliver.neu...@lrz.uni-muenchen.de and John Fremlin v...@penguinpowered.com, maybe they can help you. Regards, Karsten - parv --
[sane-devel] is buying parallel port to usb converter for ibm ideascan worth while?
Hi, parv schrieb: is buying parallel port to usb converter for ibm ideascan worth while? computer is dell i5000e, w/ a usb ports, 25-pin parallel port, and serial port. from this 1999 thread, his scanner may be a scanmaker 330cs... http://www.mostang.com/mail-archive/sane-devel/1999-12/0 210.html ...has anybody tried to use this scanner? A scanmaker 330CS --should-- work with the microtek2 backend. However, I don't know if sombody has it running. I'm not sure if the trich with the USB-converter will work. There is a special kernel module for microtek USB scanners but I suppose it has at least to be modified for working with an converter. Regards Karsten Festag -- ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Re: Microtek SANE bug and fix for ADF
Hi all, I included the patch and hope it will solve the problem with crashing the X-server. I experienced this too one or two times when canceling a scanimage via ctrl-c but didn't follow it. I also have some experimental code for the X12USL in there, don't expect too much but if possible, please test the new version (microtek2_20011120.tar.gz on my homepage http://home.t-online.de/home/karsten.festag) and send me a logfile of the session as described in the manpage. As for the SCSI-trace: I managed to get the original windows driver running under linux with the emulator program 'wine'. It is possible to log the commands with the normal version of wine; I patched it to see also the data, not only the commands. Regards, Karsten Michael Thomson wrote: Hi guys Thanks for your patch - I have also seen these symptoms on a Microtek X12 USL with *no* document feeder - both the X-server crash (eek) and the coloured stripes down the page. Karsten Festag maintains the microtek2 backend, so hopefully your patch will be implemented shortly, and Karsten can see if there's a more general solution to cover the no-feeder situation. On the coloured lines question, Karsten requested a SCSI trace of a scan, to capture the actual data being transferred. I don't have access to a SCSI probe / analyser, so I can't help him debug the problem. Are you able to get your hands on an analyser? Alternatively, do you know a way to 'tap into' the /dev/sg driver? I tried looking at /proc/scsi/sg/debug but that didn't get me much info. Perhaps I need to recompile / set some environment variable, but I'm not sure where to look for info on this. Hopefully we'll all have perfect scans one day! Thanks again Mike Thomson -- \\|||// (@ @) Michael Thomson mthom...@iee.org *---oOO-(_)-OOo-* * * * Minds are like parachutes; They only work when open. * * * * .oooO Oooo. (Sir James Dewar)* *--( )---( )* \ ( ) / \_) (_/ ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Microtek SANE bug and fix for ADF
Hi Maurice,
thank you very much for your bug report, I agree to Henning, this is the best
kind
of bug report I can imagine.
I must admit that I never checked this killing part of the code, it is legacy
from
the time before I started working on the microtek2 backend.
The problem with the stripes is known for the X12USL, I currently try to fix
this
and I'm looking for some log of the data and commands that the windows driver
sends to the scanner. There are two users trying to get the Microtek Scanwizard
running with wine but I haven't any results yet. Hoping for the best :-). If you
have the possibility and the will to do this, please tell me, I will give you
some
more information how I did this with my scanner (Phantom330CX).
Best regards,
Karsten
Maurice Hilarius wrote:
If you have a Microtek or similar scanner with an automatic document feeder
(ADF) then there is a bug in the SANE code for using this feeder device.
We have been working with a Microtek ScanMaker X12USL, and ran into a
problem with the code for the ADF handling.
After a multi-page scan, it would crash you right out of X!
As this is not a desirable feature, we have been looking into the reasons
for this.
Fortunately we have found it, and I include a patch at the end of this
message.
The problem is in the 'cancel_scan()' function in microtek2.c.
When using the automatic document feeder, after it has scanned all the
pages, and there are no more pages to scan, this function is called after
an I/O error ir produced by the lack of a page to feed.
It is then supposed to stop the scanner from trying to scan any more pages.
A comment in the code says:
/* READ IMAGE with a transferlength of 0 aborts a scan */.
This is fine, but then 'close(ms-fd[1])' may be called
ms-fd[1] equal to -1 (which does not have any nasty consequences,)
BUT! a bit below that you effectively have 'kill(-1, SIGTERM);'.
Try 'man 2 kill' to see what this does. :-)
After this patch:
--- sane-backends-1.0.5/backend/microtek2.c~Sun May 27 04:20:20 2001
+++ sane-backends-1.0.5/backend/microtek2.c Mon Nov 19 19:11:05 2001
@@ -1403,8 +1403,15 @@
status = SANE_STATUS_CANCELLED;
close(ms-fd[1]);
-kill(ms-pid, SIGTERM);
-waitpid(ms-pid, NULL, 0);
+/* if we are aborting a scan because, for example, we run out
+ of material on a feeder, then pid may be already -1 and
+ kill(-1, SIGTERM), i.e. killing all our processes, is not
+ likely what we really want - --mj, 2001/Nov/19 */
+if (ms-pid 1)
+ {
+ kill(ms-pid, SIGTERM);
+ waitpid(ms-pid, NULL, 0);
+ }
return status;
}
With this revision of the code runs of batch scans using ADF settings
terminate properly and without any other visible side-effects.
I have no idea if other backends have similar problems; 'kill()' call
is used in a number of places.
Meanwhile, an other trivial trouble we see is that 'scanimage' without any
explicitly specified format is still using an extension of '.pnm' even if
'--format tiff' is given.
For further excitement the manpage claims that out%d.tif is _always_ the
default; at least in the presence of '--batch'.
Perhaps this is related to the features of a given scanner, but with the
ScanMaker X12USL, (while using the microtek2 backend), we are getting
stripes on both sides of scanned images.
'--backend-calibration' options, which some docs suggest may help with
that, is listed by 'scanimage --help' as [inactive].
Indeed, it seems to not make any difference.
Does anyone have any suggestions or ideas for what to do with that problem?
Maurice Hilarius and Michal Jaegermann
maur...@harddata.com
mic...@harddata.com
With our best regards,
Maurice W. Hilarius Telephone: 01-780-456-9771
Hard Data Ltd. FAX: 01-780-456-9772
11060 - 166 Avenuemailto:maur...@harddata.com
Edmonton, AB, Canada http://www.harddata.com/
T5X 1Y3
___
Sane-devel mailing list
sane-de...@www.mostang.com
http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Re: Weird vertical stripes on Microtek ScanMakerX12USL (sane-1.05)
Hi, I am currently try to solve the problems with the X12USL. The colored stripes look somewhat similar on all devices so I think it is not a hardware problem. What I urgently need is a log of the data that is transferred via SCSI when scanning with the windows (or Mac?) driver. I managed this for my scanner by using a patched version of wine running the original windows drivers and Levente Novak managed this for his scanner too. I don't know what is possible on a Mac, but if you have an idea, please let me know! There seems to be a growing interest in sopport of the X12USL, so it will be worth the work. Regards Karsten Novak Levente wrote: On Sun, 11 Nov 2001, Michael Thomson wrote: Hi Henning Thanks for your tips - I've successfully built installed sane-backends-1.06 and sane-frontends-1.06 as well as xsane-0.80 now. Sadly I'm still getting weird stripes, but I found a previous discussion on this and I've mailed the folk involved to see if they made any progress. To answer your question, sane-1.05 came precompiled with my distribution: Yellow Dog Linux 2.1 from Terrasoft (www.yellowdoglinux.com) Usually if you get vertical stripes in scanned images, it means that there is no (or there is a wrong type of) shading correction. Every CCD or CIS is composed of photoelements slightly different in characteristics, so usually the scanned images are not directly converted to images but corrected for lamp and sensor unevenness. I had similar problems with Microtek Phantom 636cx, until Karsten Festag corrected the shading function in microtek2. Since then, everything is working fine. The only strange thing in your image is that the stripes are not dark like in my case but coloured. It seems to me it is a wrong (buggy?) shading correction rather than a non-existant one. Or a communication problem between the scanner and the computer which corrupts the data? Levente ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] microtek2 backend and SANE-1.0.6
Hi Folks, I'm going on holidays for the next two weeks, so I won't be able to work on the microtek2 backend in this time. But I have done some improvements though not all of them are really finished (Support for C6 USB, 10bit scanning with Scanmaker 9600XL). I hope to solve the C6 problems until code freeze and consider the 10bit color depth problem with the 9600 as not release critical because 8bit and 12bit are o.k. Thats why I would like somebody with CVS access to add the microtek2_20010828 version and the manpage (on my homepage http://home.t-online.de/home/karsten.festag) to the CVS thou I want to change both until code freeze. Is this o.k. ? Regards Karsten
[sane-devel] scsi * * Scanner not working?
Hi all, I (and possibly others) have problems using scsi * * Scanner in the conf file. In this case no scanners are found. If I compile my backend with SANE-1.0.4 all works fine. Is there a bug in sanei-scsi? Regards Karsten This is a debug output of SANE-1.0.4: [microtek2] parse_config_file: read line: scsi * * Scanner [microtek2] parse_config_file: found device scsi * * Scanner [sanei_debug] Setting debug level of sanei_scsi to 100. [sanei_scsi] searched device is /dev/sg0 [microtek2] attach_one: name='/dev/sg0' [microtek2] add_device_list: device='/dev/sg0' [microtek2] add_device_list: md=0x80e4840, malloc'd 2128 bytes [microtek2] free hdev at 0x80e43e8 [microtek2] attach: device='/dev/sg0' [microtek2] scsi_inquiry: mi=0x80e4844, device='/dev/sg0' [sanei_debug] Setting debug level of sanei_scsi to 100. [sanei_scsi] sanei_scsi_open: SG driver version: 30119 [sanei_scsi] sanei_scsi_open_extended: using 131072 bytes as SCSI buffer And this one is from SANE-1.0.5: [microtek2] parse_config_file: read line: scsi * * Scanner [microtek2] parse_config_file: found device scsi * * Scanner [sanei_debug] Setting debug level of sanei_scsi to 100. [microtek2] add_device_list: device='/dev/scanner' [microtek2] add_device_list: md=0x80e4560, malloc'd 5164 bytes [microtek2] free hdev at 0x80e2ea8 [microtek2] attach: device='/dev/scanner' [microtek2] scsi_inquiry: mi=0x80e4564, device='/dev/scanner' [sanei_debug] Setting debug level of sanei_scsi to 100. [sanei_debug] Setting debug level of sanei_scsi to 100. [sanei_debug] Setting debug level of sanei_scsi to 100. [sanei_scsi] sanei_scsi_open: sanei_scsi_max_request_size=131072 bytes [sanei_scsi] sanei_scsi_open: open of `/dev/scanner' failed: Datei oder Verzeichnis nicht gefunden
[sane-devel] microtek2 backend
Hi all microtek2 users, your backend maintainer is back from a few days off now. I have a lot of mails to read and answer but not much time in the next days. So please be patient if you expect something from me. But don't hesitate to remind me again if you don't have an answer to your question in the next two weeks. There is a new version of the backend on my homepage at http://home.t-online.de/home/karsten.festag It would be nice if many people thest this version and tell me the results. Greetings Karsten Festag
[sane-devel] Re: bug in XSANE?
Hi Oliver, O.k., I didn't thought enough what happens to the data if one applies a function to it... I think I understood it now. But: even if I reset the color corrections directly before the scan, the histogram has its spikes+holes. But there is no visible difference between an image scanned by xscanimage and xsane, both with linear transfer function. So I won't complain. Regards Karsten Oliver Rauch wrote: when you set color corrections to default value: gamma=1.0, brightness=0, contrast=0 before you do the scan/preview scan the histogram should not have any spikes/holes. When you use other color correction values with xsane or define a custom gamma table with xscanimage you will get the spikes/holes.
