- 1. [TRLog] Re: Dates (score: 1)
- Author: n6tr@teleport.com (n6tr@teleport.com)
- Date: 14 Jan 2000 04:44:02 -0000
- Yup - sure enough. Looks like my development computer has a small issue with Y2K! Tree -- FAQ on WWW: http://www.contesting.com/trlogfaq.html Submissions: trlog@contesting.com Administrative request
- /archives//html/TRLog/2000-01/msg00042.html (6,872 bytes)
- 2. [TRLog] Re: Dates (score: 1)
- Author: n5nw@midsouth.rr.com (Marty Watt)
- Date: Thu, 13 Jan 2000 22:49:51 -0600
- Or perhaps a dead internal clock battery? -- Marty, N5NW ______________________________________________________________________________ Lakeland (Memphis), Tennessee http://marty.w.tripod.com/ N5NW@m
- /archives//html/TRLog/2000-01/msg00043.html (7,291 bytes)
- 3. [TRLog] Re: Dates (score: 1)
- Author: LRod@pobox.com (LRod@pobox.com)
- Date: Fri, 14 Jan 2000 04:51:40 -0000
- I actually found a Y2K problem in another piece of software that I use, and I'll bet a lot of other folks here use: WS-FTP. I had an older version (4 something, I think) and when I went to update my
- /archives//html/TRLog/2000-01/msg00044.html (7,654 bytes)
- 4. SV: [TRLog] Re: Dates (score: 1)
- Author: sm3cer@contesting.com (Jan-Eric Rehn/SM3CER)
- Date: Fri, 14 Jan 2000 17:33:06 -0000
- Hello, I had a similar problem with my WS_FTP. When I updated my files they got the year 100. Seems to me you were closer to 2000 with your 1900 :-) Everything went fine after an update to a later ve
- /archives//html/TRLog/2000-01/msg00045.html (9,750 bytes)
This search system is powered by
Namazu