Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Noam]

I have been waiting patiently for almost a <BR>years for X10 to fix the problem with my <BR>Activity Monitor. It just stops recording <BR>activity at random. A new interface, <BR>reinstalling, Wiping and reinstalling <BR>everything on the Pc, and numberous updates <BR>to AHP have all failed to fix this. Numerous <BR>e-mails to X10 have gone unanswered. I just <BR>send another e-mail to [Specific <BR>technician's name withheld] at X10 today. I <BR>hope I get some osrt of an answer. Even <BR>a "We haven't figured it out yet, but it is <BR>on our list of things to do" would be more <BR>than I' have gotten in the past several <BR>months.

[Dan Lawrence]

My guess, as a user, is that either you have
a botched AHP installation or a oddball PC
hardware problem.

The fix for the first one is not easy, but it
can be done.

1. Back up your .ahx files. That's your
modules, timers and everything else.

2. Un-install AHP. Everything. After the
un-install is finished, delete the Active
Home Pro folder and everything in it. (The
AHP uninstalled does not delete everything.)

3. Run regedit. This opens the Registry
Editor. Search for everything Active Home
Professional or X10 and delete every key you
find. This is time and labor extensive.  Once
you have found everything in the Registry,
close the Editor and reboot.

4. Re-install AHP.

If this has already been done with the same
problems, it's time to put the crowbar in the
wallet and buy a new PC, as your current one
has major hardware problems.

[X10 Pro]

Noam: The problems you're seeing *are* still
on my list. It's a long list, but there are
several Activity Monitor-related problems
that we need to investigate and resolve, so
we will get to it.

[Noam]

Dan:
Thaks for the suggestions. I have already
tried wiping the PC, reininstalling
everything from the OS on up, and rebuilding
the AHX files FROM SCRATCH, and even
replacing the CM15A interface. That didn't
work. I was thinking it might be some USB-
related issue, but I suggested that to the
X10 folks several months ago, and they never
got back to me (indicating that they didn't
think that was the root of the problem). In
light of today's response by X10-Pro to my
post, I still think it is a software-based
problem.
X10-Pro:
I got your e-mail. Thanks for getting back
to me. I'm curious to compare notes with
other users who are having this same
problem, to try and find a common thread,
and perhaps nail down the root cause of the
problem. Please let me know if there is
anything I can do to help.