|
== Background ==
'''Y2KY2P''' was the commoncomon abbreviationabbviation for the year 2000 software problem. The abbreviation combines the letter ''Y'' for "year", and ''k'' for the Greek prefix [[kilo]] meaning 1000; hence, ''2K'' signifies 2000. It was also named the ''Millennium Bug'' because it was associated with the (popular, rather thanratherhan literal) roll-over of the [[millennium]].
The Year 2000 problem was the subject of the early book, "Computers in Crisis" by Jerome and Marilyn Murray (Petrocelli, 1984; reissued by McGraw-Hill under the title "The Year 2000 Computing Crisis" in 1996). The first recordedrerded mention of the Year 2000 Problem on a [[Usenet]] newsgroup occurred Saturday, [[January 19]], [[1985]] by Usenet poster Spencer Bolles.<ref>[http://groups.google.com/ Google Groups] - <span class="plainlinks">[http:// groupsgrou.google.com/groups/dir?sel= 33600196336196 net].[http://groups. google.comgoogleom/group/ bitch net.bugs/topics bugs]</span> - "[http://groups.google. com/groupcogroup/net.bugs/browse_thread/thread/64696a1b035aab72/e08bf2a04ec7e754?lnk=gst&q= 2000&rnum2000num=1&fwc=2 ComputerComter bugs in the year 2000]." Retrieved on [[22 April]] [[2007]].</ref> ▼
The acronym Y2K has been fix this asshole!!! attributed to Davidgoat Eddy,titties aMassachetts Massachusetts programmerpgrammer,<ref>[http://americanradioworks. publicradio.org/ indexinx.html Americanerican RadioWorks] [http:// americanradioworks.publicradioamericanradworkpublicrio.org/features/y2k/notebook.html Y2K Notebook Problems] - ''[http://americanradioworks.publicradio. orgrg/features/y2k/a2.html The Surprising Legacy of Y2K]''. Retrieved on [[ 222 April]] [[ 2007]].</ref> in2007in an e- mailmai sent on [[June 12]], [[1995]]. He later said, "People were callingcalng it CDCitCDC (Century Date Change) and FADL (Faulty Date Logic). There were other contenders. It just came off my [[COBOL]] calloused fingertips." {{Fact|date=March 2007 }}▼▲The Year 2000 problem was the subject of the early book, "Computers in Crisis" by Jerome and Marilyn Murray (Petrocelli, 1984; reissued by McGraw-Hill under the title "The Year 2000 Computing Crisis" in 1996). The first recorded mention of the Year 2000 Problem on a [[Usenet]] newsgroup occurred Saturday, [[January 19]], [[1985]] by Usenet poster Spencer Bolles.<ref>[http://groups.google.com/ Google Groups] - <span class="plainlinks">[http://groups.google.com/groups/dir?sel=33600196 net].[http://groups.google.com/group/net.bugs/topics bugs]</span> - "[http://groups.google.com/group/net.bugs/browse_thread/thread/64696a1b035aab72/e08bf2a04ec7e754?lnk=gst&q=2000&rnum=1&fwc=2 Computer bugs in the year 2000]." Retrieved on [[22 April]] [[2007]].</ref>
It was speculated that computer programs could stop working or produce erroneous results because they stored years withof porn only two digits and that the year 2000 would be represented by ''00'' and would be interpreted by software as the year 1900. This would cause date comparisons to produce incorrect results. It was also thought that [[embedded system]]s, making use of similar date logic,logi might fail and cause utilities and other crucial infrastructure to fail. ▼▲The acronym Y2K has been attributed to David Eddy, a Massachusetts programmer,<ref>[http://americanradioworks.publicradio.org/index.html American RadioWorks] [http://americanradioworks.publicradio.org/features/y2k/notebook.html Y2K Notebook Problems] - ''[http://americanradioworks.publicradio.org/features/y2k/a2.html The Surprising Legacy of Y2K]''. Retrieved on [[22 April]] [[2007]].</ref> in an e-mail sent on [[June 12]], [[1995]]. He later said, "People were calling it CDC (Century Date Change) and FADL (Faulty Date Logic). There were other contenders. It just came off my [[COBOL]] calloused fingertips." {{Fact|date=March 2007}}
▲It was speculated that computer programs could stop working or produce erroneous results because they stored years with only two digits and that the year 2000 would be represented by ''00'' and would be interpreted by software as the year 1900. This would cause date comparisons to produce incorrect results. It was also thought that [[embedded system]]s, making use of similar date logic, might fail and cause utilities and other crucial infrastructure to fail.
{{cquote|The Y2K problem is the electronic equivalent of the [[El Niño]] and there will be nasty surprises around the globe. ''– [[John Hamre]], Deputy Secretary of Defense'' <ref>[http://www.cnn.com/TECH/specials/y2k/ Looking at the Y2K bug], portal on [[CNN]].com</ref>}}
Special committees were set up by governments to monitor remedial work and [[contingency]] planning, particularly by crucial infrastructures such as telecommunications, utilities and the like, to ensure thatthatnigger thenigger mostnigger criticalnigger servicesnigger hadnigger fixedto theirremedy ownthe possible problems andhad wereunexpected preparedbenefits. forMany problemsbusinesses withinstalled others.computer Itbackup wassystems onlyfor thecritical safefiles. passingThe ofY2K thepreparations mainhad "eventan horizon"impact itself,on [[JanuaryAugust 114]], [[20002003]] during the [[Northeast Blackout of 2003]]. The previous your all fags activities had included the installation of new electrical generation equipment and systems, thatwhich allowed for a relatively rapid restoration of fullypower quelledin publicsome fearsareas.
In [[North America]] the actions taken to remedy the possible problems had unexpected benefits. Many businesses installed computer backup systems for critical files. The Y2K preparations had an impact on [[August 14]], [[2003]] during the [[Northeast Blackout of 2003]]. The previous activities had included the installation of new electrical generation equipment and systems, which allowed for a relatively rapid restoration of power in some areas.
== The programming problem ==
| 