智能卡读卡器命名:删除任何读卡器时，其余名称都会更改

本文介绍了智能卡读卡器命名:删除任何读卡器时，其余名称都会更改的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我正在编写智能卡应用程序.此应用程序将卡连接到读卡器中，有时还可以使用它.我需要观察何时不再有读取器(弹出卡或从USB中删除读取器).

I am writting a smartcard application. This application connects card in reader and sometimes works with it. I need to watch when reader is no longer available (either card is ejected or reader is removed from USB).

使用 SCardStatusChange .此功能需要阅读者姓名才能观看.

Readers are watched using SCardStatusChange. This function requires reader name to watch.

我将两个带卡的读卡器插入USB插槽.它们被识别为"USB智能卡读卡器0"和"USB智能卡读卡器1".我删除了一个阅读器. Windows说"USB智能卡读卡器1"仍处于连接状态.我插入它-再次可用.现在，我删除第二个. Windows仍然显示"USB智能卡读卡器1"已连接.这是问题所在，因为它应该是仍处于连接状态的"USB Smart Card Reader 0".跟踪例程的名称已更改，因此无法监视阅读器.

I insert two readers with cards into USB slots. They are recognized as "USB Smart Card Reader 0" and "USB Smart Card Reader 1". I remove one reader. Windows says, "USB Smart Card Reader 1" is still connected. I insert it - again both available. Now I remove the second one. Windows still says "USB Smart Card Reader 1" is connected. And this is the problem because it should be "USB Smart Card Reader 0" which is still connected. Tracking routine can't watch reader because it's name is changed.

是驱动程序问题还是XP智能卡子系统问题?使用的驱动程序是USB CCID兼容版本5.2.3790.1830(VID 076B，PID A021)，usbccid.sys.

Is it a driver problem or XP smartcard subsystem problem? Driver used is USB CCID Compliant version 5.2.3790.1830 (VID 076B, PID A021), usbccid.sys.

推荐答案

我们在项目中遇到此问题，并通过遍历每个可用的读取器并检查是否在该读取器中插入了卡来处理该问题.您将在多个品牌的USB读取器中遇到此命名问题.

We ran into this problem on a project and handled it by iterating through each available reader and checking to see if a card is inserted in that reader. You will encounter this naming problem with several brands of usb readers.

我公司的产品可让您将智能卡与网站集成；我们的一个演示列出了当前可用的智能卡读取器，它可能会帮助您测试不同的读取器方案: cardbossetway/content.agent?page_name=GetReaders+Demo

My company has a product that lets you integrate smart cards with websites; one of our demos lists the smart card readers currently available and it might help you with testing different reader scenarios: cardbossetway/content.agent?page_name=GetReaders+Demo