Regarding point 4, APIs sometimes return more general Win32 errors, like
this one.
They usually come from the reader drivers. Winerror.h is where you can
find them.
In this case 6f9h = 1785 => ERROR_UNRECOGNIZED_MEDIA
The reader doesn't recognize your card.

-----Original Message-----
From: CSE KITS [mailto:kitscseYAHOO.COM]
Sent: Sunday, November 04, 2001 8:52 AM
To: SmartCardSDKDISCUSS.MICROSOFT.COM
Subject: Reg CLASS byte

Hi,
    There are a few things I would like to clarify.

    1. What is the difference between CLA byte 0X and
   CLA bytes in the range 'B0' to 'CF'. According
   to the standard these are described as 'structure
of
   command and response according to this part of
ISO/IEC 7816'. Does that mean that they are in no way different from
the CLA = 0X case

   2. For the GET response command, what should be
the output if GET response is given after some other
command which isn't of CASE 4 (Both input and Output).
 Say a successful READ RECORD command is issued which
has returned all the given Bytes. Now should the GET
Response command following return, Invalid length
error or should it return the bytes previously
returned. My question is in what cases should the
card remember the output to be given for the
subsequent GET Response command.

   3. Some commands are described as having Lc field
as empty or length of the subsequent data field.
Does that mean that the field should be sent with
value 00 or that the field should not be present in
TPDU? (For eg. verify/Select file etc)

   4. Where can I get the status codes returned by SCardTransmit
command and other functions in general. For example I got 6f9 (hex) as
status sometimes but I couldn't decipher that from the codes given in
scarderr.h file

Thank you,
regards,
kits.

__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]