Search results

Page title matches

• Y2K and 2038
  #REDIRECT [[2697: Y2K and 2038]]
  32 bytes (4 words) - 18:11, 11 November 2022
• 2697: Y2K and 2038
  | title = Y2K and 2038 The Y2K bug, or more formally, the {{w|year 2000 problem}}, was the computer errors
  5 KB (810 words) - 06:22, 9 May 2023

Page text matches

• 887: Future Timeline
  | 32-bit timestamps roll over, causing Y2K-level chaos ::32-bit timestamps role over, causing Y2K-level chaos
  51 KB (7,042 words) - 20:12, 1 February 2024
• 607: 2038
  ...on computers means the bug could affect many more vital systems, but with Y2K passing by relatively uneventfully especially in light of the hype that pre :Cueball: Remember Y2K? This could be even ''worse!''
  3 KB (417 words) - 21:47, 13 December 2023
• 1340: Unique Date
  ...long-term benefits, rather than only the coming years or decades. The {{w|Y2K problem}} was due to using only two digits to store the year, which would h
  4 KB (676 words) - 10:26, 10 November 2023
• 1883: Supervillain Plan
  ...ical year numbering|astronomical calendars}}, or the {{w|Year 2000 problem|Y2K}} and {{w|Year 2038 problem|year 2038}} problem. Nevertheless in this comic
  7 KB (1,089 words) - 21:02, 4 May 2022
• List of all comics
  {{comicsrow|2697|2022-11-11|Y2K and 2038|y2k and 2038 2x.png}}
  28 KB (3,781 words) - 17:53, 26 April 2024
• 2661: Age Milestone Privileges
  ...hat this limit would be reached. Computers using such systems would have a Y2K-analogous bug once someone actually reached 128 years old, where anomalous
  18 KB (2,976 words) - 14:28, 16 April 2024
• Y2K and 2038
  #REDIRECT [[2697: Y2K and 2038]]
  32 bytes (4 words) - 18:11, 11 November 2022
• 2697
  #REDIRECT [[2697: Y2K and 2038]]
  32 bytes (4 words) - 18:11, 11 November 2022
• 2697: Y2K and 2038
  | title = Y2K and 2038 The Y2K bug, or more formally, the {{w|year 2000 problem}}, was the computer errors
  5 KB (810 words) - 06:22, 9 May 2023