Troubleshooting the Smart Card Reader Test (IFDTest2) (Windows Embedded CE 6.0)
1/6/2010
Applies to Windows Embedded CE 6.0 R2
The following table describes troubleshooting tips for the Smart Card Reader Test.
| Issue | Solution |
|---|---|
When running test case 1004, the system does not automatically resume after having been suspended for fifteen seconds. |
Wake the system manually, for example by using a keyboard, mouse, or other input device that has direct hardware-interrupt ability. |
Test fails when using legacy drivers. |
Certain legacy drivers, for example STCUSB.DLL, require that calls to IOCTLs be made from the kernel. If they are not made from the kernel, the test fails. To work around this issue, run Tux using the -n parameter: tux -o -n -d ifdtesttux |
The Windows Embedded CE 6.0 Test Kit (CETK) displays an informational icon that indicates that Smart Card peripheral hardware was not detected |
The CETK does not correctly detect the presence of the peripheral hardware. Therefore, the CETK incorrectly displays an informational icon that indicates that peripheral hardware was not detected. You can still test the USB CCID Smart Card reader by using the CETK, even though the CETK user interface indicates that the Smart Card peripheral hardware was not detected. |
When you are running these test cases on a Windows Embedded CE PC-based development platform (CEPC), if the Smart Card reader is inserted before you turn on the CEPC, USBCCID.dll is not loaded when the CEPC is turned on. |
After you turn on the CEPC, remove the Smart Card reader from the CEPC, and then reinsert it. |