Download this ZIP file: http://dslstats.me.uk/files/dslstats32W-6.5.zip
Everything in the ZIP file is in a directory “dslstats32W-6.5”.
However when I extract using right click “Extract Here” the name of the directory created is “2W-6.5” !
I am running PA 22.00.09 on Windows 11. I have seen the same happen with some other kinds of archive too.
If I compress a folder to a .pa using right click, Compress to folder.pa and use the new Windows 11 menu then the Options, Configuration, Miscellaneous, Use normal relative path setting is always enabled.
But I like this option disabled so I have to use the old style menu in order to get PA to compress a folder in the way I wish.
Just tried using the Modern (Windows 10) Icon set and seeing a few missing icons in both PowerArchiver Burner and PowerArchiver Encryption screens . They are all there in the Minimalistik icon set and the only difference I can see is the former is blue and the latter grey. In version 22.00.9
there were some security issues fixed in 7zip:
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
I noticed that the version of ZPAQ used is older than the latest released 7.15 https://mattmahoney.net/dc/zpaq.html also there seems to be a newer fork that adds several features https://github.com/fcorbelli/zpaqfranz
It would be useful to implement this latest version (it also maintains the same syntax and behavior as the latest official release if used the -715 flag) and add when opening a zpaq file a choice of the version of the files to show (e.g. as dummy folders represented the various versions present). Since any previous changes are stored with this format, it is possible to extract a snapshot of a certain date/version.
If I open a password-protected zipper file (created with WinRAR but I think that’s irrelevant), open it with PowerArchiver and run “Remove Encryption” on the same file, then reopen it and add a password with “Encrypt Archive,” the resulting archive will be protected with the old ZipCrypto algorithm and not AES as indicated.
(this can be verified, for example, by trying to open the archive files with Windows Explorer, which does not support the AES algorithm)
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
Unsolved .pa archive with backup parameter 'overwrite not activated' allways overwrite the archive
Two tests are involved (zip / pa)
Parameter ‘overwrite previous file’ ON (activated)
First initial run, backup created with time stamp 23:05
Second run : ok, backup is overwriten, new time stamp 23:07
Parameter set to ‘overwrite’ OFF (not activated)
First run with new parameter setting shows a time stamp of 23:31:
Second run : Backup to D:\Backups\PA Backups\Test overwrite\test zip overwrite off.zip started at 12/06/2017 23:33:49
The time stamp in explorer still is on 23:31… perfect, no overwrite
Now still with the param OFF, I change something to the soure file and saved it : file time stamp 23:44
Perfect, the zip archive is overwritten with the changed source.
Final test for the zip : a second run will show the time stamp of 23:47… no overwrite, perfect
CONCLUSION FOR AN ARCHIVE WITH ZIP COMPRESSION : parameter overwrite ON/OFF works perfect
Now the tests with a backup archive with PA COMPRESSION contains a BUG.
If you activate or disactivate the overwrite parameter, the archive will ALLWAYS BE OVERWRITEN !!
I changed the .pbs to create a .PA compressed backup, with the parameter overwrite OFF
First run , archive created with time stamp 0:16
Second run : source file unchanged, parameter overwrite OFF, the time stamp changed. The archive is OVERWRITTEN !!!
The Archive option in the .pa is empty ?
Zip is filled in
thanks for the details, checking this one out
Confirmed both, logged in. thanks very much! :)
just checked 85 and 86, seems to work fine.
Would you mind sending us the pbs script you are using to support and we will try with that
No problem, it’s on the way up
thanks for sending it @pirrbe
We tested and confirmed it occurs when Queue/testing it turned on
logged in for fixing. thanks again!