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.
Hello!
Is there currently no portable version of PA2023 available?
(When) do you plan to release one?
Thanks!
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.
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.
"Compress to…" problems
-
Hi guys,
In the last few weeks I’ve been looking into deploying a set of standard PowerArchiver settings across my domain, but I am encourtering some problems.
In our environment we are using XP SP2 with PowerArchiver 2004 v9.20.07.
I have set the temporary directory (along with the default add location, startup location, checkout location and default extract location) to the user’s home area (H:\ drive), but when they attempt to compress a file (without the Options menu) which exists on a drive to which they do not have write permissions, the user is left with a file in H:\ with a random name and no extension. The file is 0 bytes. I imagine this is because the temporary directory is H:.
Is there any configuration I can change to force the creation of the archive on H:\ regardless of where the original file exists? A registry change, perhaps??
Alternatively, is there a way I can only give users the Compress to Zip + Options selection on the right-click context menu, and not have “Compress to abcd.zip” so they have to enter the options menu?
Any help will be greatly appreciated!
Thanks,
Rick Giagnacovo
-
Is there any configuration I can change to force the creation of the archive on H:\ regardless of where the original file exists? A registry change, perhaps??
I don’t think it is possible to force the target drive/folder for compression.
@rgiagnacovo:Alternatively, is there a way I can only give users the Compress to Zip + Options selection on the right-click context menu, and not have “Compress to abcd.zip” so they have to enter the options menu?
Again, I don’t think so, apparently PA will only display “Compress with options” if at least one format is also activated.
Of course, if you disable the Shell Extensions completely then everyone has to use PA’s dialogue where these options would be available for setting/changing. But that is not a good solution.
However, there is “extra information” available regarding “registry settings for deploying PA” from premium support, see http://www.powerarchiver.com/support/
