With running the HG612_stats.exe manually, I get a perfectly good result. It runs through the 38 steps (why not 39?)
I might add a dummy 39th step just for you.
I wonder if any of the younger readers know what we're on about
, and creates the two expected logfiles in Ongoing_Stats, alongside an ERROR logfile with a line showing "reply(config.Shell) O.K. Status = 1. "
That ERROR file is the wrong one.
That line should end up in the file of the same name, but in the
Event & Error Logs folder.
I had forgotten to direct that information to the correct file in the 'new' logs folder
That shouldn't have caused a problem though & I have fixed it now that you have alerted me to it.
I then get to see the data in the two tabs of the GUI tool.
Running it a second time adds a line to the modem_stats.log file
So the problem seems to be that HG612_Run never actually starts HG612_stats, or at least doesn't do so in a way that works, or gets included in the windows task manager.
Do you actually have
HG612_Run.exe in the Scripts folder?
I have attached a definitely working copy just in case it's missing/corrupted.
What happens if you double-click
HG612_Run.exe directly from the Scripts folder?
You shouldn't see anything on screen, but it should run
HG612_stats.exe silently, with the various log files updated accordingly.
One thing that MIGHT cause the task not to run is how it was set up via the GUI.
If you chose not to enter a password, but you actually use one when logging in to Windows, the task would have been set up, but probably not to run.
See the attached screenshot of the Task Scheduler's 'General' tab - from my own Windows 7 machine.
I need to enter a username & password when logging in to Windows, but the task was created with the
Run whether user is logged on or not option already selected.
It might be handy if you could post a copy of your
HG612_stats.ini file for us to have a close look - just in case..........