Technical cause[ edit ] The latest time that can be represented in Unix's signed bit integer time format is This is caused by integer overflow.
Background[ edit ] Y2K is a numeronym and was the common abbreviation for the year software problem. The abbreviation combines the letter Y for "year", and k for the SI unit prefix kilo meaning ; hence, 2K signifies It was also named the "Millennium Bug" because it was The computer bug problem y2k with the popular rather than literal roll-over of the millenniumeven though most of the problems could have occurred at the end of any ordinary century.
There were other contenders.
Y2K just came off my fingertips. Since programs could simply prefix "19" to the year of a date, most programs internally used, or stored on disc or tape, data files where the date format was six digits, in the form MMDDYY, MM as two digits for the month, DD as two digits for the day, and YY as two digits for the year.
The biggest issue, like the Y2K bug, is that computer systems that control crucial infrastructure stop working all at the same time. Planes crashing out of the sky was the common scaremongering. Y2K computer bug turns teen criminals into senior citizens. Reports of sexual assault on an 83 year old woman by an 80 year old man, and two missing 'youths' of ages 83 and 84 were among the flawed reports given by the faulty system, which caused the system to read year as year , and interpret the year of birth of the parties involved as their ages. The year problem is caused by bit processors and the limitations of the bit systems they power. The processor is the central component that drives all computers and computing devices. It crunches the numbers and performs calculations that allow programs to run.
As space on disc and tape was also expensive, this also saved money by reducing the size of stored data files and data bases. Some such programs could not distinguish between the year and the year Other programs tried to represent the year as This could cause a complete failure and cause date comparisons to produce incorrect results.
Some embedded systemsmaking use of similar date logic, were expected to fail and cause utilities and other crucial infrastructure to fail.
Some warnings of what would happen if nothing was done were particularly dire: While some commentators and experts argued that the coverage of the problem largely amounted to scaremongering it was only the safe passing of the main "event horizon" itself, 1 Januarythat fully quelled public fears.
Some experts who argued that scaremongering was occurring, such as Ross AndersonProfessor of Security Engineering at the University of Cambridge Computer Laboratoryhave since claimed that despite sending out hundreds of press releases about research results suggesting that the problem was not likely to be as big a problem as some had suggested, they were largely ignored by the media.
The need for bit conservation[ edit ] "I'm one of the culprits who created this problem. I used to write those programs back in the s and s, and was proud of the fact that I was able to squeeze a few elements of space out of my program by not having to put a 19 before the year.
Back then, it was very important. We used to spend a lot of time running through various mathematical exercises before we started to write our programs so that they could be very clearly delimited with respect to space and the use of capacity.
It never entered our minds that those programs would have lasted for more than a few years. As a consequence, they are very poorly documented. If I were to go back and look at some of the programs I wrote 30 years ago, I would have one terribly difficult time working my way through step-by-step.
Many tricks were used to squeeze needed data into fixed-field character records. Saving two digits for every date field was significant in this effort. In the s, computer memory and mass storage were scarce and expensive. Early core memory cost one dollar per bit. Programs often mimicked card processing techniques.
Over time the punched cards were converted to magnetic tape and then disc files, but the structure of the data usually changed very little.The year problem is caused by bit processors and the limitations of the bit systems they power.
The processor is the central component that drives all computers and computing devices. It crunches the numbers and performs calculations that allow programs to run. The Year problem relates to representing time in many digital systems as the number of Just like the Y2K problem, the Year problem is caused by insufficient capacity of the chosen storage unit Embedded systems that use dates for either computation or diagnostic logging are most likely to be affected by the bug.
The biggest issue, like the Y2K bug, is that computer systems that control crucial infrastructure stop working all at the same time. Planes crashing out of the sky was the common scaremongering. The Y2K (Year ) problem came to exist culturally because of a fear that computers would fail when their clocks were meant to update to January 1, The cause of the Y2K problem is pretty simple.
Until recently, computer programmers have been in the habit of using two digit placeholders for the year portion of the date in their software. For example, the expiration date for a typical insurance policy or credit card is stored in a computer file in MM/DD/YY format (e.g.
- 08/31/99). The Y2K (Year ) problem came to exist culturally because of a fear that computers would fail when their clocks were meant to update to January 1,