Print

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

[jim weinel]

My PC (HP 750n, 1.6G P4, 512 Ram, XP Home)
slows to a slow crawl when I try to run
ActiveHome Pro updated to 3.170.  It
ran "ok" on 3.169.  I started v3.169 tonight
and saw that an update was available.  I
clicked on the update icon and the update
successfully installed.  Then the AHP
startup splash appeared and hung there for
several minutes; no action would complete. I
saw rundl32.exe in the running process list
and recalled that someone earlier reported a
newer startup application so I changed my
desktop icon to run ActiveHm.exe.  There was
no change to the scenario even after a
reboot.  When I look at running processes in
Windows Task Manager, I see x10nets.exe
constantly taking 48-98% of the CPU time and
29-75 MB of memory.  These values fluctuate
wildly as long as AHP is "running".  Any
operation takes minutes to complete.  Twice,
I have gotten an alert that "The system is
low on virtual memory - Windows will
increase the size of virtual memory paging
file."  In both cases, AHP aborted operation
with no warning or error reports.  At that
time, x10nets.exe activity goes to zero cpu
time and the system is back to normal. I
have never received this virtual memory
message in the 3 years I have had this PC.

v3.170 is unusable for me. Is there a way to
drop back to v3.169??

[jim weinel]

OK, after several more reboots and retries,
I did an XP System Restore to a checkpoint
that had been created just a couple of hours
before the update to v3.170.  That reverted
my AHP back to v3.169.  Now the program is
operating "normally" with no observable CPU
time on x10nets.exe (and just over 5M on the
memory usage).  That'll teach me to jump on
an AHP update the day after it is offered!
Shouldn't they mark these things "Beta"??

[X10 Pro]

We'll see if we can get a similar situation
here. This build should be very stable, and
the X10Net service shouldn't use much in the
way of system resources.

[nelson]

Perhaps it should be stable, but I'm
experiencing a slowdown also. It relates
specifically to v3.170. It did not occur in
the last few versions.

[X10 Pro]

Nelson: Does this happen as soon as you run
AHP, after a period of time, or when you
perform commands?

[nelson]

Well...I just connected and ran the
program. There was no slowdown at all this
time. However, I continue to have problems
with erratic behavior on timers and macros.

[nelson]

This problem just happened again...computer
slowdown. I had just installed v3.171
without the 15a attached. the installation
went well.
I removed the 15a from power and removed
the batteries to reset everything for a
fresh start. Attached to power and inserted
the batteries. When I attached the usb
cable the computer immediately slowed to a
crawl.

[X10 Pro]

We're looking at this today. I need to get
more information from you. If so, I'll let
you know.

[X10 Pro]

Nelson: Can you e-mail me at
ahpsupport@x10.com so I can get some more
information from you?

[jim weinel]

Continuing the saga: Having dropped back to
v3.169 as noted earlier, I today noted the
major update v3.171.  Installed the update
from within the application as before and
this time the reopening of AHP completed
through the splash box.  I checked my task
manager and x10nets.exe had no CPU
activity.  When I tried to change room
locations, the hard drive started thrashing
again as in v3.170 and x10nets went wild in
task manager (just as before).  After 4
minutes 10 seconds of no response (no room
change), I got the virtual memory too low
alert again and just a few seconds later,
the AHP application "disappeared" from the
screen.  A few seconds later, the AHP icon
in the task bar vanished and x10nets as
observed in task manager settled down.

It seems that any version after 3.169 will
not work on my PC.  X10Pro, are you still
looking at this as you stated earlier???

[jim weinel]

Update:  I rebooted the PC and after startup
stabilization, I opened AHP v3.171.  This
time it opened without hiccup and I could
perform normal operations.  After a few
minutes of trying several features, I closed
the application.  After answering the prompt
confirming that I wanted to exit, the AHP
page disappeared and an error report
appeared: "X10 Module has encountered a
problem and needs to close...." I clicked
for more information and a box entitled "x10
Module" appeared with this data:

szAppName :      szAppVer : 0.0.0.0
szModName : ntdll.dll
szModVer : 5.1.2600.1217     offset :
00033aed

It also referred to technical info in a
temporary folder WER14.tmp.dir00.  These
files are located in the folder (all are
timestamped with the date/time the error
occurred):

appcompat.txt
manifest.txt
x10nets.exe.hdmp
x10nets.exe.mdmp

Please advise if any of this data would help
in resolving this problem.

[X10 Pro]

Jim: Can you e-mail ahpsupport@x10.com so I
can get some more information from you?

[jim ebbitt]

I too am having this problem since updating
from 3.169 to 3.172. AHP ( and my computer
in general) become totally unresponsive
soon after opening AHP and when I open task
manager, x10nets is using up to 100% cpu.
To regain control, I must end process on
x10nets.  3.169 was very stable, no
problems at all. Can I go back somehow to
3.169 as this is useless to me now?