Ha ha. I doubt there will be anything left running. This issue only affects stuff which

was fixed for 2000, which means they were already legacy then.

Most solutions chose a pivot method, by translating 50-99 as 1950-99 and 00-49 as 2000-2049 for example. A bit short sighted using such an early pivot year unnecessarily.

The other solution (which I used) was to use symbols so (and I cannot remember in which order or how many). So dates were stored as 97,98,99,9!, 9", 9# etc and translated at the system level. From memory the set we used would end somewhere in the 2040s but there's no way that software will still be running then.

They chose pivots rather than changing to a full four digit date for the simple reason that it was less risky. If you extended your storage to 4 digits everywhere then there was a high risk that you'd miss a few. Whereas a mistake with a pivot would result in an incorrect year, a mistake with storage expansion would result in the old famous GPF / Blue Screen of Death.

Posted By: Steve in Holland on February 26th 2018 at 15:18:24

Message Thread

Reply to Message

In order to add a post to the WotB Message Board you must be a registered WotB user.

If you are not yet registered then please visit the registration page. You should ensure that their browser is setup to accept cookies.

Log in