ScardGetStatusChange() API May Cause Deadlock in Smart Card Resource ManagerID: Q235899
|
The Smart Card Resource Manager may stop responding (hang) in the following situation:
There are two processes (A and B) each with a single thread gaining access to the same card (in the same reader) simultaneously. Each of the processes runs the following sequence in a finite loop:
SCardEstablishContext
SCardConnect
SCardGetStatusChange(SCARD_STATE_UNWARE,.....)
SCardBeginTransaction
SCARDTransmit (many times)
.....
SCardEndTransaction
SCardDisconnect
SCardReleaseContext
A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack
that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support Services
phone numbers and information on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this fix should have the following file attributes or later:
Date Time Size File name Platform
----------------------------------------------------
6/17/99 8:53AM 65,536 Scardsvr.exe x86
Q154871 Determining If You Are Eligible for No-Charge Technical Support
Microsoft has confirmed this to be a problem in Windows NT 4.0.
Additional query words:
Keywords : kbbug4.00 kbfix4.00
Version : winnt:4.0
Platform : winnt
Issue type : kbbug
Last Reviewed: August 9, 1999