C L. wrote:
Already got the epkowa and related stuff installed. Debug does't provide more
clues either other than show the libs being loaded then closed. The only clue
I've seen so far is that Inappropriate ioctl error in my strace log.
What's really annoying, I had this epson v10 working
C L. wrote:
Bingo!!! Now it's working! At least as root (I should be able to sort that
out, need to edit the /etc/udev/rules/libsane.rules.) I didn't come across
any documentation mentioning that interpreter line. That's the secret
ingredient I was missing =)
There likely is none. Our
C L. wrote:
Hey btw, how do you compile iscan to enable debug in epkowa? I don't get
anything from 'SANE_DEBUG_EPKOWA=255' - only more verbosity in
'SANE_DEBUG_DLL=255'
epkowa no longer uses integer values for the debug level. It has the following
levels in increasing level of feedback:
Le jeudi 28 janvier 2010 11:34:55 Andrey Loginov, vous avez ?crit :
Hello
Please check changed genesys_device.c in attachment. And also the scan
with scan area changed.
And there are some other staff to do (like scan button and page feed
sensor). How can we proceed with this staff?
? ??,
Le jeudi 28 janvier 2010 23:32:51 Dipl.Geogr.G.Birkenfeld, vous avez ?crit :
So, nobody an idea about creating/suggesting a SANE driver for this one ?
Thanx
Hello,
the first step would be to identify the chips in your scanner. Maybe by
disassembling your scanner. But
On Thu, Jan 28, 2010 at 4:11 PM, Oliver Schwartz Oliver.Schwartz at gmx.de
wrote:
Hi all,
On 28.01.2010 at 14:39 m. allan noah wrote:
I would do both- process ID combined with a hash of the device name,
I believe that would defeat the purpose. The whole point of the mutex is to
protect
Hi Allan,
Anyway, I've commited a hash function now. The new code should also
work on FreeBSD 8.0. If anyone can try it, I'd be much obliged.
I did not see any commit message. did you git push?
Err - yes, and it told me that it had pushed 4 or 5 objects. That was
my first git
/attachments/20100129/5930e80f/attachment-0001.c
