-
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.
Extracted File Immediately Deleted
-
I have a gzipped raw access log file produced by a Linux (Apache) server. The file name is of the form sitename.com-month-year.gz. Note the two periods in the file name. The gzip file contains a single file with the same name except without the extension (sitename.com-month-year).
A. The first time that the file is available, it can be successfully extracted to a new folder.
B. Later a revised gzip file of the same name becomes available. I try to extract this new file to the same folder overwriting the old one. PowerArchiver asks Confirm File Overwrite? Judging by the file sizes, it wants to replace the old extracted file with the new compressed gzip file. (90 megabytes replaced by 5 megabytes.)
I answer Yes. The extraction process runs. PowerArchiver again asks Confirm File Overwrite? Now it wants to replace the 90 megabyte file with one with a size of 0 bytes. Before I can respond, the original 90 megabyte file is deleted from the folder. (After this it doesn’t matter what I answer. The original file is gone. The folder is empty.)
C. I run the extraction process again, answering Yes again to the overwrite question. Now PowerArchiver wants to replace the non-existent 90 megabyte file with the gzip file. The extraction process runs and the created file is immediately deleted.
D. Now I delete the empty folder and start the extraction again using the destination written in the extraction history menu. The extraction runs immediately but the file is again deleted right after creation.
E. It appears that if I enable the Overwrite Existing Files option AND delete both the old file and its folder, I can use PowerArchiver to create a new folder and successfully extract the file. Strangely, the extraction process runs twice but at least the file is not immediately deleted.
Is there a way to get this file extracted easily?
Windows XP, PowerArchiver Version 13.00.22
-
can you send us those files to test somehow? Best via support:
http://www.powerarchiver.com/support/(link to the files?)
that would be very helpful!
-
can you send us those files to test somehow? Best via support…
I sent the links to two files using the support form. See Ticket ID: 25938.
By the way, I don’t think this happened with earlier versions of PowerArchiver. I think it started in the last month or two.
-
This is new version PA 2012 RC1 13.00.24:
http://dl.powerarchiver.com/2012/powarc1300rc1.exeThis should work now!
Please check and let us know!
-
[QUOTE=spwolf;29431This should work now!
Please check and let us know!Nope. Still broken. Here’s the steps I used to test the new version.
A. Downloaded and installed PowerArchiver version 13.00.24.
B. Downloaded a new compressed raw access log similar to the one I provided a link to in Support Ticket ID 25938.
C. Opened the destination folder to watch the progress of the extraction.
D. Invoked PowerArchiver by opening the compressed (.gz) file.
E. Started the extraction.
F. The PowerArchiver progress bars advance to 100 percent and a file is written to the destination folder.
G. The uncompressed file is immediately deleted.
In an attempt to find other failure modes, I deleted all files from the destination directory. Then I tried the extraction again. Now PowerArchiver asks me to confirm a file overwrite. It wants to replace a non-existent file of about 103 megabytes with a file of the same name with “?” bytes. It’s confused but I answer Yes anyway. The extraction takes place and the file in the destination directory is immediately deleted.
-
please send us 7zipped your PA settings that you can save via Options> Configuration> Save settings to a file.
Previously it extracted the file 2x in shell, 3x in main PA, but for me now it works fine.
Here it never deleted the file. It might be connected to your settings, or maybe AV?
-
please send us 7zipped your PA settings …
I have attached CMB_PA_Settings.7z to Ticket ID 25938.
-
to try and solve this i had a similar problem to this a while back when i had a rouge program on my stem it would delete files of certain types after i extracted them from Pa could that be the problem
-
About a week ago I received a note from support on the trouble ticket that I filed. They have reproduced the problem in the 32 bit version of Windows. Eventually a fix will be forthcoming.
-
Hi,
please check PA 2012 13.00.25 via Patchbeam and see if it works better now… thanks!
p.s. problem was that for these files (not every gz!), under 32bit, PA engine would set the files with hidden flag, so they ended up being hidden :-).
-
…check PA 2012 13.00.25 …and see if it works better now…
I installed 13.00.25 and restarted my computer. I opened one of the raw access logs that always failed before. Now it extracts the file and does not delete it.
We’re now back to the PowerArchiver I remember. Whatever was broken in version 13 is now repaired. :)
-
great!