Pete Chown wrote:
> > If by "old buttons" you're talking about non-JavaCard, yes we support
> > them on all platforms ...
>
> Yes, the non-Java iButtons were the ones I was referring to. Where can
> I get the Linux drivers for these devices? I couldn't find them on the
> web site.
The followin
[EMAIL PROTECTED] wrote:
> If by "old buttons" you're talking about non-JavaCard, yes we support
> them on all platforms ...
Yes, the non-Java iButtons were the ones I was referring to. Where can
I get the Linux drivers for these devices? I couldn't find them on the
web site.
Marcus Oestreicher wrote:
>
> Pete Chown wrote:
>
> Actually, are you sure that the iButton and the Schlumberger JavaCards
> use
> the same file format ? I would expect, that their converters create
> different
> file formats, e.g. you can not use the converter shipped by
> Schlumberger.
> Althou
Pete Chown wrote:
>
> David Corcoran wrote:
>
> > First, the iButton provides a C-API for communicating to the iButton.
>
> Ah, that is interesting. I found Windows drivers for the old iButtons,
> together with the big Java thing that will drive the Java iButtons under
> Windows or Unix. In o
Pete Chown wrote:
>
> David Corcoran wrote:
>
> > First, the iButton provides a C-API for communicating to the iButton.
>
> Ah, that is interesting. I found Windows drivers for the old iButtons,
> together with the big Java thing that will drive the Java iButtons under
> Windows or Unix. In o
David Corcoran wrote:
> First, the iButton provides a C-API for communicating to the iButton.
Ah, that is interesting. I found Windows drivers for the old iButtons,
together with the big Java thing that will drive the Java iButtons under
Windows or Unix. In other words as far as I could see th
Hi,
I'll try to answer your questions:
First, the iButton provides a C-API for communicating to the iButton. I
looked at writing an IFD_Handler at one time but never got around to it.
I think that would be great.
I'm guessing that your problems come when trying to compile the card
drivers. Th
