DTM test failure: Windows Vista Client x64: Smart Card reader
-
Monday, August 08, 2011 9:02 AM
Hi,
We are trying to get support for the below issue. Please give us the appropriate contact person details, so that we can sort this issue at the earliest possible.
Please treat this as a high priority issue. Your comments on the below issue at the earliest possible is very much appreciated.
We are working on a USB Smart Card Reader firmware.
When we tried running DTM Tests (DTM 1.6), the below test fails.
[Category] Subcategory: [Device] Input->Smart Card Reader
Failing Test:- IFDTest Part D: Smart Card Provider Test->Test No. 2->READ BINARY 30 bytes
Error reported:- IOCTL call failed: Returned 45dH (NTSTATUS c0000186H)
Device Used: SMSC USB Smart Card reader
Card Used: Infineon Technologies PC/SC Compliance Test Card.
OS: Windows (TM) Vista Business, Ver 6.0 Service Pack 2 (Build 6002).
Driver Used: Microsoft USBCCID.sys V6.0.6002.18005.
The same problem, however, does not occur with Windows 7 OS.
We suspect the problem to be in the USBCCID driver of Vista, which does not handle WTX request properly.
This failure seems to be already listed as the DTM filter #1715 (Screenshot attached "DTMfilter_1715.png") (Link:- https://winqual.microsoft.com/EC/ECDetails.aspx?id=1903).We have installed the "WLK updated filters" package dated 5th August 2011.
But, when we view our submission package (DTM CPK file) using "DTM Log Viewer for the Windows Logo Program - Version 3.2.0.0", this failure is still listed under failed tests without any filter applied.
Thanks and Regards,
Suriaprakash M,
Principal Engineer - Software,
Standard Microsystems India Pvt. Ltd.,
Module 1, 4th Floor, Block A, SP Infocity,
#40, MGR Salai, Perungudi,
Chennai - 600 096, Tamil Nadu, INDIA.
Email: Suriaprakash.Mariappan@smsc.com
Mobile :+919381453832
Skype ID: msuriaprakash
All Replies
-
Tuesday, August 09, 2011 6:49 AM
We have got a response by directly communicating with
logofb@microsoft.com.The reason for the filter not being applied, was due to the following difference.
The errata shows:
IOCTL call failed:\nReturned 79H
our log indicates:
IOCTL call failed:\nReturned 45H
The failing assertion string is identical besides the 79H to 45H. Since the failing assertion is identical and our reader is passing in Win 7, we will be allowed to use 1715 as a manual errata due to our situation and urgency.
- Marked As Answer by Suriaprakash M Tuesday, August 09, 2011 6:49 AM
-
Wednesday, May 09, 2012 6:22 AM
Hi Suria
Thanks for taking time and posting the solution as well. It was useful.
Karthikeyan

