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.
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!! :)
