On Fri, 8 Jan 2010 11:22:52 -0800, Charles Mills wrote: > >But isn't the problem being described backwards? Is the external symptom >expired cards not being recognized as expired, or is it valid cards being >treated as though expired? Assuming the latter, the problem would seem to be >not that an expiration date is being misinterpreted but rather that today's >date is being misinterpreted. The card "knows" it expires in 2010 but >"thinks" today's date is 8 January 2016. If so, you can't "fix" the machines >(other than to provide the mag stripe workaround), you have to "fix" the >cards by reprogramming or reissuing them. There's no "window" solution >possible; the only solution is fixing the chips. Am I wrong? > It's unlikely that the cards contain a crystal clock and a battery to run it. So, the ATM supplies the date, x'2010' to the card which misinterprets it as 2016 and reports itself as expired.
-- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
