Hi Arno, i guess you are using my driver? which version? with which version of pcsc?
> >Got an Aladding eToken. > >Sending 5 bytes: > >0x00 0xA4 0x00 0x0C 0x00 > >Command successful. > >Received 2 bytes: > >0x90 0x00 my testpcsc doesn't do that. did you hack testpcsc yourself? my testpcsc without this extra test will run several times in a row without errors, i cannot find what is wrong. can you please try opensc, and run the opensc explorerer? what happens if you run e.g. "ls" several times in a row? what kind of token is this exactly? i can see that the token claims to be a eToken Pro 4153, while i have an eToken Pro 4151. Vladimir: what is the difference? Sep 20 14:29:30 quirx kernel: usb_control/bulk_msg: timeout my token implementation is completely user based. maybe the etoken has a bug in it's usb code, as Peter suggests? I have never seen any usb timeouts with my token. Regards, Andreas _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
