-
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.
Additional paths created in archive
-
I’m creating an archive with extension .tar.gz
PA is creating additional paths in the archive, that is, creating a path that is NOT on the local system. The pathnames, in all cases, are being named with a backslash.
It appears to be happening for all paths, where there are no files within that path.
This is a problem I reported in April this year, see this post
If I use PACL to examine the archive, it reports the additional paths, for example …
pathname1\pathname2\pathname3\pathname4\
0 Tarred 0% 0 04/12/2007 20:29:34 00001d73If I use 7-Zip or PEAZIP to open the archive created by PA, they both show the additional paths in the archive.
Any chance of this being fixed please ??
-
is this happening to all paths or only if path+filename is over 99 char?
thanks
-
is this happening to all paths or only if path+filename is over 99 char?
It is happening to all paths that have no files.
There were 3 paths that had no files, and PA created the archive with 3 additional paths, each path underneath those three, and they were all named backslash.
I’m sure it is a different problem to the “length” problem.
The length problem was occurring when extracting (uncompressing) a tar.gz, and this problem is happening when an archive is being created.
Besides, I just checked one of those paths, and it was only 49 chars (path+filename).
This would be easy to replicate, just create 2 paths, one with files in it, and one without files, then create an archive of tar.gz
-
thank you!
-
so it has to have 4 levels of path? can you attach example archive please?
thanks
-
so it has to have 4 levels of path?
Actually, a small test just showed the same error, and there were only 3 levels of paths. Here is the structure I used
F:>dir temp\powera~1\ /s
Directory of F:\temp\powera~1
07/19/2007 03:49 PM
<dir>.
07/19/2007 03:49 PM<dir>…
07/19/2007 03:56 PM<dir>pathwithfiles
07/19/2007 03:49 PM<dir>pathwithoutfiles
0 File(s) 0 bytesDirectory of F:\temp\powera~1\pathwithfiles
07/19/2007 03:56 PM
<dir>.
07/19/2007 03:56 PM<dir>…
03/12/2007 02:41 PM 1,273 index.php
1 File(s) 1,273 bytesDirectory of F:\temp\powera~1\pathwithoutfiles
07/19/2007 03:49 PM
<dir>.
07/19/2007 03:49 PM<dir>…
0 File(s) 0 bytesTotal Files Listed:
1 File(s) 1,273 bytes
8 Dir(s) 19,059,482,624 bytes freeF:></dir>
</dir>
</dir>
</dir>
</dir>
</dir>
</dir>
</dir>
The folder was called ‘powerarchiver’, and I created a tar.gz of it, and yes, the same problem again. Other achivers show the extra path with a backslash, and here is the output from a verbose list from PAEXT
PowerArchiver Command Line (PACL) Version 4.01 [Mar 07 2005]
Copyright© 1999-2005 ConeXware, Inc. All Rights Reserved. Registered Version
This product is licensed to: ******* *********
Archive Extr.—ZIP,CAB,LHA,ARJ,RAR,ARC,ACE,TAR,GZIP,BZIP2,UUE,ZOO,B64,YENC,…
Internet: http://www.powerarchiver.com Email: support@conexware.comArchive –> f:\temp\patest.tar.gz [GZIPed TAR]
Name Length Method Ratio Size Date & Time CRC-32
–---------- -------- -------- ----- -------- ------------------- --------
powerachiver\pathwithfiles\index.php
1273 Tarred 0% 1273 03/12/2007 14:41:56 00001ded
powerachiver\pathwithoutfiles\
0 Tarred 0% 0 07/19/2007 15:49:30 00001c1f
*Totals 2 0 0% 0 07/19/2007 15:57:22
-
peter - powerarchiver also shows extra backslash or?
-
peter - powerarchiver also shows extra backslash or?
PA only shows an empty path (screendump attached).
-
peterr,
The issue should be fixed in 10.20 Beta 3. Thanks!
-
Thanks Ivan. :)
-
Please check with Beta 3 preview:
http://www.powerarchiver.com/test/release10/powarc1020b3.exeand let us know if it works properly now.
thanks!
-
Installed beta 3 preview, and used it to open the previously created archive, and noticed it didn’t show the path without files at all.
Created a new archive with Beta 3 preview, and PA didn’t show the path without files.
Here is what PAEXT showed with a verbose listing of the newly created archive patest2.tar.gz , displaying the path without files …
D:\PACL>paext -v f:\temp\patest2.tar.gz
PowerArchiver Command Line (PACL) Version 4.01 [Mar 07 2005]
Copyright© 1999-2005 ConeXware, Inc. All Rights Reserved. Registered Version
This product is licensed to: ******** ************
Archive Extr.—ZIP,CAB,LHA,ARJ,RAR,ARC,ACE,TAR,GZIP,BZIP2,UUE,ZOO,B64,YENC,…
Internet: http://www.powerarchiver.com Email: support@conexware.comArchive –> f:\temp\patest2.tar.gz [GZIPed TAR]
Name Length Method Ratio Size Date & Time CRC-32
–---------- -------- -------- ----- -------- ------------------- --------
powerachiver\pathwithfiles\index.php
1273 Tarred 0% 1273 03/12/2007 14:41:56 00001ded
powerachiver\pathwithoutfiles
0 Tarred 0% 0 07/19/2007 15:49:30 00001bc3
*Totals 2 0 0% 0 08/02/2007 20:51:04
and this is what the Beta 3 preview release of PA showed , that path without files is not shown …
-
Thanks!
Empty folders wasn’t shown at all in 10.20 - will be fixed in 10.20 Beta 3 Public.
-
Please check with Beta 3 Rev2:
http://www.powerarchiver.com/test/release10/powarc1020b3.exeand let us know if it is fixed.
thanks!
-
Please check with with 10.20 RC1 and let us know what happens.
http://www.powerarchiver.com/test/release10/powarc1020.exe
thank you!
-
The path without files is now showing okay, in 10.20.09
Thanks for fixing it. :)
