Page history

DavidB4-bot

→‎Legacy of Y2K: HTTP --> HTTPS #2, replaced: http://www.washingtonexaminer.com → https://www.washingtonexaminer.com

DavidB4-bot

→‎External links: HTTP --> HTTPS [#1], replaced: http://www.cnn.com → https://www.cnn.com

1990'sguy

→‎Legacy of Y2K: Add.

DavidB4-bot

Spelling/Grammar Check, typos fixed: 1990's → 1990s (5)

DavidB4-bot

clean up

JDano

better caption

JDano

add photo

JDano

clean up

TheAmericanRedoubt

Added hyperlinks and Proof Read and Categories and See Also

ArthurA

small correction -- the Unix Y2K38 problem only affects 32 bit machines; 64 bit computers do not have a 2038 issue.

JTitor

→‎Legacy of Y2K

Taj

adding references, category

NathanG

wikify

DinsdaleP

no edit summary

DinsdaleP

→‎Approaches to Y2K Remediation

DinsdaleP

no edit summary

DinsdaleP

Cointinued the expansion of the article

DinsdaleP

no edit summary

DinsdaleP

General cleanup and clarification of the issue

DinsdaleP

Added commentary and a source for cost info

Ed Poor

tens of billions of dollars were spent converting computer programs to handle four-digit years

Ed Poor

something had to be done

Ed Poor

Y2K moved to Y2K problem

Ed Poor

With memory as expensive as it was in the early days of modern computing, it was a common practice to save storage space by using two-digit years.

Ed Poor

New page: The '''Y2K''' problem was identified in the late 1990s by computer scientists.