-
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.
PA and Vista Ultimate Blue Screens
-
During my installation of PA 2007 I received a Blue Screen referencing the fvevol.sys module.
Since then, my computer will crash every few days with the same error… :(
Has anyone else had this problem?
Is this a know issue with some versions of PA?I enjoy using PA over other software and am very interested in getting this fixed…
Thank you in advance for any help…
-
it runs fine here… I would suppose it is some kind of hardware issue on the computer… Do you know what is fvevol.sys actually?
What exactly do you do when it crashses? (outside of installation).
thanks,
-
The fvevol.sys is the BitLocker Drive Encryption Filter Driver.
When I receive the blue screen, all I do is reboot and it seems to hold for awhile…I do not know if it is related to PA 2007 or not, It was when I was installing it that I ran into the first blue screen, so that kinda stuck in my head…
-
The fvevol.sys is the BitLocker Drive Encryption Filter Driver.
When I receive the blue screen, all I do is reboot and it seems to hold for awhile…I do not know if it is related to PA 2007 or not, It was when I was installing it that I ran into the first blue screen, so that kinda stuck in my head…
try installing 10.01 and see if it happens then. There shouldnt be any issues since bitlocker encryption should be completly transparent to applications, there is nothing for us to do.
-
Thanks…
I will update PA 2007 and see what happens…
–mcannon-gso
-
There is also an Vista compatibility update for many applications that was released today, you might want to download it via Windows Update, if you have not before.
It might help.
-
What time today did it come out?
My system was set to download updates everyday @ 3am.It was after this time that I received the BOD…
-
and you have been receiving only after that? It could be telling. You can check your Windows updates and see if it was already installed, and uninstall it possibly.
-
spwolf,
I have upgraded to the latest version.
However, I think I figured it out… It actually was a coinsidence that when I was installing PA and when the updates were installing, my disk defrag was running. I think when that is running and a reboot is done without stopping it first causes the BSOD…
I will keep a close eye on this to see if these are the facts……
Thanks for your help and advise…
Cheers =)
-
I am glad you got it figured, althought it should not happen still.
What defrag are you running? Included with Vista or 3rd party?
You might want to report it to their support, so it gets fixed, even if eventually. BSOD should really not happen with Vista.
thanks!
-
I am glad you got it figured, althought it should not happen still.
What defrag are you running? Included with Vista or 3rd party?
You might want to report it to their support, so it gets fixed, even if eventually. BSOD should really not happen with Vista.
thanks!
I am running the included Defrag. I can not call support on this since I have purchased an OEM version. Is there somewhere else I can post this for them to see? I have been sending my problem reports to them for analysis.
-
Hi,
You will need to contact the following:
- If Vista came Pre-installed, then you would contact the system vendor.
- If you purchased an OEM version of Vista not with a PC then you cannot contact anyone for support. However, you can try the Microsoft Forums and Community Message Boards for User-To-User support.
If you were refering to the .dmp files created on error, try attaching them here, or emailing to me at the email in my profile, and I will see if I can help you by reading it and see what is causing problems.
Thanks, Andrew Robinson.
