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.
CRC error when out of space
-
When I try to extract a multi-part RAR file (i.e. r01, r02) to a drive that runs out of space during extraction, PowerArchiver reports a CRC error in the part that it is extracting from when the drive runs out of space… freeing up space and re-attempting extraction works fine with no CRC errors.
This has been going on for awhile because I’ve had it happen before with earlier versions. Is it a known problem?
Thanks.
-
So what’s the problem? PowerArchiver reports an error because there is no enough space and so it is not possible to restore the original file there.
-
But it doesn’t report an error saying that there’s no space left. It says there’s a CRC error in the file it’s extracting when space runs out when that’s not the real problem.
-
it is general error that says many things, including crc and lack of space, right? :-).
we will see if we can be more specific, thanks.
-
No, the error expliticly mentions a CRC error and only a CRC error.
The exact text is as follows, in a dialog with a red X icon:
“There is a CRC error on file:<file being=”" extracted=“” from=“” multi-part=“” rar=“”>
Volume:<part being=“” extracted=“” when=“” out=“” of=“” space=“”>Continue?"
…with Yes/No buttons.
If I then try and extract the same file to a drive that has enough space, it succeeds without any problems.</part></file>
-
@mbg:
No, the error expliticly mentions a CRC error and only a CRC error.
The exact text is as follows, in a dialog with a red X icon:
“There is a CRC error on file:<file being=”" extracted=“” from=“” multi-part=“” rar=“”>
Volume:<part being=“” extracted=“” when=“” out=“” of=“” space=“”>Continue?"
…with Yes/No buttons.
If I then try and extract the same file to a drive that has enough space, it succeeds without any problems.</part></file>
great, we will see if we can improve it… thanks!
-
This problem has been bugging me for a long time now. CRC error implies that the archive is corrupt and not “not enough space”. To get rid of this problem just check if there’s enough space on the drive for all the files in the archive…and warn user if there’s not enough space. Since every type of archive doesn’t contain extracted file sizes you can do a “free space” check right before poping up the error message and decide on what message to display. That’s VERY easy to code… :cool:
-
it was wrong error shown, it will be fixed, i think it is in internal versions.
-
This post is deleted! -
please check with official beta 1, and let us know if this has been fixed… thank you!
