-
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.
-
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.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files. -
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 memory crash with 7zip
-
Hi there,
once again… :)
You had this issue solved in last version and here it is again in the new version.
But this time I found the reason I hope.Doing my packups with 7zip of a directory. In this directory are also zip files. Whenever PA reaches the zip files that shall be compressed with 7zip it crashes with the error that the hdd is full or the directory not writable.
Unfortunately the workaround to change the compression level does not work anymore. So again no backups. :confused:
The backup with zip instead of 7zip doesnt even start. Only creates a huge progessor gain.Regards, alex
-
how many files total, both size and count, are to be backed up? thanks
-
Sorry for the delay…
9.6gb, 122000 Files and 13000 Folders…
In the previous version it worked very well…!!
-
try turning off optimized compression and see if it helps.
As to the zip, try waiting a bit - i think it is not crashing but it is taking time to build an list of files to be compressed…
thanks
-
Didn’t work either…
-
waiting a bit didnt work for zip?
-
How long…? Waited for 20 Minutes…
Something was changed for the new release I guess… :(
-
Even in the new update the error occurs. Any new ideas?
-
nope, nothing has changed… we have tested internally and we can not reproduce… we will try more.
-
Is there any more Information I can give you…
-
Would it help if I change backup type from normal to full?
-
i dont think so… try changing some other options to see if something else might be affecting it.
We have just tried creating backup from 20 GB/77,000 files and everything worked properly.
Try breaking that backup into 2 different backups - does that help?
thanks!
-
Two different jobs or just split files?
-
two different jobs… see what happens then?
thanks!
-
we believe that this issue has been fixed in Beta 1, please check it out and let us know if it works properly.
thanks!
-
Problem still exists. No improvement here…
-
well then it is some other issue :-).
so it happens only when zip files are there?
-
I splitted the same Folder in 4 jobs and it worked…
SAME FILES…!!!
Folder in 1 job crashes…
-
is there an difference now between different compresion levels in 7zip? solid/non solid?
-
Didn’t check yet. I just did a check with the same settings as the 4 jobs just in 1 job.
-
can you try compressing same folder via shell extensions, manually (not in backup), with same compression settings… does that work?
-
I uninstalled it. ALL backups didn’t run with errors solved in the last version. Did a rollback hoping things to work again.
-
Dear PA Team,
I don’t know how you are tesing. Maybe I should be one of your beta testers.
Did the rollback. Some old backup jobs work, some don’t. How can this be? Right click works. pbs does not work. I just don’t know what your QA is doing.
Look I am trying to use the tool as a daily backup tool. Wasn’t it ment that PA can do this too?
Somehow with every new verson bugs in doing backups get bigger…
Very disappointing…!!! -
…Maybe I should be one of your beta testers…
You are (as are the rest of us using it) - PA 2010 is a beta.
-
Dear PA Team,
I don’t know how you are tesing. Maybe I should be one of your beta testers.
Did the rollback. Some old backup jobs work, some don’t. How can this be? Right click works. pbs does not work. I just don’t know what your QA is doing.
Look I am trying to use the tool as a daily backup tool. Wasn’t it ment that PA can do this too?
Somehow with every new verson bugs in doing backups get bigger…
Very disappointing…!!!two big 7zip backup issues were solved in this version, and we cant reproduce issue you have so you have to help us somehow :-).
-
Can you please post your pbs file here?
I have tried many situations to reproduce this but could not, we simply need more information. I have tried compressing 200,000 files and 80 GB of data and backup worked fine.
