-
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.
Extensions (.cbr) doesnt work properly in shell
-
I have a variety of comic book archive formats that I deal with:
.cbr == RAR file
.cbz == ZIP file
.cb7 == 7z fileI’m not sure if I did something myself to cause this, but I see that both CBR and CBZ files are listed under PA’s File Formats list in Options. In addition, the shell has those file types described as “PowerArchiver RAR File” and “PowerArchiver ZIP File” respectively. In the case of CBZ files, I can drag-n-drop with the right mouse button and get the drop menu actions I’ve got configured in Options - namely, Extract Here and Extract to <folder_name>. But for CBR files, I get no such drop menu action. Using an alternative File Manager (Directory Opus) I can force the drop menu to appear, but PA just creates an empty folder from ‘Extract to <folder_name>’ action. My guess is it’s trying to process the CBR file as if it were a ZIP format archive instead of a RAR format.
Theories aside… is there an official way to add an extension to be treated like specific type of archive format? If the CBR and CBZ files appear in the File Formats list because they’re supposed to (and not because of somethign “I” did), then would PA not treating CBR files as RAR be a bug…?</folder_name></folder_name>
-
this post should be in the wishlist. though has been asked for before. Basicall you want a windows style assocation window that ou can associates different formats too. I would much prefer if pa can automatically detect the format without changing the extention or having to associate the extension. this can be done
-
steje, what version of PowerAchiver are you using?
Check under “Configuration / File Formats” - near the bottom there should be an entry for both CBR and CBZ.
Are these ticked (associated)?Edit: Just reread your post - sorry I misunderstood.
Can you confirm that the shell extension options are correct for CBR. If so, then you may have found a problem.
Adding extensions by user is already in wishlist
http://www.powerarchiver.com/forums/showthread.php?t=4611 -
this is a bug then…
-
i was talking about being able to associates any extension to an archive.
which could a sparate wish sorry
-
logged in, thanks for the report!
-
@__TBGBe__: I am using PA v12.12.03
And yes, I do have both the CBR and CBZ formats checked in the File Formats page under Options->Configuration. I don’t know how I can really “confirm that the shell extension options are correct for CBR”. The shell extensions are enabled to my preferences, and work on all other normal file extensions (most notably - all of the same CBR files simply renamed to RAR, extract fine using the drop-menu shell extension).
So… is PA defining these file associations itself? As I mentioned - I couldn’t recall if I had monkeyed around with Windows file type associations to make that happen somehow. If PA is already supposed to be ‘aware’ of CBR files - then it would seem this may in fact be a bug.
To davidsplash point… the ability to specify our own extensions (and either manually associate it with a known archive format - or have PA figure it out dynamically) would be great… but if PA is ‘supposed’ to know about CBR files - then I’d prefer to keep this thread focused on that topic rather than enhancement requests.
@__Mili__: by “logged in” - does that mean you’re acknowledging this is a bug - and it’s been logged with support or something?
-
Exactamundo Steje, let’s see what the dev team has to say. :)
-
@__TBGBe__: I am using PA v12.12.03
And yes, I do have both the CBR and CBZ formats checked in the File Formats page under Options->Configuration.
Yes. That’s what I meant with my edit :o
I don’t know how I can really “confirm that the shell extension options are correct for CBR”. The shell extensions are enabled to my preferences, and work on all other normal file extensions (most notably - all of the same CBR files simply renamed to RAR, extract fine using the drop-menu shell extension).
I just meant if, when right clicking on a CBR file in explorer, does PowerArchiver offer extract etc.
To davidsplash point… the ability to specify our own extensions (and either manually associate it with a known archive format - or have PA figure it out dynamically) would be great…
That is what the wishlist I linked to is about (note my request for not just ZIP).
For your CBR problem, devs are/will be looking at it. :cool:
Sorry if I confused you. :o
-
Thanks for the replies…
@TBGBe: Yep - just wanted to be clear and specific.
About the context menu / shell extensions. I wasn’t (don’t) normally just right clicking on the file - I’m right-click drag and dropping to produce the ‘drop menu’.
In any case, if I right click on the CBR file… I get the ‘extract’ context menu option… It seems to run but extracts nothing. However, if I open that same file (without even renaming it to RAR ext) in the PA GUI… it lists the file contents fine, and I can then extract them from within the PA UI to a folder by either hitting the Extract button on the toolbar, or by dragging them from the PA UI to a folder.
So, it appears to be a bug in the context menu handler / shell extension…?
-
fixed in latest Beta!
-
Thanks Mili! Good to hear - appreciate the notification… was that in a v13 beta?
-
yes, latest beta (13.00.22)
Thanks :) -
Thanks again… are there yet any soft guesstimates for when v13 may be planned for release?
-
Thanks again… are there yet any soft guesstimates for when v13 may be planned for release?
PowerArchiver 13.00 has been released already… Since beta 2, we consider it more stable than 2011 and you can start using it.
