This issue was spotted recently & I have been working on an update that seems to deal with it.
I'm not sure about leaving a text file open being a possible trigger, but it could have some relevance, although I haven't seen that cause any isses at my end.
Could you confirm which particular file or files seemed to trigger the issue?
With a lot of help from ColinS (testing various debugging versions & forwarding resulting error log files etc.), we seem to have found that the method used to allow access to a HG622 modem in v 1.1 has actually introduced a bug for some HG612 users.
Users most affected appear to be those with very slow PCs or having the programs working on very 'busy' PCs, especially when used as servers.
I have attached a copy of the bug-fix version (using an alternative & still automated method of determining & accessing a HG622, that now doesn't cause any issues for HG612 modem users) if you wouldn't mind trying it out.
Simply use it in the Scripts folder instead of the current version of HG612_stats.exe (after termininating any left over instances of HG612_stats.exe, CMD.exe and Conhost.exe - or rebooting the PC).
For now, it generates a specific error log file in the Ongoing_Stats folder named "ERROR.LOG_file_ERROR.TXT"
If any issues are still spotted, it would be most helpful if that log file (or snippets of it) could be posted for my detailed inspection.
FWIW, this version also deals with the known occasional Windows bug, where more than one instance of a Windows Scheduled Task attempts to run, even though it is already running.
The Task Scheduler setting to NOT run another instance doesn't always seem to work as Microsoft intended it to.
(At least on my Windows 7 PC).
http://support.microsoft.com/kb/2461249/en-us?sd=rss&spid=14019Assuming the debugging version does fix matters properly, I'll release a 'normal' version in due course.