[sane-devel] Dusting-off with the Gimp/Coolscan2
> It works quite nice, though still not perfect. You can get a complete > tar from my homepage (www.xs4all.nl/~ljm). I'm afraid the tar link doesn't work for me: "The requested URL /~ljm/dirtyduster.tar was not found on this server." Andras === Major Andras e-mail: and...@users.sourceforge.net www:http://andras.webhop.org/ ===
[sane-devel] epson 2450(firewire) crashes usb
On Monday 19 May 2003 15:20, rob wrote: >Hi, > >I've just discovered that scanning crashes the usb system. What I > get in syslog is this message: > >May 19 19:53:03 samantha kernel: uhci.c: a400: host system error, > PCI problems? >May 19 19:53:03 samantha kernel: uhci.c: a400: host controller > halted. very bad > >Getting any more info is tricky as both my keyboard and mouse are > usb. > >It's probably been a couple of months at least since I last > scanned something so it's hard to know when the problem started > prior to that it's been working great for at least 6 months. > >I'm running debian sid. 2.4.20. libsane 1.0.11. The scanner is > the perfection 2450 photo. The crash happens after a couple of > minutes of use. It happens with both the uhci and usb-uhci. With > uhci the scanner continues to scan fine with usb-uhci it locks > the scanner up too. I don't have any other firewire devices to > test with. It might be your motherboard, older via chipsets would do that quite regularly, or even totally freeze the machine in mid-scan. > >The command used is: > >scanimage --focus-position 'Focus 2.5mm above glass' --source >'Transparency Unit' --mode gray --film-type 'Negative Film' -x > 25mm -y 35mm -l 8.5mm -t 3.3mm --format pnm --resolution 2400 > --depth 16 > filmNoir13.pnm > >If I can give any more info let me know. > >Thanks -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
[sane-devel] can not initialize sane when linux system booting up
On Monday 19 May 2003 14:14, T.M.Thanh wrote: > Hi folks, > > Sane can't initialize my Acer 640 BU Scanner when linux system > booting up (I use RED HAT 9 and Mandrake 9.1). If I want to run my > scanner on Linux, I have to turn it on and restart my system to > Windows then reboot system to Linux and run XSane. Or I have to > turn it on and boot into Windows then reboot into Linux. That's my > workarround :-) > Could any body help me ? You need to specify the correct firmware file in snapscan.conf. Please read the documentation concerning USB scanner firmware on http://snapscan.sourceforge.net . If you boot into windows the firmware file is downloaded to the scanner from your windows scanning application. Back in Linux the snapscan backend will detect that the firmware is up to date and don't attempt a download. If you power-cycle your scanner the firmware has to be downloaded again, which is only possible if you give the correct firmware file in snapscan.conf. -Oliver
[sane-devel] epson 2450(firewire) crashes usb
Hi, I've just discovered that scanning crashes the usb system. What I get in syslog is this message: May 19 19:53:03 samantha kernel: uhci.c: a400: host system error, PCI problems? May 19 19:53:03 samantha kernel: uhci.c: a400: host controller halted. very bad Getting any more info is tricky as both my keyboard and mouse are usb. It's probably been a couple of months at least since I last scanned something so it's hard to know when the problem started prior to that it's been working great for at least 6 months. I'm running debian sid. 2.4.20. libsane 1.0.11. The scanner is the perfection 2450 photo. The crash happens after a couple of minutes of use. It happens with both the uhci and usb-uhci. With uhci the scanner continues to scan fine with usb-uhci it locks the scanner up too. I don't have any other firewire devices to test with. The command used is: scanimage --focus-position 'Focus 2.5mm above glass' --source 'Transparency Unit' --mode gray --film-type 'Negative Film' -x 25mm -y 35mm -l 8.5mm -t 3.3mm --format pnm --resolution 2400 --depth 16 > filmNoir13.pnm If I can give any more info let me know. Thanks -- rob
[sane-devel] Exif informations
> >And I would like to have some informations, about the date, the > >parameters, the version, the author and all that I have > > The scanner cannot determine data about the author, when a photo was > taken, or which aperture and shutter speed was used as a 35mm camera It can, however, tell the frontend a list of settings that are important, which are then to be saved into the output file by the frontend. In the case of coolscan2, this could be exposure and focus information, which would indeed be useful. To sensibly do this, we need to amend the SANE standard, however, in such a way that the backend can specify which options are to be saved. I'm not familiar with EXIF, so would you mind if I asked what exactly it is? Is it just information embedded into a JPG file, or can it be used with other formats as well? Andras === Major Andras e-mail: and...@users.sourceforge.net www:http://andras.webhop.org/ ===
[sane-devel] can not initialize sane when linux system booting up
Hi folks, Sane can't initialize my Acer 640 BU Scanner when linux system booting up (I use RED HAT 9 and Mandrake 9.1). If I want to run my scanner on Linux, I have to turn it on and restart my system to Windows then reboot system to Linux and run XSane. Or I have to turn it on and boot into Windows then reboot into Linux. That's my workarround :-) Could any body help me ? -- Trinh Minh Thanh, M.D. Hanoi - Vietnam
[sane-devel] Dusting-off with the Gimp/Coolscan2
Hi, I am now able to dust-off my slides when scanning with the coolscan2-backend. I use a combination of the original dust-off plugin from Andreas and a little fu-script (which looks a bit like the one I posted earlier). It works quite nice, though still not perfect. You can get a complete tar from my homepage (www.xs4all.nl/~ljm). ljm -- (c) ljm @ xs4all . nl. No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] Exif informations
On Monday 19 May 2003 00:13, Till Kamppeter wrote: > Perhaps it would really be a good idea for a scanning frontend to add > EXIF data of at least the image size, color depth, scanner resolution, > scanning time, ... to JPEG images. image size in pixel, color depth and scanner resolution are stored in jpeg and tiff files (at least by xsane). I do not see a reason to add the= se values twice (e.g. jpeg + exif). image size in mm or inch can be calculated by these values. Oliver --=20 http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:oliver.ra...@rauch-domain.de
[sane-devel] can not initialize sane when linux system booting up
Hi, On Mon, May 19, 2003 at 07:14:58PM +0700, T.M.Thanh wrote: > Sane can't initialize my Acer 640 BU Scanner when linux system booting Does sane-find-scanner fin the scanner? If not, it's a kernel issue. If it's found by sane-find-scanner but not "scanimage -L", maybe you haven't given the correct path to the firmware filr in snapscan.conf? Bye, Henning
[sane-devel] new kde, kills sane
On Monday 19 May 2003 13:18, Gene Heskett wrote: >Humm, the missus just came in and said can you scan this? The > last time I used the scanner it was working great, but now the > icon that launches xsane goes thru the root warning and then > scans for devices forever, or until I call ksysguard and kill it. > >sane-find-scanner shows this: >--- >[root@coyote root]# 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=0x04b8, product=0x010f) at >/dev/usb/scanner0 >found USB scanner (vendor=0x1453, product=0x4026) at > libusb:002:005 ^not a scanner, but a usb-serial > adaptor^ found USB scanner (vendor=0x04b8 [EPSON], > product=0x010f [EPSON Scanner 010F]) at libusb:002:003 > # 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. >- > >scanimage -L hangs forever also, but can be ctrl-c'd. >Next, I reconfiguring and reinstalling all 3 pieces, which if that >doesn't fix, I'll be back. >xsane is .90, sane-backends is 1.0.11, sane-frontends is 1.0.10, > and it all worked great before I installed kde-3.1.1a and or that > usb-serial adaptor, a prologic that works just fine also. Update, it turned out it was hanging on the epson backend (from iscan-1.5.0) so I disabled that in dll.conf and its working. Then the print plugin for the gimp seems to have gone awol. Gimp says it crashed. So I'm damned if I do, and damned if I don't it seems. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
[sane-devel] new kde, kills sane
Humm, the missus just came in and said can you scan this? The last time I used the scanner it was working great, but now the icon that launches xsane goes thru the root warning and then scans for devices forever, or until I call ksysguard and kill it. sane-find-scanner shows this: --- [root@coyote root]# 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=0x04b8, product=0x010f) at /dev/usb/scanner0 found USB scanner (vendor=0x1453, product=0x4026) at libusb:002:005 ^not a scanner, but a usb-serial adaptor^ found USB scanner (vendor=0x04b8 [EPSON], product=0x010f [EPSON Scanner 010F]) at libusb:002:003 # 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. - scanimage -L hangs forever also, but can be ctrl-c'd. Next, I reconfiguring and reinstalling all 3 pieces, which if that doesn't fix, I'll be back. xsane is .90, sane-backends is 1.0.11, sane-frontends is 1.0.10, and it all worked great before I installed kde-3.1.1a and or that usb-serial adaptor, a prologic that works just fine also. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
[sane-devel] can not initialize sane when linux system booting up
On Monday 19 May 2003 12:14 pm, T.M.Thanh wrote: Hi I have just installed mdk 9.1 and have no problem. I do however ensure the the scanner is turned on at boot up, a lesson learned when using mdk9.0 and having to configure this scanner myself in the first place. I note in your message that you might be in the habit of turning the scanner on later. Maybe try this first before trying anything else. Good luck for now > Hi folks, > > Sane can't initialize my Acer 640 BU Scanner when linux > system booting up (I use RED HAT 9 and Mandrake 9.1). If I > want to run my scanner on Linux, I have to turn it on and > restart my system to Windows then reboot system to Linux and > run XSane. Or I have to turn it on and boot into Windows then > reboot into Linux. That's my workarround :-) Could any body > help me ? -- Regards Frank 025853824 Either big or small, a challenge requires the same commitment to resolve.
[sane-devel] Exif informations
Hi, On Mon, May 19, 2003 at 12:13:32AM +0200, Till Kamppeter wrote: > Perhaps it would really be a good idea for a scanning frontend to add > EXIF data of at least the image size, color depth, scanner resolution, > scanning time, ... to JPEG images. One could also add a dialog, where > the user can also fill in other fields as author?s name, camera model > and settings, ... "Author" as in the one who scanned the image could be predefined by the real name field of /etc/passwd. If the frontend can get the list of devices, also the manufacturer and model of the scanner is known. But these features should be optional. Not everyone may like to see his name, the date and more details on some random scan he wants show on his website. Bye, Henning
[sane-devel] Exif informations
Georges Roux wrote: > I use this device: > device `coolscan2:usb:libusb:001:004' is a NikonLS-40 ED > film scanner > > it's a film scanner (USB). > And I would like to have some informations, about the date, the > parameters, the version, the author and all that I have > to know about the image and more... if you please. May be it's a dream, > but yes there is a library who can help to do that. > I use exif command line, to search about somes images, and I think may > be usefull to retrieve the applied correction. > I don't understand why a scanner can't do less than my digital camera. > The scanner cannot determine data about the author, when a photo was taken, or which aperture and shutter speed was used as a 35mm camera does not store this on the film. A scanner also cannot add the scanning time to its output. In contrary to digital cameras a scanner has no internal clock. The author´s name can even not be added by a digital camera, as this information is not kjnown to the camera. You can use tools like exif or gexif to manually add EXIF data items to JPEG files. Perhaps it would really be a good idea for a scanning frontend to add EXIF data of at least the image size, color depth, scanner resolution, scanning time, ... to JPEG images. One could also add a dialog, where the user can also fill in other fields as author´s name, camera model and settings, ... Till
[sane-devel] Epson GT6000 parport scanner on RH Linux
Hello Eric, i have the same scanner working on Suse Linux 7.3, 8.0, 8.2, Mandrake 8.2, 9.0, 9.1. I should work with Red Hat, too. The only thing you have to do is "switch off" (comment with #) all other backends in dll.conf and enable parport in epson.conf (pio 0x378). Comment all other settings in epson.conf. I tried it with several older sane Versions, all i tried worked. I get always a E-C Message in Scanners panel. But after I am starting any frontend, the "ready" light is on and the scanner works fine. Maybe commenting out entrys in dll.conf will solve your error. Please let me know if it works. Best Regards to down under, Harald. Am Sonntag, 18. Mai 2003 12:54 schrieb Eric Mills: > Hi, > > For some time now I have been trying to get my GT6000 working locally on > RH Linux (7.3, port 0x378). With both the standard 1.0.7 sane provided > and the latest 1.0.11 backends with .10 frontends, I get the following > problems: > > 1. Without debugging turned on the scanner appears to be reset upon > entering any front end and then the backend goes into an infinite loop. > Scanner puts up E-1 in the window after 30 seconds. > > 2. With DEBUG=128 initialisation passes, but the backend seems to decide > the scanner has an ADF with looney size parameters (0 length) which > cases an invalid parameter error on the first scan request. > > Does anyone have one of these old parport scanners working in the same > configuration? Karl does not have access for any suggestions. > > Thanks, > Eric Mills > > ___ > Sane-devel mailing list > sane-de...@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel
