MX on Windows OS - Revision history

Relleray: removed extraneous space after - on service creation

2023-02-03T15:49:39Z

removed extraneous space after - on service creation

← Older revision		Revision as of 15:49, 3 February 2023
Line 192:		Line 192:
	\|		\|
	# '''Navigate to the folder with your MX installation'''.		# '''Navigate to the folder with your MX installation'''.
	# '''Install MX service''' (as an administrative user) using <code>CumulusMX.exe - install</code>		# '''Install MX service''' (as an administrative user) using <code>CumulusMX.exe -install</code>
	# '''MX is now set up as a service'''.		# '''MX is now set up as a service'''.
	# There are other optional parameters (e.g. -port, -debug, -locale) you can add by editing registry		# There are other optional parameters (e.g. -port, -debug, -locale) you can add by editing registry

Sfws: /* How to run MX */ typo

2022-06-12T11:46:49Z

How to run MX: typo

← Older revision		Revision as of 11:46, 12 June 2022
Line 149:		Line 149:
	We need to run MX in order for it to generate a web server that will enable us to see the [[MX_Administrative_Interface\|admin interface]] where we can change [[Cumulus.ini\|settings]], view our weather data, or edit various [[:Category:Cumulus_Files\|Cumulus files]] (extreme records or log files).		We need to run MX in order for it to generate a web server that will enable us to see the [[MX_Administrative_Interface\|admin interface]] where we can change [[Cumulus.ini\|settings]], view our weather data, or edit various [[:Category:Cumulus_Files\|Cumulus files]] (extreme records or log files).

	If this is your first run of MX, please see[[First_Run_of_MX\|First Run of MX page]].		If this is your first run of MX, please see [[First_Run_of_MX\|First Run of MX page]].

	There are two ways to run MX:		There are two ways to run MX:

Sfws: /* How to run MX */ add link to new page

2022-06-12T11:46:31Z

How to run MX: add link to new page

← Older revision		Revision as of 11:46, 12 June 2022
Line 147:		Line 147:
	=How to run MX=		=How to run MX=

	We need to run MX in order for it to generate a web server that will enable us to see the [[MX_Administrative_Interface\|admin interface]] where we can change [[Cumulus.ini\|settings]], view our weather data, or edit various [[:Category:Cumulus_Files\|Cumulus files]] (extreme records or log files).		We need to run MX in order for it to generate a web server that will enable us to see the [[MX_Administrative_Interface\|admin interface]] where we can change [[Cumulus.ini\|settings]], view our weather data, or edit various [[:Category:Cumulus_Files\|Cumulus files]] (extreme records or log files).

			If this is your first run of MX, please see[[First_Run_of_MX\|First Run of MX page]].

	There are two ways to run MX:		There are two ways to run MX:

Sfws: /* Access to admin interface */

2022-05-22T13:05:04Z

Access to admin interface

← Older revision		Revision as of 13:05, 22 May 2022
Line 300:		Line 300:
	=Access to admin interface=		=Access to admin interface=

	The admin interface URL '''http://:8998/''' needs to have that wildcard "" replaced by a precise location if we are to access the [[MX_Administrative_Interface\|admin interface]] to change [[Cumulus.ini\|settings]], view our weather data, or edit various [[~~Log Files~~\|Cumulus files]] (extreme records or log files).		The admin interface URL '''http://:8998/''' needs to have that wildcard "" replaced by a precise location if we are to access the [[MX_Administrative_Interface\|admin interface]] to change [[Cumulus.ini\|settings]], view our weather data, or edit various [[:Category:Cumulus_Files\|Cumulus files]] (extreme records or log files).

	The missing part of the URL depends on how your local network is set up.		The missing part of the URL depends on how your local network is set up.

	If you are accessing the admin interface on the same device as that running MX then the "" can be replaced by "localhost", i.e. '''http://localhost:8998/''' will be used to load the admin interface into your browser.		If you are accessing the admin interface on the same device as that running MX then the "" can be replaced by "localhost", i.e. '''http://localhost:8998/''' will be used to load the admin interface into your browser.
			** (Note "localhost" will work even if you host your own database server or own web server, each of these uses a different port number to ensure the correct server is loaded)
	In the more general case when you want to access the admin interface from anywhere on your local wired and wireless interface, then the "" needs to be replaced by a string of 4 numbers representing what is called a IPv4 address (w.x.y.z) of the device you have installed MX on.		In the more general case when you want to access the admin interface from anywhere on your local wired and wireless interface, then the "" needs to be replaced by a string of 4 numbers representing what is called a IPv4 address (w.x.y.z) of the device you have installed MX on.

