Hi everyone, some good news about PowerArchiver… I’ve managed to get in touch with the original developer of PowerArchiver, Ivan Petrovic, and he has confirmed that the product is not dead or abandoned, in fact it is still very much alive! There has been a hiatus over the past months for various reasons, but that we should expect to see stuff coming through in the coming months (hopefully the next 2 months).
I had a large .tar file (a backed up WSL) and I want to delete a few directories and their contents from it using PA2023.
PA just destroys the whole archive as soon as I try to delete a directory, leaving it in a state where PA2023 won’t even open it any more.
I tried several times and also tried compressing it to .tar.xz instead - same result.
This should either actually work, or it should say operation not supported and do nothing.
Hello!
The regular version of PA 2023 is out for over 6 months now, but there is still no sign of the portable release.
(When) will there be one?
Thanks!
Hello!
Is there currently no portable version of PA2023 available?
(When) do you plan to release one?
Thanks!
Win 11 64 bit
I have some archives which have been encrypted, using the encrypt option either in pbs or when interactively creating a zip. When I open these, and look at files, I am asked for passwords, which I know, and then can view items or decrypt the files in the archive (tools>decrypt files).
However, when I use the Actions>Remove Archive Encryption (whether using the same zip or asking to write another), the routine shows progress bar to the end, but then just hangs i.e. “OK” never activates. All process information shows this stalled/hanging.
What can I do to sort this out?
For example:
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
powerarc_2023-09-18_17-00-19.png
powerarc_2023-09-18_17-01-05.png
PA 22.00.09
344c6c52-f03f-407b-ad76-8130b31936bb-image.png
PA 22.00.09 shows a nag screen, when I try to open some setting windows. I have already PA 2023 Toolbox and PA shows, that it’s licensed in the info dialog.
a860bd81-3e71-4ce0-9988-74cd4189d43e-image.png
0836bc83-8046-4a91-bc7b-68bd231100a3-image.png
PA 22.00.09
Some labels in the help toolbar are not translated:
b3c1f5c4-b73d-49d8-9ed0-56294840838c-image.png
I’m looking forward to deploying PowerArchiver 2023 to my users. Can you tell us when the MSI will be available for download and distribution?
Thanks.
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.
Solved Memory leak compressing ubuntu-17.04-desktop-amd64.iso
-
I have read at https://encode.ru/threads/130-PowerArchiver?p=52611&viewfull=1#post52611 that FreeArc Next has the better compression ration while compressing ubuntu-17.04-desktop-amd64.iso.
So I tried the same with PA 17.00.69. Good news is that you guys, made it, making an even smaller resulting file.
The thing is that I guess I have detected a memory leak, because memory usage reached the 2GB while compressing, which should not be the case, considering that a 24MB PLZMA dictionary with 4 execution threads is about 900MB of memory usage.
For your information, in the same scenario, WinRAR was at 800MB of memory usage on peak.
Can you please take a look? Maybe I am wrong, and this is the normal behaviour. Maybe Windows Task Manager is not properly reporting the usage.
Thanks.
-
@nikkho there is no memory leak, those settings only apply to custom mode, not to optimized strong mode. So you are using a lot of memory of course, 64M at those settings (extreme), and also real 4 threads are used for that file. Advanced tab is least worked on feature in PA so far :). Many improvements there are still possible.
That file is compressed, so i think advantage comes due to lzmarec coder + rep1 dedup. I think it would do even better with 128 MB, lets try it :)
-
@nikkho btw, for me, real winner is Optimized Fast and Ultra or Max mode. It will finish in 30s on my computer and still be reasonably smaller due to rep1 :). Effect is better on other isos that are not as compressed as this one.
-
With the new settings, the reduction was amazing, going from 1.571.555.291 bytes to 1.037.033.705 bytes!!
Switches wers: c_out=plzma4:mt4:c16M:d128M:mc16:fb273:lc1:lp0:pb0:a1; c_adr=plzma4:mt1:d22:lc0:pb2:lp2:fb273; c_hif=lzma2:x1:d22:mt1; rep1:fb15000:c300M:mem2000M { reflate:x9{ x64flt2{ deltb:c=1000K { deltb:c=1001K { c_out }} } / c_hif } }As espected, peak memory usage raised to about 6GB with those new settings, but speed was comparable to previous trial.
-
@nikkho try c=256M, it will go down more :)
-
@nikkho memory is not a problem on x64, it works well. Of course, it is also dependent on dictionary size.
-
of course, for us, we cant set more than 64m by default, it would be unreasonable… but sure, it is fun for testing :)
-
check with large D with new release:
https://forums.powerarchiver.com/topic/5747/fast-ring-powerarchiver-2017-17-00-67-68-69-70-71-73
