Cumulus.ini (preserving history): Difference between revisions

Cumulus.ini (preserving history) (view source)

Revision as of 11:21, 1 August 2020

1,035 bytes added , 11:21, 1 August 2020

m

→‎Initialisation

Sfws

5,838

edits

@@ Line 418: / Line 418: @@
 == Initialisation ==
-When Cumulus 1.x.y is run for the very first time, the ''Station settings'' screen within the '''Configuration''' menu is displayed, so that the basic minimum settings can be entered into a 'Cumulus.ini' that it will then create. Should you accidentally delete Cumulus.ini this would happen again, so it is always best to take a backup of the complete Cumulus directory and sub-directories so nothing is lost in such a situation.
-For Cumulus MX, again when it is run for first time, unless it has been given a Cumulus.ini file created for Cumulus 1, you will need to set some settings. However, Cumulus MX does save a back up automatically at the end of each day.
+See [[Setup]] for detailed advice, on how to choose the settings when you first run Cumulus (1 or MX).
-See [[Setup]] for further advice, noting in particular that some settings (such as units, date/time formats) should stay unchanged, because if you do change those you will need to edit all the other files that Cumulus creates to reflect those changes.
+Note in particular, that some settings (such as units, date/time formats) must be got right first time. If you do change those later, it is a lot of work because you will need to edit all the other files that Cumulus creates to reflect those changes.
+=== Initialisation by Cumulus 1 ===
+When Cumulus 1.x.y is run for the very first time, the ''Station settings'' screen within the '''Configuration''' menu is displayed, so that the basic minimum settings can be entered into a 'cumulus.ini' that it will then create. Should you accidentally delete Cumulus.ini this would happen again, so it is always best to take a backup of the complete Cumulus directory and sub-directories so nothing is lost in such a situation.
+=== Initialisation by MX ===
+For Cumulus MX, if it has been given a '''Cumulus.ini''' file created for Cumulus 1, then apart from a couple of parameters already mentioned, MX has all the settings it needs.
+However, if Cumulus MX is being run for the first time and it does not inherit a file, it needs some settings before it can do anything.  The difference is that MX just hangs, unless you look at the Terminal output or the file it creates in [[MXDiags]], you won't know it is waiting for settings. You need to start up the admin interface and go into the various settings pages yourself to select what MX needs to continue to work. You then need to stop MX so it stores those settings and can use them next time it starts. Although some settings can take effect while MX is running, others only take on their new values when MX is restarted.
+Should you accidentally delete Cumulus.ini, or should you close MX badly so it does not manage to correctly save the entire contents of Cumulus.ini, MX has an advantage in that it saves Cumulus.ini into the backup folder every time it restarts and every time it does a rollover.
 == Settings controlled by application ==