Re: MUSCLE 61XX in Microsoft PC/SC implementation

2001-08-02 Thread Carlos Prados
Hi, --- Axel Heider <[EMAIL PROTECTED]> wrote: > Hi, > > some time ago I got this response from Eric Perlin > from > Microsoft about their PC/SC implementation: > > > This is no work for the driver. This needs to be > handled > > by the app. I recommend a little layer on top of > > SCardTr

Re: MUSCLE 61XX in Microsoft PC/SC implementation

2001-08-02 Thread David Corcoran
Hello, Maybe then the ICC Service Proviver should be intelligent enough to send a Get Response when a 61 XX is returned and carry on with other transactions when the full data is returned. Dave *** Unix Smart Card Developers - M.U.S.C.

Re: MUSCLE Re: 61 XX

2001-08-02 Thread Anna Erika Suortti
On Thu, 02 Aug 2001 09:19:53 +0200 Laurent Boulard <[EMAIL PROTECTED]> wrote: > David Corcoran wrote: > > >Hello, > > > >Points well taken. It seems unanimous that the driver should take care > of > >Get Response. I shall update the IFD Handler documentation to > reflect > >this. Thank you so

MUSCLE Reflex 72 problem (additional info)

2001-08-02 Thread Nikolay Stanchenko
>Hello! >I have just compiled and installed new Reflex 72 driver with pcsc-lite-0.9.3. (I use >Mindrake 7.2 Linux) >I connected to card normally, but when I transmit to the card any command I get >status code 64A0 (undocumented). >Where is problem? >Thank you! >Nikolay Stanchenko >JSC TKK A

MUSCLE Reflex 72 drivers

2001-08-02 Thread Nikolay Stanchenko
Hello! I have just compiled and installed new Reflex 72 driver with pcsc-lite-0.9.3. (I use Mindrake 7.2 Linux) I connected to card normally, but when I transmit to the card any command I get status code 64A0 (undocumented). Where is problem? Thank you! Nikolay Stanchenko JSC TKK **

MUSCLE 61XX in Microsoft PC/SC implementation

2001-08-02 Thread Axel Heider
Hi, some time ago I got this response from Eric Perlin from Microsoft about their PC/SC implementation: > This is no work for the driver. This needs to be handled > by the app. I recommend a little layer on top of > SCardTransmit to hide the pecularities of T=0 (vs T=1). I think the the MU

No Subject

2001-08-02 Thread David Corcoran
Hello, Sorry for the mistake. I accidentally posted my majordomo password to the site while trying to administer some users. After about 1/2 hour I finally figured out how to configure majordomo again and luckily no-one stole my password. I will have to be more careful I did change passwo

Re: MUSCLE Is 61xx handled in your driver?

2001-08-02 Thread Peter Tomlinson
The clean way to organise this is: (a) An application in the terminal issues APDUs (b) The software layer receiving the APDU knows whether the card is being operated with T=0 or T=1, and sends information down to the card driver as appropriate; if T=0 and a case 4 APDU, the APDU is split into a

Re: MUSCLE GPR400 ifd and T=0 vs T=1 from the driver perspective

2001-08-02 Thread hariharan swaminathan
Hi, Check out this link: http://www.corbina.ru/~versia23/ALLSAT/SatXpress/SmartCard/Iso7816-4.htm This has some useful info about T=1 and T=0 protocols. You can check the source code for Infineer Smartcard drivers ( available under Source drivers in download page in www.linuxnet.com ). I fol

Re: MUSCLE Is 61xx handled in your driver?

2001-08-02 Thread Peter Tomlinson
CLA INS P1 P2 Lc Le in 7816-4 speak (section 5.3.1 Fig 3) Peter T Bristol UK - Original Message - From: "David Corcoran" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 31, 2001 9:26 PM Subject: Re: MUSCLE Is 61xx handled in your driver? > I think you should handle the

Re:MUSCLE 61XX in Microsoft PC/SC implementation

2001-08-02 Thread Sergio Rdz. Parra
Enviado Thu, 02 Aug 2001 14:47:35 +0200 Axel Heider <[EMAIL PROTECTED]>Escribió: >Hi, > >some time ago I got this response from Eric Perlin from >Microsoft about their PC/SC implementation: > ... Since when we use Microsoft as a reference??? Nothing personal, but I would listen to a Gem

AW: MUSCLE Re: 61 XX

2001-08-02 Thread Frank Thater
> > One question: How does the reader know which CLA byte to use? > In our driver for the ECO5000 we use the CLA byte of the former used command apdu. For example: The command apdu looks like this: 0x00 0xC0 0x00 0x01 0x02 0x3f 0x00 If the driver recognizes that a "Get Reponse" is neccessary he

Re: MUSCLE Is 61xx handled in your driver?

2001-08-02 Thread Andreas Schwier
> In the perfect world yes ! but, sadly, people sometimes doesn't follow > correctly the ISO7816 or misunderstood it. I have cards (W4SC as an > example) which send back a GET RESPONSE even for a APDU without data. > This is really annoying as I have to modify my application to take care > of this

Re: MUSCLE Re: 61 XX

2001-08-02 Thread Laurent Boulard
David Corcoran wrote: >Hello, > >Points well taken. It seems unanimous that the driver should take care of >Get Response. I shall update the IFD Handler documentation to reflect >this. Thank you so much for your suggestions. > Jim rees said: I agree that the application should not hav