| Author |
|
GCollins
Groupie
Joined: March 27 2011
Location: United States
Online Status: Offline
Posts: 54
|
| Posted: April 16 2014 at 12:50 | IP Logged
|
|
|
Hello Dave and all,
I'm running PowerHome 2.1b on an old XP machine. All devices are operating with X-10 protocol (most are actually Lightolier Compose using their implementation of X-10, some are /Insteon in X-10 mode, some are just genuine old school X-10). My interface is a Smarthome 2413S (v1.5).
I need to move PH to a new a new PC, and the plan is that it will be running Win7 Home Premium 64-bit.
Should I just go back with PH 2.1b, or do you recommend moving to one of the newer betas? If I upgrade, what is the correct incremental sequence, and links for same?
Thanks!
Gregg
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 17 2014 at 10:20 | IP Logged
|
|
|
Gregg,
You'll definitely want to move up to the 2.1.4 beta as its more stable and has better compatibility with the later versions of Windows.
To upgrade to 2.1.4, you'll first install 2.1.2 available here: http://www.power-home.com/forum/forum_posts.asp?TID=2723&PN= 1. Then you unzip version 2.1.4 on top of your install. You can find this file on page 5 of the above thread. Make sure that you install into c:\powerhome vs the old directory of c:\program file\powerhome.
Copy over your old database and ini files (default located on the old machine in c:\program files\powerhome\database\pwrhome.db and c:\program files\powerhome\pwrhome.ini respectively). Use these copies and overwrite the versions in your new install. Open your pwrhome.ini file and manually edit the directory location to match your current install (usually only the database location and the webserver location). Run the database upgrade utility and upgrade your database to the 2.1.2 version. You should now be able to run PowerHome with all of your previous settings and registration.
If version 2.1b has been working fine with you (no issues with Insteon I2CS devices), then you shouldnt need the I2CS patch. If you do, you can find it on the forum.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
GCollins
Groupie
Joined: March 27 2011
Location: United States
Online Status: Offline
Posts: 54
|
| Posted: April 18 2014 at 12:19 | IP Logged
|
|
|
Dave,
Great summary and easy to execute, thanks.
Only problem was that program startup initially failed due to "Error 39 accessing external object property autoresolve at line 11 in constructor event of object uo_socketserver". I saw elsewhere in the forums that turning off User Access Control in Windows solved similar problems, and that proved to solve my problem, too. Prior attempts to solve by turning off firewall and AV were useless (so those things are back on now!).
I'm glad PH is running, but I'm a bit apprehensive about not having UAC. Is there a better way to fix besides just disabling UAC?
I'm looking forward to a closer look at this new version in coming days. For now, my devices seem to back under normal schedule control. Also on my list is to finally get PH running as a service with automated shutdown and startup capabilities. I never could get that working with v2.1b under WinXP.
Thanks,
Gregg
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 20 2014 at 21:32 | IP Logged
|
|
|
Gregg,
My guess concerning UAC is that the Catalyst socket controls did not get registered properly. I would re-enable UAC and then launch a command prompt using "Run as administrator". Once there, navigate to c:\windows\system32 (or possibly c:\windows\syswow64). Run:
regsvr32 cswskax6.ocx
and make sure that it registers properly. Reference the second post on this page: http://www.power-home.com/forum/forum_posts.asp?TID=2723&KW= regsvr32&PN=0&TPN=3
Unfortunately, I wouldnt both with trying to run PowerHome as a service on Windows Vista and up. Microsoft changed the way that services run and they have their own desktop space. PH will run (as a service) but you won't be able to view the client application at all. To resolve this, I'll be separating the app into two parts, a server and a client with the server able to run as a service as it won't have any visible windows.
Dave.
|
| Back to Top |
|
| |
cmhardwick
Senior Member
Joined: July 08 2006
Location: United States
Online Status: Offline
Posts: 290
|
| Posted: April 22 2014 at 03:13 | IP Logged
|
|
|
Will the client be able to be on a separate machine Dave? That would be nice, then unless something weird happened, I wouldn't have to remote in the machine running the service to do PH programming stuff.
__________________
Cicero, Enjoying automation!
|
| Back to Top |
|
| |
GCollins
Groupie
Joined: March 27 2011
Location: United States
Online Status: Offline
Posts: 54
|
| Posted: April 22 2014 at 22:32 | IP Logged
|
|
|
Dave,
Manual registration from the ..\syswow64 directory worked, including for the other controls listed in your referenced post.
Not having the service functionality, I'll experiment instead with putting PH in the Startup group. My goal is to have automated scheduled restarts so I can let Microsoft do their thing with weekly patching.
Thanks,
Gregg
|
| Back to Top |
|
| |
GCollins
Groupie
Joined: March 27 2011
Location: United States
Online Status: Offline
Posts: 54
|
| Posted: April 22 2014 at 22:51 | IP Logged
|
|
|
An update...
Perhaps my fear of abruptly shutting down PH with a Windows restart command is unfounded, at least with my simple PH configuration. A test revealed no obvious undesirable fallout, and the program seems to have re-launched flawlessly via the Windows Startup group. Helps that the default PH startup options are currently acceptable for me (although perhaps there are command line parameters if not).
Thanks again,
Gregg
|
| Back to Top |
|
| |
GCollins
Groupie
Joined: March 27 2011
Location: United States
Online Status: Offline
Posts: 54
|
| Posted: April 22 2014 at 23:47 | IP Logged
|
|
|
Further update...
To restore the appearance of my Control Center to pre-upgrade condition, I followed step #9 in your 7th post in this thread:
http://www.power-home.com/forum/forum_posts.asp?TID=2723&KW= force+full+command&PN=0&TPN=13
Regards,
Gregg
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: April 26 2014 at 14:03 | IP Logged
|
|
|
Gregg,
Glad to hear everything worked out ok and that launching PowerHome at startup is working for you. Concerning the startup options...in the PH Explorer under Setup->Preferences you can set the default startup options (vs command line parms) if they're not to your liking  .
Cicero,
Yes...the visual half of PowerHome should be able to run on a remote machine (they'll likely be two versions though...one that runs on the same machine as the server so as to connect directly to the database and one that runs remote which will synchronize via sockets).
Hope this helps,
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: New Installation - What Version to Use?
