Good Morning ! Thanks for all your replies. Here´s some more info:
1) regarding the different ATRs ------------------------------------------------------ > Dr. Rousseau wrote: >> Observation: The ATRs displayed are different, depending on >> which reader I place my card. > > Strange. I have never seen this. You may have two different ATR for a > cold reset and a hot reset. But not for two cold reset. > With the same card and using the same driver? Same card: yes. Same Driver: No (SDI010: CCID driver, CardMan: Vendor Driver) 2) regarding the non working commands ------------------------------------ > Dr. Rousseau wrote: > This is 6E 00 = Class not supported > 0xFF is an unusual class byte. Are you sure of this value? The APDUs/Commands I use are from the Document "Interoperability Specification for ICCs and Personal Computer Systems Part 3: Requirements for PC-Connected Interface Devices", which can be found at http://www.pcscworkgroup.com/specifications/files/pcsc3_v2.01.07.pdf . The commands specified there work nicely on the CardMan. Could it be that this document is referring to a Version "2" of the PCSC standard ? (v2.01.07...) Is there possibly a Version "1", that would define different commands ? 3) regarding the SDI010 vendor driver: ------------------------------------- > Joseph Antony wrote: > The issue is because SELinux maybe enabled. You may try to disable > SELinux and verify Thanks for the tip ! I did some testing and now have the vendor driver running. I had to do two things: - Disable SELinux. This removed the "cannot restore segment prot after reloc: Permission denied" error - After that, I noticed that there was a error message at boot time saying that the module sdi010x could not be loaded because of a "format mismatch". To rectify this, I went to <downloaded>/sdi010_ver2.0.1/src/2.6 and recompiled the module (make, make install). After that, the module loaded correctly, and pcscd loads the driver and shows response to placing/removing the card. The responses I get from this driver are similar to Dr. Rousseaus CCID driver. Obviously, these two drivers agree on not liking my commands ... thanks everybody, best regards, Dieter Ludovic Rousseau wrote: > On 24/04/06, tscher <[EMAIL PROTECTED]> wrote: > >>Hi Dr. Rousseau, >> >>thank you very much for your hint. I downloaded and installed your >>driver (no errors), removed the "original" SDI010 driver, and startet >>everything up. The driver loads nicely, and pcscd shows a response as >>soon as I place a card on the reader. >> >>Observation: The ATRs displayed are different, depending on which reader >>I place my card. > > > Strange. I have never seen this. You may have two different ATR for a > cold reset and a hot reset. But not for two cold reset. > > >>Now, I send the APDU "0xFF, 0xCA, 0x00, 0x00, 0x00" to retrieve the >>serial number of the card. The SCardTransmit() returns SCARD_S_SUCCESS, >>but only receives 2 bytes, which are the two status bytes. The status >>bytes values are "110" and "0". Does this indicate an Error ? > > > This is 6E 00 = Class not supported > 0xFF is an unusual class byte. Are you sure of this value? > > >>(When I do this with the Omnikey, I get 6 bytes - 4 bytes UID + 2 status >>bytes. The Status bytes are "90" and "0" on an successful operation.) > > c > > -- > Dr Ludovic Rousseau > > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle > > _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
