-
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.
Vista Drag and Drop
-
I’ve noticed in PA2007b5 when trying to drag and drop a file from the archive to the Windows desktop, it gives you the “not-allowed” cursor.
If you try a second time, it will work fine.
Also, may I recommend the DevExpress VCL components. Their new ribbon control looks perfect and gives glass and all that.
Thanks :P
-
just me?
-
try b6 and let us know… devex is for .Net, and their Delphi version isnt out yet and wont support glass on the ribbon…
-
we use old devexpress vcl stuff in our delphi applications :) but i didn’t realize the haven’t updated ExpressBars vcl yet.
When are you gonna redo PA in C# like every other delphi shop is doing? :P hehehehe
-
we use old devexpress vcl stuff in our delphi applications :) but i didn’t realize the haven’t updated ExpressBars vcl yet.
When are you gonna redo PA in C# like every other delphi shop is doing? :P hehehehe
5 years after Borland closes shop? :-)
-
technically they did :P what’s their new name now for ide’s? codegear or something? my CTO wrote them a pretty nasty letter. hehe
anyhow, same problem exists in b6.
If you drag a file from the archive to the desktop i get the “No-no” cursor. When I let go of the mouse button it goes back to normal, then when i highlight over the PA window, it’s back to the “No-no” cursor. A second attempt at dragging to the desktop is successful.
-
same problem in beta 7
open an archive, select a file and start to drag it. instantly you get the denied cursor. try it again and it works fine.
-
hate to be a bastard but it’s not fixed in beta 8 either.
i do a lot of dragging and dropping from archives during the day. any chance of this one getting fixed?
-
same in b9…
is this on your radar to fix? can you reproduce it?
-
The issue I have is that when I drag and drop in Vista, it goes through the actions of extracting but nothing appears in the folder I’m dragging to. I’m using b9, and it is reproducible
-
same in b9…
is this on your radar to fix? can you reproduce it?
we will be checking it out for b10…
-
The issue I have is that when I drag and drop in Vista, it goes through the actions of extracting but nothing appears in the folder I’m dragging to. I’m using b9, and it is reproducible
i’ve seen that on XP, too.
-
i’ve seen that on XP, too.
well in XP it works fine in general, so please report specific situation (there are hundreds of them possible). It is hard to troubleshoot if it works fine on general document…
-
oh, this problem i haven’t seen on XP…
the problem where you will drag and drop a bunch of files to the desktop or an explorer window. it goes through the motions of extracting everything, but nothing shows up in the window you dragged it to, and seemigly it’s gone… almost like it never copies from a temp folder or something… i haven’t reproduced that one on Vista yet since I’m having the problem that this whole thread is about :)
-
oh, this problem i haven’t seen on XP…
the problem where you will drag and drop a bunch of files to the desktop or an explorer window. it goes through the motions of extracting everything, but nothing shows up in the window you dragged it to, and seemigly it’s gone… almost like it never copies from a temp folder or something… i haven’t reproduced that one on Vista yet since I’m having the problem that this whole thread is about :)
we will be checking it out over the weekend and I will let you know how it goes…
-
we will be checking it out for b10…
does that mean it may have been fixed in 10, or post beta 10?
no change in b10 :)
-
please check with RC1… thanks
-
no change unfortunatley.
edit: correction. slight change.
now, when dragging to the desktop you still get the ‘don’t allow’ cursor, but when you drop it, it kind of hangs on that cursor for a while, then it actually does extract it to the desktop.
better than previous builds, but still not quite right.
are you able to reproduce this on your vista copy?
-
anything i can supply you with to help get this resolved before the final?
-
actually, this does appear to be a vista issue, but something that can be fixed…
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=736086&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=788540&SiteID=1
i think that will explain the issue pretty well. i might try and put together a test app tomorrow.
-
just wrote a quick test app in delphi 6 doing nothing special. works fine. must be something PA is doing.
-
just wrote a quick test app in delphi 6 doing nothing special. works fine. must be something PA is doing.
we couldnt figure it out for the final, but we will check it again for 10.01… Sorry!
-
no worries. just don’t let it fall off the radar and i’m happy.
also, i’m a delphi developer (it’s my job) if you need any help with it at all.
-
Download latest version (english only) via website or via web update and see if this issue has been fixed.
thanks,
-
YAY! it’s fixed!
thanks a lot!!!