-
When the function for testing archives is invoked via the shell context menu (PowerArchiver > Test) then all the files in the archive get extracted to the current folder.
The test dialog reports as many errors as there are files in the archive but it fails to give any hint as to which files are supposed to be erroneous or what the nature of the problem might be. Comparing the extracted files to the originals shows no differences at all.
The .7z in question was produced with maximised compression settings in 7zip (taking forever but resulting in smaller archives than .7z produced by PowerArchiver with maximised settings). Therefore I wanted to see whether PowerArchiver can at least test .7z that it produced itself. Hence I had PowerArchiver convert a .pa with the same contents to .7z. There weren’t any errors reported but the resulting .7z contained fewer than half of the files contained in the .pa (137 of 366), so I scratched that test.
Performance is abysmal when testing via the context menu (e.g. almost 2 minutes for testing a .7z that 7zip tests in 4 seconds), but that is most likely due to the fact that the extracted files are written to disk. Testing the same .7z in the PowerArchiver GUI takes only 8 seconds but causes the mysterious appearance of a UAC dialog, as reported elsewhere.
The testing function is vital because PowerArchiver has a history of producing archives that it cannot unpack without errors or that do not conform to the respective file format standards (e.g. ZIP) so that other programs report them as erroneous.
The point of creating archives is that the files in them will most likely have to be extracted at some point. If the extraction cannot be guaranteed to produce correct results then the whole program is absolutely pointless. Actually, worse than pointless - it causes data loss and hence damage.
-
In PowerArchiver 2023 22.00.06 configuration, the option labelled “Start PowerArchiver 2023 Starter when my computer starts” seems to be redundant.
I am only allowed to change this option when PA Starter is disabled, and then it seems to be ignored.
When I enable PA Starter this option is forced to the enabled state.
I think it’d be good to remove “Start PowerArchiver 2023 Starter when my computer starts” completely. I’ve always found it confusing having both options.
Added later: However i don’t particularly want to use queue but I do like having the PAStarter icon in my tray area.
-
W10 Pro 22H2 - 64 -bit
PA 22.00.06 (PA 2023)
It has been the case with previous versions of PowerArchiver, but I had hoped that the latest might behave differently. Not so, I’m afraid.
I have, for various obscure reasons, created a few .pa archives, mainly in the hope that they will save me some more space. From time to time, I use the “Test” option to check that important archives are OK and uncorrupted.
With every .pa archive I’ve tested, the process runs through OK but then reports that there are errors. This is always the number of files in the archive e.g. if 11 files, then 11 errors reported.
In the .pa, I can:-
preview the files (usually PDF) extract some or all files and look at or use them convert the .pa to a .zip or .zipx archive, which then works fine and tests without errorsIs it the case that the Test routine isn’t designed for .pa archives, or is there another reason? Although the .pa seems to function properly, despite the test reporting errors, I would like to be sure that every .pa is OK and not “broken”.
Some of the .pas are quite old and produced with earlier PA versions (they are truly “archives”). If I extract all the files in the old .pa, create a new, fresh .pa and add back the files to that, then test the new, no errors (at least in the .pa I’ve tried this on) are reported. This would suggest a mismatch between old .pas and newer versions of PA itself.
-
-
Clipboard02.jpg
See the, supposedly, blank space where the green box is? It’s like that in Modern Light theme too. I can toggle it, but it’s missing text or shouldn’t be there I guess?
Thanks :)
-
Dear @Alpha-Testers and all of our users,
time has come for testing of PowerArchiver and PACL for macOS.
Please let us know here if you have Mac and can test latest builds.Features implemented:
PowerArchiver 2020 - tabbing, opening, extracting, adding, testing, favorite folders, support for multiple languages, opening via Finder, explorer mode, installer.
PACL 10 - support for most formats and features in Windows version.Upcoming: Tools such as archive converter, batch zip, multi-extract.
To start testing, please sign up here in this thread, and we will send you latest build.
thank you!
Ashampoo_Snap_Wednesday, November 20, 2019_12h54m56s_008_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m05s_009_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m14s_010_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m30s_011_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m39s_012_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h55m49s_013_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h56m00s_014_.png Ashampoo_Snap_Wednesday, November 20, 2019_12h54m43s_007_.png
76e97ab9-8d75-4175-9ce8-446500031f38-image.png
-
For some reason, the PowerArchiver functions in the Windows 11 context menu no longer work after the last Windows Update. Only the functions in the classic context menu function as they should.
I’ve tried uninstalling PowerArchiver and using RevoUninstaller to remove all bits and pieces that were left behind and did a clean install of PowerArchiver, it didn’t fix the issue. Other items in the Windows 11 context menu work.
PA Crash as soon as the installation finish…
-
Hi,
I have a MacBook Pro running Parallels v7 with a VM Microsoft XP Pro SP3. I installed PA 2011 and as soon as the installation ended and I click “Finish” with the “Run PA” option on I get the only windows error message asking if I want to send the report.
Does anyone have any idea why PA is not working on the VM? did I miss the prerequisite where it says “do not sun on a VM”?
Thanks,
-
Hello,
And you were previously able to install PowerArchiver using previous versions? This started with 2011?Has anything changed in the VM machine in between?
-
Hi,
I have a MacBook Pro running Parallels v7 with a VM Microsoft XP Pro SP3. I installed PA 2011 and as soon as the installation ended and I click “Finish” with the “Run PA” option on I get the only windows error message asking if I want to send the report.
Does anyone have any idea why PA is not working on the VM? did I miss the prerequisite where it says “do not sun on a VM”?
Thanks,
from what you sent via support, it looks like you are using PA 2009, not PA 2011?
maybe some mixup with installations?
-
If you installed PA 2011 when PA 2009 was running, then it is possible that PA2009 .exe was left until restart, so now you have PA 2009 exe and rest of the files from PA 2011, which is why it would be crashing.
-
Hi again and thank you for the fast reply.
The very first time I installed the PA was the newest downloaded directly from the website because I wanted to know if it works in the VM to pay for the upgrade. Since that did not work I try the version I have license for (2009) but none of them worked.
Right now I don’t have any version install in my VM. Any suggestions?
Thanks,
-
there should be no problems with VM, we run PA in different virtual machines all the time, we do a lot of our testing like that.
can you clean up your installations, restart VM and install latest version from our website, then send us screenshot of the crash so we can see better whats going on.
-
I follow your advice and remove the PA from the VM, then restart it and re install the new downloaded version of PA.
Here are the pictures:




 -
We have few people running the VM on OS X, and everyone is using vmware and not parallels… did you ever try vmware?
i remember that we tested in parallels few years ago when it came out, but that was probably different version then.
-
No I haven’t try vmware, I have a license for Parallels and I would like to keep it this way. If PA does not work with parallels that will be ok I just needed to know if it was worth it for me to upgrade to a new version. WCS I will be using some open source as I did when PA failed, not a big deal.
Thank you for your fast response and help.
-
i will try to see if someone has parallels check it out there, our 3 guys in the office used vmware for os x vm.
we dont have official os x testing computers… yet :-)
-
Your efforts are appreciated I would prefer to have PA (because I like it) than 7zip or winzip. One thing I like about parallels is “Coherence” and that is a feature that I haven’t see in VMWare.
Thanks,
-
I found why it crashes: when I use the VM without the “coherence” feature the PA works!!!
It only crashes when in “coherence” mode!!!
-
great!