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.
CRC errors when working with WinRar ZIP files
-
Hi. I am using two PCs - one at work with old version of PA (named 2009, I can check the exact version number on monday if that helps you) and no way for upgrades (corporate policy, will be explained later) and another one at home with latest version of PA.
Few weeks ago we were informed at work that PA is getting replaced with WR which is recommended to be used, while we may keep the old version of PA installed. And this is where the problem started. At work I am creating large backup ZIP archive (around 15 GB compressed) using Win Rar 5.00 x32 running under Windows XP Pro x32. Next I am copying it onto external USB HDD and getting home. I am copying it then from external HDD to my personal HDD. As always just to be sure everything went fine I run Test operation on this archive using PA 13.x. I got thousands of CRC errors. My first thought was that this file was corrupted while moving between HDDs. But that was not the case. I got my home HDD hooked to work PC and the Test procedure went fine using WR 5.00 and PA 2009 that I got there installed. So knowing the file is not damaged I’m back with my personal HDD to home. It seems PA 13.x is wrong claiming there are CRC errors. Just to be sure I have installed at my home PC trial version of WR 5.00 (x64, running under Windows 7 x64) and the Test procedure is completed just fine. I can extract every file from this archive and they are working fine after that. So I did upgrade from PA 13.x to PA 14.01.06 - still same situation, thousands of CRC errors while running Test procedure.
Looking closely into that case I was able to isolate the problem. PA 13/14 claims there is a CRC error only on files inside this ZIP archive that have unusual characters in their filenames. By unusual I mean common Polish national characters that can be found in Windows-1250 charset (e.g. Unicode #017A character). All other files can be extracted and working file when using PA 14.
Any fix for this? It’s weird that old version of PA 2009 doesn’t have this bug, but it could be related to new multicore ZIP engine that was introuduced somewhere between those versions…
-
can you send us one example archive but with single file or something like that? I cant tell you whats wrong before checking it out.
WR has pretty wonky ZIP support, it is better to use RAR which you can open with PA. They have multicore support for RAR, I dont think they do for ZIP, so it will be faster that way.
We always have to add workarounds for various different archivers that dont implement perfect support for zip specification.
-
you can send archive to support at conexware dot com… much appreciated!
-
Hello, I attempted to reproduce this by including the Unicode #017A character in a filename and creating an backup archive via WinRar 5.00
Tested in latest PowerArchiver and it worked fine.
If you can, please do send over a sample archive to support at conexware dot com and we will take a closer lookThanks
