Microsoft Windows CE 3.0  

T1_DATA

Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

The T1_DATAstructure is used by the Smart Card Driver Library for processing T1 I/O. It should not be directly modified by a driver.

typedef struct _T1_DATA {
UCHAR
InfSize;
ULONG
BytesReceived
;
ULONG
BytesSent
;
ULONG
BytesToSend
;
UCHAR
LastError
;
UCHAR
NAD
;
ULONG
PrevState
;
UCHAR
Resend
;
UCHAR
Resynch
;
UCHAR
SSN
;
ULONG
State
;
UCHAR
Wtx
;
} T1_DATA, *PT1_DATA;

Members

The following member is important for the driver:

InfSize
Current information field size that can be transmitted.
BytesReceived
Number of bytes already received from the smart card.
BytesSent
Number of bytes already sent to the smart card.
BytesToSend
Number of bytes remaining to send.
LastError
The T1 error code of the last block received.
NAD
The Node Address byte to be sent to the card.
PrevState
The state before an error occurred.
Resend
A resend counter.
Resynch
A resync counter.
SSN
The Send Sequence Number; either or 1 as defined in ISO 7816-3
State
The current state of the protocol.
Wtx
Contains the waiting time extension for a T=1 transmission. If nonzero, this is a multiplier for the block waiting time. Usually, the driver should time out if the block waiting time expires. Several smart card operations need longer time, so the smart card answers with a waiting time extension, and therefore the block waiting time must be multiplied with the Wtxvalue. Note that this value only applies as a waiting extension if the value is nonzero.

 Last updated on Tuesday, July 13, 2004

© 2004 Microsoft Corporation. All rights reserved. 500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.