Cheers.
The particular settings I used were the result of slightly random iteration and experimentation.
I won't say they are the most appropriate, though they do look reasonable and seem to work.
I wouldn't expect Windows 8 to be different than Windows 7 in the way task scheduler works. (But then I wouldn't expect it to be different in the way OpenWith launches scripts, and it is.)
As you have seen, I do prefer the idea of launching the 'real' exe direct where possible.
~~~
One thing I have seen was the mechanism getting 'stuck' somehow when one instance tried to run but couldn't because another had the log file open; or similar conflict.
That happened particularly with the older scripts which could take a long time to run; especially during system startup when there was lots of contention for disk.
I'm not sure I've seen it happen with the new exe version.
Sometimes, once that happened things could get locked enough that manual intervention was needed to clear it.
I've got several quite long gaps in my stats because of that: when the internet was running well I didn't notice the missing stats.
Sometimes the result was that task scheduler would launch the task but it wouldn't effectively run.
When task scheduler fails to execute the task, are you sure there isn't a long-running old version still running but doing nothing?
The task scheduler setting 'If the task is already running, stop the existing instance' could help with that, depending what the exact lockup was.
--
Moved (with trepidation turned relief) to BT Infinity 2 for upload speed. Happy BE user for several years.