-
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
-
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.
USB Portable version
-
Dear Powerarchiver,
Will you make a usb portable version for your customers , anytime in the future. Lots of crypto now has support for the usb portable versions.
Sascha
-
Hi cyruslocal
This request has come up a few times.
Here’s a couple of similar threads. -
portable version is coming this year for sure…
-
if anyone has any suggestion on what middleware to use, let us know :-)
-
if anyone has any suggestion on what middleware to use, let us know :-)
Have you any idea’s yourself? If so what are they?
-
Will you be releasing in -both- U3 version and a single doubleclick .exe file ?
Personally… I am not in favour of U3 software on my USB thumbdrive, but I do like to have PA as portable version.
(again, this is my personal taste, others may like to have the U3)Maybe you wish to consider :
-
release a portable version with a separate registration (for those not willing to buy the full version, because they wish to keep their system as clean as possible and want to carry around a portable version all the time), in both U3 and single .exe
version -
have a portable version created from within the (paid) full version: a kind of backup/export to a portable version on thumbdrive.
(some programs have this option, e.g. Directory Opus)
=
-
-
U3 is dead so no U3 for sure…
-
Hi!
if anyone has any suggestion on what middleware to use, let us know :-)
How about as a Portable Apps version? Easy to use and very user friendly installation to the USB Memory stick and running from USB Memory stick. I know most of the programs released as Portable Apps are open source, but I don’t see any problem release a commercial program like PowerArchiver as a portable version running in Portable Apps.
Kind Regards
Micke
-
it is one we are looking at too… do you have any experience with it Micke, how about shell extensions support and associations?
-
Hi!
it is one we are looking at too… do you have any experience with it Micke, how about shell extensions support and associations?
I’ve been using it for about a year now. Have tested and used it in Windows XP, Windows 7, Ubuntu 10.04 and Linux Mint 10 through Wine. I find it very user friendly and I haven’t got into any problem using it. Since all the Portable Apps programs are Windows versions, not all of them will work through Wine in Ubuntu, but that’s something I can live with.
However, you can’t associate a file extension to a portable apps program. At least I haven’t tried to do that, because the whole point in using Portable Apps it that the programs don’t get installed on the computer and that they won’t leave any traces after running.
If I could for example associate .odt extension (LibreOffice Writer) to the Portable version of LO Writer, this would get problems after exit the portable apps program and removing the USB Memory stick, if no other programs on the computer could open .odt files. Instead I have to start the program and then open the file from the program.
Another point is that you should keep all the documents and images your are using with Portable Apps on the same USB Memory stick, since you want both the programs and the document to be portable. You can also from the running Portable Program open files that are stored on the hard drive.
I haven’t seen any shell extension support and as far as I know, it’s not supported because of the reasons I just mentioned.
I have also tested running Portable Apps on a computer that I have no admin rights on and it run without any problem. It takes some time to start the selected program from the USB Memory, but once it’s started I really can’t say that it feels any different from running it installed on the computer.
If it would come a Portable Apps version of Power Archiver, the user would have to first open PA and then from PA open the selected archive. I believe this is acceptable since we are not install or changing anything in the OS on the computer and all the programs will run directly from the USB Memory stick.
I’m not sure if all this answered your question, but personally I like Portable Apps a lot and I had no problem using it. It’s also very convenient to have all the programs I need in my pocket and if I also would be able to have PowerArchives on a USB Memory stick, it would be even better.
Kind Regards
Micke -
Micke - i know how it works… i would still like both of those to work and to be able to automagically “uninstall” themselves once stick has been removed.
It may be possible to actually do that… i think only that would bring real portability to the equation - otherwise, what is compression utility without shell and associations? :-)
-
so… do we make extra effort to make it work perfectly (shell, assoc), or do we just package it with 5 minute job like portable apps and lunch it?
-
make the extra effort !
thanks !!! -
Hi!
Micke - i know how it works… i would still like both of those to work and to be able to automagically “uninstall” themselves once stick has been removed.
It may be possible to actually do that… i think only that would bring real portability to the equation - otherwise, what is compression utility without shell and associations? :-)
Yes, that would certainly make it real portabillity, but the question remain, will it work on all circumstances, even when you don’t have administrator rights to the OS?
Kind Regards
Micke -
Hi!
Yes, that would certainly make it real portabillity, but the question remain, will it work on all circumstances, even when you don’t have administrator rights to the OS?
Kind Regards
Mickewell it wouldnt when you dont have admin of course, just like anything else that requires admin access… but it could work if you do have it.
-
Hi!
so… do we make extra effort to make it work perfectly (shell, assoc), or do we just package it with 5 minute job like portable apps and lunch it?
I like the idea of using shell integration, file association etc. but for me personally, it’s really not that important. I already have all that in the installed non portable version of PA.
When it comes to a Portable version of PA, I don’t see it as a replacement for the non portable version of PA. Instead it’s more like a supplement to the non portable installed version of PA.
Because of this, I personal really don’t need the shell and file association for a Portable version of PA. It’s good enough if I can run it from the USB Stick and open archives within PA.
But that’s just my personal opinion. I’m not going to complain if you make a Portable version that works with shell intregration, file association and restore everything after the USB Stick is removed.
Kind Regards
Micke -
so… do we make extra effort to make it work perfectly (shell, assoc), or do we just package it with 5 minute job like portable apps and lunch it?
You can do it in two steps.
- Make a powerarc.exe that doesn’t require information to be written to the registry, gets all of the required configuration information from files in the directory the executable resides in, and doesn’t need COM information installed in the registry (there are ways to configure COM objects in manifest files instead). This is the basic portability requirement, and lets anyone use the program from a USB stick without admin rights on the computer and without needing to buy into any particular ‘portability shell’.
Of course, you don’t get shell integration. But sometimes I just want to look at or extract files from an archive that might not be supported on the machine I’m currently at. I can figure out how to open it from within PA - I’m not completely dense. Also, I happen to have a portable file manager (XYPlorer) that can be configured with portable file associations - I could configure that file manager to portably open PA’s files.
- create a package for Portable Apps (or whichever you decide on) that brings the bells and whistles for those who want them. As far as I know, the work done for #1 would help with integrating things into this step - it certainly wouldn’t make things harder.
-
good insights, thanks.
-
I cant find yet any link please.