-
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.
12.00.49 Bug report
-
I can reproduce this.
Open archive, click on extract, and try to click on the drop down MRU box. PA locks for 5-10 secs, then a black rectangle appears for a further 5-10 secs - it is the shape and size of the expected MRU list. Then the list appears and the rest of the extract box disappears. One is then left with the PA window with the extract box hidden underneath it.
The previous version (RC3?) worked fine, my 12.00.49 on my netbook is unaffected, just my main PC.
Patchbeam reported the update as the release version, but RC4 is available on the site. I need the previous version to be able to use PA again. Please let me know where I can get it from.
Tnx.
Guy
-
I cannot reproduce this on either my desktop or laptop. Makes me think something else is clashing with this feature.
-
I cannot reproduce this on either my desktop or laptop. Makes me think something else is clashing with this feature.
Since rebooting this PC for something else, all is well. None of my other PCs (3) had this issue at all. Cancel the brown trousers <g>!
Guy</g>
-
what AV do you use?
-
we didnt do any changes that would cause this function to behave differently… but you never know… and also since we recompiled, some AV might have reset their pa.exe whitelist.
someone reporting PA starting slowly, but that also happened only once.
-
I use eset NOD 32. As I said, all is well after a reboot…damn computers making me look like a schmendrick<g>. very strange.
guy</g>
-
This post is deleted! -
Had to go back to 12.00.41 (RC3) as RC4 is totally unusable. So far, RC3 is okay. I did notice, with RC4, it took noticeably longer to the extract dialogue to appear after pressing ‘extract’ than with RC3.
Guy
-
so what happens? What OS?
-
maybe save your settings and send it over to us via support at conexware dot com. So we can try exactly the same settings.
And this happens only with extract window location MRU?
-
also that suggests that MRU had some specific folder that for some reason PA did not like… do you use maybe network folders, network drives, removable drives, etc? anything similar that would cause you to think about?
-
-
maybe save your settings and send it over to us via support at conexware dot com. So we can try exactly the same settings.
And this happens only with extract window location MRU?
Yes. All settings have been deleted as I could not do in inplace downgrade…had to manually uninstall first.
Guy
-
also that suggests that MRU had some specific folder that for some reason PA did not like… do you use maybe network folders, network drives, removable drives, etc? anything similar that would cause you to think about?
I thought of that but one moment RC3 was working, the next RC4 was not. Also, RC4 seemed to work one minute and not the next - the change happening after a reboot.
I have just ‘patchbeamed’ my RC3 to RC4 and all is well so far. MRU is empty so far and I’ll do some experimenting later.
Thanks
Guy
-
just save that mru so we will see when it happens again… it happens only with the mru there, right?
-
The problem is apparent the moment I click ‘extract’ as there is a delay before the dialogue box appears.
Only one setup has been affected, it is okay so far, will update if it occurs. Please let me know of the location where the MRU is stored.
Cheers
Guy
-
just use options> save settings to a file… and send it over…
that way we have everything in case it is connected to another option as well.
-
Will do.
Guy
-
did you get it happen again?
-
Hi,
No I did not…sorry for not posing earlier. I deliberately set a folder to my external drive in the MRU and them turned off that drive…no problems.
I’ll keep monitoring…
regards
guy
-
patchbeam to .50.
We made some changes which we thought could optimize this… but we couldnt reproduce it, so it might or might not help :-)
-
patchbeam to .50.
We made some changes which we thought could optimize this… but we couldnt reproduce it, so it might or might not help :-)
Thanks. I cannot reproduce it now either (before the update) ;).
Regards
DrT
