PA 2023 22.00.08
Long time no seeing. So I start up the new year with a first problem : the virtual driver cannot be installed. Reason : it is missing in the Fast Ring PatchBeam Update Service…
Virtual driver PA 2023-01-28 152607.png
It seems a standard problem with new releases :-)
Can I have a link or can it be fixed. Thank you. CU later
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 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.
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.
Adding a file and a directory fails?
Hello PowerArchiver team,
I am now trying the program. I am using the latest version (10.11.01).
I noticed a behavior that I don’t know if it is a bug or intended. I think it is problematic.
Here it is:
I created a new, empty ZIP archive.
Then I opened a folder (in Windows Explorer) named ‘Foo’.
This folder contains two folders and one file:
1. When dragging the empty folder to the PowerArchiver window, it is not added.
2. When dragging the empty folder and the non-empty folder, only the non-empty folder is added.
3. When dragging the file and another folder together (empty or non-empy), only the file is added.
As I see it, all three behaviors are problematic, while the third one is a fault.
Another thing I think you should change is that when dragging a single folder or adding it via the Add dialog box, the content of the folder is added, but not the folder itself. I think it is makes more sense to add the folder and it’s content, just as it being done when selecting more than one folder at a time.
Please let me know what you think. I’ll he happy to give more information if you need it.
thanks for the info - we will check it out.
OK, sure. I’ll come back to see what you came up with
Can you confirm that this is indeed a problem?
And another small suggestion:
Why not implement the go back/go forward option for zip files to?
we are looking at it right now
3. should be fixed.
2. You need to enable “normal relative path” option in configuration> misc. for this to work as you intend it. Let me know if it works properly then.
1. You can not just add empty folder without any files to zip archive currently. There has to be an file being added or it doesnt work.
I hope that helps.
Thanks for the answer. I hope you will fix what need to be fixed. I also want to add that imho, the program should also support adding empty folders, unless the format does not allow it (which I find hard to believe).
And I’ll check the option you where referring to. It seems to be exactly what I meant.
BTW, I just bought a license.
I also want to add that imho, the program should also support adding empty folders, unless the format does not allow it (which I find hard to believe).
I believe that this is the case for Zip files (that the format does not support empty folders). My understanding is that the Zip format contains files with no hierarchy, just a filename that may include a full or partial path. The display of files in folders by utilities like PA is something they generate by getting all the files names and building a directory structure from the list of paths.
Therefore, there is no way for the zip directory to have a path without at least one file to go with it. This may or might not apply to other archive formats.
it is problem of the engine (not format), since it does not allow for no files to be added (it thinks it is an error)… rest of mwb’s explanation is correct.
i think this will be improved for PA 2008.