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
powerarc_2023-09-18_17-00-19.png
powerarc_2023-09-18_17-01-05.png
Hi there,
there were some security issues fixed in 7zip:
https://www.zerodayinitiative.com/advisories/ZDI-23-1165/
https://www.zerodayinitiative.com/advisories/ZDI-23-1164/
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
Hi,
From where I get PAVD2023.EXE? PowerArchiver 2023 tries to open it.
But it seems, it tries to download PAVD2021.EXE.
Thanks
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.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
Bug in 7z archives properties
-
when you create a 7z archive and then check its properties via PA, sometimes PA will fail to tell its compression, stating 0% when it’s not true…
For example, download this 7z archive:
[http://greg79.altervista.org/sw/debian jigdo-win-0.7.1a.7z](http://greg79.altervista.org/sw/debian jigdo-win-0.7.1a.7z) (right click and save)Then open it with PA (I’m using 9.11.01), and see that it states it has a 0% compression, while it hasn’t obviously.
Open it with WinRAR, for example, and it’ll correctly say
Uncompressed size: 2.515.893
Compressed size: 781.091
Compression ratio: 31%If it worked, PA would say 69% (to 100).
Can anyone of you confirm that, and check with some 7z files of your own?
Thanks! -
I can confirm this!
I have downloaded your archive and I have tha same problem (0%)
Also I created my own 7z archives… the same problem…Thanks,
-
any news about this, spwolf? :rolleyes:
-
any news about this, spwolf? :rolleyes:
Hi,
As mentioned in another thread, current PA does not display this info for 7zip files (under filelist either). Once we implement new 7zip code, you will be able to see this info, where available (unless it is solid archive I assume). We will have to redesign the properties window in any case, as mentioned on the wishlist.
thanks,
-
Hi,
As mentioned in another thread, current PA does not display this info for 7zip files (under filelist either).
this is not true…
in fact, I have that issue only with some 7z files, not with all of them!!look!
with the above file, all works perfectly…and it’s a 7zip file!
so,I think this is a bug, not a missing feature…
by the way…both files, are files I compressed to 7zip with PowerArchiver…and my settings for compressing include the “solid archive” option…so both files are solid archives.
what do you think?
-
Well, you are correct - 7zip saves original file size anyway.
Upon checking it a bit more - it is because of using Explorer view. It works just fine under Classic view. It seems that for 7zip, PA displays current archive path compression size info, while for other formats it shows overall info (size) at all times.
So reason % doesnt work in this case is because its compressed size is bigger than original file size and it really does not know what to do then.
thanks,
-
It seems that for 7zip, PA displays current archive path compression size info, while for other formats it shows overall info (size) at all times.
So reason % doesnt work in this case is because its compressed size is bigger than original file size and it really does not know what to do then.
I can’t understand…
what is bigger than original file size? the 7z archive’s uncompressed size is 2.515.893, its compressed size is 781.091…
what do you mean by “current archive path compression size”?
anyway, you’re right…under classic style view compression properties are correctly shown.
but, eventually, don’t you think this is a bug? I sure do.
-
If you check at the status bar, you will see that it shows current uncompressed data for FILES in the PATH that you are currently in. This means when calculating % in the properties, it comes out to negative since uncompressed size is less than compressed size. If you check at the status bar, you will see what I mean. When you go throught paths, you will notice how the values change and they should not for this purpose.
I think it is actually useful since you can now see current path info however it really should work as in Classic mode and that way compression % would be correct as well. It will be our priority to fix this BUG for next version.
thanks,
-
If you check at the status bar, you will see that it shows current uncompressed data for FILES in the PATH that you are currently in. This means when calculating % in the properties, it comes out to negative since uncompressed size is less than compressed size. If you check at the status bar, you will see what I mean. When you go throught paths, you will notice how the values change and they should not for this purpose.
ooh, ok, now I understand!
I think it is actually useful since you can now see current path info however it really should work as in Classic mode and that way compression % would be correct as well.
right! :)
It will be our priority to fix this BUG for next version.
thanks
thank you!
-
at least, for the file in my first post!
I’ll be checking with some other ones!in the meantime, very well done, guys!! :)
