-
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.
-
-
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.
Deleting large archives
-
I have noticed I cannot delete large archives, please see the attached.
The file is not open in explorer in any operator-instigated way. All affected files are approx 4.5Gb on an NTFS partition. Smaller files can be deleted without issue. Is this related to (I assume) PA showing the archive contents in the delete dialogue box?
Cheers
DrT
-
Any thoughts on this or any ideas on how I can test if PA is involved?
Currently I have to use an unlocking/deleting facility.
Cheers
DrT
-
this is an iso file, right?
-
Yes. I can delete smaller ISO files even from the same location., but this one is approx 4.5GB. It is an OpenSuSE distro ISO.
The attached is what I see then I try to delete the ISO and a screenshot of an Unlocker screen to show why. PC only turned on 30 mins ago. 100% reproducible.
As usual, happy to run any tests etc to help out.
Regards
DrT
-
great!
-
great!
Does that mean I have found something useful? If that is the case, why are only large ISOs affected?
Regards
DrT
-
Obviously it’s an issue so very helpful… I would guess that iso files over 4gb cause some internal issue in listing code hence the lock… We will know more once Feb team fixes it, but reproducible report is 80% of the work already
-
Okay, thanks.
DrT
-
lets check this out, reporting back with results or questions.
thanks for the details
-
Created two 4.8+gig ISO files, mounted/unmounted them, extracted them and they deleted fine afterwards.
I’m downloading openSUSE-Tumbleweed-DVD-x86_64-Current.iso and trying with that.Let me know if you did anything specific after which this ISO file became undeletable.
Thanks!
-
I am doing nothing to these files. I cannot delete any OpenSuSE distros, I have both 13.2 distos and latest snapshots of Tumbleweed…that’s 4 in total; even after just turning on my computer. Done nothing to them at all. All I have to do is download and try to delete. I don’t know whether it is a size issue, but I could delete a Knoppix distro at 4.1 GB.
The on thing I have noticed, is that before the first delete attempt, which always fails, there are no locking processes. These show up (as per the above screenshot) only after the first failed attempt.
Cheers
DrT
-
Basically, you downloaded this file and then when attempting to delete it it gives you the said error?
I’ve downloaded the same, file and it deleted just fine.
Please run me through the process starting with obtaining the file and deleting it at the end. What exactly goes on in between?
Let me know, I’ll give it a try. -
I can turn on my computer and do nothing and still cannot delete those files without an unlocking utility. I downloaded the files a good week or two ago.
It gets even more spooky. I d/l one of these files to another PC and have exactly the same problem. OS is the same, Win 7 x64.
<smoking gun=“”>Uninstalled PA and rebooted and COULD delete file. Re-installed PA and cannot delete file</smoking> . Saved my settings and reapplied them before trying the second delete (which failed).
I did save my settings before uninstalling - anybody want the reg file for testing?
-
. . . you have preview turned on? Try turning it off (Alt-P) and see if that helps?
-
. . . you have preview turned on? Try turning it off (Alt-P) and see if that helps?
I did. Turning it off made no difference.
Cheers
DrT
-
Sorry. I thought it might help. I had some problem deleting files when preview was open in PA mini. I thought it was worth a try.
One other possibility. If you have that file type set to always use Volume Shadow Copy Support, it might keep the file open in explorer.
The last option is there is something about the partition (I assume that is J:?) that is causing the problem.
-
Hi,
See post #13 for some tests that I ran on another computer. Strangely, only my four OpenSuSE ISOs are affected.
In short, I can delete the files without PA installed.
Cheers
DrT
-
hmmm, lets try with your settings. If you can please send them over(in a cab file) to support at conexware dot com and I can try to reproduce that way.
Did you perform an installation of the said ISOs before attempting to delete them or can you reproduce it by just downloading the file and attempting to delete it right away after download?
thanks again!
-
Just download and try and delete - that’s all I did on my test.
Email just sent, subject as per this thread.
Happy to test and fixes or send any further info.Cheers
DrT
-
i will check it out if need be :-)
-
this was reproduced by the team, and written in for a fix… thanks for the report!
-
You are more than welcome.
Regards
DrT
-
can you check latest official release:
http://dl.powerarchiver.com/2015/powarc150106.exethanks!
-
can you check latest official release:
http://dl.powerarchiver.com/2015/powarc150106.exe
thanks!Issue seems fixed, but the version installed is 15.01.05 not 15.01.06 as expected.
Cheers
DrT
-
Issue seems fixed, but the version installed is 15.01.05 not 15.01.06 as expected.
Cheers
DrT
cool, ISO support has been improved as well… version is fine, thanks!
-
Sorry to report but the problem is back. Using the latest version.
I am clearing out my Linux ISO folder and the issue has presented itself with the OpenSuSE 13.2 x64 ISO (I’m now using Tumbleweed). The file is locked by 5 explorer.exe processes.
I copied the file to a different computer and got the same problem.
I shall keep the file for testing purposes to check any fixes.
Regards
DrT
-
Sorry to report but the problem is back. Using the latest version.
I am clearing out my Linux ISO folder and the issue has presented itself with the OpenSuSE 13.2 x64 ISO (I’m now using Tumbleweed). The file is locked by 5 explorer.exe processes.
I copied the file to a different computer and got the same problem.
I shall keep the file for testing purposes to check any fixes.
Regards
DrT
is this the same ISO as before? Since PA did not get update in-between, so what else changed?
-
is this the same ISO as before? Since PA did not get update in-between, so what else changed?
There was an update and we thought the issue had been fixed, please see messages #23 & 24. It is the same file, viz openSUSE-13.2-DVD-x86_64.iso, the problem exists on two PCs with the same file and same version of PA (the latest). The OS is Win 7 x64 in both cases.
The problem was reproduced by yourselves as per earlier in the thread.
Regards
DrT
Update:- Another ISO is affected - a Tumbleweed ISO. Just moving it to another computer to check if the delete fails there too…it does.
-
Any more news on this issue?
Mni tnx,
DrTeeth
-
i reproduced it and re-opened it in bug tracker… we will see with next update, soon.
-
Figured it out, archive was wrongly read… now it reads it correctly:
http://www.powerarchiver.com/test/release15/powarc150202.exethere are two image files inside of that ISO file. It should be fine now, check it out! Thanks!
-
Hi spwolf,
It looks like you got the sucker now. Could you please explain what the issue was?
Thanks, DrTeeth
-
Hi spwolf,
It looks like you got the sucker now. Could you please explain what the issue was?
Thanks, DrTeeth
archive was recognized wrongly, hence the issue with it locking up the file… now this ISO MBR format is recognized properly in preview and it works fine.
-
Hello, this should be fixed in the latest update. Tested here and confirmed :)
You may update via Patchbeam or use this direct download link;
http://dl.powerarchiver.com/2015/powarc150304.exePlease let us know and thanks for your help!