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.
I confirm that, on my machine, 9.00.35 fixes the screen positioning problem.
Unfortunately, it suffers from lots of other bugs & problems that Power Archiver has suffered from for some time, some of which I reported back in 2002. See list below. Further details available on request.
1. When you try to create a new LHA archive using the Power Archiver “New” button on the toolbar, it crashes with an access violation once you’ve finished with the Add dialog box.
2. When creating an LHA archive (from the Explorer shell - the only way I managed to do it with getting an access violation), it fails to add an end-mark to the end of the file. (This is just a single byte containing the binary value 0. It needs to be appended to the end of the file to indicate there are no more files inside the archive.) Without this end-mark, the “official” lha32.exe utility complains about a missing end-mark when extracting or testing the archive.
3. Cannot cope with ZIP compression methods “DCLImplode” (used by PKZIP 2.50+ and the PKZIP run-time library), and “Reduce” (used by PKZIP 0.95, made obsolete by PKZIP 1.00+ but still supported for extraction up to PKZIP 2.04g and also by all versions of WinZip). For the Reduce method, the component that you use for extraction (Dynazip) calculates the CRC incorrectly.
4. The Test action does not work properly. Sometimes, when a file produces a CRC error, testing does not report problems with subsequent files. Other times, inability to decompress a file is not reported at all. This means that the Test action is unreliable, and therefore worthless.
5. Fails to recognize the default compression method of the Microsoft compress.exe utility (i.e. the method used when none of the -z, -zx or -zq options are given).
6. Fails to extract previous versions of a file in an ARJ Chapter archive. It lists all chapters (i.e. versions) of the file, but always extracts the latest version from the ARJ archive no matter which one you select to extract.
7. Fails to decompress .Z files, created with the unix “compress” utility.
8. Power Archiver uses an incorrect definition of the “System default” startup folder. It should work the way it does in WinZip and other utilities: the system default folder is the one I specify in the Properties box of the shortcut I use to run the utility. Instead, it considers the system default folder to be its installation folder.
9. Fails to create CAB archives containing files beginning with a dot character, i.e. “.*”, or containing certain non-English characters.
I have moved this post into thread of its own from:
Although, these should be in separate posts, according to their issues. Please post separate issues in separate threads or it will be much harder for us to deal with it.
1. - Can you explain step by step what have you done to get the error? (works here)
2. We will check it out
3. This is an Wishlist item, although I doubt we will support older/unused methods
4. Can you please explain situations in which specific case this does not work, without that we can not fix it.
5. This is an wishlist item, although I doubt we will support unused methods
6. Another wishlist item, we will check it out.
9. Thanks we will check it out. This is an open issue with CAB, BH formats.
You should have entered all these issues in separate posts, except for maybe 3,5,6,7. Nevertheless, thank you. Please report anything else you find.
Thanks, I will post separate items later (I’m busy right now) for those issues which need further information.
For the rest, thanks for looking at them. I don’t think it matters much if you don’t support old and hardly-ever-used compression formats/methods (items 3,5,6,7).
But it is important to recognise such unsupported methods and produce an appropriate warning message, rather than pretending to support them and getting into trouble half-way through reading the file.
I have fixed the issue with number 8.
Issue with number 1 I couldn’t reproduce - can you please explain step-by-step.
I will look into other decompression/compression issues related with special formats…