Hello,
i'm new in this list because i'm intrested in this smartcard theme, but
also because i've a very actual problem with
towitoko2.0.2 driver and pcsc-lite-0.8.4. The problem was already
discussed in the "MUSCLE memory-cards and muscle?"-thread between the
18.01.2001 and the 21.01.2001. I
Thomas Schmidt wrote:
Hello,
i'm new in this list because i'm intrested in this smartcard theme, but
also because i've a very actual problem with
towitoko2.0.2 driver and pcsc-lite-0.8.4. The problem was already
discussed in the "MUSCLE memory-cards and muscle?"-thread between the
--- Andreas Schwier [EMAIL PROTECTED]
escribi: Hello
On Sam, 20 Jan 2001, you wrote:
I never really understood the reason for
handling
the transmission
protocols at application level. For the
application
it should not matter, if
the card uses T=0, T=1 or a memory card
Hello,
--- Andreas Schwier [EMAIL PROTECTED]
escribi: Hi Dave
I never really understood the reason for handling
the transmission
protocols at application level. For the application
it should not matter, if
the card uses T=0, T=1 or a memory card interface,
What happens if card supports
Hello,
I would put my hand in the fire, and guess that the
following happens with memory cards and protocol RAW:
* The pcsc daemon calls the ifdhandler function
IFDHControl().
* The driver maps the command to a CT command, instead
of a ICC command.
* 6E 00 is returned because this is the CT-BCS
On Fri, Jan 19, 2001 at 01:33:12PM +0800, [EMAIL PROTECTED] wrote:
Hi,
Hi Christian.
I got the same problem.
I'm using a chip drive driver, a SLE 4428 as a smart card and
towitoko2.0.2, and pcsc-lite-0.8.4.
I am using exactly the same configuration, just the smart card is no-name.
And I got
Hi,
That is probably a bug in pcscd in winscard.c SCardTransmit PROTOCOL_RAW
automatically maps to IFDHControl instead of Transmit. Anyone have
suggestions on how I can either create a new PROTOCOL_MEMORY or something.
Dave
*
David
Hi Dave
I never really understood the reason for handling the transmission
protocols at application level. For the application it should not matter, if
the card uses T=0, T=1 or a memory card interface, it should just handle
command and response APDU's. I suggest to introduce a PROTOCOL_GENERIC,
On Tue, Jan 16, 2001 at 10:10:13AM -, Guillaume LAISNEY wrote:
You can access any memory card thru PCSC-lite sending APDU-like
commands with SCardTransmit and ISO commands (look at ISO 7816-4).
Check that your reader's driver is compliant with the card you want to
access to. If so,
Hello,
You can see the sample code in the tester app that
comes with the towitoko driver at
http://www.geocities.com/cprados.
Also some time ago I found two interesanting apps that
uses CT-API to access memory smartcards, that I would
like to introduce in this mailing list:
smartcard:
On Tue, Jan 16, 2001 at 10:10:13AM -, Guillaume LAISNEY wrote:
You can access any memory card thru PCSC-lite sending APDU-like commands with
SCardTransmit and ISO commands (look at ISO 7816-4).
Check that your reader's driver is compliant with the card you want to access to. If
so, you
11 matches
Mail list logo