I did some more testing on the W7 problem system. Ran weatherdisplay.exe as administrator – no change to behavior (except Startwatch wouldn’t start it any more) so reverted to 252 and took off the run as administrator on the properties. The ID on the system is an Administrator of the system anyway.
The ‘non responding’ starts each minute at about :08 seconds and continues until about :45 seconds. During that time, clientrawrealtimeftp continues to upload clientraw.txt at 10 second intervals, but the contents of clientraw.txt do not change. During the ‘responding’ mode, the clientraw.txt contents updates normally.
As I said, on the cloned system, none of this behavior was observed – it’s only on the production system that 269 is exhibiting the issue.
it is odd
if you could try this test:
exit WD
renamed the data files folder (e.g datafilesbackup)
start up WD
see if problem is still happening (e.g couple of minutes)
as a test
then exit again and delete the created datafiles folder and rename the datafilesback to datafiles again
renamed datafiles. Installed 271 .exe and then unzipped the 272.zip over it.
Started 272 - same issue. Did Save/Exit.
Installed 269.exe - started WD, same issue did Save/Exit.
Installed 262.exe - started WD, same issue did Save/Exit.
renamed datafiles and put original datafiles back.
Installed 252.exe - started WD, no issues with ‘window not responding’
Looks like somewhere between 252 and 262, the main window dispatch loop code was modified and now has an issue that prevents response/updates to the main window creating ‘window not responding’.
Somewhere between 253 (which I don’t have) and .262 is where the problem now manifests.
the changes I made between those version were lost in that WD2 thread with the forum crash
it is odd though how you only seem to be the person with this particular problem
are you able to repeat the same test but with the webfiles and logfiles folders renamed?
(and just do the test with buld 272)
thanks Ken
That was the first test I’d done (renamed datafiles, installed 272, started WD) – it showed the ‘non response’ at the same times as before :05 to about :45.
I did the other tests using the same (newly created) datafiles on all the versions I had downloaded (269 and 262) with same results.
Only 252 seems to work normally (no ‘non response’).
Tis very strange, I agree. Did you modify the main dispatch loop code somewhere between 252 and the current beta?