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 errors
Is 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.
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.
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.
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
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.
Adding files to a .pae archive
I have an archive which is encrypted and contains several files. From time to time, I wish to add files (plain pdfs) and delete others from the .pae file.
I open the file with the password, which is OK (the archive is opened in a temporary folder), and add the file. This appears to go OK, and I am asked if I want to update the encrypted file (Yes). However, when I go back to the encrypted archive, the file has NOT been added.
This also seems to happen when I wish to delete files from the encrypt i.e. they are still there!
O/S is Win XP Pro.
what compression format is used?
Zip, normal compression, Rijndael aes 256 bit, no other encryption options selected
seems to work here… few questions:
- what version are you using?
- are you using password manager?
PA 9.62.03, and not using Password Manager.
I have just had another trial and the problem is still there.
If the decrypted archive is output to a temporary folder, would that be a problem?
The encrypted pae file is contained within another archive file (plain old zip), which is NOT in My Documents, but in a subfolder of Documents and Settings.
If I open the containing zip and extract the pae to my normal MY Documents/Archives directory, I seem able (after a brief test) to work on it correctly i.e. the problems I mentioned in the first place don’t occur.
Next I will extract the pae file to the D & S subfolder and see if it works OK there. If it does, then the problem may be connected to decrypting an archive from within and unencrypted zip archive. If it doesn’t then the problem may perhaps be something to do with the directory structures and where things are.
Will post back directly I have done this.
ah, so you are working on pae file inside of an zip file?
Correct. I am working on the pae file directly within the zip i.e. opening zip, selecting and opening pae file from there, adding files, closing pae.
I have tried this in a different manner. I have opened my zip, and extracted the pae file to the same (non My Documents) directory, and then worked on it from there (the pae sits alongside its container zip file).
This seems to work, but not without oddities. If I add a file, I then close the pae and am then asked for the password. This is refused, and then I get the pae showing the file as
filename.zip+ (i.e. the pae content), which I can then open with the password.
It would seem that working on a pae nested in a zip is not correct.
I am also working with “reuse PA windows” enabled, so I don’t get multiple occurrences of PA running. Perhaps this inhibits what is effectively the use of 2 PA files (zip and pae) at the same time?
hm, I dont think we ever tested pae inside of zip. Have to do that.
Why are you adding pae file to the zip file? Is there any specific reason to do that?
As to the oddity - it is normal behaviour. You change pae file, it asks you for the password to update the file. If you do not give the password, it will not re-open the pae file.
I find that it is useful sometimes to work with “container files” (DEC VAX VMS style) to hold all data in one place. This allows me to effectively ignore anything else in that directory or folder, as the important stuff sits in the container zip.
The concept is pretty much the same as ordinary files within an archive; where if you want to, you can open, for example, a pdf or document with the appropriate application, do things to it and save the altered file back to the archive.
The difference in this case is that there is a third level i.e. zip file holding encrypted (pae) zips, in turn containing other application files some of which may themselves be further encrypted.
I realise of course that there is no compression advantage between the “container” zip and the pae’s within - it’s only a file management strategy.
I take your point about the other zip behaviour I mentioned.