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 on Windows 11. I have seen the same happen with some other kinds of archive too.
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
there were some security issues fixed in 7zip:
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
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.
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
Two new bugs to report.
When renaming a file in a large archive, if you press ‘enter’ twice, or click ‘ok’ once and then click it again, it will generate an error and sort of crash. Its like it somehow has already started the rename process, yet the controls let you try and start it again, and then it crashes. I say sort of, because the program stays open and the archive stays open, but you get an error message, and the listing of the files in the archive disappears from onscreen. I also say ‘large’ archive, as you only get time to try and click twice if you are dealing with a large archive. If it is a smaller one then the process completes and removes the window before you would have a chance to click a second time (although on slower computers this would probably be just as big a problem on the smaller files). I found this out because I had pressed ‘enter’ and then when it took a bit with the window still sitting there, I thought I must have hit ‘shift’ by accident or that maybe ‘enter’ was not accepted, so I then clicked the ‘Ok’ button, and was greeted with the bug. I then tried doing a similar rename, but just clicking the “Ok” button twice, and it does the same thing.
The second bug is concerning password entry. If you drag and drop a file onto a open copy of Power Archiver you will get the “Drag and Drop” window. This particular ‘add’ window seems to have a bug in the password entry validation scheme. If you select any of the encryption methods, and then enter a password, but then re-enter it in the second dialog box incorrectly, it goes away without warning you in with a dialog that the passwords don’t match. I found this out because I was trying to add a file to an archive with password protection and accidentally typed the password wrong in the re-type window, and then clicked to add the file to the archive, whereupon I got the warning that I had selected an encryption option yet had not entered a password, as it had correctly discarded the mismatching passwords, but had not warned me. I have tried other methods of invoking the ‘add’ window, and it seems that only the ‘drag and drop’ version of the ‘add’ window has this bug concerning entering non-matching passwords while trying to apply encryption.
thanks - in the future, please report bugs in separate threads, and name the thread accordingly so we can easily indentify which is which…
Sorry about posting both in one thread, I didn’t realize that it would be a problem. If these should be in different threads though, you will have to split them - as I don’t seem to be able to delete or rename a thread I have started. Also, do give feedback once you have examined/fixed the bug. Its nice to be able to track the progress of things and its interesting to find out what the underlying issues were in the first place.
NP, just for the future…
The issues should be fixed in 10.1.
Please check prerelease version 10.1 B1:
And let us know if this fixes your issue.
Well, I can happily report that both bugs are fixed in that latest build that you left a link to. Sorry for taking so long to notice your post! Anyhow, both bugs are properly squashed, and that is good! However, now I have noticed something else odd about the rename dialog. It now correctly disables input once you have begun a rename operation, BUT if you are simply changing one character of the existing name, the file won’t get renamed. If I were to try and rename a file called “beta1.exe” to “beta2.exe” it would not rename it. But if I changed more than one character, such as renaming it to “bEta2.exe” then it would work. Anyhow, thanks for fixing the first two bugs, and good luck squashing this last annoyance.
The issue should be fixed in Beta 2.
This should be fixed in latest version:
Please let us know…