You shouldn't have to reset the timers, unless the Interval changes. Just
set the AutoReset property to true.

Signature
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.
> Hi,
>
[quoted text clipped - 16 lines]
>
> Graham
| Hi,
|
[quoted text clipped - 16 lines]
|
| Graham
Windows is not a real-time OS, so there is no guarantee that the event will
fire at the exact interval you specified, another thread in the system may
run at a higher priority currently blocking delivery of timer events to your
application. When that happens the event will be delayed, the event may even
get lost especially when using short intervals like 200 msec.
Willy.
Oxns - 07 Jan 2006 09:44 GMT
Willy,
Thanks for the reply - I understand the limitations of Windows - in fact I
am seriously considering an embedded hardware solution with a REAL RTOS
(Forth) for this application ;-)).
I still would however expect the timer period to remain accurate, even if
some ticks start late (as they were blocked), I would expect these to
recover, but the effects appear to be cumulative :-(( - when one is delayed
the next also appears to be delayed - hence my question about when the timer
tick actually gets reset.
I'm also used to embedded systems for many years and would always ensure
that the first thing an interrupt handler often does is to reset its source.
Thanks agin though.
Graham
> | Hi,
> |
[quoted text clipped - 33 lines]
>
> Willy.
"Peter Huang" [MSFT] - 09 Jan 2006 04:56 GMT
Hi Oxns,
As Willy said, Windows NT family is not designed to be a RTOS.
Here is a link for your reference.
http://www.omimo.be/magazine/97q2/winntasrtos.htm
Best regards,
Peter Huang
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.