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.
Compression/File Extension Type
i have created 3 back up jobs to run at various times overnight :
on all 3 jobs i have chosen the standard “.ZIP” compression, rather than the newer .ZIPX , and made sure that the file name ended in zip - i.e.
however - the physical output file is always created as .ZIPX , i have renamed it - and opened it with an older zip utility - which appears to read the archive with no problem - so its more of a curiosity rather than a problem
this may be reporting an older thread , my apologies if it does
I can confirm this…double checked to make sure I’d selected zip and not zipx but the backup still ended up with a zipx extension.
I think it all stems from where you enter your ‘archive filename’ as seen in screenshot…
it defaults to zipx and it’s here I changed it an everything worked fine.
Thanks for your comment moles42
i do remember actually checking this when i created the backup parameters, and also has happend on 3 backup jobs…
i also opened up the backup job script file and double checked
Archive=Z:\Backup\Daily\daily.zip < –— ZIP :)
however - what i have noticed, which is interesting (well i think so), when creating a backup, and going thru the wizzard , even though i selected ZIP in the file name, and ZIP as the compression type - when getting to the end of the wizzard and selecting “backup now” - it created a ZIPX file - HOWEVER - the next day when the 3 jobs ran automatically as part of a schedule they created a correct ZIP file - so im wondering if its a bug in the wizzard (backup brogram), where subsequent runs are read from the backup script file
(i hope this makes sense) …
please try with .12 release (redownload Preview version from our site), we didnt do anything specifically for this, but i could not reproduce it.