Millenium Bug

2000 will start soon, a new era of greatness and miracles. . . Unless you own a computer or use a computer. In 2000, the gift of Pandora 's Box was sent to the world of computers, and the money was slowly disappearing. The bug in 2000 was not a real "bug" or "virus" but a mistake in the computer industry. Many PCs, mainframes, and software are not designed or programmed to calculate future years ending with double zeroes.

The Y2K problem, the Y2K problem, and the Y2K problem are aliases to the same main problem and all computers faced this problem at midnight on January 1, 2000. Some people say this is just a bug, some experts call it "the end of the world". This problem arises from older systems that store the year part of the date in two digits (ie, 1997 is stored as "97"). Years ago, COBOL programmers used this method to save memory. It was because it was very expensive. This is actually a very smart system. It's simple, it saves a lot of memory and functions. However, the original programmer ignored the big problem. When the century (or a thousand years) ends with "00", the computer misunderstood "00" as "1900" instead of "2000".

Changing a two-digit date field to a four-digit date field is one way to fix the worm. In this way, you will need to convert all the references and usage of the two-digit year format to a 4-digit year format and change the data and program. You also need to convert all software programs that use the updated data. This may be the only complete and permanent solution to the problem. This approach will provide infinite future dates for companies. Unfortunately, expanding the date field from 2 to 4 has some disadvantages. The most obvious point is that each program that references the data and the database must be modified to convert the date. These changes are primarily manual, not automated processes.

Adding a 28-year time bridge with the system clock reversed is another way to fix the worm. This method is effective for systems where the source code can not be used or replaced. This method creates a bridge script that inverts the system clock for 28 years and adds or subtracts 28 years from the date data. This offset holds the same date for one week and one month, so the number is 28. When the 28th anniversary of January 1, 1972 increases, it will be Saturday, January 1, 2000. This applies only to the leap year once every four years.