-
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.
I think PA just blue screened my Vista x64 SP1 PC
-
Had been using default classic skin for a longtime so I decided to change it to the modern skin. Didn’t like the skin so I proceeded to go to the skins options and there were two others listed MyPA and Longhorn. Changed to Longhorn and PA suddenly crashed. Any attempt to reopen PA just caused an instant “This app stopped working” message from Vista. I then decided to go to the PA program directory and delete those two skins hoping that would cause PA to revert to default skin. As I was clicking through the directories, I noticed that my sound as screwed up as in static filled and the “click” sound effect was instead the “stop” or “crash” sound effect instead. Figured it was time for a reboot so I went to the start menu and selected to restart the PC. Within 20 seconds I got a blue screen. Powered down the PC and cold booted it and got a windows recovered from a serious error message. Immediately deleted those two skins and got PA to start again, but this was very troubling. This Vista install isn’t 3 months old and I had no issues up until this point. Using latest PA 2007 build, btw.
****** I tried to repro on an XP PC and although I didn’t get it to crash, there are definite problems with those two skins. If you switch back and forth between them, they will glitch up. It will for example show the MyPA skin even though it clearly shows Longhorn skin as being checked. Those skins should be removed from the installer if they’re not going to be updated. TBO, neither one of them are that great, especially LH.
-
Thanks Denzilla,
Im sure one of the developers will get back to you with regards to this issue. In the mean while can you provide a bit more information of your system specs of which this issue occured. ie, CPU, RAM, Vista Version ie Ultimate, Home etc… also if possible any programs that were runing as well.
Can any other users who own Vista try and replicate this and report it please? This will allow PA to gain an idea to the overall impact to other users.
-
I’m unable to reproduce this on vista x86.
-
Just tried it on Vista home premium 32 bit and could not reproduce.
What version of PA are you using ? as there was a problem with these skins in an earlier version as posted HERE
-
I could be a specific problem with Vista x64, SP1 or a combination of the two. My hardware:
Asus M2N-X motherboard
A64 X2 4400+
2GB Corsair VS DDR-667
Sapphire Radeon HD 3450 PCI-E
Seagate 250GB SATA II
Vista x64 w/SP1I had no other apps open at the time other than a few things in the systray (KAV7, APC powerchute, ATI control panel)
-
I could be a specific problem with Vista x64, SP1 or a combination of the two. My hardware:
Asus M2N-X motherboard
A64 X2 4400+
2GB Corsair VS DDR-667
Sapphire Radeon HD 3450 PCI-E
Seagate 250GB SATA II
Vista x64 w/SP1I had no other apps open at the time other than a few things in the systray (KAV7, APC powerchute, ATI control panel)
skins should not be used in x64… it is our error, it was supposed to be disabled when it detects x64.
so as an workaround, dont use skins in x64 :-).
-
skins should not be used in x64… it is our error, it was supposed to be disabled when it detects x64.
so as an workaround, dont use skins in x64 :-).
Just glad to hear there was an actual reason for the blue screen. Its actually the first blue screen I ever had. Seen them on other people’s systems, but never my own. Rather scary :p