Hello,
I'm using pcsc-lite 1.2.9beta6 on Debian Linux and I encounter a little
problem.
I'm analysing it for weeks/months now trying to determine where the
origin is, and it seems to be linked to a difference of behaviour in
SCardDisconnect calls.
If I repeatedly close a connection (every few minutes) to a smartcard
using SCARD_LEAVE_CARD in case of normal behaviour (not on errors),
it finally ends with a "RPC transport error", which generally ends by a
failure in pcscd ("service not available") or a "sharing violation" on
the reader.
If I always close connections with SCARD_RESET_CARD, it seems to behave
normally in the same conditions.
I had a look to the function and there are several flags reset in case
of a call to SCARD_RESET_CARD.
Is it possible that if these flags are not reset, it may lead to
troubles on the communication layer under certain circumstances ?
NB: I spied the communication between the card and the reader and I
observe SCardTransmit calls which never reach the card.
NB2: I don't think the problem may be located in the driver as
otherewise "SCARD_RESET_CARD" wouldn't have any effect.
NB3: This situation is tricky and can't be easily reproduced in a short
example.
I tried to analyse as far as I could, but if anyone has a suggestion on
how to confirm this or not, he is welcome.
Thanks in advance for your answers/comments.
Fabien
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
