Subject: From: Date:

Re: [ECS] Security-IFC-A LEC1964.aol.com Wed, 8 Jul 1998 22:39:01 EDT

---

    Mark,
     I also noticed this error message. As you recall I have recently upgraded
from ECS 3.2 to ECSW 3.4 and I was seeing this error message several times
during a 24 hour interval. Two, as I recall, were 3am & 9am as well as some
other very specific times. It finally dawned on me what might be the problem
and sure enough it was.
     Years ago I got tired of resetting the CMOS clock, that was gaining
almost 14 seconds per day, and did a little experimenting to see if I might
correct this time error by incrementing the "Second". I found that this
somehow would change the CMOS clock and not just ECS time as I would expect. I
then added several Event lines to increment the "Second" at equal intervals
throughout the day. As a result, the accuracy of ECS time was "right on"
requiring no adjustment for months. It was very irritating for ECS to Announce
the "on the hour" time five minutes before the hour. Of course I need to
remove these statements since I don't know what the drift will be on the CMOS
clock for this new motherboard.
     If my understanding is correct, the CMOS clock is a group of counters
that gets "ticked" over by a timebase. The timebase is an oscillator and
divider network whose obvious function is to keep the time when the computer
is "off". The CMOS battery provides the power. My experience tells me there
will be drift I just don't know how much.
     Mark, is this something "Windows" doesn't like you to do or allow you to
do?

Thanks, Larry.

---