On 29/11/05, Gary Pearman [EMAIL PROTECTED] wrote:
Is there any chance you could post the code that you're using to
initialise the BasicCard?
At the moment regardless of what protocol I use (SCARD_PROTOCOL_T0,
SCARD_PROTOCOL_T1 or SCARD_PROTOCOL_ANY), I just get Protocol
unsupported errrors.
Gary,
I just installed the latest pcsclite and I am working with an Omnikey
reader (3121 USB driver on their site): it works OK (Suse 10)
Regards,
Philippe
Gary Pearman wrote:
The thing is, it also fails if I try T=1.
prothandler.c:108:PHSetProtocol() Protocol T=1 requested but
On 29/11/05, Gary Pearman [EMAIL PROTECTED] wrote:
The thing is, it also fails if I try T=1.
prothandler.c:108:PHSetProtocol() Protocol T=1 requested but unsupported
by the card
This debug line was _not_ in your previous debug trace. I guess you
changed the card and used a T=0 card to
I've been using the same card all along. Here is the debug output from
the same program, just with the protocols set to T=0 and T=1.
pcscdaemon.c:258:main() pcscd set to foreground with debug send to
stderr
pcscdaemon.c:463:main() pcsc-lite 1.2.9-beta9 daemon ready.
I've written a simple program using libbasiccard and libpcsclite that
gets the ApplicationID from a ZeitControl BasicCard. The problem is that
the program returns the correct value when run in Windows, but returns
garbage when run on Linux.
I think I'm missing something simple, but not sure what.
On Mon, 2005-11-28 at 11:53 -0600, Philippe C. Martin wrote:
Hi,
I do not know about libbasiccard, but pcsclite works fine for me on a
ZC5.5 (T=1) - mdk 10.1 (testing this week on suse 10.0)
Regards,
Philippe
The first time I run my program, I get a card busy error, the second
time it
Hi,
This dumps _seems_ to show pcsclite is unhappy figuring out the
protocol - did you try to force it (T=1 or T=0) ?
You might want to try with another reader also (or update its driver ?).
Regards,
Philippe
Gary Pearman wrote:
On Mon, 2005-11-28 at 11:53 -0600, Philippe C. Martin