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.
Annoying bug when using "Batch Archive Creation"
Hi, this is a bug that I reported earlier in 2009 thru’ email after trying a trial version and in a very detailed way, but regrettably it is still present. :(
I don’t have the enough time to recreate it thoroughly again, but I’ll try the best to let you understand anyway.
Let’s say I want to use the “BAC” tool to create a “x” amount of ZIP, 7ZIP or other compressed files. I take for example, 10 JPG files and compress them to ZIP format. It is all right, but here begins the problem:
It doesn’t matter the file type or amount of files you use, PA will always alters the name of the resultant compressed files “adding them a dash followed by the extensions” of the files you are working with.
Since I don’t know English very well, I hope these graphical steps from this example, help you understand my above explanation:
1- Select 10 JPG files to convert them to ZIP format:
2- Run the conversion and get the result:
As I said before, it doesn’t matter the amount of files nor the file type you are using, PA will always rename the resultant files. In this specific case, you may observe what I mean in the “_jpg” part of the files.
After all the conversions, there will always be an “_xxx” renaming addenda for all the files, made by PA.
3- The right result should be, “directly”, this:
I hope you can fix this, so nobody else will have to make an additional step with a renaming tool, just to fix the files.
Thanks for writing Juan!
The extensions are there to keep filename conflicts from occurring.
If you have Test.doc and Test.jpg and Test.png all in the same folder and you want to create batch ZIP archive. You would have 3 Test.zip files all going to exact the same location and Windows does not allow that
That’s comprehensible, but I think those particular cases you mention are not the “general” cases of a regular user. Moreover, PA doesn’t make any distinction when it manage the files, I mean, the renaming process will be always there although you don’t need it.
The best solution you can implement here would be a “context sensitive” PA’s feature, i.e., in the eventual case (just in those particular cases) a user have a similar situation to the one you mentioned before, PA will detect and apply that renaming process automatically. And in all the other cases when it is unnecessary it applies the renaming process, it just will not do it.
yes, but it is not simple at all ;-). So we can put it on wishlist for one of the future versions.
btw. we changed it to this behaviour because we got plenty of bugs reported when people had same filenames ;-).
bump to take a look at this for b4
Hi, maybe you can find some workaround to this, it’s been three years so far after all and it’s still present. :)
By the way, could you make some of your program windows’ re-sizable? Mainly the ones related to “Archive Converter…” and “Batch Archive Creation…”.