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.
if you down load any sony dvd player firmware update it shows the powearrchiver iso icon but can not be opened with powearrchiver. the file is called SNEEC900.BIN
I think Sony and other brands encrypt iso so users can’t alter the files contained such as firmware etc can’t be modified.
Out of curiosity have you tried another zip program to see if this is the cause?
if that was the case shouldn’t powerarchiver be able to detect this and inform me
Not really, think about it. The whole point of them ensuring their devices can be updated correctly is to secure the data and method in which it’s contained.
So they would use there own software or code to create a locked down version using ISO as a format. it doesnt really mean it is the same structure of an ISO, An example would be DVD’s within them are VOB Files which are split Mpeg’s saved differently so additional methods can be attached when playing a dvd.
In order for powerarchiver to read a format and display the contents or tell the user its encypted that ISO format must be created using the set method of rules including Encryption.
It wouldnt be a very secure method if third party applications like PowerArchiver, WinZip, Stuffit or winrar could not only Open the format but read it and even tell you it’s encryption method.
That then give’s hackers an imidiate platform to go off, make atempts to alter the code and then the source code which is not what sony, panasonic or any other major brand would like.
just tried with powerIso and no good :)
how the average user supposed to know this if pa does not inform the user that the iso has been locked?
shouldn’t pa tell us?
I am sure there is a prompt that PA or other apps could implement that would tell the user it can’t recognise the ISO format.
However, PA isnt the only application that isnt able to read this particular ISO.
If its an unrecognied format how can it be reported?
ie when you open an exe with notepad you dont get a error message from notpad saying it cant read it you just get raw rubbish code interprited as best as possible by that application.
If PA cant read or understand the format how can it report to the user other than “Cant Recognise Format”
that will be up to the development team to decide on. :)
doesnt it tell you it cant read it?
As with everything David’s use of ISO’s will be different to my own bar the ISO’s I download and create from my own licenced software etc i dont have any issues so I have never had a situation when an error message need to apear.
this bin file is not an iso file at all… it is firmware for device, it is not going to be openable by any iso software.
PA does associate with bin files because some of them are legitimate disc images. There is no way to know which one is which without actually opening the file.
;) Thats what i was trying to say… its may be classed as a file but as its firmware it may not be associated correctly as an ISO.
true but it would be nice to be able to open these files as they are an archive format. It would be nice for powearchiver to tell me it cant open them for a reason not associate an icon to them just becasue they may or may not open in powerarchiver.
Bin is a popu;ar format and it would be nice to be able to work with them. I know that some are protected but it would be nice to know that.
it cant un-associate the icon obviously, because it doesnt know what kind of file it is until it opens it up.
it is like that for every format… Thats simply not possible to do.
You can un-associate it yourself if it bothers you, but there is not much else we can do as there are proper disc images with extension name .bin.