Bugtamer

Hi Manfred, 1) On the new PC, are the archives in the same location as on the old one? 2) I understand you've already tried opening the workspace. - Menu "Workspace" - Option "Open workspace...". 3) Have you tried importing the *.bcfg files (modified or not)? - Menu "Workspace" - Option "Import...". 4) Do any error or warning messages appear in the logs? Regards.

Hi Philip, Yes, I think it's as you indicate, something to be prepared for in the near future. From what I've been able to find out, it seems that a new parameter (e.g., java --enable-native-access=ALL-UNNAMED [...] or anything more specific than ALL-UNNAMED) will need to be added to the launchers (areca_run.bat and areca_run.sh), but I haven't been able to test it to confirm since I haven't been able to reproduce the message. Could you tell me: Operating system (I've tested both Windows and Linux)...

WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning

Hi Philip, Yes, I think it's as you indicate, something to be prepared for in the near future. From what I've been able to find out, it seems that a new parameter (e.g., java --enable-native-access=ALL-UNNAMED [...] or anything more specific than ALL-UNNAMED) will need to be added to the launchers (areca_run.bat and areca_run.sh), but I haven't been able to test it to confirm since I haven't been able to reproduce the message. Could you tell me: Operating system (I've tried both Windows and Linux)...

Linux file date not preserved

Since I haven't received any further messages, I understand the issue is closed with the advice provided above. If not, feel free to reopen the issue. Regards

Linux file date not preserved

We'll use the notation Areca A for the locally installed version and Areca B for the downloaded version (usually a new version). Rename (or move to another folder) Areca A to avoid a name conflict later. It's recommended that the new name or location identify that version to allow you to restore that specific version. Download and unzip the Areca B version to the destination folder. If you don't want to make any changes to your Areca workflow, rename Areca B to the name Areca A had before applying...