Hello, I'm currently developing a cardreader authentification prototype at work - it's basically nothing more than reading out the CARD ID on the card and assigning a name to it. It is supposed to run under 3 OS's - that is NT 4.0, Win2000 and Linux. We're using a towitoko chipdrive external (serial)
Win32 is making no problems - but Linux is. The application just sends a reset, a request ICC and a read binary command through the CT API to the CardReadre and i get my 7 char- card id back. But, under Linux i get unexpected results - instead of the card id i get weird bytes - example: �U��� - that's not encrypted or masked or whatever, i checked. I believe this has to do something that the Linux CT Api is communicating with the card/reader with the wrong bitrate/parity etc, it's the only explanation i can come up with. FYI - i am able to get "normal" error codes from the reader like 62 00 (card not inserted). So i can communicate with the cardreader just fine. It's the card that's making me problems, it's a Siemens SLE4004. I've read that you can somehow set the communication speed through the CT api - i have searched this mailing list and found an example for gemcard readers - that didn't work. Can anyone give me examples (ie commands etc) how to set the baudrate *************************************************************** Unix Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/ To unsubscribe send an email to [EMAIL PROTECTED] with unsubscribe sclinux ***************************************************************
