-
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.
-
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.
UNSOLVED Smart AI: Preferences not intuitive
-
Sorry, in this scenario: What will happen?
Is FIPS mode auto, on or off?
Is PowerSave mode auto, on or off?
Is Touch mode auto, on or off?For all three settings, I can select on, off or auto - what’s the catch of the switch on top to enable/disable Smart AI? How does it influence my selections for the three options below?
-
FIPS, PowerSave Mode, Touch Mode are all part of the SmartAI component and therefore the settings in the dropdowns are applied when Smart AI is turned on at the top.
Thanks for bringing this up, would a textual description at the top help in clearing up how the settings work?
We’re always looking to present new options/features as clear as possible, and this helps us in that.Let us know! thanks!
-
@Mili said in Smart AI: Preferences not intuitive:
FIPS, PowerSave Mode, Touch Mode are all part of the SmartAI component and therefore the settings in the dropdowns are applied when Smart AI is turned on at the top.
Thanks for bringing this up, would a textual description at the top help in clearing up how the settings work?
We’re always looking to present new options/features as clear as possible, and this helps us in that.Let us know! thanks!
help section would help for sure :)
-
@Mili So, if I understand you correct, I’ll have to enable Smart AI to use the components. But if I set all components to on or off, there’s nothing “smart” about it?
If I disable Smart AI, the three components will be disabled even if I’ll set them to enabled? Wouldn’t it be better to disable the component’s options if “Smart AI” is disabled in first place?I think a description would be very helpful in any case.
-
@BigMike said in Smart AI: Preferences not intuitive:
@Mili So, if I understand you correct, I’ll have to enable Smart AI to use the components. But if I set all components to on or off, there’s nothing “smart” about it?
If I disable Smart AI, the three components will be disabled even if I’ll set them to enabled? Wouldn’t it be better to disable the component’s options if “Smart AI” is disabled in first place?I think a description would be very helpful in any case.
right now you dont have to enable smartai to enable options, it is work in progress. I guess big selector could switch them all to Auto or Off.
Otherwise, when it makes sense, there will be more than a single option… each individual option is different, and you might want to use touch mode but do not want FIPS.
By default, most of them will be on Auto, now or in the future, and that is the main point - being able to change options intelligently based on users computer usage, without them having to go into options.
-
@spwolf For sure, I understand, that I want to set the single components to different states. And ON/OFF/AUTO are valid options for each. But I think, the global SmartAI slider is not intuitive (but if it’s still work in progress, I guess it will get better).
-
Hi @spwolf, I’ve just had a look at the new preview.
Now, I think, I understand what’s the effect of changing a setting.
But as the settings dialog seems to be unfinished, I can’t really ensure it by testing…But I still think the UI could be simpler.
Now, there is one slider to enable “SmartAI”, which gives you the possibility to enable SmartAI for FIPS, power saving and touch UI via another checkbox.
If this “SmartAI” slider is disabled or the corresponding checkbox is unchecked, I can configure each of the three setting by a combo box.Then there is another slider for “SmartAI for themes” which gives me the possibility to select a themes for standard and dark mode.
The sliders are completely superfluous in my opinion.
The checkboxes and the comboboxes can easily combined if you add an “Auto” or if you like “SmartAI” option, as it was before.
If one setting, stands on “Auto”, SmartAI needs to be enabled. If none of the three is configured for auto selection, SmartAI could be disabled.Same for the skin selection: If the same skin is selected for standard and dark mode, SmartAI for themes is off, if different themes are selected, SmartAI for themes is on.
-
@BigMike I also think it can still be improved… incoming i guess :)
-
I’ll continue to give my input, while it’s work in progress. Complaining after release is somehow not the right way…
-
@BigMike said in Smart AI: Preferences not intuitive:
I’ll continue to give my input, while it’s work in progress. Complaining after release is somehow not the right way…
please do… appreciated!
-
Hi,
I’ve reported this already per mail, when I sent my updated translation files, but actually never got a reply:
If I first open up the SmartAI properties, while “SmartAI” and “Auto detect color mode” are disabled, the “Auto” check boxes are enabled (red in the image), enabling SmartAI and disable it again, the check boxes will also be disabled.
Even worse: Enabling the light/dark mode detection disables the Theme dropdowns (why??), switching it off/on again, won’t enable these dropdowns, they stay disabled (blue in the image)The gestures list and the gesture dropdown cut the text, this is also the case for English texts. It’s impossible to know, what the gesture looks like/what action will be performed. (yellow in the image)
-
good points @BigMike
reproduced all and logged in, as well as an improvement report for the gestures text.
thanks! -
Just to report back: Still not working in 19.00.58
