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.
When you click on the Buy Now link, you come across four tabs - Home or Work, Enterprise Unlimited, Educational Discount, & Gift Discount.
What is the difference between a licence purchased via Gift Discount and a Home/Work licence?
Also, how can I renew the PowerArchiver Select plan a year after the purchase? Will it remind me automatically?
Comment panel hidden by preview panel
I’m not trying to invent bugs. I just happened to notice this.
I’m using the Classic interface, and under Actions > “Archive Comment…”, I have “Show comments when opening archives” selected. Also, under Miscellaneous in the options panel, I have “Automatically dock archive comments” selected.
The screen shots make this the most clear. When I arrange the comment and preview panels as seen in the first image, and then close and reopen PA (using an archive that has a comment), the result is the second image. The comment panel is there, but it’s “behind” the preview panel (i.e. if I close or move the preview panel, the comment panel is there).
When the comment and preview panels are reversed as per the first image (i.e. comment panel on the left rather than the right), PA can handle it just fine. The comment and preview panels stay put.
I found this bug (feature?) by accident, after trying to arrange the PA window the way I wanted it (comment panel on right). I started this thread as a “Comments not automatically shown” bug, but then realized the comment panel actually is there, it’s just hidden.
every bug is an bug :).
as to the panels, they are killing us, killing us :)
Overall, I love the panels.
I forgot to mention that I know the comment panel is “hidden” because if you close the preview panel (or drag it like mad), you can then see the comment panel.
we love them too, but there are many small issues with size/position, and frankly last two weeks we are banging our heads against it :)
if you like to know behind the scenes stuff, we are one of the few programs that tries to properly resize their panels/windows when you resize overall window. And these unicode components that are using are not really built for that (hence not many other programs have that). Its something that most people dont notice, but appreciate nevetheless :).