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.
Changing file focus does not work properly
When you try to change the focused item by the use of the keyboard. (Pressing A key will focus the first file that start with A) it does not work most of the times. I could link a preview if needed.
maybe because if you press them “fast” enough it adds them together (so pressing a and then b, will look for “ab” not b.).
Or not :-). Let us know.
The matter is that when I press a key, it does not always focus a file/folder. Sometimes it does not work for only a particular letter, this usually happens when I press its key twice, and others it does not work until I use the arrow keys to select another file/folder, make a click on a file/folder or in any part of the PowerArchiver windows.
If needed I could create a demo and upload somewhere.
so it is not an issue of it adding them together if you write them fast after each other?
In some cases it is because the key is pressed “too quick”. (It usually only works when the time interval between pressed keys is more than 1365 milliseconds but sometimes it works with less time too.)
The other behaviours do not always happen. Could it be due a software conflict?
if you could send an video or something that explains it better, it would be very good. I tried it few times and seems to work fine, but i might not be trying exactly the same thing as you.
The pressed keys are not displayed properly. I will try to upload a better demo in some days. (http://www.megaupload.com/?d=XXO4UZUW )
In the demo you can see:
1. At the beginning the “4.txt” icon is not the one it should have.
2. When the Desktop (Escritorio) is selected (Not using “C:\Documents and Settings\Administrador\Escritorio” link of the Explorer Display Stile but “Escritorio”) and a file is deleted, PowerArchive does not refresh itself
3. When key 1 is pressed two times, 11.txt file is not selected. And the same happens with the other ones.
3. Is that only for numbers, it works fine for letters?
1. weird, does that happen a often?
2. PowerArchiver does not refresh after deletion or creation, you have to press F5. Reason for it is that some users experienced AV’s with automatic refresh which we could not reproduce so that was the easiest soution (having to press F5 rather than automatically getting an AV).
1. I do not really know. I just realized this when I was creating the files for the demo.
2. In my computer PowerArchiver refreshs itself after deletion or creation of files/folders. It only does not do it on Desktop.
3. It is for numbers and letters. (aa.txt, 11.txt)
Some focus problems are generated due to the Internet view of the preview window. For example previewing pdfs.
3. i got it, it is when we have same characters typed in…