-
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files. -
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
PAOP zipping files only between certain sizes
-
I’ve discovered a very strange behavior:
Context:
PA 2010 FR v11.50.66
PAOP 2.03.03 US
Windows 2000 FR, Windows XP SP3 FR, Windows Vista FRI’ve setup PAOP to compress files automatically over 300KB, but when sending files, PAOP compresses files if they’re over 300KB (that’s OK), but only if they’re under - let’s say 1MB (I’ve not precisely found where the limit is).
I’ve then tested with PAOP 2.03.03 but with PA 2009 v11.03.04, and there, the upper limit seems to be around 5MB !!!
If the size of the joined file is over the “limit” I’ve found, the file is simply joined and not compressed (there’s no zip file containing the file, the file is in the mail as it would be with no use of PAOP).
No error raises, I just see the PA compression window popping up and closing immediately (quicker than if it does the compression).It has nothing to see with extensions (I’ve tested with several Excel or Word files), some are well-compressed, some not (depending on their sizes). And of course, .xls and .doc aren’t defined as excluded extensions for PAOP.
If there’s no special setting for that in the menus or in the registry (I don’t see where !), there must then be a bug, as it’s completely reproducible and it happens on different computers on different OSs and even with the very last and just previous versions of PA.
Did someone encounter the same ?
Can you check this problem ?
Thanks in advance.
-
I tried a 1mb, 1.7mb, and a 3mb. The first was pdf, PAOP did change the file, but being a pdf it didn’t compress it much. The second was JPG, PAOP did change the file to a zip, but once again the compression wasn’t dramatic. The final 3mb file was a powerpoint, PAOP changed the file to a zip and compressed it down to 2mb.
So on my limited testing it seems to be working.
PA 11.50.66
PAOP 2.03 -
Perhaps does it have something to see with language ?
Indeed, I’m using PA French on French OS, but with PAOP US (this last one doesn’t exist in French…).
-
Hi,
here is our internal release of PAOP 2.1 beta:
http://www.powerarchiver.com/test/release10/paop210b.exedifferences are new unicode handling of filenames (which might have been the problem in your case). Please check it out and let us know.
thanks!
-
well I know it’s an old complaint of mine but it still refuses to intergrate/show in outlook 2007 for me but I gave up in the end…just had my fingers crossed it would work this time.
-
No, sorry, even with PAOP 2.10.01 beta, there’s no change:
- a XLS file of 4702Kb is joined “as is”.
- a XLS file of 1095Kb is joined “as is”.
- a XLS file of 517Kb is joined ZIPPED.
(My compression lower limit is set to 300Kb)
There still seems to be an “upper limit” (around 1Mo for me), so that files between 300Kb and 1Mb are correctly compressed while sending, and files outside this range are not…
-
No, sorry, even with PAOP 2.10.01 beta, there’s no change:
- a XLS file of 4702Kb is joined “as is”.
- a XLS file of 1095Kb is joined “as is”.
- a XLS file of 517Kb is joined ZIPPED.
(My compression lower limit is set to 300Kb)
There still seems to be an “upper limit” (around 1Mo for me), so that files between 300Kb and 1Mb are correctly compressed while sending, and files outside this range are not…
can you export your reg key:
HKEY_CURRENT_USER\Software\PAOutlookand zip it and send it to support at conexware com. This way we will be able to reproduce this issue with exactly your settings.
thank you,
-
OK, I just sent the requested file to you…
