Re: Y2K Skepticism

Harvey Newstrom (harv@gate.net)
Thu, 09 Apr 1998 12:36:56 -0400

Dismissing the problem without looking at the facts is just as bad as
exaggerating the problem. Most people use Microsoft products on
Microsoft Windows, so here are a few examples from Microsoft Technical
Support. Unless you apply these patches as they come out, your Windows
PC will fail in the year 2000:

Windows 95 DATE command rejects years 2000 or later as being "incorrect
date format":
<http://support.microsoft.com/support/downloads/dp3060.asp>

Windows 95 File Manager shows incorrect date for year 2000 or later:
<http://support.microsoft.com/support/kb/articles/q172/7/07.asp>

Windows NT 3.5.1 FTP service displays incorrect date for the year 2000:
<http://support.microsoft.com/support/kb/articles/q182/5/97.asp>

Windows 3.1 and 3.1.1 File Manager shows garbled date for years 2000 or
later:
<http://support.microsoft.com/support/kb/articles/q85/5/57.asp>

Microsoft Access defaults years '00-'29 to year 2000 instead of correct
year:
<http://support.microsoft.com/support/kb/articles/q155/6/69.asp>

Microsoft Access 97 will incorrectly interpret ALL dates converted from
Access 7.0 due to Year2000 compliance enhancements:
<http://support.microsoft.com/support/kb/articles/q160/5/03.asp>

Microsoft Excel interprets two-digit dates differently on different
versions:
<http://support.microsoft.com/support/kb/articles/q164/4/06.asp>

Microsoft PowerPoint translates two-digit dates incorrectly after the
year 2000:
<http://support.microsoft.com/support/kb/articles/q182/5/46.asp>

Microsoft Visual Basic interprets two-digit dates differently on 16-bit
and 32-bit systems:
<http://support.microsoft.com/support/kb/articles/q162/7/18.asp>

--
Harvey Newstrom <mailto:harv@gate.net>
PGP 5.5 Fingerprint:  F746 7A20 EB7D 27BA 80A5  4473 D8E1 6A54 1EB0 56F7
PGP Public Key available from <ldap://certserver.pgp.com>