Re: A problem with time...

From:

"Doug Harrison [MVP]" <dsh@mvps.org>

Newsgroups:

microsoft.public.vc.mfc

Date:

Tue, 13 Jun 2006 12:29:24 -0500

Message-ID:

<2kst82197k3eqv6d87ffksomvonn1ttvqf@4ax.com>

On Tue, 13 Jun 2006 17:00:08 GMT, Phil <spam@recycle.bin> wrote:

I have written a program that keeps track of a large quantity of items,
e.g. how long they have been in certain places, then updates a list
display. I've noticed though that the computer it is running on has
started /gaining/ time though - up to 10 minutes every hour !

I'm not doing anything to alter the time, but I am doing lots of calls
at various intervals to get the current time, just using;

CTime ct=CTime::GetCurrentTime();

I'm using timers rather than threads to run in the background and keep
the main screen updated. I'm not killing my timers when the program is
closed tho, would that have an adverse effect ? or are there any other
obvious reasons that would cause a computer (Win2K) to gain time... some
problem with using GetCurrentTime or timers for instance ?

(I've not ruled out that the computer it's running on is faulty, but
it's not that easy to check that at the moment).

Based on what you've described, your program should not be causing this
problem. What happens when you reboot and don't run your program? If your
computer continues to gain time, it could be the hardware and/or OS at
fault. There was a problem in this area with some Dell systems circa 2002
losing time, and it was partly the W32Time service at fault. I've
personally observed a WinXP system to run at 94 sec/min after switching
from multiprocessor to uniprocessor.

--
Doug Harrison
Visual C++ MVP