-
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.
UNSOLVED 17.00.91 I couldn't create a largish .pa in a subfolder in my GoogleDriveSync folder and things went weird. Repeatable on my PC.
-
I couldn’t create a largish .pa in a subfolder in my GoogleDriveSync folder. I right click on a subsubfolder and choose “Compress to subfolder.pa”. I’m expecting a .pa file somewhere in the region of 15MB in size. However PA halts with an error saying it doesn’t have access and leaves an unfinished .pa file and a .pa.tmp file. One of them, if I remember right the .pa file proves very difficult to delete. I went in to safe mode in the end and then I could delete it. I’ll try and investigate further soon.
-
@brian-gregory interesting… maybe gdrive is trying to sync the file and then PA cant access it?
-
@Mili can check it out…
-
Have been trying to reproduce the error, but works every time. A 20MB .PA archive created out of a subfolder in GoogleDriveSynch folder, is created properly.
Was this a one time issue for you @Brian-Gregory or happens every time?
-
Okay wait for me to investigate further.
Fails every time on my PC, but there is loads of other stuff install that might be interacting.
Seems like what I said about being unable to delete the file was wrong too, it deletes fine if you wait a while. -
if it’s a certain type of file, or maybe it is in use, let us know. we’ll try with a scenario as similar as yours
thanks again!
-
Still seen here with .92. It seems to be only when the .tmp file is created as well as the .pa file. It also seems more likely to happen when the directory being compressed is larger. Originally the directory was about 45MB of file and with Google Drive Sync (Now Backup and Sync from Google) disabled the result was an about an 18MB .pa file. But I think it’s more likely to happen if you use larger sizes. I was using Optimize Strong and Ultra.
-
@brian-gregory said in 17.00.91 I couldn't create a largish .pa in a subfolder in my GoogleDriveSync folder and things went weird. Repeatable on my PC.:
Still seen here with .92. It seems to be only when the .tmp file is created as well as the .pa file. It also seems more likely to happen when the directory being compressed is larger. Originally the directory was about 45MB of file and with Google Drive Sync (Now Backup and Sync from Google) disabled the result was an about an 18MB .pa file. But I think it’s more likely to happen if you use larger sizes. I was using Optimize Strong and Ultra.
i would guess that google sync takes over the file trying to sync it before it is done. If you go to Add window> Options, and turn off Use current folder as temp, it will use temp folder and copy end result to your google sync folder… that way it should work fine.
-
@spwolf I think the problem is that PA want’s to rename the .tmp file. Why does it work that way, if the .pa file is temporary and the .tmp file is going to be the final archive why not just use the names the other way round?
-
@brian-gregory because tmp file keeps copying into pa files at the end of different compression steps… if you disable same folder for temp in options, it will just copy end result to that folder and you would avoid this issue.
But pretty sure the problem is that google starts syncing (and locking) that file right away, while PA is still being written. Same when I tried to use Outlook pst file in google sync folder, it would cause corruption since it would lock it at the same time when Outlook is using it.
-
@spwolf No that doesn’t make any difference. It still creates both files. It appears to do one step into the .pa file copy it to the .tmp file do another bit in the .pa file append to the .tmp file etc and at the end delete the .pa and rename the .tmp to .pa.
-
@brian-gregory it should be in temp folder… @mili will log it in.