Ok here goes!! This is what I did.
First and this is a major point I am using DSM 7.2.1. I am not sure if the.NET 8 install is available on DSM 6.
First I created a shared directory on my raid volume called cumulusmx
I then downloaded CMX4 to my Windows Pc, unzipped it and copied the entire contents to my the cumulusmx directory on the NAS.
I then copied my V3 Cumulus.ini and strings.ini to the NAS cumulusmx Directory.
I then copied my V3 /data and /Reports folders to the NAS cumulusmx Directory.
I then renamed the /data folder in the CumulusMX directory to /datav3.
I then installed the .NET 8 runtime from the Community package source (if you do not have this source in your Package Center settings add it as
http://packages.synocommunity.com/).
I then SSH'd into the NAS under my user and tested the .NET 8 install by using "dotnet –-info" at the command line.
This should give you something like this :
David@SynologyNAS:~$ dotnet --info
Host:
Version: 8.0.4
Architecture: x64
Commit: 2d7eea2529
RID: linux-x64
.NET SDKs installed:
No SDKs were found.
.NET runtimes installed:
Microsoft.AspNetCore.App 8.0.4 [/volume1/@appstore/dotnet8-runtime/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 8.0.4 [/volume1/@appstore/dotnet8-runtime/share/dotnet/shared/Microsoft.NETCore.App]
Other architectures found:
None
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download
Using the SSH command line I then navigated to cumulusmx directory in the volume1 directory i.e. David@SynologyNAS:/volume1/cumulusmx$ (this assumes you know how to use basic linux commands such as CD to get to a directory).
I then ran the data conversion by using the command line "
dotnet MigrateData3to4.dll".
The data conversion should then run hopefully with no errors. Also note I did not have any Custom Daily log files, so no parameters were needed.
I then set up two tasks in Control Panel Task Scheduler, one to start CumulusMX and the other to stop it, so that it would automatically start and stop CumulusMX i.e. on a restart or DSM upgrade. So to do this click on Create and choose Triggered Task > User-defined script.
The “
CulmulusMX Start” task is setup to run under root on
Boot-up with Task settings to Run Command
dotnet /volume1/cumulusmx/CumulusMX.dll
The “
CulmulusMX Stop” task is setup to run under root on
Shutdown with Task settings to Run Command
pkill -f "dotnet"
OK that should be all, so to start Version 4 for the first time go back to main page of the Task Scheduler, highlight “
CumulusMX Start” and then click on
Run in the top headings of Task Scheduler.
Updating to a new version I run the “CumulusMX Stop” task, delete the interface and runtimes directories, and then copy the new versions from the release. I then copy all the main CumulusMX files from “Acknowledgements,txt” to “Updates.txt” over the existing files and then start CumulusMx as above.
Any problems let me know.