Closed digitalentropy closed 4 years ago
Why do you expect a prompt to select a reader?
I agree the continuous loop is a bug somewhere.
I was expecting it only because of what the screenshots looked like. It appeared that the system would list readers and then ask the user to select a reader to interrogate.
Apologies if that assumption is incorrect.
I can't reproduce the problem on my Windows 10. Please apply this patch, rebuild and try again.
diff --git a/pcsc_scan.c b/pcsc_scan.c
index e054624..6e6b29c 100644
--- a/pcsc_scan.c
+++ b/pcsc_scan.c
@@ -630,6 +630,7 @@ get_readers:
{
time_t t;
+ printf("rv: 0x%08X\n", rv);
if (pnp)
{
#ifdef WIN32
Current output is as follows:
Scanning present readers...
0: Alcor Micro USB Smart Card Reader 0
1: JAVACOS Virtual Contact Reader 0
2: JAVACOS Virtual Contactless Reader 1
rv: 0x00000000
It still loops over and over, regardless of card state.
OK. Try again with this new patch:
diff --git a/pcsc_scan.c b/pcsc_scan.c
index e054624..f231e14 100644
--- a/pcsc_scan.c
+++ b/pcsc_scan.c
@@ -635,6 +635,7 @@ get_readers:
#ifdef WIN32
/* check if the number of readers has changed */
LONG newNbReaders = rgReaderStates_t[nbReaders-1].dwEventState >> 16;
+ printf("nbReaders: %d, .dwEventState: 0x%08X\n", nbReaders, rgReaderStates_t[nbReaders-1].dwEventState);
if (newNbReaders + 1 != nbReaders)
#else
if (rgReaderStates_t[nbReaders-1].dwEventState &
New looping message:
Scanning present readers...
0: Alcor Micro USB Smart Card Reader 0
1: JAVACOS Virtual Contact Reader 0
2: JAVACOS Virtual Contactless Reader 1
nbReaders: 4, .dwEventState: 0x00040002
What version of Windows do you use? What is the output of pcsc_scan if you unplug one reader, for example the Alcor Micro USB reader?
Windows 10 (Current)
I can check exact version number when I get back.
Microsoft Windows [Version 10.0.18363.657]
Try the version available at http://ludovic.rousseau.free.fr/softwares/pcsc-tools/pcsc_scan.c
I am observing an issue with pcsc_scan.exe detecting my readers and then looping over and over rather than presenting a prompt to select reader and action.
The issue is observed when compiling from scratch and also when using the pre-compiled Windows binary.
I've uploaded a log of the output I am observing in both scenarios.
log.txt
Any thoughts on possible causes?