Subject: From: Date:

Re: [ECS] Michael's lockup Mark Gilmore Fri, 05 May 2000 06:15:42 -0400

---

I'm checking for such an error return (on the SETTIMER call).
-- 
Mark Gilmore
Omnipotence (ECS home automation software)
http://www.usit.com/omnip
423-745-0026
Hours: Mon-Sat, 9AM-8PM/EST


Ingo Pakleppa wrote:
> 
> 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

---