Hello Francois, Hello Genaro,

A couple of points (hope maybe? :-) on memory cards support for OCF.

[EMAIL PROTECTED] (Fran�ois Leblanc) at ISS1 wrote:
>> I use GCR410 with PCSC and i want to access memory cards. On
>> connection PCSC read ATR response but in memory cards without ATR??? 
>> I get Exception.
>> [...] PC/SC Error SCardConnect return code = 80100066

Genaro Anzures wrote:
> In fact, PCSC only works with microprocessor cards (those using T=0
> and T=1 protocols), memory cards have its own synchronous protocols.
> So you better use the Gemplus API 4.3 that allows you to use both
> microprocessor and memory card types with a GCR410 reader.
> 

Yes, Genaro is right. Neither OCF 1.2 nor PC/SC 1.0 currently support
memory cards. The (historical) reason is I believe because most of
the available memory cards do not follow the relevant ISO norms
(which name I forgot), the situation is even worse than for
microprocessor cards :-). Usually, APIs and drivers written by a given
company will be able to access memory cards of ... the same company,
for example the Gemplus GCR API is able to access either microprocessor
cards (all types) or memory cards (only Gemplus). There are probably
other examples of APIs and drivers for memory cards using proprietary
protocols.

I'm not sure whether the memory card you want to use is following
the ISO specs or not, but in the latter case, or if you have the
detailed specs of its protocol, you can try the following:

1) If your card is ISO:

 - wait for the next version of PC/SC that is supposed to support the
   synchronous protocols. You can find whitepapers and presentations
   at http://www.pcscworkgroup.com/Library/Presentations.html but
   no implementation is currently available. (and if I understood
   well, it will be the driver's responsibility to do the job).

2) If you have the specs:

 - instead of using the OCF PC/SC wrapper, you can use the Gemplus
   pure Java driver for your GCR410 (GemplusCardTerminal) and write
   some code dedicated to your card protocol. This has been suggested
   on the mailing list by Jean-Pascal <[EMAIL PROTECTED]>
   the trick is to use a direct access method: 'sendTerminalCommand':

   Jean-Pascal wrote in:
   http://www.opencard.org/archive/opencard/0913.html
   <<
      I receive a lot of answers, thanks.
      Many of them tell me that it was impossible to read
      a GPM416 smart card because it's a memory card.
      I just succeed in by using the sendTerminalCommand method of
      GemplusCardTerminal class. if you want to take a look:
      I beleive that It could be better.
      If you have any comments about it, I enjoy it.
      begin 600 Card.java
      [...]
    >>
    I can send you the "Card.java" code by email in case you are
    interested (or see the URL above). Of course, if you use a card
    that is different from GPM416, you'll have to adapt his code to
    your card's protocol specs.

3) If your card is a Gemplus memory card:

 - also if the card you are using is a Gemplus one, a solution,
   as Genaro suggested, could be to use an OCF wrapper for the
   Gemplus GCR API just like IBM provides a wrapper to PC/SC. I also
   have an alpha version of this, so if you're interested... :-).

Hope it'll help.

Cheers,
Christophe.

 = The nice thing about standards is that there are so many =
 = of them to choose from.   -- Andrew S. Tanenbaum         =
--
-------------------------------------------------------------
[EMAIL PROTECTED] - Gemplus Research Lab
Phone: +33 4-42-36-57-83 | Disclaimer: I don't speak for Gemplus
Gemplus doesn't speak for me... it is better that way!
-------------------------------------------------------------


---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/

! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
!                           [EMAIL PROTECTED]
! containing the word
!                           unsubscribe 
! in the body.

Reply via email to