Looks promising.
It would be best if the Locations could all work as relative locations.
You may well find they do anyway without any extra work, as long as the exe is launched with the appropriate current directory.
I'm not sure why the Drive value is necessary; unless it is used to set appropriate defaults for the rest.
[Locations]
Main_folder = .
Scripts_and_Programs = Scripts
Apps_folder = Apps
Current_Stats_folder = Current_Stats
Ongoing_Stats_folder = Ongoing_Stats
(some people might prefer ".\Scripts" etc for clarity; either should work)
I agree about the Drive (at the moment).
That value isn't actually used. It may be at some other time though, so I included it just in case.
I had to include the full paths for users that may wish to split up the various folders across various drives/other folders elsewhere (maybe some on a server & some on a local PC or a memory stick/SSD drive for whatever reasons.
Personally, I'm not worried about automatic graphing.
Robuster automatic scripting will be great; but I'd rather do graphing on demand.
Perhaps I could/should change its title.
I only ever intended to graph on demand.
It can be
completely automated by running a simple batch file if required.
What it is used for is to turn graphing on or off when obtaining the snapshot Plink log data.
By default, the scripted version automatically went on to generate the graphs.
That option could be edited directly in the script (TestStats2.BAT), but it is easier/safer to do in the ini file.
e.g. I remotely monitor a couple of remote connections where there is no need to graph the Plink logs each time they are harvested on a schedule.
I have the logs emailed to me (again on a schedule) & I graph them at my end by dragging & dropping the log onto the older script or new program icon.