News for hackers. Stuff that matters.
Re:2010 bug hits millions of Germans by Timothee on Thursday January 07, 2010 @01:43PM (#1037697)
Does anyone know what the nature of the bug is? The article lacked on this aspect unfortunately.
[ Parent | on HN ]
Re:2010 bug hits millions of Germans by sp332 on Thursday January 07, 2010 @02:56PM (#1037896)
I thought this was discussed earlier this week, but I can't find a link anywhere. The representation of the date is ambiguous about decimal/hexadecimal. So some devices are reading "10" as equal to 16, yielding the year 2016 instead of 2010.
[ Parent | on HN ]
Re:2010 bug hits millions of Germans by aarongough on Thursday January 07, 2010 @02:40PM (#1037857)
Perhaps they thought they would improve on the 2 digit method of representing years, and used a single digit method instead?

ie: 2009(9) -> 2010(0)

I would be pretty sad if it was a bug as obvious as this though. No idea what the real bug is likely to be...

[ Parent | on HN ]
Re:2010 bug hits millions of Germans by ugh on Thursday January 07, 2010 @01:52PM (#1037725)
None of the many German articles I read about the topic mentioned the exact nature of the bug.
[ Parent | on HN ]
Re:2010 bug hits millions of Germans by ABrandt on Thursday January 07, 2010 @02:13PM (#1037787)
My first guess would be that the software somehow recognized "2010" as "1910". Not sure exactly what dating structure would lead to this though.
[ Parent | on HN ]
Re:2010 bug hits millions of Germans by please on Thursday January 07, 2010 @02:30PM (#1037832)
as a workaround one can put a strip of tape over the chip, that way the magnetic strip on the other side gets used.
[ Parent | on HN ]
Re:2010 bug hits millions of Germans by 83457 on Thursday January 07, 2010 @03:33PM (#1037972)
The dreaded Y2.01K Bug
[ Parent | on HN ]
Re:2010 bug hits millions of Germans by zb on Thursday January 07, 2010 @06:21PM (#1038316)
Actually, Y2k01. Engineers don't use decimal points - it's too easy for them to disappear during copying.
[ Parent | on HN ]