History Main / MillenniumBug

31st Dec '16 11:00:19 PM legoking831
Is there an issue? Send a Message


** The original ''[[VideoGame/BackyardSports Backyard Baseball]]'' also contains a [=Y2K=] bug. Upon beating the game, your name will be entered into the Hall of Fame with a date on the achievement as well, with the date written in a MM/DD/YY format. If an award is obtained and your computer's internal clock is any day past 1999, it will instead read as MM/DD/1YY. So, if you won it on, say, January 15 2003, it would read as 1/15/103. Curiously, the team photo doesn't suffer from any such bug, correctly displaying the year as "[=20XX=] Team Photo".

to:

** The original ''[[VideoGame/BackyardSports Backyard Baseball]]'' also contains a [=Y2K=] bug. Upon beating the game, your name will be entered into the Hall of Fame with a date on the achievement as well, with the date written in a MM/DD/YY format. If an award is obtained and your computer's internal clock is any day past 1999, it will instead read as MM/DD/1YY. So, if you won it on, say, January 15 2003, it would read as 1/15/103. Curiously, the team photo doesn't suffer from any such bug, correctly displaying the year as "[=20XX=] Team Photo". Even more oddly, the record book ''also'' doesn't have this problem, despite using the ''exact same date format'' as the Hall of Fame!
31st Dec '16 10:58:06 PM legoking831
Is there an issue? Send a Message

Added DiffLines:

** The original ''[[VideoGame/BackyardSports Backyard Baseball]]'' also contains a [=Y2K=] bug. Upon beating the game, your name will be entered into the Hall of Fame with a date on the achievement as well, with the date written in a MM/DD/YY format. If an award is obtained and your computer's internal clock is any day past 1999, it will instead read as MM/DD/1YY. So, if you won it on, say, January 15 2003, it would read as 1/15/103. Curiously, the team photo doesn't suffer from any such bug, correctly displaying the year as "[=20XX=] Team Photo".
6th Nov '16 3:35:06 AM LB7979
Is there an issue? Send a Message


* God calls Bill Gates, Boris Yeltsin and Bill Clinton for an urgent message. He informs them the world will end next week and they are to relay a message to their people. Yeltsin goes back to Russia and says there is [[GoodNewsBadNews bad news and terrible news]] -- the bad news is there really is a God, and the terrible news is the world will end next week. Clinton holds a press conference in Washington and says there is good news and bad news -- the good news is there really is a God, and the bad news is the world will end next week. Bill Gates returns to Microsoft and holds an full employee conference, saying he has good news and great news. The good news is God knows what a wonderful, important person he is, and the great news is they don't have to worry about fixing the millennium bug!

to:

* God calls [[UsefulNotes/MicrosoftWindows Bill Gates, Boris Yeltsin Gates]], UsefulNotes/BorisYeltsin and Bill Clinton UsefulNotes/BillClinton for an urgent message. He informs them the world will end next week and they are to relay a message to their people. Yeltsin goes back to Russia and says there is [[GoodNewsBadNews bad news and terrible news]] -- the bad news is there really is a God, and the terrible news is the world will end next week. Clinton holds a press conference in Washington and says there is good news and bad news -- the good news is there really is a God, and the bad news is the world will end next week. Bill Gates returns to Microsoft and holds an full employee conference, saying he has good news and great news. The good news is God knows what a wonderful, important person he is, and the great news is they don't have to worry about fixing the millennium bug!
28th Oct '16 3:27:30 PM WillKeaton
Is there an issue? Send a Message


