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.
Unsolved 17.00.91 I couldn't create a largish .pa in a subfolder in my GoogleDriveSync folder and things went weird. Repeatable on my PC.
-
I couldn’t create a largish .pa in a subfolder in my GoogleDriveSync folder. I right click on a subsubfolder and choose “Compress to subfolder.pa”. I’m expecting a .pa file somewhere in the region of 15MB in size. However PA halts with an error saying it doesn’t have access and leaves an unfinished .pa file and a .pa.tmp file. One of them, if I remember right the .pa file proves very difficult to delete. I went in to safe mode in the end and then I could delete it. I’ll try and investigate further soon.
-
@brian-gregory interesting… maybe gdrive is trying to sync the file and then PA cant access it?
-
@Mili can check it out…
-
Have been trying to reproduce the error, but works every time. A 20MB .PA archive created out of a subfolder in GoogleDriveSynch folder, is created properly.
Was this a one time issue for you @Brian-Gregory or happens every time?
-
Okay wait for me to investigate further.
Fails every time on my PC, but there is loads of other stuff install that might be interacting.
Seems like what I said about being unable to delete the file was wrong too, it deletes fine if you wait a while. -
if it’s a certain type of file, or maybe it is in use, let us know. we’ll try with a scenario as similar as yours
thanks again!
-
Still seen here with .92. It seems to be only when the .tmp file is created as well as the .pa file. It also seems more likely to happen when the directory being compressed is larger. Originally the directory was about 45MB of file and with Google Drive Sync (Now Backup and Sync from Google) disabled the result was an about an 18MB .pa file. But I think it’s more likely to happen if you use larger sizes. I was using Optimize Strong and Ultra.
-
@brian-gregory said in 17.00.91 I couldn't create a largish .pa in a subfolder in my GoogleDriveSync folder and things went weird. Repeatable on my PC.:
Still seen here with .92. It seems to be only when the .tmp file is created as well as the .pa file. It also seems more likely to happen when the directory being compressed is larger. Originally the directory was about 45MB of file and with Google Drive Sync (Now Backup and Sync from Google) disabled the result was an about an 18MB .pa file. But I think it’s more likely to happen if you use larger sizes. I was using Optimize Strong and Ultra.
i would guess that google sync takes over the file trying to sync it before it is done. If you go to Add window> Options, and turn off Use current folder as temp, it will use temp folder and copy end result to your google sync folder… that way it should work fine.
-
@spwolf I think the problem is that PA want’s to rename the .tmp file. Why does it work that way, if the .pa file is temporary and the .tmp file is going to be the final archive why not just use the names the other way round?
-
@brian-gregory because tmp file keeps copying into pa files at the end of different compression steps… if you disable same folder for temp in options, it will just copy end result to that folder and you would avoid this issue.
But pretty sure the problem is that google starts syncing (and locking) that file right away, while PA is still being written. Same when I tried to use Outlook pst file in google sync folder, it would cause corruption since it would lock it at the same time when Outlook is using it.
-
@spwolf No that doesn’t make any difference. It still creates both files. It appears to do one step into the .pa file copy it to the .tmp file do another bit in the .pa file append to the .tmp file etc and at the end delete the .pa and rename the .tmp to .pa.
-
@brian-gregory it should be in temp folder… @mili will log it in.
