Author |
|
jostim Groupie
Joined: February 12 2007 Location: United States
Online Status: Offline Posts: 45
|
Posted: March 11 2007 at 12:22 | IP Logged
|
|
|
People-in-the-know,
When I close or reinitialize PH, I get the message:
"pwrhome.exe has encountered a problem and needs to Close. We are sorry for the inconvenience.
If you were in the middle of something, the information you were working on might be lost".
Sometimes when that happens I can't restart PH or even restart the computer. If I check "Task Manager", there is no application running, but there is a process 'pwhome.exe' that I can't end. I have to power-cycle the pc to get it running again.
Other times I can just restart PH and everything is fine again.
Sorry about all these questions. I guess I am not just a noob, but also a clutz.
Any ideas?
Thanks.
__________________ - jos
|
Back to Top |
|
|
dhoward Admin Group
Joined: June 29 2001 Location: United States
Online Status: Offline Posts: 4447
|
Posted: March 13 2007 at 21:01 | IP Logged
|
|
|
Jos,
This is unusual and not normal behaviour. Ive seen this happen on occasion and almost always seems to be tied to PowerHome being in the middle of processing in an improper loop. Usually the result of a macro or process that cant finish because of being called from an "Immediate" type trigger. Check your triggers and make sure that all of them are "Queued" instead of "Immediate".
If none of your triggers are "Immediate", then it's got to be something else. Have you noticed when it locks up if you've done anything outside of normal PowerHome background processing such as learning an IR remote, adding new devices, or manual type processes being done in the PowerHome Explorer? Ive come across a similar type problem once that I havent isolated yet that seems to be linked to auto-learning an IR remote and prematurely closing the learn window before all codes are learned.
Let me know,
Dave.
|
Back to Top |
|
|
Deano Groupie
Joined: February 19 2003 Location: United States
Online Status: Offline Posts: 75
|
Posted: March 14 2007 at 12:14 | IP Logged
|
|
|
Dave,
I've seen similar behavior on reinit as in bug post and while I have been trying to get rid of "immediate" I'm sure I still have some left. Fell into the immediate trap trying to get X10 to go faster, thinking the immediate meant do it now dam it, when apparently it means don't do anything else until your done with this thing.
I seem to recall that Multi-X triggers need to be immediate but is there anything else. How about immediate in Macro calls and formulas?
|
Back to Top |
|
|
TonyNo Moderator Group
Joined: December 05 2001 Location: United States
Online Status: Offline Posts: 2889
|
Posted: March 14 2007 at 21:05 | IP Logged
|
|
|
Immediate is safe when you know you won't trash anything.
Dave said...
Quote:
In general, you should always make your triggers as "Queued". The immediate function is there to handle certain situations where you MUST know a status or similar at that exact moment and in that case, you should QUEUE your actions within the called macro. |
|
|
|
Back to Top |
|
|
jostim Groupie
Joined: February 12 2007 Location: United States
Online Status: Offline Posts: 45
|
Posted: March 19 2007 at 11:13 | IP Logged
|
|
|
Dave,
Thanks for your suggestions. I know I don't have any triggers set to 'immediate'. I am traveling, but when I get home I will check to see if there is anything else set to immediate. I'll let you know by Tuesday, 3/20.
thanks
__________________ - jos
|
Back to Top |
|
|
jostim Groupie
Joined: February 12 2007 Location: United States
Online Status: Offline Posts: 45
|
Posted: March 20 2007 at 09:46 | IP Logged
|
|
|
Dave,
I checked, and I have nothing set to immediate; nothing in macros, nothing in triggers, nothing in timers.
I also tried to start PH, do nothing and reinitiate or shut PH down. It still crashes in both cases and sometime hangs the machine.
Any ideas?
Thanks.
__________________ - jos
|
Back to Top |
|
|