-
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
-
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.
Minimize toolbar/ribbon question
-
In two of the windows (FTP and backup), when I switch to the tab, part of the windows are cut off.
I must click on the window and scroll to see them.
See the attached images.
THOUGHT IT WASN’T A PROBLEM . . . BUT IT IS.
-
I couldn’t get the same result on my system buddy…
all seemed fine on this end…sorry. -
I am perplexed.
One other comments; two questions.
Not only am I facing the problem above, I had some trouble getting the View / explorer style (with folders) to stick. Although it momentarily seems to work. BTW, I am using modern toolbar 2010 black skin.
I can see the window normally if I 1) click the tab, and 2) then click in the PA window (the ribbon collapses and the presentation of the files looks like). In the past, I thought things looked fine even with the ribbon open. In fact I don’t think the clicking in the main PA window made the ribbon disappear.
I prefer the QAT before the ribbon. But with the ribbon open now, it covers the QAT.
Looking at the registry. Should I delete the PA that doesn’t say INT? Also with PowerArchiverInt I have 3 registry keys: Toolbar, DToolbar2, and DToolbar4. Is that normal?
Or should I perhaps do a complete uninstall and reinstall?
And I don’t see the test button anywhere on my toolbar. Unlike Luxor, I did not see it under tools.
-
I couldn’t get the same result on my system buddy…
all seemed fine on this end…sorry.Can’t seem to recreate it here neither.
But just because others can’t recreate it doesn’t mean that it’s not a bug.
Trust me I’ve been there. ;)Could you perhaps highlight the area in question in your screen-shots, just in case I’m misunderstanding the problem. (probably not but you never know) ;)
And I don’t see the test button anywhere on my toolbar. Unlike Luxor, I did not see it under tools.
:D
-
I cannot got back and mark up the pics I sent. But please go back and look at them. On one, when the ribbon is open, the QAT and the top line of the main window is blocked.
In the other, to see the main window and QAT, the ribbon collapses.
Could the registry settings I asked about matter?
-
I cannot got back and mark up the pics I sent. But please go back and look at them. On one, when the ribbon is open, the QAT and the top line of the main window is blocked.
In the other, to see the main window and QAT, the ribbon collapses.
That’s what I thought you meant, just wanted to be sure.
@Socrates:Could the registry settings I asked about matter?
I’ve no idea. I would wait for input from either spwolf or Mili on that one.
They may require you to send your registry settings to try and find the problem, so leave it alone until they tell you different. -
yeah, send over the registry please…
-
I take it, the same thing is not happening with you?
This is a quirk I have never seen in PA.
I DID install .22 very early yesterday. Then I saw you (or Moles?) posting about test – and I could find test AT ALL – I thought maybe it was something they had quickly fixed, so I tried to install what I thought was the later .22 (it actually did a “repair”)
-
test is when you open archive, you will see in the Home ribbon, under Tools tab, Tools icon… click on it and dropdown will give you several extra tools including Test.
-
(not in Tools ribbon, in Home ribbon)
-
here we go.
-
(not in Tools ribbon, in Home ribbon)
See. You hid it so well you can’t remember where it is. :D
-
while i am already creating screenshots….
we did it because german/french and probably few other translations ended up looking like these due to extra characters in button names.
as you can see from above pic and this one, it was really messy to use.
-
ah, i get it… you minimized the ribbon possibly and then you clicked once on backup, in that case, ribbon toolbar goes over window.
you need to doubleclick again on the backup, but doubleclick, and then ribbon will go back to its own space.
-
The complete uninstall and reinstall solved all the problems sans one.
I don’t get the little pop-up preview option, as shown in Sir Richard’s pic.
-
you have to click on file that can be previewed, it is context sensitive…
-
you have to click on file that can be previewed, it is context sensitive…
For example a .jpg, .txt or .pdf file
-
Sorry. It has to be a previewable file. My bad,