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.
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.
Weird anomaly where Modified time is sometimes rounded up
File’s Modified time is sometimes rounded up if seconds is 58 or 59.
This is a weird anomaly that occurs with PA, WinZip, DOpus ZIP (and probably other archive apps). When creating a ZIP archive the Modified time of some files is rounded up when the seconds component is 58 or 59. eg. If the file being Zipped up has a Modified time of 05.54.58, then the same file in the Zip archive will have a Modified time of 05.55.
If I manually set the Modified time to exactly the same time of 05.54.58 and then Zip the file up, the same file in the Zip archive will now have a Modified time of 05.54.
I have no clue as to what’s going on. Any ideas ?
I’ve attached a sample file which illustrates this problem.
EDIT: Sorry, I tried to attach the file but the process of downloading it affects the modified time, and so the problem no longer exists.
BTW, I noticed this problem because sometimes after Zipping up a folder, I will Compare the contents of the original folder with the contents of the Zip archive, getting it to flag any files whose modified date is different.
I have done some quick testing and readup (google is the king). Apperantly Win32 filetime is set at 100 interval of nano second since Jan 1, 1601, while zip format standard specs say that it is using “MS DOS format” (I think milliseconds is the lowest MS dos file format goes). This means that there is some rounding up to at the end, and notice that once you extract the file once you compress it again there wont be any more of rounding up anymore.
Very interesting thought there, i really did not know this before…
i come across this problem, however its not just msdos thats the problrm but a computers internal clock can also cause problems