A few weeks ago I brought up my IFD handler with the then version of
firmware we had produced and noted that the driver's Create/Close/and
cleanup functions would all be called during system boot, and before any
Smart card app could be called. No surprises, but I did at one point suspect
that the asynchronous nature of Open/Close was causing a serialization blue
screen. That proved to be something else, but I well remember the fact that
Creat, Close, and Cleanup were all invoked by Windows Smartcard services
during thast early testing.
Now, several weeks and many fixes later, I note that Create only is now
called. Close and Cleanup never get invoked until I shutdown the system.
However, this affects Standby/Hibernate since the IFD handler fails the
Standby/Hibernate POWER IRP because it has an open handle. One of the
firmware fixes involved correcting the ATR. Does the ATR have ANYTHING to do
with setting a state that Windows Smartcard services will not close it's
handle to the reader, as evidenced in earlier testing?
Gary G. Little