The most important such glitch occurred in Germany, where upwards of 20 million bank cards became unusable, and with Citibank Belgium, whose digipass customer identification chips stopped working. Other systems affected include EFTPOS terminals, and the PlayStation 3 (except the Slim model).
#Sas date calculator software
Windows Mobile was the first software reported to have been affected by this glitch in some cases WM6 changed the date of any incoming SMS message sent after 1 January 2010 from the year 2010 to 2016. Thus a BCD 10 16 interpreted as a hexadecimal encoding erroneously represents the decimal number 16.įor example, the SMS protocol uses BCD encoding for dates, so some mobile phone software incorrectly reported dates of messages as 2016 instead of 2010. But the decimal number 10 is encoded in hexadecimal as 0A 16 and in BCD as 10 16.
The numbers 0 through 9 are encoded in both hexadecimal and BCD as 00 16 through 09 16. The main source of problems was confusion between hexadecimal number encoding and BCD encodings of numbers. This was dubbed by some in the media as the "Y2K+10" or "Y2.01k" problem. Some systems had problems once the year rolled over to 2010. Systems that used a string of length 9 characters to record the time as seconds since the Unix epoch had issues reporting times beyond the one-billionth second after the epoch on 9 September 2001 at 01:46:40 (the "billenium"). Such a program will not be able to correctly deal with years beyond 2068.įor applications required to calculate the birth year (or another past year), such an algorithm has long been used to overcome the Year 1900 problem, but it has failed to recognise people over 100 years old. įor example, a program may have been changed so that it treats two-digit year values 00–68 as referring to 2000 through 2068, and values 69–99 as referring to 1969 through 1999. Some programs were made Y2K-compliant by continuing to use two digit years, but picking an arbitrary year prior to which those years are interpreted as 20 xx, and after which are interpreted as 19 xx. In the last few months before the year 2000, two other date-related milestones occurred that received less publicity than the then-impending Y2K problem.įollow-on problems caused by certain temporary fixes to the Y2K problem will crop up at various points in the 21st century.
The Domain/OS clock, which is based on the number of 4-microsecond units that has occurred since 1 January 1980, rolled past 47 bits on 2 November 1997, rendering unpatched systems unusable. Values on and after this day do not fit into a signed 16-bit integer, but overflow and return negative values. On 18 September 1989, these programs began to fail, the date being exactly 32,768 (2 15) days since the zero date. Some mainframe programs were written to encode dates as the number of days since a 'zero date' of 1 January 1900, storing them as signed 16-bit binary integers. This was recognized when the later COS-310 operating system was developed, and dates were recorded differently. The Digital Equipment Corporation OS/8 operating system for the PDP-8 computer used only three bits for the year, representing the years 1970 to 1977. There were numerous problems and crashes related to this bug while an alternative format was developed. On 4 January 1975, the 12-bit field that had been used for dates in the DECsystem-10 operating systems overflowed.
0 kommentar(er)
