Print

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

[rucanunes]

Hello,

I'm running Win Vista 32 and AHP 3.236 with CM15.
Every time I try to access the "hardware configuration" on Tools menu, my AHP crashes.
I think this is related with location or time format...

Could someone please help me? 

Thank you!
R nunes

[Dan Lawrence]

I presume you are NOT in the US or Canada, according to the screen shot you posted.

[rucanunes]

I'm from Portugal.

[Dan Lawrence]

Doesn't X10 Europe have a website with a web BBS like this one?

[rucanunes]

I don't know! Is there a problem me posting here?

[Brian H]

No problem with your posts here; but you may get better information from an other site.
The software for the US and Canada is not the same as some of the versions for other countries. Some features and functions maybe missing; different or modified to match the hardware being sold.

[Akasonny]

Woops...and a semi-related problem:

Using Windows VISTA and AHP version 3.236...

When, in Preferences, I click on Still Capture, AHP crashes every time. This is a new one on me!

[texreeves]

I'm having the exact same problem, with the same screen shot.
I'm not running vista (win xp), and I'm not in Portugal
(actually in the US).  But since I can't run the HW config
without crashing, I can't change the setup.

Note:  This is a new install for me (never had AHP before,
upgrading from AH)

My suspicion is that the default TZ and/or location, etc,
is bogus in rev 3.236, but that with a valid .ahx it isn't a problem.
Since I don't have a valid .ahx I can never create one.
Any possibility of someone providing a .ahx file that is
known to work with 3.236?

[PJFota]

I am having this same problem.  I just installed 3.236 and every time I try to change the time zone under Hardware Configuration the program crashes.
I am in the US running Windows Vista 32.

[PajamaGuy]

Just for grins, with AHP not running, find your active AHX file and rename it.  Then start up AHP and with a clean ahx file, see if the same error happens.

[texreeves]

Thanks, I've tried that, but still the same problem.

[Dan Lawrence]

Try uninstalling AHP, delete the folders (Active Home Pro and Common Files/X10) and reboot.  Re-install AHP and see what happens. If it still crashes, try and get 3.228 and install that. If it does not crash, create your .ahx file and load the CM15A, then try to upgrade to 3.236.

[PajamaGuy]

Make sure you get 'em all:

OS:\Program Files\Active Home
OS:\Program Files\X10 (may be X10 Drivers and or X10 Hardware)
OS:\Program Files\Common Files\X10
OS:\Program Data\X10

User Files\My Docs\Active Home Pro

And you might want to uninstall the USB CM15A and the VA11A.

...and you have to stop the ActiveHome and X10NETS processes via TaskMgr before you can delete all of the folders.

The order is:
Shut down AHP
Make a copy of your AHX file and put it somewhere NOT in your ..."MyDocuments\Active Home Pro"
Use TaskMgr to stop all X10 & ActiveHome Services
Use Control Panel to Remove Active Home Pro and DO NOT SELECT Automatic, Select CUSTOM and then SELECT-ALL as you step through it.
Then Delete the folders   (sometimes with Vista you have to reboot first)
REBOOT!!!!!!!!!!!
Re-install.  If you don't get the registration screen(s) - you didn't uninstall completely and you're not going to be happy.  If you use On-Alert and KR10As, do not let it update to 3.236 - stay at 3.228.

[texreeves]

OK, in my case it was some sort of bogus .ahx file (and this bogus file was created as the default new .ahx file).
On one PC I discovered this by installed the marmitek version (which did not crash but wanted european modules),
and then re-installing the US version but using the .ahx file that had been created from the marmitek version.  Once I saw that this
did not crash either, I then used a different PC and just modified the original (crashing) .ahx, and verified what the
problem was.

The <data ts .../> line is the only one that needs changing, here's a line that works (and once it works, you can use the
tools/hw config to change it to what you want):

   <data ts="0" macromemory="58" timermemory="20" duskdawnmemory="140" freememory="7916" transhc="2" transhcmask="65535" transhcmode="1" monitoredhc="1" geolocset="1" locationisus="0" locationindes="-1" geo_lat="55.76" geo_lon="-71.70" dd_res="3" delay_override="219" />

I suspect that all that needed changing was:
geolocset="1" locationisus="0" locationindes="-1" geo_lat="55.76" geo_lon="-71.70"
but didn't experiment further.

[-Bill- (of wgjohns.com)]

OK, in my case it was some sort of bogus .ahx file (and this bogus file was created as the default new .ahx file).
On one PC I discovered this by installed the marmitek version (which did not crash but wanted european modules),
and then re-installing the US version but using the .ahx file that had been created from the marmitek version.  Once I saw that this
did not crash either, I then used a different PC and just modified the original (crashing) .ahx, and verified what the
problem was.

The <data ts .../> line is the only one that needs changing, here's a line that works (and once it works, you can use the
tools/hw config to change it to what you want):

   <data ts="0" macromemory="58" timermemory="20" duskdawnmemory="140" freememory="7916" transhc="2" transhcmask="65535" transhcmode="1" monitoredhc="1" geolocset="1" locationisus="0" locationindes="-1" geo_lat="55.76" geo_lon="-71.70" dd_res="3" delay_override="219" />

I suspect that all that needed changing was:
geolocset="1" locationisus="0" locationindes="-1" geo_lat="55.76" geo_lon="-71.70"
but didn't experiment further.

Good to know!   

I don't suppose you kept a copy of the corrupt .ahx file that you could email me by any chance?