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 quick lookup does not work always in explorer mode
quick lookup does not work always in explorer mode
It happens on the same file explorer, but not inside archives.
First of all, the directory listing should be long enough to better understand what is happening.
Let’s assume these are the folders visible on screen:
To type and find the files, first you must focus on the file explorer, by clicking some empty space or let’s say the first folder abc.
If you then type e or efg on the keyboard it will select the folder efg.
Let’s say we have a folder xyz on the list down there, but it is not yet visible. If you type x or xyz it will beep because it cannot find it for some reason. If I scroll down the list until xyz becomes visible, only then can I find it by typing x or xyz. Same for every file, so to have the full functionality I can scroll down the list until bottom, now each filename on the current directory will be accessible by typing until changing the directory or restarting PowerArchiver
@john I understand what the issue is, and have identified the cause - internally we have an option of smart refresh option for file list window of external explorer interface (when browsing hdd) and that will refresh only visible part of the screen. When I activate full refresh, it seems to be just fine.
As to the focus, got it… we will check rest of the windows too. Thanks.
@john Looks like this has been fixed. Can you check it out on your examples and let us know? Thanks!
You can find updated version here:
This issue doesn’t appear to be fixed, e.g. pressing z does nothing until I scroll to the bottom.
Thanks @john !
I checked and noticed the same, we have logged it in.