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.
PAFree - Installation / Setup
-
Just installed 11.63.11 to see what it is like :p
Install Configuration preselected Classic View - but it is described as Classic with Preview.
But the Preview is disabled in “Free Mode”.Shell extensions still allows selection of the burner options (although they do not appear in actual shell menus).
While not really bugs - these may cause some confusion to new users.
-
By the way - the Trial Pay “advert” doesn’t fit in the pane, lower line(s) of text missing unless it is really expanded !
-
send us screenshot of trialpay… thanks for the classic view with preview part, missed that one ;-).
and?
-
Seems to be a text formatting problem.
-
closing and starting it again… works now?
-
Not consistent.
On first display it may be OK but then displays wrong after a while. Problem can be “provoked” by resizing whole PA window (especially horizontally). -
yeah, noticed that myself… we will take an look while we are doing next update.
-
Can I download the PA 2010 v11.63 free version and use the existing PA 2010 Pro Key to update to PA 2010 Pro v11.63?
-
@Keith:
Can I download the PA 2010 v11.63 free version and use the existing PA 2010 Pro Key to update to PA 2010 Pro v11.63?
Hi Keith, mine did. I installed over the top of my existing version, and it recognised my licence. :)
Windows 10 *64 - Latest TP (Fast)
-
Is there a real reason to download & install the free version? When I’m already running the Latest Pro Version?
at least according to PA’S Web Update
-
@PowerAngel:
Is there a real reason to download & install the free version? When I’m already running the Latest Pro Version?
at least according to PA’S Web Update
there is slightly real reason ;-). Few minor things were updated.
Keep in mind that it will recognize license and also that it will also correctly web update to any future Pro version as well ;-).
-
Hi, may I know when do you plan to update the main download website with the latest 11.63 version? By the way, could you please make separate installers (Pro & Free)?
Thanks in advance.
-
you can use that version, it will work fine.
We plan to issue beta version of 11.xx official release.
why do you need separate installers? (just asking).
thanks!
-
Just because a practical matter; I mean, seeing the size of the previous “Pro only” version and comparing it with the size of the latest “all in one”, the difference is noticeable. But that’s not all because, why a determined user who only want the “free” version of your program, would wanna download the “Pro” version at the same time?
As with many others diverse programs, if you have a free “lite” alternative of the program, you should offer it just like that. At the same time, all the other people who knows the additional features included in the Pro version and wanna try them, will have to download just the trialware of that “Pro only” package.
This is similar to a hypothetical x86-x64 versions distribution: why a determined user with a x86 architecture and os, would want to download an “all in one” x86-x64 combined package or vice versa?
Of course there will be users that will not mind about all these, but I think regarding options, the more the better.
-
I think we will keep Free version as it is now - where it is easier to see Pro version features even in Free version. It is also helpful to us to maintain single executable.
-
(of course there will be always an Pro version with minimum size, even if that wont matter too much as next versions will have better web update that only downloads patches).
-
it should be fine now in .12 release.
-
-
-
So I guess “web update” is just - not yet :p
@TBGBe:By the way - the Trial Pay “advert” doesn’t fit in the pane, lower line(s) of text missing unless it is really expanded
Fixed.
@TBGBe:Install Configuration preselected Classic View - but it is described as Classic with Preview.
But the Preview is disabled in “Free Mode”.Shell extensions still allows selection of the burner options (although they do not appear in actual shell menus).
No change - but so minor probably not worth making code changes for.
