05-09-2011, 07:50 AM
I installed 3.2.8 over the weekend, but immediately hit a problem and had to revert back to an earlier version.
After install, I got the missing file exception as noted by many others which was easily resolved by adding the missing file back from the link in the forum post. Thereafter it would start up OK, and apparently all looked well...
However, *ANY* attempt at communication with Comfort caused comfigurator to absolutely lock up... it would show \"(Not Responding)\" in the title bar, and it became completely unresponsive to any input. No amount of time passing resulted in it coming back to life (I left it in this state overnight, and it was still frozen the next morning). When in this state the only possible course was to kill the program via Task Manager.
I did numerous reboots and tried numerous different options that required communication with Comfort; - Scan for modules, set time, upload config etc. - any & every attempt to communicate with the panel ended with the application freezing.
So I uninstalled it via control panel, reinstalled an older version, repeated the above actions, and everything was back functioning as normal & I was able to upload a config file with no such problems, thus seemingly exhonorating my PC or other parts of the infrastructure as being the cause...
Note that during the above tests I tried both with my normal config file loaded, and with an \"empty\" config and the results did not vary, so I don\'t believe anything in my config file could have been the cause.
So for now I am back running an older version and I guess I\'ll try again when 3.2.9 comes out... :-(
Regards
Paul G.
After install, I got the missing file exception as noted by many others which was easily resolved by adding the missing file back from the link in the forum post. Thereafter it would start up OK, and apparently all looked well...
However, *ANY* attempt at communication with Comfort caused comfigurator to absolutely lock up... it would show \"(Not Responding)\" in the title bar, and it became completely unresponsive to any input. No amount of time passing resulted in it coming back to life (I left it in this state overnight, and it was still frozen the next morning). When in this state the only possible course was to kill the program via Task Manager.
I did numerous reboots and tried numerous different options that required communication with Comfort; - Scan for modules, set time, upload config etc. - any & every attempt to communicate with the panel ended with the application freezing.
So I uninstalled it via control panel, reinstalled an older version, repeated the above actions, and everything was back functioning as normal & I was able to upload a config file with no such problems, thus seemingly exhonorating my PC or other parts of the infrastructure as being the cause...
Note that during the above tests I tried both with my normal config file loaded, and with an \"empty\" config and the results did not vary, so I don\'t believe anything in my config file could have been the cause.
So for now I am back running an older version and I guess I\'ll try again when 3.2.9 comes out... :-(
Regards
Paul G.