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.
WinRAR 5 has a rather useful option in some cases, which is to be able to create an archive by replacing identical files with a reference to the first occurrence (hardlink) within the archive.
In case you choose to convert the file with PowerArchiver to another format, however, the resulting archive does not have all the files. It does not consider those that were present as hardlinks.
If you do a normal extraction of the RAR archive instead, even with PowerArchivier, all the files are extracted correctly.
When adding to a file archive, and selecting for example PA format, strong optimization method, extreme compression. In the Advanced Options section you change to Automatic, EXE Filter and PDF filter . You return to the main section and save the Profile. When you then reload the profile you do not have the Automatic options of EXE Filter and PDF saved there.
I noticed that instead if you change other options they are saved correctly (except for the Filter box values).
Also among the various changes to the advanced options you click the “Calculate RAM usage” button the value seems to be added to the previous one. You can see it for example just by clicking the button twice in a row, the value changes. Edit: actually after many attempts now it seems to write a stable value (it does not change with each click). Maybe a synchronization problem in the calculation?
Used PowerArchivier 2023 but there is the same behavior with the 2022
Deflate64 gone?
-
I upgraded to PA 2010 B3 recently and I notice that Deflate64 is no longer an option for compression.
Is it just a bug that it’s not showing in the beta builds or is it gone for good?
-
It’s now a “method” option for Zip files - called Deflate.
-
if that was the case, wouldn’t there be two methods then?
IE: deflate and deflate64 under method.
-
if that was the case, wouldn’t there be two methods then?
IE: deflate and deflate64 under method.
its gone because we now have many options and with testing we decided that df64 is not needed - it is considerably slower while providing minor gains in compression strenght.