Sfws: /* Packages to install */

2022-05-22T12:58:33Z

Packages to install

← Older revision		Revision as of 12:58, 22 May 2022
Line 71:		Line 71:
	<big>We shall install the Cumulus software listed on [[Software]] page</big>:		<big>We shall install the Cumulus software listed on [[Software]] page</big>:
	# '''CumulusMX''':		# '''CumulusMX''':
	#* '''CumulusMX.exe''' is written in C#, that has been developed by Mark Crossley, ~~but~~ ~~still~~ ~~contains~~ some code by Steve Loft		#* '''CumulusMX.exe''' is written in C#, that has been developed by Mark Crossley, some code is contributed by other developers, some is library code used when it can be, and there remains some code by Steve Loft
	#* Download '''CumulusMX zip file’’’ from the link at[[Software#Latest_build_distribution_download]]		#* Download '''CumulusMX zip file’’’ from the link at[[Software#Latest_build_distribution_download]]
	# [[Software#Create_Missing\|'''Create Missing''']]:		# [[Software#Create_Missing\|'''Create Missing''']]:

Sfws: Minor resequencing of page

2022-05-22T12:54:17Z

Minor resequencing of page

Show changes

Sfws: Slight rewording of recent change, to make it clearer (after feedback)

2022-04-13T06:47:42Z

Slight rewording of recent change, to make it clearer (after feedback)

← Older revision		Revision as of 06:47, 13 April 2022
Line 93:		Line 93:
	#*# Microsoft tell developers to put code in '''C:\Program Files''' or ''c:\Program Files (x86)'' as these are read only folders except when software is being installed, and Microsoft tells developers to put data files for that software in '''c:\ProgramData'''		#*# Microsoft tell developers to put code in '''C:\Program Files''' or ''c:\Program Files (x86)'' as these are read only folders except when software is being installed, and Microsoft tells developers to put data files for that software in '''c:\ProgramData'''
	#*# Cumulus MX has not been developed in accordance with those Microsoft specific rules		#*# Cumulus MX has not been developed in accordance with those Microsoft specific rules
	#*# Consequently, if you did wrongly install MX in the above hierarchy, the read-only rule would mean that Microsoft stores any files that MX updates in ~~say~~ ~~the~~ ~~[[Data~~ ~~folder\|data~~ ~~sub-folder]]~~ ~~after~~ ~~the~~ ~~software~~ ~~installation~~ ~~into~~ ~~''C~~:~~\Users\user_name\AppData\Local\VirtualStore\Program Files\CumulusMX\data'' (and similar redirection for other sub-folders)~~		#*# Consequently, if you did wrongly install MX in the above hierarchy, the read-only rule would mean that Microsoft stores any files that MX updates in another place and MX would not find them, here are two examples:
			## When you use the Settings pages in MX, instead of creating/updating a [[Cumulus.ini]] file in the same folder as "CumulusMX.exe", Microsoft would create/update the file in ''C:\Users\user_name\AppData\Local\VirtualStore\Program Files\CumulusMX\Cumulus.ini''
⚫	#*# The problem then is that your Microsoft Windows computer now has two "data" (and other) sub-folders, so MX ~~gets~~ ~~confused as to~~ which sub-folder to look in ~~for each file within the data (and other) sub-folders~~ (as any file not updated is in installation sub-folder, while any file that has been updated is in the redirection sub-folder).
			## As MX runs, instead of creating files in say the [[Data folder\|data sub-folder]], Microsoft redirects any file changes, after the software installation, into ''C:\Users\user_name\AppData\Local\VirtualStore\Program Files\CumulusMX\data'' (and similar redirection for other sub-folders)
		⚫	#*# The problem then is that your Microsoft Windows computer now has two "data" (and other) sub-folders, but MX cannot know which sub-folder to look in, (as any file not updated is in installation sub-folder, while any file that has been updated is in the redirection sub-folder).

