|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: When will IOCTL_SMARTCARD_XXX code and SCRD_XXX code be send?
From: Walter Oney (waltoney
ONEYSOFT.COM)
Date: Sun Nov 23 2003 - 22:19:28 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Angela wrote:
> I'm newbie in PCSC smartcard driver programming. I changed the smaple code in the DDK, bullltlp3 and can succussfully transmit and receive APDU data. However, I always get IOCTL_SMARTCARD_POWER, IOCTL_SMARTCARD_GET_ATTRIBUTE, IOCTL_SMARTCARD_IS_ABSENT 15 seconds after the driver has detected a card insertion event, even though the card is still being connected. Do anyone know under what condition do all those commands are sent? There can I find those documentations? I really have no idea where I should start to debug with.
The Windows resource manager has detected that no one is actually using
the card, so it powers the card down. It normally keeps an IS_ABSENT
outstanding at all times so that it will know when the card is removed.
I hope you don't really mean that the card "is still being connected"
after 15 seconds. That would be a staggeringly long delay for a reader
to finish resetting a card and would render the reader basically
unusable in most applications. Do you perhaps mean to say that the card
"is still inserted and powered"?
You can do a "net stop scardsvr" to halt the resource manager.
Thereafter, do an "ifdtest -m" to do some simple manual tests of your
reader and driver. Once you've got the simple stuff working, unpack your
set of PC/SC test cards and run the full-blown IFDTEST.
--
Walter Oney, Consulting and Training
SmartCard drivers a specialty
Check out our schedule at http://www.oneysoft.com
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]