The Y2K bug was a computer software flaw based on a time factor that, at the start of the year 2000, might have caused all manner of problems. Shannon O'Donnel experienced the hysteria that arose from this potential issue, although she noted that in the end, the bug caused no problems at all, failing to turn off even a single light bulb. (VOY: "11:59") This prediction was almost correct; a nuclear power plant in Japan had a monitoring computer go down briefly, and minor events elsewhere occurred, but nothing major.
| Attributes | Values |
|---|
| rdf:type
| |
| rdfs:label
| |
| rdfs:comment
| - The Y2K bug was a computer software flaw based on a time factor that, at the start of the year 2000, might have caused all manner of problems. Shannon O'Donnel experienced the hysteria that arose from this potential issue, although she noted that in the end, the bug caused no problems at all, failing to turn off even a single light bulb. (VOY: "11:59") This prediction was almost correct; a nuclear power plant in Japan had a monitoring computer go down briefly, and minor events elsewhere occurred, but nothing major.
- The Y2K bug (also known as the millennium bug or simply Y2K) was the result of a practice in early computer program design that caused some date-related processing to operate incorrectly for dates and times on and after between December 31, 1999 and January 1, 2000. This fear was fueled by the attendant press coverage and other media speculation, as well as corporate and government reports. People recognized that long-working systems could break down when the "...97, 98, 99..." ascending numbering assumption suddenly became invalid. Companies and organizations world-wide checked and upgraded their computer systems. Fear of the Y2K "event" caused some people to take extreme measures, such as stocking up on food and weapons. (MM: "TEOTWAWKI")
|
| Length
| |
| dcterms:subject
| |
| Controlled
| |
| Roar
| |
| dbkwik:god-zilla/p...iPageUsesTemplate
| |
| dbkwik:godzilla/pr...iPageUsesTemplate
| |
| dbkwik:memory-alph...iPageUsesTemplate
| |
| dbkwik:x-files/pro...iPageUsesTemplate
| |
| FirstAppearance
| |
| Name
| |
| Type
| |
| Caption
| - Y2K Bug in The Godzilla Power Hour
|
| Relationships
| |
| Weight
| |
| Allies
| |
| Height
| |
| Species
| |
| Enemies
| |
| Nicknames
| |
| Forms
| |
| abstract
| - The Y2K bug (also known as the millennium bug or simply Y2K) was the result of a practice in early computer program design that caused some date-related processing to operate incorrectly for dates and times on and after between December 31, 1999 and January 1, 2000. This fear was fueled by the attendant press coverage and other media speculation, as well as corporate and government reports. People recognized that long-working systems could break down when the "...97, 98, 99..." ascending numbering assumption suddenly became invalid. Companies and organizations world-wide checked and upgraded their computer systems. Fear of the Y2K "event" caused some people to take extreme measures, such as stocking up on food and weapons. (MM: "TEOTWAWKI") When January 1, 2000 finally did come around, though, there was no collapse of modern infrastructure. (TXF: "Millennium")
- The Y2K bug was a computer software flaw based on a time factor that, at the start of the year 2000, might have caused all manner of problems. Shannon O'Donnel experienced the hysteria that arose from this potential issue, although she noted that in the end, the bug caused no problems at all, failing to turn off even a single light bulb. (VOY: "11:59") This prediction was almost correct; a nuclear power plant in Japan had a monitoring computer go down briefly, and minor events elsewhere occurred, but nothing major.
|
![[RDF Data]](/fct/images/sw-rdf-blue.png)