You would need the source code to kodak's backend to do that. I don't
think they make that available.
allan
On Wed, Sep 6, 2017 at 6:03 AM, fm8758ye wrote:
> Thank you, and I have contacted Kodak last month but have received no
> response from them. In the likely case my
Thank you, and I have contacted Kodak last month but have received no response
from them. In the likely case my request is ignored, it is possible for me to
sniff packets on windows or linux and add support to the backend myself (I will
look for a driver programmer for help)?
Fan
The .conf file is not the backend, it is just configuration. The real
code is a compiled library, usually installed somewhere in /usr/lib...
The sane standard does not require that backends expose button options
to the frontend. So, the kvs_i1200 backend can be sane compliant, but
not support
Hi Fan,
if you can perform normal scanning with sane, then the scanner seems to
be supported by the sane-backend you are using. The next question is, if
the backend is capable of reading the option values corresponding to the
buttons. If can't see any value change if you press one of the buttons
Dear Allan,
Thank you for the input, do you mean the file kds_i1200.conf has to provide
button support? I looked at the other conf files under sane.d and they all look
alike without any mentions of buttons. In the case that I have to contact
kodak, what should I ask them for?
Fan
Hi Wilhelm,
Thank you for your prompt reply. I have tried holding onto buttons, every one
of them, and none of the values change. I have tried compiling with
"scanbuttond =yes" with the same results. When installing the kodak official
driver, it does provide a kds_i1000.conf which lists the
kds_i1200 would have to provide button support. I suggest you contact kodak.
allan
On Fri, Aug 18, 2017 at 12:14 AM, fm8758ye wrote:
> I am trying to implement scanbd with the scanner as a scan station. However,
> I got stopped at the first step as scanimage -A only shows
Hello,
scanbd depends on sane to detect button presses. For rare cases there is
the old scanbuttond backend included into the sources of scanbd. In this
case, you have to manually compile and install scanbd.
In the log-file you will find all options (including the buttons id they
are detected by
I am trying to implement scanbd with the scanner as a scan station. However, I
got stopped at the first step as scanimage -A only shows scan options (such as
mode and profiles) and does not show any sensor or button. Holding down the
front buttons and doing scanimage -A shows no value