--On Wednesday, July 09, 2003 12:09:30 -0700 Wan-Teh Chang <[EMAIL PROTECTED]> wrote: > Buffer length probably incorrect -- help len_out=200 write_bytes=195 > buffer_out[4]=0!
The egate driver has to parse the APDUs it transfers to figure out the size of the "data" part of the PDU, and whether or not there will be response data. The parsing is done somewhat crudely, and can get confused. In this case, however, (some of) the APDUs appear to be bogus. The data length in the APDU header is 0, but there is a payload. Depending on how the card responds to the command, the driver will either send the payload to the card or drop it on the floor. I suspect that the card never accepts the payload and responds with a 63XX SW. If your application is otherwise working, you can ignore the messages. _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
