Why can’t we simply advance our clocks on the computer to 1159pm on 12/31/99 and wait a minute and see what happens?? If the computer works fine if not fix it?
My case being I have to spend all next week writing emergency measures and running reports for our hotel in case our computers, which have been Ok’d for Y2K go out. It seems like a waste of time.
This posted twice, please refer to my other post. Or mod please delete one.
In a general sort of way, yes, that test is OK.
Provided that you do everything that the computer will do in the new century, including updating databases and printing checks.
And some of the more sophisticated database programs (like the ones that guarantee that, even if there is a power failure half-way through, every transaction is either completely performed or completely cancelled, the client always knowing which of the two, even if the transaction involves thousands of individual updates to the database) do not like having the clock set back, and some auditors don’t like to hear the words, “Oh, that was just a test check.”
And for some monster real-time systems, this kind of playing around just isn’t possible or acceptable.
John W. Kennedy
“Compact is becoming contract; man only earns and pays.”
– Charles Williams
I made that suggestion in another thread and was immediately taken down by TubaDiva. She said not to do that because some systems will delete important files if there is a drastic change in the system date. I don’t really know the specifics, but if you try it I would recommend doing a full backup of your files first.
Mr. K’s Link of the Month:
Make a DOS boot disk. Load to that disk. Then run the test. That is safe. Or get one of the many free programs PC or Mac from www.download.com for testing.
Mark, your computer hardware might be just fine but wait till you see what the application software does. Whoa. Some car guy input the new 2000 year cars and they came out as horseless carriages 
This is a re-post from the other thread so it can just die:
markxxx
How can I put this? Actually, you can just change the date, it’s just a machine it
doesn’t know any difference.
Now, should you? That is a whole different thing. There are several thing that can happen even if your test proved ok.
First, the machine is not going up in smoke or anything because of a date being wrong.
If you just sit and watch it after the date should have rolled over you aren’t likely to
see much.
That said though, every time you make chages to a file the time and date are recorded
on the file. If you change something while you are checking and then switch back to
the correct date. The date of the file is now later than the present date. Is that going
to cause a problem when another change is made? Can it update a file with a time and
date later than the one you are trying to use. You may have just created yourself a
Y2K problem.
Another thing, Windows saves the registry each time you shutdown. If the registry is
saved with a date later the the actual date and something happens to your system in
the next week where Windows may need to go to a backup copy of the registry, how
will it know which is the latest copy.
Little things like that are why it might not be a good idea, especially if you have data
that would be hard to recover.
Now, to add a few more comments, Handy is right about checking out your hardware from DOS boot disk. You can manually change the date & time and see what happens, just remember to set it back before you let Windows load.
The bigger problem is confusing your applications with the date changing around.
As was mentioned, have a backup before you go making changes like that.
Well OK, but if changing the date will work for simple test but not for further tests, just when WILL we know for sure our equipment works.
Supposing it works fine on Jan 1,2000 does this mean it’s ok for Dec 5, 2000. Or will we never know till something comes up?
Markxxx in general terms I’ll go thru this step by step.
That’ll get you to the point that everyone says it will work.
Now, will it really work? Here’s a timeline that may help. The main problem stems from interpreting 2 digit years, so, the 1st week of January will be critical. If your critical applications can handle the years properly for daily operations then so far so good.
The next hurdle will be month end closing for January. By then most of the daily operations will have been checked out.
The next hurdle will be February 29th. If the leap year works and everything else has to this point, anything else is probably minor, maybe a year end closing problem.
Remember to follow the money. If the electric meters stop turning the power companies aren’t making money, not likely to happen. Lot’s of budgets and fiscal years are already in the year 2000. Airlines tickets and credit cards have already been issued into year 2000. Social security checks have already been printed, ready to mail.
I think we are pretty well ready, not there won’t be glitches, but not show stoppers. Hope this helps a little.
Im pretty sure Norton 2000 by Symantec does a through check of hardware & software.