First off, I've never pointed the finger at MX & demanded it be fixed for me. Just stated that my ini file is getting corrupted.
And I know damn well there aren't a string of others chiming in saying "it happens to me all the time".
That's why I'm putting it out there; I've got an issue, and am looking for a solution.Your routine must have an error that is stopping Cumulus prematurely.
And a very random one at that. What is in? 3 times in 5 months?
April 27th, (well a few days earlier, only posted after the fact).
Not an easy thing to trap.
Good suggestion. My CumulusShutdown.exe was compiled 10/10/2016, so has not been revisited since then.If your shutdown script is just that hotkey routine....Could you use a WinWaitClose to wait until the MX window closes before you do the return.
That's the only area I can bring up for question.If your shutdown script is more than that routine, what does it do next, perhaps it needs a delay there?
All this is just controlled by two Tasks.
Start Cumulus and Update WeatherLink
The Start Cumulus Task contains just one action, run the program C:\CumulusMX\CumulusMX.exe.
One key point to note with that task though is it's state: "Running" (0x41301)
It remains in that state until MX is closed down.
Is that relevant? Dunno.
Maybe the timing is too tight with those pings & WL is attempting to grab the Com port too soon & that's causing the wheels to fall off....
As it runs at 6 & 9am & 9pm, I've had ump-teen dozens of opportunities to stand there & gaze at the laptop as an hour rolls over; everything seems correctly timed on the screen.
The other thing in the equation is CumulusUtils; it opens the ini file.
But I tend not to think it's involved as it's only called in the script that runs at the 9:00am rollover;
And my most recent issue occurred at the 6:00am WL update.....