-
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.
-
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. -
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
-
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.
X64 support
-
Will PA support windows xp 64bit?
some other compression utility that I wont name here dont as the shell extention doesnt work right now
-
-
thats not a good thread to look at and I dont want to bring it up by responding there. Basically we have to re-write shell extensions in 64bit and then they should work. When we get time, we will check it out and see if it works.
Problem is that Win64 does not support 32bit shell extensions, and hence they wont/dont work…
-
ok thanks for the quick answer
-
Basically we have to re-write shell extensions in 64bit and then they should work. When we get time, we will check it out and see if it works.
That means, x64 support is far away? You gave the same answer for sfx support, but in the last four years you didn’t find time to update the sfx support. It seems that the only way to get x64 support is to use another archiver. :(
-
That means, x64 support is far away? You gave the same answer for sfx support, but in the last four years you didn’t find time to update the sfx support. It seems that the only way to get x64 support is to use another archiver. :(
Interesting, we certainly did update PowerArchiver over the years, did we not? :-). Of course, feel free to use any software you wish to use. As I said, we will check it out once we have time (since 9.5 is priority), if we can get it to work, great.
-
Yes, of course you did. But some users are still waiting for self-decrypting .pae files. ;)
But I think it’s not only done with rewriting the shell extension. Even a 64bit shell extension has to check if the right-clicked file is an archive. So you have also to move your archiver libraries to 64bit too.
-
Could you make 1 shell extension work in x64. It only has to work in the alphas. It doesn’t have to be in the final. I would like The extract to folder (name)
Is very annoying to have to work from with in main window to extract….
Thanx…
Guido
-
Hi!
I hope 64 bit support will be available for PowerArchiver too soon.
I understand that it involves some work to convert it, but I think you guys will make more and more people very happy with this. A very good way to go ahead of the competition!
Besides converting the whole application to something 64 bit, I think it is possible to use the simple context menu options really simple with the use of command line switches. I know some people fixed it for WinRAR as you can see in this forum: http://www.neowin.net/forum/index.php?showtopic=311399&pid=585832076&st=0.
Could you please instruct us Windows XP x64 people how to do such thing for PowerArchiver?
Thanks in advance!
-
The shell extension / context menu items of PowerArchiver are accessible from the 32-bits version of Windows Explorer by using the workaround described on http://www.extended64.com/blogs/bhpaddock/archive/2005/05/22/539.aspx.
I do not know the exact implications from this, but it is usefull for tools like PowerArchiver, TortoiseCVS and others.
-
The shell extension / context menu items of PowerArchiver are accessible from the 32-bits version of Windows Explorer by using the workaround described on http://www.extended64.com/blogs/bhpaddock/archive/2005/05/22/539.aspx.
I do not know the exact implications from this, but it is usefull for tools like PowerArchiver, TortoiseCVS and others.
Hopefully we will check it out soon enough so we can see if it is possible for it to work properly under 64bit…
thanks for the tip.
-
Any plans already to release a version with support for Windows XP 64-bit?
There is a lot of talking about it on PlanetAMD. I am sure you win some new customers if
64 bit support is implemented. WinZip doesn’t got it yet (but something called Squeez does). I only don’t want all that other stuff, I want Powerarchiver! -
Any plans already to release a version with support for Windows XP 64-bit?
There is a lot of talking about it on PlanetAMD. I am sure you win some new customers if
64 bit support is implemented. WinZip doesn’t got it yet (but something called Squeez does). I only don’t want all that other stuff, I want Powerarchiver!we are working on it right now…
-
:D :D :D :D :D :D :D :D :D
-
great to hear ;)
-
we are working on it right now…
Great! I hope PA could be the first choice of Win64 users. ;)
-
we are working on it right now…
Good to hear because some competitors are starting to offer x64 Shell Ext. support.
By the way, as I’m new to the forum I must say this: PA 9.x rocks … ;)
-
Any flash news on progress?
-
We are working on it - I hope this month we shall have patch for Win XP x64.
-
We are working on it - I hope this month we shall have patch for Win XP x64.
Any chance for x64 support in PA 9.5?
-
It should be available for testing quite soon.
-
It should be available for testing quite soon.
You need a smilie for “Thumbs up” in the forum. :)
-
p.s. just an reminder - x64 shell extensions were added to Beta 7 of PA 2006…
-
Doesn’t work on my pc with B7
Guido
Windows 11 Pro ENU x64
Intel Core I7
32 GB RAM -
did you restart your computer after installation?
-
ofcourse ;)
guido
Windows 11 Pro ENU x64
Intel Core I7
32 GB RAM -
ofcourse ;)
guido
well give us more info, we have tried with 4-5 different computers and it all went well….
-
what do you want?
I have a english Windows…
I also installed winrar. Maybe that’s the problem.
Guido
Windows 11 Pro ENU x64
Intel Core I7
32 GB RAM -
You have english Windows X64, build … And you are running AMD…?
etc, etc… And after installation, you do not get any shell extensions for PA? (quick check if they are on in the config?).thanks,
-
You have english Windows X64, build … And you are running AMD…?
- AMD 3500+
etc, etc… And after installation, you do not get any shell extensions for PA? (quick check if they are on in the config?).
- I’m not getting any shell ext at all. I tried turning them on and off. Also in combination with the shell ext from winrar.
Do you want me to check some reg keys ?
Guido
edit: typo
Windows 11 Pro ENU x64
Intel Core I7
32 GB RAM -
ok, so you WinXp x64 users - make sure PA installs under Program Files and not Program Files (x86). Windows will not let shell extensions to run from x86 folder!
This is only valid for people who had already installed PA on the computer so PA’s installation will look at last installation folder. New installations will go into “64bit” Program files by default.
thanks!
