Bugtamer

Hi all! Those of you who have tried any of the new untested versions (8.2.6 or higher) can give me feedback on whether they worked well or if you encountered any problems. If you experienced any issues running Areca, please let me know. May be can be fixed. When the SWT library is updated, new platforms, such as those based on ARM, may be available. linux ppc64 ppc s390x s390 macos x86-64 x86-32 solaris sparc x86-32 aix ppc64 ppc hpux ia64

Windows Locked Files and Locked File Filter crashes

It appears that creating new Targets or editing them later would fail, but a backup could be launched if it was already created. This issue should be fixed by areca-backup-8.2.6 release or go to the latest release.

Windows Locked Files and Locked File Filter crashes

Hi Ron, I just reproduced the error described on Windows 11 with JRE 25 and JDK 21, 17, and 8, all from Temurin 64 bits, with Areca version 8.2.5. I'll take a look and see what it could be.

Hi Manfred, I dedicate some of my free time to the Areca project, and I've been busy lately. So, sorry for not replying for so long. I remember that editing the XML and removing _e worked in tests on my local machine. Regarding the location of the files (configurations and archives), it's probably not relevant. It is worth noting, however, that it's preferable not to overwrite one version of Areca with another, especially to avoid overwriting areca/config/fwk.properties, which contains ACL preferences...

Hi Stefan, It occurs to me that working in a Unix-like environment might have caused a problem with ACL permissions, something that wouldn't happen in Windows; either with read or write permissions (as applicable). Areca's ACL support needs to be compatible with the system it's trying to read from or write to, and it also needs to have sufficient permissions to do so. You can check if any ACL errors appear in the Log panel when you start Areca. If so, there's specific help for troubleshooting these...

Hi Artur, In theory, you should be able to decompress the data, but its metadata (creation dates, read-only access, ACLs, etc. - I don't recall if the path is also considered metadata) might not be fully recoverable due to the missing folders. In my experience as a user (I'm not the original developer), I seem to recall having to decompress the archives twice in some specific cases to extract the original files. Areca includes an "external" decompression and decryption tool for these types of operations,...