-
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 17.00.91- File "Move" = folder delete
-
I notice that this continues to be a problem. To recap:-
I have a .zipx archive, to which I wish to move all files in a folder.
If, under Miscellaneous settings, I do NOT have “Enable Advanced Add…” checked (i.e. simple Add screen), when I select the files and Move them, they disappear from the folder, thus leaving an empty folder. This is what I would expect when I am selecting files within the folder and not the folder.
However, if I tick the “Enable Advanced Add…” option and use that screen to Move the files, the effect is to move the files and also delete their folder. In other words, the Move action moves the containing folder as well as the files. If just one file is unselected and left in the folder, then the folder is not deleted.
If I had selected “Move” for the folder (not the files), then I would expect the folder to be moved (deleted) from the folder/directory structure and into the archive. This is, however, not satisfactory when I wish to Move all the files in the folder to the archive, but leaving an empty folder for future use.
I have tested this using different parameters in each of the two Add screens e.g. store paths, don’t store paths etc. but there isn’t any difference in how the screens operate.
-
@pa_fan I used the PA explorer (view Explorer display style), left side folders, right side the files of an opened archive. I moved all files of that archive to the other…(right to left dual screen) no problem, the emptied folder is still present. And then removed the files back to their original archive. (PA 2017.00.91 - simulations with advanced add not enabled and enabled).
-
@pirrbe said in 17.00.91- File "Move" = folder delete:
@pa_fan I used the PA explorer (view Explorer display style), left side folders, right side the files of an opened archive. I moved all files of that archive to the other…(right to left dual screen) no problem, the emptied folder is still present. And then removed the files back to their original archive. (PA 2017.00.91 - simulations with advanced add not enabled and enabled).
Interesting. I’ll try that out of interest. I do find the Explorer view in the archive window not the best method for the way I have things arranged, and I don’t especially find the multiple narrow panes to be that easy to work with.
However, it still leaves the problem I mention above, in the case where I’m working with two open PA windows; one being the open folder and the other the Advanced add window. I find this method (whether using either of the two Add windows) far easier on my system, with my folder tree layouts.
This isn’t a new problem, as it came up in my testing for 17.00 at the early part of the year. I reported it against 17.00.55, and, looking at the post, it remain marked as “Unsolved”.
https://forums.powerarchiver.com/topic/5711/17-00-55-zipx-move-and-replace-files
-
hmmm, tested again. tested creating zipx various ways, with enabled/disabled advanced add window, selecting all files inside a folder and Moving them into a zipx archive, empty folder stayed empty(not deleted) in each case.
How exactly are you compressing? I’ll try the exact same way
-
@mili PA_Fan, héee… do you open two sessions of PA and each with a diff configuration ?? (able/unable add win).
-
@pirrbe Nope.
-
Test folder, 6 files.
Move 5 files to test archive per settings in shots 1 and 2 and selection in shot 3
Folder remains with 1 file left
Move remaining file per next shot. Note that the folder and file boxes are bold-ticked.
File moves, folder disappears.Only one instance of PA running.
If I use the “Simple” add window, I can perform exactly the same steps, but after the last file is moved, the folder remains.
-
got it, it occurs when selecting files via the Select files/folders button.
Does not occur when D&D files inside.Thanks very much for the details, logging it in
-
I got hit by something like this, I think, today. 17.00.92, 64-bit. Using PA Scheduler / script once a week to archive (ie move) files over 35 days old into zipx – which has been happening without incident for months. This morning’s run deleted the source folders, complete with newer – unarchived – content. Files lost irretrievably as a result. :(
-
The Backup application does not have the Action field as the Add window does, where you can select to either Move/Add/Update/Freshen the archive. That option is available in the Add window
Maybe you have the “Delete original files after backup” selected?
You can send us the .pbs script to support at conexware dot com and we can check it out to see why the files were/are deleted