Supposedly, on the first of January, 2000, the world was going to be destroyed by a computer glitch named the 'Millennium Bug' ([[IHaveManyNames also referred to as '[=Y2K=]' or the 'Year 2000 problem']]) whereby numerous computer systems would think the year was 1900 instead of 2000, resulting in planes falling out of the sky, satellites going wrong and [[ArsonMurderAndJaywalking all the]] [[Series/RedDwarf calculators going to silicon heaven]]. (Most of the actual problems were just cosmetic, such as programs displaying the year after "1999" as [[http://catless.ncl.ac.uk/Risks/20.72.html "19100"]], or desktop internal clocks resetting to 1981 as a crash-preventing exception).

to:

Supposedly, on the first of January, 2000, the world was going to be destroyed by a computer glitch named the 'Millennium Bug' ([[IHaveManyNames also referred to as '[=Y2K=]' or the 'Year 2000 problem']]) whereby numerous computer systems would think the year was 1900 instead of 2000, resulting in planes falling out of the sky, satellites going wrong and [[ArsonMurderAndJaywalking all the]] [[Series/RedDwarf calculators going to silicon heaven]]. (Most of the actual problems were just cosmetic, such as programs displaying the year after "1999" as [[http://catless.ncl.ac.uk/Risks/20.72.html "19100"]], "19100,"]] or desktop internal clocks resetting to 1981 as a crash-preventing exception).
28th Oct '16 3:26:31 PM WillKeaton
Is there an issue? Send a Message


* The first generation Zune, Microsoft's competitor to the [=iPod=], was hit by a Y2K-esque bug when the date rolled over to December 31, 2008[[note]]the 366th day of a leap year[[/note]], causing the music player to instantly lock up and crash, and remain unusable till the device was hard restarted, the batteries drained, or the date rolled over again.

to:

* The first generation Zune, Microsoft's competitor to the [=iPod=], was hit by a Y2K-esque bug when the date rolled over to December 31, 2008[[note]]the 2008,[[note]]the 366th day of a leap year[[/note]], year,[[/note]] causing the music player to instantly lock up and crash, and remain unusable till the device was hard restarted, the batteries drained, or the date rolled over again.
28th Oct '16 3:23:50 PM WillKeaton
Is there an issue? Send a Message


* There was also ''[[http://www.imdb.com/title/tt0776740/ [=Y2K=] Year to Kill]]'', an AfterTheEnd movie that goes back and forth between SoBadItsGood and utterly awful.

to:

* There was also ''[[http://www.imdb.com/title/tt0776740/ [=Y2K=] Year to Kill]]'', Kill,]]'' an AfterTheEnd movie that goes back and forth between SoBadItsGood and utterly awful.
28th Oct '16 3:23:25 PM WillKeaton
Is there an issue? Send a Message


Funnily enough, just when people started to relax when the 1999-2000 transition came to pass and nothing really major happened to computers across the globe, something actually did come along and wreak havoc on computers worldwide: the ILOVEYOU virus, or the "Love Bug" as it came to be misremembered. For the sequel to the Bug itself, watch for the [[http://en.wikipedia.org/wiki/Year_2038_problem Year 2038 problem]] (when the [-UsefulNotes/{{UNIX}}-] system time integer exhausts its [[UsefulNotes/BinaryBitsAndBytes 32 bits]]), coming soon to a computer near you. Fortunately, by that point, we will certainly be using 64-bit time[[note]]And we'll not have to worry about this issue until the year [[TimeAbyss 292,277,026,596]][[/note]]; however, many embedded systems still use 32-bit time and will continue to do so for years -- maybe until 2038. Considering the previous panic, though, it is unlikely companies will let it come that far by then.

to:

Funnily enough, just when people started to relax when the 1999-2000 transition came to pass and nothing really major happened to computers across the globe, something actually did come along and wreak havoc on computers worldwide: the ILOVEYOU virus, or the "Love Bug" as it came to be misremembered. For the sequel to the Bug itself, watch for the [[http://en.wikipedia.org/wiki/Year_2038_problem Year 2038 problem]] (when the [-UsefulNotes/{{UNIX}}-] system time integer exhausts its [[UsefulNotes/BinaryBitsAndBytes 32 bits]]), coming soon to a computer near you. Fortunately, by that point, we will certainly be using 64-bit time[[note]]And time;[[note]]And we'll not have to worry about this issue until the year [[TimeAbyss 292,277,026,596]][[/note]]; 292,277,026,596.]][[/note]] however, many embedded systems still use 32-bit time and will continue to do so for years -- maybe until 2038. Considering the previous panic, though, it is unlikely companies will let it come that far by then.
22nd Oct '16 12:17:31 AM Morgenthaler
Is there an issue? Send a Message

Added DiffLines:

* [=Y2K=] is referenced in the Deltron 3030 song "Virus":
-->I want to develop a super virus\\
better by far than the old [=Y2K=].\\
This 3030 the time of global unification.
20th Oct '16 5:22:03 AM FuzzyBoots
Is there an issue? Send a Message

Added DiffLines:

* This is thought to be the cause of worldwide loss of broadcast power and thereby communications in ''Literature/TheDireSaga''. [[spoiler:It's actually engineered by a group of artificial intelligences who were attempting to pin down a separate set of artificial intelligences to be killed.]]
31st Aug '16 1:00:40 AM B4ULoveShine
Is there an issue? Send a Message

Added DiffLines:

*''VideoGame/DanceDanceRevolution'' 3rdMIX gave us End of the Century, complete with line such as, "Some people think the Year 2G is so [scary], let's wait and see/The World will [shut] down, most won't admit".
**Yes, DDR 3rdMIX was released in 1999.
This list shows the last 10 events of 221. Show all.
http://tvtropes.org/pmwiki/article_history.php?article=Main.MillenniumBug