-
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.
Speed: current folder
-
Hi. For some reason, since the move to 11.60 (I’m now using 11.60.26, but it has been this way since I moved from 11.50.whatever) the option in Miscellaneous, Speed: use current folder as temp, which should mean that instead of extracting to a temp folder then copying to the right place PA should just extract to where I asked, doesn’t work. It’s a small thing (just need to wait a few seconds while PA initiates the copy, and then for the files to be copied), but rather annoying. Is anybody else experiencing this?
BTW I’m extracting by d&d from the main window. This issue doesn’t present when using context menu or the “extract” button on the main window. -
Hi. For some reason, since the move to 11.60 (I’m now using 11.60.26, but it has been this way since I moved from 11.50.whatever) the option in Miscellaneous, Speed: use current folder as temp, which should mean that instead of extracting to a temp folder then copying to the right place PA should just extract to where I asked, doesn’t work. It’s a small thing (just need to wait a few seconds while PA initiates the copy, and then for the files to be copied), but rather annoying. Is anybody else experiencing this?
BTW I’m extracting by d&d from the main window. This issue doesn’t present when using context menu or the “extract” button on the main window.drag and drop always goes to the temp first, thats the only way it can work in vista/win7 and as an positive spin, it also lets you work around uac in vista/win7.
-
drag and drop always goes to the temp first, thats the only way it can work in vista/win7 and as an positive spin, it also lets you work around uac in vista/win7.
So this explains the other poster’s complaint about extracting archives not respecting his/her wishes to move the file to the folder s/he wanted. PowerArchiver 2010 is designed for Windows 7…which is why it has to do the temp deal this way.
I’m not so sure about this. Doesn’t this mean temporary files downloaded are filling up the temp directory? Why can’t there be an option setting there or a button that allows PowerArchiver users to DELETE the temp files downloaded there? If you can’t or won’t do this…it forces me to create a customized button using Directory Opus 9.5 to purge that directory as a separate step. This shouldn’t be necessary.
-
So this explains the other poster’s complaint about extracting archives not respecting his/her wishes to move the file to the folder s/he wanted. PowerArchiver 2010 is designed for Windows 7…which is why it has to do the temp deal this way.
I’m not so sure about this. Doesn’t this mean temporary files downloaded are filling up the temp directory? Why can’t there be an option setting there or a button that allows PowerArchiver users to DELETE the temp files downloaded there? If you can’t or won’t do this…it forces me to create a customized button using Directory Opus 9.5 to purge that directory as a separate step. This shouldn’t be necessary.
i am not sure what you are talking about at all :-).
Drag and droping files from PA window to Explorer, extracts files to temp folder first and then moves them to destination folder.
It has nothing to do with downloaded files or any other reported issues.
-
i am not sure what you are talking about at all :-).
Drag and droping files from PA window to Explorer, extracts files to temp folder first and then moves them to destination folder.
It has nothing to do with downloaded files or any other reported issues.
But my interpretation of your remarks suggests this procedure fills up the temp folder all the same. It is the same thing. Whether I manually drag and drop from PA to Explorer or even downloaded files into the directory I want. I’m getting the impression that’s what PA is doing (based on your comments) - it’s still filling the temp folder…even if I don’t want it to.
I’m afraid I disagree here. I don’t recall other file managers doing this procedure. I’ll ask around to see if Directory Opus does the same thing. Maybe it does. I just don’t feel comfortable knowing my files are directly sent to the temp folder even if I don’t expressing ask it to do this. This behavior in Windows XP isn’t necessary…as I’m not planning to upgrade to Win 7. There should be an explicit option to either allow or disallow this behavior especially for Win XP users.
-
But my interpretation of your remarks suggests this procedure fills up the temp folder all the same. It is the same thing. Whether I manually drag and drop from PA to Explorer or even downloaded files into the directory I want. I’m getting the impression that’s what PA is doing (based on your comments) - it’s still filling the temp folder…even if I don’t want it to.
I’m afraid I disagree here. I don’t recall other file managers doing this procedure. I’ll ask around to see if Directory Opus does the same thing. Maybe it does. I just don’t feel comfortable knowing my files are directly sent to the temp folder even if I don’t expressing ask it to do this. This behavior in Windows XP isn’t necessary…as I’m not planning to upgrade to Win 7. There should be an explicit option to either allow or disallow this behavior especially for Win XP users.
You are completely misunderstanding what is being said here:
a. When you are drag and dropping from ARCHIVE to disk, PA uses temp folder. None of the files are left in the temp folder. It is not being filled up.
b. When you drag and drop in any other case (from folder to other folder), temp folder is not being used.It seems to me that you dont have this issue at all, you seem to mind the fact that something was done for “Win 7” users while you are “Win XP” user. There is no reason for that - PA was built for Win XP for past 8-9 years. There is an limit on number of options we can have without it being too cluttered. We already have hundreds of options, so we try to keep new ones at minimum, unless they are necessary.
-
a. When you are drag and dropping from ARCHIVE to disk, PA uses temp folder. None of the files are left in the temp folder. It is not being filled up.
Don’t know if this matters, but explorer says “copying files” rather than “moving files”, so maybe temp folder is filling up (that’s not really a concern for me, I assume that windows will know to empty it when required. Speed, however, is important).
One more thing. I’m not a programmer, but if PA can skip using a temp folder while not using d&d, why not always (is there an inherit difference?)?
Also, I haven’t yet updated my laptop to win7, but I was using both PA11.50 on my laptop and earlier versions on my win7RC desktop before, and in both cases I seem to remember being able to extract using d&d without using a temp folder. Might be mistaken, but I don’t think so. I even think that I checked this very issue for someone on the general forum once.
If those earlier versions could do it, what has changed? -
Don’t know if this matters, but explorer says “copying files” rather than “moving files”, so maybe temp folder is filling up (that’s not really a concern for me, I assume that windows will know to empty it when required. Speed, however, is important).
One more thing. I’m not a programmer, but if PA can skip using a temp folder while not using d&d, why not always (is there an inherit difference?)?
Also, I haven’t yet updated my laptop to win7, but I was using both PA11.50 on my laptop and earlier versions on my win7RC desktop before, and in both cases I seem to remember being able to extract using d&d without using a temp folder. Might be mistaken, but I don’t think so. I even think that I checked this very issue for someone on the general forum once.
If those earlier versions could do it, what has changed?it is moving the files, regardless of whatever the dialogue says (just clarifying so people dont think files are left). Windows actually is not that good with managing your temp folder.
Only way for us to have d&d working from archives is via temp folder (in Vista/Win7). It has been like that for quite a while, from early PA 2009 betas, maybe even sooner than that (forgot when was Vista supported added in PA).
Drag and drop is not the same action as extract files to folder, it calls specific drag and drop windows functions which can be very beneficial (for instance in this case with UAC) and maintains compatibility with other windows apps (so you can drag and drop not only to Explorer but any application that supports it).