Sfws: Note at start

2022-04-06T20:39:58Z

Note at start

← Older revision		Revision as of 20:39, 6 April 2022
Line 1:		Line 1:
	{{Template:WorkInProgressBanner}}{{Template:Version badge Mx}}		{{Template:WorkInProgressBanner}}{{Template:Version badge Mx}}

			The banner above has been included as, at the time of typing this, everything on this Wiki page has been typed by a single contributor, who no longer uses Microsoft Windows to run MX. Cumulus MX is evolving rapidly, and any documentation in any page of this Wiki tends to quickly become outdated. It is therefore essential that at least one other contributor takes over updating this Wiki page.

	=Introduction=		=Introduction=

Sfws: Add explanation for why do not put in "Program Files"

2022-04-06T15:37:34Z

Add explanation for why do not put in "Program Files"

Show changes

Sfws: /* Report and data files to copy across from any previous Cumulus location */

2021-08-27T18:15:43Z

Report and data files to copy across from any previous Cumulus location

← Older revision		Revision as of 18:15, 27 August 2021
Line 21:		Line 21:
	All the (optional) files in the [[Reports folder]] can be copied across from a previous installation. It should not matter which release created past files, although ideally you need to ensure that the report naming and encoding described on that linked page remain the same.		All the (optional) files in the [[Reports folder]] can be copied across from a previous installation. It should not matter which release created past files, although ideally you need to ensure that the report naming and encoding described on that linked page remain the same.

			<br>
⚫	~~All~~ ~~the~~ ~~files~~ in ~~the [[data folder]] can also be copied across~~, ~~but~~ be ~~aware~~ ~~your~~ ~~new installation~~ ~~has~~ to ~~use~~ the ~~same~~ ~~"locale"~~ as ~~the~~ ~~old~~ installation, ~~or MX will struggle as the locale affects how new lines are stored, and how MX expects old lines to have been~~ ~~stored.~~ Microsoft Windows uses different line terminators to other operating systems, although MX should cope, any third party routines reading your data files will probably not accept a line terminator change.

			Whilst you should copy ALL the files in the [[data folder]], from any old installation into the new installation, there are several extra considerations:
⚫	If your previous Cumulus installation was of the legacy software, version 1.9.4, or earlier, then you need to do a lot of reading:
			* '''Your new MX installation will ignore any entries prior to the MX Start Date''' when it reads from [[Monthly log files]], such as [[Standard log files]], and [[Extra Sensor Files]]:
⚫	* [[Amending dayfile]] tells you about how MX is far more fussy about the content in [[dayfile.txt]]
			** See [[Cumulus.ini#Data_Logging\|'''StartDate=xxxxx''']] parameter, edit using ''Station Settings → Common Options → Advanced Options → Records Began date''
⚫	* [[:Category:Ini Files\|.ini files]] explains how time-stamps are formatted differently in the extreme tracking files
			* Be aware your new installation has to use the same "locale" as the old installation, or MX will struggle as the locale affects how new lines are stored, and how MX expects old lines to have been stored the same way.
⚫	* [[Migrating from Cumulus 1 to MX]] gives some advice about differences in settings, but be aware that the way MX handles settings varies by release, and information on the linked page may be out of date
		⚫	* If your old installation, is on a different operating system to the Microsoft Windows for your new installation, remember that Microsoft Windows uses different line terminators to all other operating systems, although MX should cope with mixed line terminators, any third party routines reading your data files will probably not accept a line terminator change.
		⚫	* If your previous Cumulus installation was of the legacy software, version 1.9.4, or earlier, then you need to do a lot of reading:
		⚫	** [[Amending dayfile]] tells you about how MX is far more fussy about the content in [[dayfile.txt]]
		⚫	** [[:Category:Ini Files\|.ini files]] explains how time-stamps are formatted differently in the extreme tracking files
		⚫	** [[Migrating from Cumulus 1 to MX]] gives some advice about differences in settings, but be aware that the way MX handles settings varies by release, and information on the linked page may be out of date

	==Configuration Files to copy across from any previous Cumulus installation==		==Configuration Files to copy across from any previous Cumulus installation==