Until recently I had my Cumulus installation running on a Windows 7 machine, and used a scheduled task to start it up. A few weeks ago I moved Cumulus to a Windows 10 machine, but did not get around to implementing the scheduled task revision to startup Cumulus. Unfortunately, this meant that when I rebooted a couple of hours before leaving on a four day trip last week, I forgot to restart Cumulus, so my Weather Underground and personal web site did not update for days.
So just this morning I added a Cumulus startup line to my existing scheduled task triggered by my user logon on the Windows 10 machine.
It worked. So, corrour24, it can work with current version cumulus and Windows 10. What remains is possible configuration differences, either of our host machines, or of Cumulus, or of details of how we did the scheduled startup. Mine was not based on Steve's FAQ, so may differ from yours materially.
Just hitting the highlights:
In Task Scheduler|Task Scheduler Library
general properties: set to run only when user is logged on, and to run at highest privileges
Trigger: at log on (of my own user ID), delay task for 30 seconds
Action: start a program (which in my case is set to run a batch file)
looking into the contents of the batch file itself, the line which actually starts up Cumulus is this one:
Code: Select all
start /d "C:\Tools\Cumulus" cumulus.exe
Obviously the directory specification part of this reflects the location where I have Cumulus installed on my PC, which is almost certainly different from yours.
As part of the history of my development of other things I do to my PC with this delayed startup batch file, I generally have a few seconds of delay between each actual program start. The construct I use for this is the timeout command. For example:
imposes a delay of 5 seconds