Steve Hayes wrote in a message to All:

 SH>  * Crossposted from: Blue Wave

 SH> Since everyone is talking about it, I thought I'd have a
 SH> look to see what software on my computer will work after
 SH> 2000, so I set the date three years ahead.

 SH> According to the clock and my word processor it is now

 SH> 2002-01-15 5:24 AM

 SH> Ok, so XyWrite is Year 2000 compliant for a start!

 SH> And it gets the correct date from the system clock on my
 SH> ancient 386 SX-16 with a ROM BIOS dated sometime in 1991.

 SH> I'm writing this in XyWrite and Blue Wave, so if Blue Wave
 SH> works correctly, and RemoteAccess works correctly, and
 SH> BinkleyTerm and Watergate work correctly, that is the date
 SH> that should appear in the header of this message - assuming,
 SH> of course, that your reader is working correctly.

 SH> Actually Blue Wave has a bug that makes it give the time as
 SH> 5 hours different from the real time, but that's a different
 SH> thing. 

 SH> If the date you see in the header is different from

 SH> 2002-01-15

 SH> then somewhere along the line, some software isn't Y2K
 SH> compliant - and it could be your reader :-)

 SH> You might like to check it!

 SH> Keep well,
 SH> Steve Hayes 

 SH> ... BBSs for genealogy:
 SH> http://www.geocities.com/7783/bbs1.htm 

 SH> ___ WtrGate v0.93 Unreg
 SH>  - Origin: Unisa Editorial, Pretoria, Gauteng, RSA
 SH> 27-12-429-8641 (5:7106/20) 

Both this message and the copy I saw in the BINKLEY echo show the same date
-- January 15, 1999,  which is presumably the date you actually wrote it. 
Are you looking at your outgoing packets to be sure that you've got the
date you think you have in there?  I'd use INSPECTA or similar.  BTW,  I
looked both with TimED (which is an older version 1.01 and presumably
non-compliant) and in Maximus,  with the identical date displayed.

email: roy.j.tellason%tanstaaf{at}frackit.com 
---