"July is a blind date with summer", Happy July! @TRY3STEPS.COM
Dear Reader, If you use TRY3STEPS a lot, this message is for you. This incredible nonprofit organization helps the world with answers. We love you, we share answers. Your love helps us thrive. The more we give, the more we have! Thank you for inspiring us. (Secure PayPal)

*Everything counts! No minimum transaction limit!
Stay Updated with the World! Subscribe Now:: YouTube.com/c/Try3Steps
Say Hello to Try3Steps Group! Join Now:: GoogleGroup@Try3Steps

Search Another Question

Showing posts with label affecting. Show all posts
Showing posts with label affecting. Show all posts

Apr 9, 2019

[Ans] What "bug" was supposed to start affecting computers on January 1, 2000?

Step 1 : Introduction to the question "What "bug" was supposed to start affecting computers on January 1, 2000?"



The Y2K bug was a computer flaw that was projected to create havoc on computer networks when dealing with dates beyond December 31, 1999. The flaw, faced by computer programmers and users all over the world on January 1, 2000, is also known as the "millennium bug." As the year 2000 approached, computer programmers realized that computers might not interpret 00 as 2000, but as 1900. After more than a year of international alarm, feverish preparations, and programming corrections, few major failures occurred in the transition from December 31, 1999, to January 1, 2000.

[Answer] What "bug" was supposed to start affecting computers on January 1, 2000?

Step 1 : Introduction to the question "What "bug" was supposed to start affecting computers on January 1, 2000?"



...The Y2K bug was a computer flaw that was projected to create havoc on computer networks when dealing with dates beyond December 31, 1999. The flaw, faced by computer programmers and users all over the world on January 1, 2000, is also known as the "millennium bug." As the year 2000 approached, computer programmers realized that computers might not interpret 00 as 2000, but as 1900. After more than a year of international alarm, feverish preparations, and programming corrections, few major failures occurred in the transition from December 31, 1999, to January 1, 2000.