[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ms-smartcardddk
Subject:    Re: T=1 Cards
From:       Baiju Nair <bnair () OKI ! COM>
Date:       1997-12-19 21:59:30
[Download RAW message or body]


Klaus Shutz,
 Thank you for your hint. When I specified the protocol type it worked
fine.

>From the perspective of an user why should I tell the driver that the
command is of
protocol X. After all the protocol selected is different it is not going
to work.
After a card has been inserted , when it is reset, the driver knows the
protocol
used in the card or even I can select the protocol.

Since driver can handle it internally, what is the necessity of
expecting the protocol type
with the command header.

Baiju


> ----------
> From:         Klaus Schutz[SMTP:kschutz@MICROSOFT.COM]
> Reply To:     SmartCardDDK
> Sent:         Friday, December 19, 1997 4:33 PM
> To:   SmartCardDDK@DISCUSS.MICROSOFT.COM
> Subject:      Re: T=1 Cards
>
> Baiju,
>
> The only two reasons why you can get this error is:
>
> -       You didn't set the protocol field of the IO-request-header to
> SCARD_PROTOCOL_T1
> -       The current state of the reader is not SCARD_SPECIFIC
>
> Regarding the value of T1.IFSC it'll bet set in the function
> SmartcardT1Request.
> But you can check the value of CardCapabilities.T1.IFSC. It should
> show you
> the current
> value for the card you're using.
>
> Klaus U. Schutz
> Microsoft Corporation
>
>
>
>
>         -----Original Message-----
>         From:   Baiju Nair [SMTP:bnair@OKI.COM]
>         Sent:   Friday, December 19, 1997 12:27 PM
>         To:     SmartCardDDK@DISCUSS.MICROSOFT.COM
>         Subject:        T=1 Cards
>         Importance:     High
>
>         When I tried to transmit card command to a T=1 kind of card
>         SmartcardDeviceControl
>         returned STATUS_INVALID_DEVICE_STATE. But
>         ReaderCapabilities.CurrentState
>         value is 6. CardCapabilities.ProtocolSelected is 2. But
> T1.IFSC is
> 0,
>         Bytestosent is 0.
>         While resetting the card I'm calling
> SmartcardUpdateCardCapabilities. It
>         returned a success also.
>         What could be wrong?
>
>         This scenario was not there with beta2 DDK.
>
>         Baiju
>



[prev in list] [next in list] [prev in thread] [next in thread]