5,838
edits
Category:Cumulus MX: Difference between revisions
m
→two approaches
m (→two approaches) |
|||
| Line 491: | Line 491: | ||
== two approaches == | == two approaches == | ||
#One popular approach is to rename your current install directory, then unzip the new release, letting it create a new '''CumulusMX''' folder. Copy across Cumulus.ini into that new directory, and then copy the contents of the '''data''' and '''Reports''' directories from your ''current install'' to the new install. Don't forget to copy '''strings.ini''' and any other set-up files across too. | #One popular approach is to rename your current install directory, then unzip the new release, letting it create a new '''CumulusMX''' folder. Copy across Cumulus.ini into that new directory, and then copy the contents of the '''data''' and '''Reports''' directories from your ''current install'' to the new install. Don't forget to copy '''strings.ini''' and any other set-up files across too. | ||
#However, if you have a lot of set-up files, if you are downloading on a different device, or on a different disc to where you are running MX, then after downloading simply copy the changed files into the existing MX directory on the device where you run MX. Then you know all your existing files are there, and you only change the minimum number of files as specified in the release notes (on forum or in Wiki). | #However, if you have a lot of set-up files, if you are downloading on a different device, or on a different disc to where you are running MX, then after downloading simply copy the changed files into the existing MX directory on the device where you run MX. Then you know all your existing files are there, and you only change the minimum number of files as specified in the release notes (on forum or in Wiki). | ||
== Updating when files within release might overwrite your edits === | == Updating when files within release might overwrite your edits === | ||