Subject: From: Date:

RE: [ECS] Michael's lockup Ingo Pakleppa Fri, 05 May 2000 09:57:45 -0700

---

Mark already said that this is not the problem. But in any case, it could 
even be a single application using many timers. Unfortunately, there is no 
way to find out.

At 04:31 AM 5/5/00 -0400, Michael David wrote:
>Hi Ingo!
>
>What would be using up all my timers?  All I have running on the machine (NT
>4.0 SP6a) is ECS, ACE server, Norton Antivirus, and D4 (a neat little clock
>auto-synchronization program).  Is there some way I can see how many timers
>have been started?
>
>Cheers!
>
>Michael David
>michael@michaeldavid.com
>
>
>-----Original Message-----
>From: Ingo Pakleppa [mailto:ipakleppa@home.com]
>Sent: Friday, May 05, 2000 4:08 AM
>To: ecs-list@netbloc.com; ecs-list@netbloc.com
>Subject: Re: [ECS] Michael's lockup
>
>Maybe he simply ran out of timers? Windows has a limit of, I believe, 25
>timers systemwide that can be active at any one time. If you try to start
>more timers, the SetTimer() function will simply return an error.
>
>Ingo
>
>At 04:52 PM 5/4/00 -0400, Mark Gilmore wrote:
> >Does anyone have a theory on what could "eat" Win TIMER messages ?
> >ECS sets a Win timer to .25 seconds, and then sleeps until
> >it receives a message. When the timer msg is received, it
> >executes Events and resets the timer.
> >
> >The problem is that Michael's old lockup has returned,
> >whereby ECS occassionally freezes until he moves the mouse.
> >This triggers a Win message, which then "wakes up" ECS.
> >The lockup means that ECS never received the timer message.
> >
> >The reason it is happening again is that I used an improved
> >method of coding around the problem, whereby I used a SECOND
> >"insurance timer" (ASSUMING that ONE would "get thru").
> >But apparently, this timer is being "killed" as well as the 1st.
> >
> >???????
> >--
> >Mark Gilmore
> >Omnipotence (ECS home automation software)
> >http://www.usit.com/omnip
> >423-745-0026
> >Hours: Mon-Sat, 9AM-8PM/EST

---