[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-smartcardddk
Subject:    Flag SCARD_UNPOWER_CARD in ScardDisconnect
From:       Zambelli Giampietro <gzambelli () EUTRON ! IT>
Date:       2000-01-19 17:27:17
[Download RAW message or body]


Hi all,
I've a problem executing in an application program the command
SCardDisconnect(hCard,SCARD_UNPOWER_CARD). The problem doesn't take place at the
first execution, but at the second one. Here the SCardConnect command fails with
error "80100065 - The reader cannot communicate with the smartcard, due to ATR
configuration conflicts".
I wish to point out the substituting the
SCardDisconnect(hCard,SCARD_UNPOWER_CARD) with
SCardDisconnect(hCard,SCARD_LEAVE_CARD) or with SCardDisconnect(lngCard,
SCARD_RESET_CARD) I have NO problem with every successive execution.
So I'd rather have more information about the action involved by
SCARD_UNPOWER_CARD flag in the resource manager.
What are correct actions to perform to re-initialize after a
ScardDisconnect(hCard,SCARD_UNPOWER_CARD). Are there specific action the
Smartcard driver is required to do (I mean some field in SmartCardExtension to
set to let the resource manager reconfiguring correctly) ?
Currently, the smartcard driver I'm using handles the RDF_CARD_POWER mandatory
callback at the same way for the three possible MinorCode SCARD_COLD_RESET ,
SCARD_WARM_RESET ,SCARD_POWER_DOWN. Does the resource manager expect different
behavior?
At the time being I don't want to implement special behavior for
SCARD_POWER_DOWN at firmware level because I'm convinced that setting the
correct field in Smartcard common structs would be enough to let the Resource
Manager behaves correctly.
I also tried to monitor the SmartcardExtension struct before a succesfully
ScardConnect and before the SCardconnect that fails but up to now no result.
Someone has suggestions or better solutions ?
Thank you in advance for any kind of answer.
Giampietro.



[prev in list] [next in list] [prev in thread] [next in thread]