-
-
Re: Explorer.exe Crash on right click
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).
-
In the latest version of PA, on W11 (latest build/SP) when you try to use the first level context menu - NOTHING HAPPENS (particularly when you do this from Downloads or Documents folders) - however I noticed that it DOES WORK when you use the context menu from the Desktop. Going to the second level context menu does work however.
-
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 errorsIs 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.
-
Clipboard02.jpg
See the, supposedly, blank space where the green box is? It’s like that in Modern Light theme too. I can toggle it, but it’s missing text or shouldn’t be there I guess?
Thanks :)
-
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.Features implemented:
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.
thank you!
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
76e97ab9-8d75-4175-9ce8-446500031f38-image.png
Problem with German "Umlaut"
-
Hi,
using PA11.02.03 (11/2008), with this version (and previous ones), opening an archive including filenames with German “Umlauts”, these do not display correctly:
i. E. a filename “dänermark.mdb” displays as “dõnemark.mdb”
This does not happen, if the file was compressed using PA. These files were compressed using a backup software. But, extracting this very archive using filzip
or tugzip displays “in listing after opening” and extracts this filename correctly!
I attached an archive showing that behaviour, the file was created using tugzip, watchout for the filename after extracting using PA!
attachment_t_3432_0_ööääüüß-textdokument.zip -
archive doesnt work properly for me - can you rename it to test.zip and re-upload?
PA reads properly ANSI stored filenames in zip archives, according to specifications. There are quite few zip engines out there that have their own, different specifications, so it could be quite possible that they are using same engine.
-
Hi spwolf,
find the renamed archive “test-2.zip” attached!
The previous flename of the archive was supposed to
be “öÖäÄüÜß-Textdokument.zip” same as the name
of the included document! -
strange thing, I renamed the file and the uploader claims, that I already uploaded it previously!
I try sending by e-mail! -
ok…
-
ok, here is the problem - archive is created by software that uses non standardized zip unicode support.
Currently PA would not support it even if it had proper unicode support since current engine supports only ANSI zip archives.
Reason those 2 other softwares support it is probably they use the same zip engine so it works for them :-).
I tried opening it with every major compression software we have installed - WZ, WR, 7z, SecureZip and none of them support it either.
Good news is that we will add this support relativly soon :P
-
Additionally, way to solve the issue would to force software to save as ANSI… from my knowledge, I can guess what zip engine they use and the way to do it would be to set non-unicode support to German, in Regional and Language settings> Advanced options.
This will force that zip engine to save as ANSI and it will then work in every archiver out there. I hope that helps.
thanks!
-
Hi,
well, as I said, two competitors (I did not test any others!) do extract these fine and my customers here receive zip files from many different folks. They can not discuss if senders zip-engine is created by widely spread but non standard….;-)
Certainly a good idea to fix that soon! -
Hi,
well, as I said, two competitors (I did not test any others!) do extract these fine and my customers here receive zip files from many different folks. They can not discuss if senders zip-engine is created by widely spread but non standard….;-)
Certainly a good idea to fix that soon!well you can suggest to your customer to get zip utilities that support zip standards, and not invent their own :-).
No major utility will open these files properly, because they are badly created zip files. Luckily, we will be able to add this but again, it is not our fault if someone uses zip software not compatible with zip standards.
-
Hi,
@spwolf:well you can suggest to your customer to get zip utilities that support zip standards, and not invent their own :-)….
Well, my customers will use PA starting the next days (watch orders…), but their influence on their customers is quite limited ;-)
-
Hi,
Well, my customers will use PA starting the next days (watch orders…), but their influence on their customers is quite limited ;-)
its good that we are on the case already :P