-
-
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
7zip Memory Problem
-
There was an issue with PA not being able to compress VERY large files in 7z format, where it would just quit the compression without any warnings watsoever. Also, it took too much memory that Windows always complaied of Virtual Memory being low.
Are those two problems fixed in Beta 3?
-
Bug with 7zip just quiting was fixed in 9.5.
Memory used is still the same - if you select Ultra setting, 7zip will want 400 MB available - thats not something that can be changed since dictionary used is large and thats how 7zip manages to create smaller files. Thats why PA by default uses Maximum setting which is much less memory demanding.
-
If Ultra wants 400MB, how does does Maximum need?
Also, is there a HUGE difference between ultra and maximum? Well, anything worth the extra slowness. BTW, how much faster is maximum compares to ultra?
-
If Ultra wants 400MB, how does does Maximum need?
Also, is there a HUGE difference between ultra and maximum? Well, anything worth the extra slowness. BTW, how much faster is maximum compares to ultra?
Maximum needs some 280-300 MB less :-).
Difference in size is our around 10% on average.In any case, it is not as if you will be playing some game and compressing files, so I do think that for most of the things you will be fine with Ultra, except for compressing 10 gb of data at the same time, which might take a lot longer.
regards,
-
I have been trying to compress XBOX game backups with PA, and it basically NEVER works. Its so damn slow, and even before finishing, I get the low virtual memory messages.
I use WinRAR and they get compressed just fine. Sure that also takes time, but it has never come back with any memory low error.
I’d really like to use PA to get the smallest 7z file I can, but looks like that won’t be happening anything soon.
PS: The XBOX games are on averge about 4gb each with plenty of files/folders.
-
you are comparing rar to 7zip which is still being developed ?
-
you are comparing rar to 7zip which is still being developed ?
So what format would you suggest would be best for such big jobs as this? I want something with good compression, that isn’t slow as a dog.
-
I have been trying to compress XBOX game backups with PA, and it basically NEVER works. Its so damn slow, and even before finishing, I get the low virtual memory messages.
I use WinRAR and they get compressed just fine. Sure that also takes time, but it has never come back with any memory low error.
I’d really like to use PA to get the smallest 7z file I can, but looks like that won’t be happening anything soon.
PS: The XBOX games are on averge about 4gb each with plenty of files/folders.
Only solution is to up your virtual memory or use maximum setting instead of Ultra. Maximum should still be 5% better than WR Max.
I dont see where the problem is - if you get memory too low error, then you simply up the virtual memory. If you dont want to use more virtual memory, then use lesser setting.
Does the XBOX ISO file even compress?
-
Only solution is to up your virtual memory or use maximum setting instead of Ultra. Maximum should still be 5% better than WR Max.
I dont see where the problem is - if you get memory too low error, then you simply up the virtual memory. If you dont want to use more virtual memory, then use lesser setting.
Does the XBOX ISO file even compress?
I don’t compress the ISO file. I uncompress the ISO and then compress all the files. It does compress with WinRAR fairly well.
-
Bug with 7zip just quiting was fixed in 9.5.
Memory used is still the same - if you select Ultra setting, 7zip will want 400 MB available - thats not something that can be changed since dictionary used is large and thats how 7zip manages to create smaller files. Thats why PA by default uses Maximum setting which is much less memory demanding.
I think PA should use “Normal” (+solid) setting as a default for 7zip.
It seems that 7-zip (the software) uses “Normal” (+solid) as its default operation.
That’s why 7-zip (the software) seems to be a lot faster than PA (using context menu).
-
But what about better compression?
-
For the files I’m working with the compression difference is really little (~7KB)…
But “Normal” takes almost half of the time compering with Maximum or Ultra…
-
Well, PA 7z files take a VERY long time to finish. I’m talking on average og compressing 4gb. I use WinRAR for those huge tasks, and 7z for smaller tasks.
-
I don’t work with such big files… Have you tried to use 7zip and Normal compression with those huge tasks?
-
Briefly, yes. But its still too slow, and theres memory problems that have happened before, which makes me fearful in trusting my important games files to the 7z and PA combination.
-
I think PA should use “Normal” (+solid) setting as a default for 7zip.
It seems that 7-zip (the software) uses “Normal” (+solid) as its default operation.
That’s why 7-zip (the software) seems to be a lot faster than PA (using context menu).
whole point of 7zip is extra compression. If speed is the issue and size does not matter, ZIP is much better and faster solution than both 7zip or WinRar.
Eventually, you will be able to select default settings for compress to name.format in shell extensions, so you will be able to do that yourself.
regards,
-
So what format would you suggest would be best for such big jobs as this? I want something with good compression, that isn’t slow as a dog.
There are two good sites which give comparisons - but they have not been updated for a long time:-
ACT http://compression.ca/
Comparisons http://www.rojakpot.com/default.aspx?location=3&var1=4&var2=0But the only way to really find out which is best for you is to do some testing yourself using the type of data you will be wanting to compress.
A general rule of thumb is :-
Smaller Size = Longer Time + higher System Requirements.For you, the System is fixed (your P.C. configuration) but only you can decide “how much time” is worth “how much compression”.
-
whole point of 7zip is extra compression. If speed is the issue and size does not matter, ZIP is much better and faster solution than both 7zip or WinRar.
Eventually, you will be able to select default settings for compress to name.format in shell extensions, so you will be able to do that yourself.
regards,
I understand your point.
However, the size difference (between Maximum+Solid and Normal+Solid) is so small (at least for the files I use to work - 7KB) that it’s worth to get a bigger file but a real faster process (almost half of the time with NOrmal+Solid).
Even 7z Normal+Solid makes a smaller archive than WinRar.
Anyway, I think you have a great solution. It’ll be great to select the default settings for compress name.format in shell…
-
its not pa’s fault 7zip is still being developed the best format to use would be uha but i not supported by powerarchiver yet.
the best format that pa supports is 7zip but zip close to that in terms of use.
Its up to you but 7zip memory problem is due to indows and what ram you have. Tests have shown on one computer with 256mb ram to be better than one with 512mb ram cquse it uses windows 98 instaed of xp just shows you the problem the makers of pa and 7zip have.
-
Well, bring on UHA format support then.