On 25/12/06, Martin Preuss <[EMAIL PROTECTED]> wrote:
On Sunday 24 December 2006 21:39, Ludovic Rousseau wrote:
> On 24/12/06, Martin Preuss <[EMAIL PROTECTED]> wrote:
[...]
> I tried with 3 CCID readers and my CCID driver. I received Lun 0, 1000 and
> 2000.
[...]
Which version of PCSClite are you using then? Maybe your's is newer than
1.3.1 and it has already been fixed in your version?
I am using the SVN code. But I don't remember having changed this part.
You can get a snapshot at [1].
[...]
> I suspect a bug in your code :-)
[...]
That's what I first thought, too. But how can it be? I log the LUN in my
IFDHCreateChannelByName(), and it always says "LUN=0"...
That's ok for the first reader, but it is definately not ok for the second and
further readers. Since this function is called by PC/SC (not by my driver)
and it is always given LUN=0, how can it be a bug in my code?
Are you using a 64-bits driver with a 32-bits pcscd?
BTW: There are other strange things happening when I insert the second reader:
As my log shows (attached "pcscd.log") the name of the second reader is
unreadable (the first one is printed correctly, but the second one contains
unreadable characters? This is *before* the driver's function
IFDHCreateChannelByName is called, so there is no time for my driver to screw
anything up).
I see. Strange. The driver is loaded for the first reader so it may
corrupt pcscd memory and trash the reader name. It may also be a bug
in pcsc-lite.
You will have to instrument pcscd code and your code to see what's
wrong. Without your readers I will not be able to debug myself so will
not be very helpful. Sorry.
Regards,
[1] http://ludovic.rousseau.free.fr/softwares/pcsc-lite/
--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
