This is a great way to test your system for compliance, but be careful if
you have any programs that are time sensitive such as virus checkers which
allow several years of free upgrades and then stop. Their counters don't
go back when your date does.
This may also mess up demonstration copies of jfw.
At 10:26 PM 2/6/99 -0500, you wrote:
>Hello all;
>
>I have heard that ignorance is bliss, so bear with me as I express my
>ignorance. First, I admit there may be y2k problems in large network
>situations.
>
>I saw on the list today that there is a rumor about JFW or its' key having
>some kind of y2k problems. I have lived through the second coming of
>Christ and the end of the world at least 10 times. I am, therefore, very
>skeptical about the y2k bug causing any problems to my little PC. Here
>is what I did to prove my theory.
>
>About 3 weeks ago I did a routine backup of all my data files etc. Before
>I shut down for the night I changed the date on the computer to 12/31/99.
>The next morning the computer booted up with no problems. My calendar
>program told me the date was Saturday January 1, 2000. The next 3 days I
>ran the computer as usual except I made sure I accessed every application I
>ever used. I had absolutely no problems. After 3 days I changed the date
>back to the correct date.
>
>The only hold over from the experiment is the messages I sent those 3 days
>are the last ones in the out box. After the last one sent in 1999.
>
>In my blissful ignorance I believe it is bunk. Only an attempt by some to
>scare the public into buying new computers and/or software programs that
>are not needed.
>
>I'll probably have the first computer crash of 2000. {;-) Grin
>
>
>Dave Maynard
>Franklin NC
>[EMAIL PROTECTED]
>-
>Visit the jfw ml web page: http://yoyo.cc.monash.edu.au/~nallan/jfw
>
>
Thomas Stivers
-
Visit the jfw ml web page: http://yoyo.cc.monash.edu.au/~nallan/jfw
