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.
Error opening archive
Every once in a while I get this error:
Access violation at address 007206C2 in module ‘POWERARC.EXE’. Read of address FFFFFFFF
It happens when an archive is sent to PA from the commandline…ie double clicking archive, opening archive after downloading, etc.
If I open PA directly, I can then open the archive just fine. I can also right-click and select the extract xxx options and that works ok.
When this happens, I can also restart the computer, double-click the archive and it opens just fine.
I am using v9.02. Any ideas?
What is your OS?
XP Pro SP1
Does it happen with all kind of archives or? Is there anything specific to it?
What do you need to do to get the error show, just open the archive or?
Unfortunately, I cannot create the error on demand. I usually only open Zip archives, so I am not sure if the error will occur with others.
Usually, the error will rear it’s head when I download a file (I use IE) and open it by clicking the “open” button.
Once I get the error, no archive will open unless I either: open PA and open the file from the file menu, right-click and select extract or just restart (after which I can open the file by double-clicking it).
do you have by any chance some antivirus or some similar tool? Since I really cant see any possible reason for PowerArchiver doing this - it certainly seems as if something is doing something with a file before sending it to PowerArchiver.
Yes, I use EZArmor from CA. Perhaps I should try another antivirus? Thankfully, I am still evaluating it.
Your antivirus probably scans the file before it gets opened, and somehow it sometimes does not work, obviously :-).
Maybe you can disable this scanning option?