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.
PA 2010 Beta - Timestamp Issue with Backup
-
As I was running some backup function tests with the latest PA 2010 Beta, I decided to use the time stamp option as I was creating different test scenarios. This way, I thought, I could compare results much easier. Well, in the process I’ve discovered that the HMS portion of the time stamp is not being created properly at the time the ZIP file is actually written.
It turns out that the time stamp appended to the ZIP file is the time when the time stamp option was last manipulated in the script itself. For example, while editing the script, and specifically the time stamp option, the time stamp is shown as an example right underneath the option entry field. This, as it turns out will be the HMS time stamp appended to the backup file on the next run. There maybe more to it then this example, but this is what I’ve observed to this point.
-
it writes the timestamp at the time backup process/compression starts (not editing) - which is correct way of doing it, because thats when files start being backed up. For instance if you had very large backup, there might be big difference in time between start and finish of backup process.
thanks
-
I just ran another test and finally clued in to the subtle difference between specifying “HMS” versus “HmS” for hour-minutes-seconds in the time stamp field.
My apologies!
Carry on with your good work!