-
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.
PowerArchiver Queue tasks
-
Often I extract multiple archives by selecting all the archives and choose “Extract here”. The task are added to the queue, but often I have “empty” task in the queue. It’s only written “Extract”, but no filename. When the queue execute this task, the extract dialog pops up and the queue is stopped.
It seems like the task is corrupted.
Using Win7 64Bit.
Thanks
Eric -
After futher testing, I assume the error happen when the queue is refreshed after the first task. The tasks are added correctly.
-
Problem known? Need more information? Where is the content of the queue saved? (I got a “EAccessViolation in module pastarter.exe at 0001573F…” after a queue crash, unable to restart pastarter)
Thanks -
PS: Didn’t find an entry under
"HKCU\Software\PowerArchiver\Queue " -
we will write it up to the issue tracker and check it out for next release… thanks for reporting!
-
Thanks EricSch!
This issue has been logged into our system and I have also added the link to this topic to the report so that we may let you know once it is fixed. -
Any chance that that get fixed once?
In the version 14 I have still the same problem.
It’s annoying because queue up long task and come back later to see that the queue has stopped / or is corrupted. :confused:
Even move up / down works not always for me.Thanks
-
Any chance that that get fixed once?
In the version 14 I have still the same problem.
It’s annoying because queue up long task and come back later to see that the queue has stopped / or is corrupted. :confused:
Even move up / down works not always for me.Thanks
i will check status of this on monday…
-
how many files and what kind of files are you adding (zip, rar, 7zip, tar, multivolume, etc)? I cant reproduce this, so please send us more info…
-
Last time when it happened, there were 4 files, rar, multivolume, each file total about 1-2GB and the extraction happens on a network drive.
-
maybe it is something in the name of one of the files?
-
No, no special chars, plain ASCII charset
-
so it is not named in 30 characters with dots and - and whatnot what could cause the issue possibly?
-
Yes, perhaps something like that:
battleground.afghanistan.s01e05.720p.hdtv.x264-killers.r06
Shouldn’t give problems?
-
in perfect world no, but we will test with that since all our files worked fine.
there is also unofficial:
http://dl.powerarchiver.com/2013/powarc140022int.exetry it there, we fixed few other things in queue
-
Happened again. Just to show how the queue looks.
Didn’t try the beta version yet.Thanks