-
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.
PA - Update without Patchbeam
-
Hi Guys,
I’ve mentioned this during development but nothing was done about it.
So i am logging as an issue.
If a user removes the patchbeam application the powerarchiver application has dead links. Nor does to tell the user that Patchbeam is removed or needs installing.
These issues can be easily resolved with simple if statements and prompts.
Issue 1
In Main App clicking on Help and “Check for New Version” nothing happens…Solution
I would suggest you put in an if statment that “if” patchbeam isnt installed then prompt user and offer website link in msgbox or userform.Issue 2
In Configuration - Auto Update, on every option, tickbox and proxy are all enabled although do not work because Patchbeam is uninstalled.Solution
Put them all in frames, then on uninstall hide them all and replace with information about Patchbeam with a direct link to install. -
question is - why are you uninstalling patchbeam?
-
Two reasons my close friend….
1. To test the program’s ability with or without the patchbeam application. “The result is dead links and no clear information to the user PB is required or to consult system administrator”
2. On certain system’s i dont want patchbeam. Thus ensuring i am in complete control of major update roll outs.
And it is as simple as that, i cant see these error handling processes taking to long to implement. we have have a vba plugin menu at work that uses a thing called “FrontView” another plugin i developed. the frontview provides the user with news, updates, and database details… However, if frontview isnt available due to whatever reason it prompts the user and grey’s out sertain menu options.
-
as an administrator, you can already use our special registry keys that will disable updates from anywhere in PA :)
this is what you should use.
it is not a problem to do those things you suggested, but it is really not needed (and creates extra work, extra maintenance, extra testing). If Patchbeam is not there, then it should only suggest to reinstall it. And for admins and corporate installers, there have been these options that disable online, disable updates, heck disable half of PowerArchiver, for years now :-).
Heck, it would be as if someone deletes 7z.dll and then asks us to disable 7zip options anywhere in appliaction :-).
-
as an administrator, you can already use our special registry keys that will disable updates from anywhere in PA :)
this is what you should use.
it is not a problem to do those things you suggested, but it is really not needed (and creates extra work, extra maintenance, extra testing). If Patchbeam is not there, then it should only suggest to reinstall it. And for admins and corporate installers, there have been these options that disable online, disable updates, heck disable half of PowerArchiver, for years now :-).
Heck, it would be as if someone deletes 7z.dll and then asks us to disable 7zip options anywhere in appliaction :-).
Maybe having greyed out box’s and drop downs is a bit extensive, but i am sure a simple “if” statement that prompts the user when trying to change any settings or going to “update” explaining that patchbeam is required click here for more information etc would be less hassle.
it would be allot more professional that the application not doing anything, in my opinion. :) and you are forgetting to consider limited users who have removed patchbeam not realising its a powerarchiver extension then not being able to update it at a later date.
obviously, this can be a quick fix done at any time it doesn’t have to be now.
