5,838
edits
Updating MX to new version: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
Updating MX to new version (view source)
Revision as of 15:11, 21 January 2021
, 15:11, 21 January 2021→The rename old approach: added 2nd point about disadvantage stopping it being recommended
m (→The rename old approach: added 2nd point about disadvantage stopping it being recommended) |
|||
| Line 267: | Line 267: | ||
#The popular approach recommended by many forum contributors in many different posts (including at [https://cumulus.hosiene.co.uk/viewtopic.php?p=141763#p141763 this post by Mark Crossley for example] is to rename your current install directory, then unzip the new release, letting it create a new '''CumulusMX''' folder (or whatever name you prefer and specify in unzip options). | #The popular approach recommended by many forum contributors in many different posts (including at [https://cumulus.hosiene.co.uk/viewtopic.php?p=141763#p141763 this post by Mark Crossley for example] is to rename your current install directory, then unzip the new release, letting it create a new '''CumulusMX''' folder (or whatever name you prefer and specify in unzip options). | ||
#Copy across '''Cumulus.ini''' and '''string.ini''' into that new directory, and then copy the contents of the '''data''' and '''Reports''' directories from your ''current install'' to the new install. | #However, you will find that this option is not being recommended any more, because it relies on you knowing which files (see final point) you need to copy back. | ||
#Copy across '''Cumulus.ini''' and (if you use it) '''string.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 any other set-up files across too. | #Don't forget to copy any other set-up files across too. | ||
#*The advantage (as Mark says) is that you ensure you do use all the files in the new release, and don't miss out any he may have forgotten to mention in his release announcement. | #*The advantage (as Mark says) is that you ensure you do use all the files in the new release, and don't miss out any he may have forgotten to mention in his release announcement. | ||
| Line 273: | Line 274: | ||
#*Another advantage (as PaulMy says [https://cumulus.hosiene.co.uk/viewtopic.php?p=140262#p140262 here for example]) is that you retain your old set-up intact and can easily restore it should you have a problem with new release. | #*Another advantage (as PaulMy says [https://cumulus.hosiene.co.uk/viewtopic.php?p=140262#p140262 here for example]) is that you retain your old set-up intact and can easily restore it should you have a problem with new release. | ||
#Various people advise that you don't delete your old installation for a week or so; as you may notice something from the older version that you haven't copied across! | #Various people advise that you don't delete your old installation for a week or so; as you may notice something from the older version that you haven't copied across! | ||
#Check again that you copied across strings.ini, twitter.txt, Cumulus.ini, and similar files in the same folder level as CumulusMX.exe, as well as all the files in the '''data''' and '''Reports''' sub-folders. Then, provided you are happy, you can delete the old release when you want to reduce clutter on your storage discs. | #Check again that you copied across (you may not have all of these files, but if you have them in old installation then you need them in new installation) '''strings.ini''', '''twitter.txt''', '''Cumulus.ini''', and similar files in the same folder level as CumulusMX.exe, as well as all the files in the '''data''' and '''Reports''' sub-folders. Then, provided you are happy, you can delete the old release when you want to reduce clutter on your storage discs. | ||
===The overwrite approach=== | ===The overwrite approach=== | ||
