It was iffy on Vista, but is not a problem on XP, W7 or WHS2011. In fact I've been running it 24/7 on my server since August, and the only time it's missed a beat is when I was using the old scripts, been using the exe since September and it's been totally reliable. I'm certain it's a W8 problem.

In reply to a post by BatBoy:

Running as a service would be a very good idea.

That was always my opinion to, but to keep it standalone without an installation program, and to keep the programming simple the Bald_Eagle decided not to pursue that avenue.

When I get time I'll see if I can produce a service to run the program every minute.

In reply to a post by R0NSKI:

When I get time I'll see if I can produce a service to run the program every minute.

If you sorted out how to set it up as a service that runs 24/7, I could add the code to the existing program to trigger the harvesting every minute (if that seems to be a viable option).

TBH, I don't have the foggiest idea how to simply set anything up to run as a service ("simply" being the operative word).

Could you add code to run it every [user defined] interval?

oh, and here's some example code for a service http://www.devx.com/cplus/Article/9857

Edited by deleted (Tue 02-Apr-13 22:33:45)

In reply to a post by BatBoy:

Could you add code to run it every [user defined] interval?

I presume you mean to run the harvesting more frequently than every minute?
If that's why you ask, how do you see it being beneficial?

I could do that, but would then also have to amend the graphing elements to accommodate more frequent data harvests.

So, at the moment, I don't intend to do that.
I'm still adding subtle tweaks here & there & once I've finished, I'll release an update, probably also including the 'C' code for others to pick up & 'enhance' as they see fit.

oh, and here's some example code for a service http://www.devx.com/cplus/Article/9857

Thanks for the link. I'll have a look at that as soon as I get chance.

Update on failing task manager, Windows 8.

I still get the task scheduler failing to work properly, just forgetting to run the task.
I'm amazed Microsoft still can't provide a task scheduler that doesn't make glaring mistakes.

I also got the HG612_stats.exe still running issue yesterday.
That is very rare with the new code; I think it was because of a modem reset (something to do only very occasionally).
I changed my tasks in Task Manager so that under 'settings' it says 'Stop the task if it runs longer than: 30 seconds'
I needed to type '30 seconds' in explicitly, it wasn't offered on the dropdown.

If you look in task manager history for the task you can tell the difference between the two cases above.
For the first, there won't be regular entries in the log at all.
For the second, there will be entries saying something like
Task Scheduler did not launch task "\testhg2" because instance "{6ae24bde-a441-4554-80dc-f0f358c6176d}" of the same task is already running.
Lack of filtering and slow sorting in the Task Scheduler history window is another task scheduler issue.