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.
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.
I installed powarc-macos20001.dmg and I am attempting to create a password protected zip file. When I create the zip in the UI it doesn’t write the file to the destination folder. No error message is displayed. The PA app has full folder permission. I’m new to Mac, but have been running PA on Windows for a long time.
Will there be a new version of the Mac version soon?
Hi! I came across an issue when I tried to uninstall PowerArch 2013. I got an error “The specified account already exists” which broke the process. I got the same error when I tried to install the current version, without uninstalling the previous one.
So I can’t uninstall and I can’t install PowerArchiver. Any suggestions? OS Windows 8.1 x64.
This appears to be happening again with the Power Archiver 2022 shell extensions.
When I have Use Explorer Shell Extensions enabled in Power Archiver Configuration and right-click on c:\Users\username\Start Menu, (hidden Junction file), File Explorer crashes.
I have version 21.00.15 (03/2022) 64-bit installed in Windows 10 Version 21H2 (Build 19044.1826).
The online update feature within the program suggests there is a later version than the ‘.17’ available on the web site. But clicking either download or update just reinstalls version .17.
Either there isn’t an update OR
the “download” and 'update" links should be repaired.
Help with MFC-based plug-in
We have an internally-developed archive format that I would like to write a PowerArchiver plug-in for (which would also be for internal use only). The class that handles the archive file is MFC-based, and so I have started with an MFC DLL project. Using example source from Total Commander’s site, I believe I have the basics in place for an “operational” plug-in (OpenArchive, ReadHeader, ProcessFile, CloseArchive). But, when I add the plug-in to PA and then attempt to open a file with the plug-in’s associated extension, PA returns with the error dialog “PowerArchiver cannot open this file. It does not appear to be a valid archive.” I’m not well-versed as to the best way to attempt to debug the plug-in and see what might be going wrong. Can anyone share some skeleton source for a working MFC-based plug-in that I could use as reference? Thanks.
Did you try looking at current TC plugins, most of them come with source:
that should help you. Also, make sure plugin is entered properly in PA.
I did manage to get a plug-in up and working by using some of the shared source you pointed me to as a starting point. I do have a couple more questions, though:
1. GetPackerCaps never seems to be called. Does PA make use of this function? Reason being, I implemented DeleteFiles and added PK_CAPS_DELETE to the return value of GetPackerCaps, but PA still does not let me delete a file from my archive. I even tried removing and re-adding the plug-in from within PA first, but no luck. Does PA allow for plug-in formats to be modified (delete, freshen, add, etc.)?
2. I have need, under certain circumstances, to prompt the user for input during file extration. Currently, using AfxMessageBox, the message dialog is displayed and responds to keyboard input, but not mouse input (busy cursor is shown and no clicks are allowed). Is there a better way to handle this? Or is this somthing that I should not be doing altogether? (EDIT: This appears to only occur when dragging the file from PA and dropping it into the desktop or other Explorer window. Extract by double-click, or the Extract dialog works fine.)
Thanks for your help. PA’s plug-in architecture has saved me from having to write a GUI front-end myself.
1. PA currently does not support everything. I will check with our dev team if that particular function is used. We planned to implement more for next major release, but our plate is sooooo full right now :-).
2. Will check as well.
I am glad someone is making use of it :P.
One more (at the moment): I managed to determine that I needed to put my plug-in and settings.ini into a BH archive, then rename it as a .ppf in order to get PA to auto-install it. Using the settings.ini from the existing plug-ins as a guide, I was able to get the plug-in set up for a single extension. Is there a way to do multiple extensions from one settings.ini? I’ve tried:
But only the first extion is assigned to the plug-in. Any way to pull this off currently? Thanks again.