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.
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
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.
PA RC1 Patchbeam
-
Patchbeam crashes when run under WinXP
“Access Violation at address 0046B870 in module PATCHBEAM.EXE. Read of address 0000001C”.
Also, there is an empty square after each column name.
I cannot change skins or toolbars. I don’t mean to be funny, but is Win XP supported? I have, like many, ‘fixed’ my XP to continue to get the fixes. It is just an install I use for fun.
Regards
DrT
-
should be, I will check it out and let you know whats happening.
-
I have some further info that should help. If I install RC1 on top of the last v13 (which is uninstalled automatically as far as I can see) I cannot change the toolbars or icons - this time this was on win 7 x64. The icons always remain the modern blue-line only look. If I select classic toobar, the toolbar vanishes. None of these issues happened when I installed the 16.00.40 version on top of v13 and then upgraded to v16 RC1. Naturally, happy to supply any info you want so ask away.
DrT
-
I have some further info that should help. If I install RC1 on top of the last v13 (which is uninstalled automatically as far as I can see) I cannot change the toolbars or icons - this time this was on win 7 x64. The icons always remain the modern blue-line only look. If I select classic toobar, the toolbar vanishes. None of these issues happened when I installed the 16.00.40 version on top of v13 and then upgraded to v16 RC1. Naturally, happy to supply any info you want so ask away.
DrT
that makes sense, probably update over v13… since it uninstalls it but it keeps the setting.
We will check it out. Sucks that my test lab’s 8 core keeps going dead in the past 2 weeks, just when it is needed the most. Oh well, core-m is doing great replacing it, who would have thought.
-
Please check out the different results depending on which v of 2016 was used to upgrade.
These days, I tend to rely on installers to tell me if settings or an uninstall is needed.
I have no problem in removing the ‘old’ settings to see if that fixes the issue. Juts let me know what you want as always.
DrT
-
can you tell me what settings you had in 2013? Default 2013 to 2016 works fine. Did you have classic or modern toolbar?
-
I honestly cannot tell you other than to say that all instances of PA were identically configured. The only common denominator that I can tell is the version of PA 2016 used to upgrade.
Would it be helpful if I were to send you the current settings of the setups of PA that are okay and “broken”?
DrT
-
I honestly cannot tell you other than to say that all instances of PA were identically configured. The only common denominator that I can tell is the version of PA 2016 used to upgrade.
Would it be helpful if I were to send you the current settings of the setups of PA that are okay and “broken”?
DrT
broken one would help, cab and email please, thanks!
-
Done. Sent to ‘support@’.
DrT
-
Done. Sent to ‘support@’.
DrT
Cool, I will check it out now, thanks for sending it.
Just to confirm - upgrade process in Windows Installer will not delete your previous settings, it is not supposed to.
Sometimes when we change important parts of PA, there could be old setting that clashes with new PA. We test this usually so for instance default values will always work fine but it is up to us to make sure it works properly, there is not automated way.
In this case with PA 2016, toolbar component is completely new, so it has everything different compared to old one and we manually adjusted settings to match.
