On Saturday, November 1, 2003, at 07:49 PM, sh wrote:
Maybe none of these causes the error, it appears be the card (T=1).
Why are there problems with T=1 cards? Will there be a version someday without this limitation?
Just to clarify things, T=1 support is an ifdhandler (driver) issue, not a pcsc-lite issue.
As far as transport protocol abstraction level, there are different types of CCID readers:
1- character-level
2- TPDU-level
3- APDU-level
Character-level readers are really "stupid" and all the protocol stack needs to be implemented in the driver on the host.
TPDU-level readers do almost all the work for T=0 cards but very little for T=1. Most of the T=1 protocol has to be implemented in the ifdhandler. Implementing a proper T=1 stack is really time-consuming, this is why I have not done it yet.
APDU-level readers do all the work and the ifdhandler is really simple.
All these readers are CCID compliant, but character-level readers are like Winmodems and APDU-level readers are like proper modems.
My driver currently supports APDU-level readers (GemPC433 and GemPCTwin/GemPCKey after setting them in APDU mode) and TPDU-level readers for T=0 cards.
Another question:
is there a possibility to access memory cards (SLE4442, german health card)
with pcsc? There are many people waiting for a solution on Mac OS X, but
there is no CT-API on OS X.
As Peter said, synchronous memory cards are usually supported through an emulated set of APDUs that are reader-specific.
Cheers, JLuc.
_______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
