-
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.
Ask for Reg-Code again and again
-
Hi,
I bought PA2011 regularly in the online shop and registered my installation.
But everytime I like to decompress a zip file via right mouse menu, the non-registered box appeared and say me something like 17 days left.
If I normally start PA software and decompress the file there, it works.
What happened here??? Meanwhile this is a bit annoying :-(
Please help!!!
-
Welcome catweazle71.
I can’t recall ever seeing this issue before.
There are none of the PA team around at the moment, but hopefully there will be someone who can help you with this issue soon.
In the meantime can you tell us what OS and which version of Powerarchiver you are using (standard, professional or toolbox?) I wouldn’t think that would make a difference but the more information the devs have then the quicker they can help you.
-
Hi Luxor,
thanks for your quick answer :-)
My OS is Win7 Prof. 64bit and PA 2011 standard version is 12.00.59 (07/2011).
It is really strange, I never saw something like this before.
Could you imagine that it has something to do with an old installation? Before PA 2011 I had PA 2009. Maybe there are some old, dead or uncleaned reg entries.
Just an idea?!?!?
-
Hi Luxor,
thanks for your quick answer :-)
No problem.
My OS is Win7 Prof. 64bit and PA 2011 standard version is 12.00.59 (07/2011).
That’s great.
It is really strange, I never saw something like this before.
No neither have I and if it had arisen during the testing stages then it would have been pounced upon by the Alpha testers. ;)
Could you imagine that it has something to do with an old installation? Before PA 2011 I had PA 2009. Maybe there are some old, dead or uncleaned reg entries.
Just an idea?!?!?
It’s entirely possible I suppose, but lets wait for the devs and see what they can come up with.
They are the real brains around here. :)
-
Hi Luxor,
thanks for your quick answer :-)
My OS is Win7 Prof. 64bit and PA 2011 standard version is 12.00.59 (07/2011).
It is really strange, I never saw something like this before.
Could you imagine that it has something to do with an old installation? Before PA 2011 I had PA 2009. Maybe there are some old, dead or uncleaned reg entries.
Just an idea?!?!?
You are right on the money.
You probably have old PA 2009 installed side by side, and shell being PA 2009… try uninstalling it or uninstalling PA 2011, rebooting and then installing it again. This might replace old shell extensions with new one.
When you launch PA via shell, it is same powerarc.exe that launches when you open main PA. So it is exactly the same program, if it is registered, it should be working same in shell and main PA.
-
Thanks for the help and hints :-)
I will try this tomorrow and come back then with my report:D
-
… here. 7 Home Premium 64 bit, PA 2011 12.00.59. Fresh install - so i doubt that re-installing the app will solve the problem (there cannot be any old entries, files or whatsoever).
I have had to contact the support already in order to get a serial no. that is accepted at all (old one from the initially bought version was not longer working - resending from within my account lead to the old number, not a new one). The application itself starts now without screaming, but when using the context menu i run into the same trap as the thread starter.
More victims? Solutions? Ideas?
Regards from Germany,
Jens
-
Hmph… Can you try this version and let us know if it helps:
http://www.powerarchiver.com/test/alpha120/powarc120060int.exethanks.
-
as to the resending codes from your account - you need to do it for the PA 2011 and not for original order. PA 2011 is under free updates section. Original order will always send original order codes.
thanks!
-
Hi all,
the new version 12.00.60 works for me :D I can’t if it had worked with a new clean installation of my version (12.00.59), because I directly installed the new one.
Thank you very much for your quick solution and great support :-)))
Regards from germany,
Dirk -
Hi all,
the new version 12.00.60 works for me :D I can’t if it had worked with a new clean installation of my version (12.00.59), because I directly installed the new one.
Thank you very much for your quick solution and great support :-)))
Regards from germany,
Dirkthanks a lot for the update!
-
any substantial changes in the release you posted spwolf or was it just to cater for his issues ?
-
any substantial changes in the release you posted spwolf or was it just to cater for his issues ?
something was fixed with registration checking (but shouldnt be issue above :P) for large users… so nothing to interest an normal user really.
we will be doing .01 soon enough i guess, there are few minor issues reported so far.
-
Sorry for late reply - .60 solved the problem for me, too!