-
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.
-
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.
Test tool in shell extensions
-
Having dealt with my own particular quirks and raised a silly issue, I think this is a real one.
I have “test” selected as an option I want in the shell main menu.
But it doesn’t show up in the shell either within the PA window or within explorer.
-
is it 32bit Windows or 64 bit? I tested it on x64 and seems to be fine…i added it to submenu and showed there when clicked on zip archive… what archive did you click on?
-
32 bit
click on several archives. zipx and 7zip
-
I show you the setting in shell.
My screen capture program won’t let me capture right menu options within PA; but here is explorer RC menu.
-
ok, mili will check with 32bit when he signs on after his festivities come to the end (eating a lot of cookies due to holidays)
-
I thought perhaps relocating in on the ribbon might have made a difference
-
Works in Vista 32bit. Tried a few different archive types for testing.
-
I Use Win 7
Perhaps it works, too, if I break it apart into all the sub areas. But I don’t want to do that. Context menu is too cluttered as is.
I can get it to show up if I add it to the sub-menu (which, I think, is what Luxor has done). Could you try adding it to the main menu and see what happens?
-
-
Then either it is Vista versus 7-32 . . . or something else (one different setting?
Never been a problem before.
I can live with it in sub-menu, but since I use it a lot, I would have preferred. . . .
-
Then either it is Vista versus 7-32
Vista does something better than win7, that’s got to be a first. ;)
I can live with it in sub-menu, but since I use it a lot, I would have preferred. . . .
Have faith in the team, they are good at finding and fixing our own little personal issues. :)
Except for a couple of my personal little ones. :D
-
The test tool – even when it does appear in the sub-menu – does not work.
First, it asks me for the proper file association, and then just opens the PA window where I can, if I wish, test the archive.
But this is multiple steps for what should be two clicks (right context menu / test).
-
One more thing. I have “Test” on the QAT. But I cannot use it even when I have selected an archive. I actually have to open the archive.
That seems like an unnecessary step.
-
for Test there needs to be archive opened… it doesnt have an interface of its own.
-
I Use Win 7
Perhaps it works, too, if I break it apart into all the sub areas. But I don’t want to do that. Context menu is too cluttered as is.
I can get it to show up if I add it to the sub-menu (which, I think, is what Luxor has done). Could you try adding it to the main menu and see what happens?
send over your settings and we will try with them and see what happens on our test computers… maybe it wont show up either.
-
I have used test within the shell for as long as I have used PA. I did not have to open the archive . . . just have it chosen.
Have you decided that they will no longer be true? I can live with it within the sub-menu, as long as it works the way it used to.
-
I have used test within the shell for as long as I have used PA. I did not have to open the archive . . . just have it chosen.
Have you decided that they will no longer be true? I can live with it within the sub-menu, as long as it works the way it used to.
no, i was talking QAT and inside main PA. In the shell, it should work same as always, there were no changes in any case, just repositioning one button.
-
I stumbled on a solution. After brief tinkering, (a) “test” appeared in the main shell menu, and b) I could run test immediately, just after selecting the archive, just as it has always done before.
The problem - unfortunately - is that I am not 100% sure what I did. I was tinkering with adding and deleting several other items in the shell extensions menus. (I thought tinkering with the menus might yield a result.)
I THINK this is what I did:
Under compression:
1. removed compress to RARUnder extraction:
1. ended up with “extract archive to” and “extract archive here.” I either had one but not the other; on even took one off and added it back on.In any event, shazzam: test showed up and worked correctly, both in explorer shell AND in right clicking within the PA window. It did NOT take to me to the PA windows or require me to actually open the archive. Just selecting it was enough.
If you want, I can send you the new registry keys, and you can compare them with the one I sent this morning. Perhaps you can isolate the exact difference.
