Print

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

[Tuicemen]

Man what a pain this was to install!
Not sure why I'm always the first to have issues with the new updates
Kept getting the AHP has encountered a problem and needs to close! restarted only to see I was still at version 3.206
Installed AHP and reinstalled then updated!
that worked accept I also had to reinstall all my plug-ins(another royal pain I had to install them in the order I purchased!
installed smartmacros after iWatchout and had to reinstall iWatchout didn't want to install MyHouse but trying to install OnAlert gave me the dreaded   [/b] installed Myhouse then OnAlert installed without a hitch!
I'm sure I'll find more issues but for now value of backups has been driven home once again!
when I installed it left my AHX files but once AHP was up and running with the new version many things were not right reloading the backup AHX fixed it!
As I type this I received the dreaded "AHP has encountered a problem and needs to close message" 
Well now to start with issues!

• The bug with windows commands not working after restarting AHP still exists!
[/color]

thankfully I found a work around for this

[/list][/b]

[JimC]

Tuicemen

Thanks for the heads up. Makes me glad I was not on my computer last night , so I was unaware of the update. I think I will wait a while to install.

+1

[steven r]

...Not sure why I'm always the first to have issues with the new updates...

On the other hand, my update installed without any problems. Maybe Murphy took a vacation from my house and went to visit you. 
I haven't tested to see if they fixed any of the existing bugs I was aware of, however.

Even though I keep my CM15A connected to my computer, I was glad to hear of the DST fix. I just hope they can easily "undo" it if Congress decides not to keep the current trial DST dates.

[Tuicemen]

Seems murphy was indeed here! looks like the main culprit was my ISP!
Even with using my back up AHX files I continued to get and find problems so with my internet connection apperently back to norm I reinstalled!
This seems to have fixed most of my issues except the windows command issue reported earlier! (work arround solves that for now) 

[Dan Lawrence]

I got while I was here at the Forums!!!   The install was triggered by AHP, the upgrade closed it, applied the files and reopened AHP.  Just a precaution, I cleared the interface and reloaded the current file, everything is A-OK!!!

[JimC]

Update went smooth here. Murphy must have gotten lost on the way to my house.

[steven r]

Update went smooth here. Murphy must have gotten lost on the way to my house.

I think Tuicemen secretly sent Murphy an invitation to his all night update party. 

Rumor is that Murphy is planning something special for anyone that updates to SP3 for Windows XP on the same day. 

[Walt2]

Rumor is that Murphy is planning something special for anyone that updates to SP3 for Windows XP on the same day. 

Ah, oh. 

I did both SP3 and AHP the same day.   

I did the update to SP3, and noticed a pop up saying something about updating my preferences for IE.  So, after I was done, I gave IE a "test drive" and came to here.  To my great surprise, I read here about the update to AHP.  So, I did that too.

[Puck]

My upgrade went smoothly. However, I was surprised to see all my macro delays appeared blank in the GUI section. In the lower text section, the delays were still correct.

This occurred with both of my setups (2 independent PCs). Both are running Win2K. So far it appears that I am the only one report this anomaly so I am wondering if it is due to Win2K. I would certainly be interested in hearing from others who also are running Win2K.

The blank delays were still there thru the following:

 - When I loaded my back-up AHX files.

 - When I create a new AHX.

 - When I create a new macro and add a delay. In this case I can still manually enter the delay I want, but the up / down arrows only decrease the delay (even the up arrow decreases).

I have not had the chance yet to un-install / re-install the complete AHP software, but I will soon and report back if that helps.

[Dan Lawrence]

Zero problems with either AHP 3.228 or XP Service Pack 3!!!!  Both upgrades went easily.   I guess my residence came equipped with a Anti-Murphy shield.   

[steven r]

Zero problems with either AHP 3.228 or XP Service Pack 3!!!!  Both upgrades went easily.   I guess my residence came equipped with a Anti-Murphy shield.   

While I don't have an Anti-Murphy shield, I think I was spared since Murphy left to party at Tuicemen's house.
My SP3 update went well also. It did take 1.5 hours and require me to click ok over 50 times to my Spybot popups to allow all the registry changes, however.

[WoodCountry]

The 3.228 install went fine with no install errors.  I cleared and updated the interface memory.  Now I have one error with one Timer.  It is set to turn on a 2-pin Appliance Module at Dawn +30 mins (one half hour after dawn) but instead it is now turning on 17 HOURS after dawn, or about 22:45 !!  I deleted the timer and recreated it, updated the interface, but the problem persists.  The timer says "Dawn + 30 mins", but it still triggers 16.5 hours late.  This error started the day after I updated the software, so I have to think it was introduced by 3.228.

[Charles Sullivan]

The 3.228 install went fine with no install errors.  I cleared and updated the interface memory.  Now I have one error with one Timer.  It is set to turn on a 2-pin Appliance Module at Dawn +30 mins (one half hour after dawn) but instead it is now turning on 17 HOURS after dawn, or about 22:45 !!  I deleted the timer and recreated it, updated the interface, but the problem persists.  The timer says "Dawn + 30 mins", but it still triggers 16.5 hours late.  This error started the day after I updated the software, so I have to think it was introduced by 3.228.

Save your existing .ahx file and try re-creating your entire schedule from scratch in a new file.  AHP in the past has had problems when existing .ahx files are modified, and these problems may never have been fixed.

[ATCtechie]

I update to 3.228 the other day and since then my timers simply won't trigger. I dug in and found that every single timer event is set to run from 01/01 to 01/01 and I can't make any date change stick. They should all be 01/01 to 31/12 as I use different timers for different days of the week.

Anyone else notice this? Right now I'm dead in the water. As soon as I make any change to a timer setting the date changes itself.

Bob

[Tuicemen]

ATCtechie Sounds like a corupt AHX file if you don't have it backed up you'll have to rebuild it from scratch!