-
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 2007 installs not retaining previous settings
-
All PA 2007 betas I’ve installed clobber the old install. This means I have to both reenter the registration code and reconfigure all my settings. Even now, going from beta 4 to beta 5 required that I once again redo everything.
I most certainly hope this will be fixed.
Thanks
-
Totaly agree with you, this has also happend to me on every upgrade and it does become slight frustrating more so when you have to re configuire all your settings over and over again.
This is why in one of my posts I asked for a “Save Configuiration” button that extracts your prefered settings to a file which you can upload on the next upgrade thus stoping you from having to re apply everything all over again.
For security reasons you can understand why you need to re-enter your serial number but for beta’s i wouldnt say it was needed. more so on full releases.
-
@Sir:
Totaly agree with you, this has also happend to me on every upgrade and it does become slight frustrating more so when you have to re configuire all your settings over and over again.
This is why in one of my posts I asked for a “Save Configuiration” button that extracts your prefered settings to a file which you can upload on the next upgrade thus stoping you from having to re apply everything all over again.
For security reasons you can understand why you need to re-enter your serial number but for beta’s i wouldnt say it was needed. more so on full releases.
its an bug, so you shouldnt need to re-enter everything every time :-)
-
Cheers for that! We will let you off :0) this is what you get being beta testers!
-
All PA 2007 betas I’ve installed clobber the old install. This means I have to both reenter the registration code and reconfigure all my settings. Even now, going from beta 4 to beta 5 required that I once again redo everything.
I most certainly hope this will be fixed.
Thanks
Still not fixed in Beta 6, I had to enter all my info and redo my configuration again.
Thanks,
Normandie -
I’m also noticing the same problem.
-
it has been fixed in beta 6, problem is that it depends on previous installation you did… so in next version it will work fine for you guys…
-
it has been fixed in beta 6, problem is that it depends on previous installation you did… so in next version it will work fine for you guys…
Great, thanks alot & have a good day.
Normandie
-
Hi
I have just installed beta 6 of PA 2007, and it asks me to register again (enter my name and code) every time I run it. Is this the same problem as the one you guys have described?
Just installed it on a new install of XP without upgrading, and I also uninstalled 2007 and installed 2006, entered my details and code, checked it worked ok, then upgraded to 2007 and the same thing happened.
Is this fixed with the fix for the settings changing, or have I found a new bug?
Cheers
Matt
-
Hi
I have just installed beta 6 of PA 2007, and it asks me to register again (enter my name and code) every time I run it. Is this the same problem as the one you guys have described?
Just installed it on a new install of XP without upgrading, and I also uninstalled 2007 and installed 2006, entered my details and code, checked it worked ok, then upgraded to 2007 and the same thing happened.
Is this fixed with the fix for the settings changing, or have I found a new bug?
Cheers
Matt
you need to visit your account and get codes for PA 2007, as they are different from PA 2006 codes.
thanks,
-
Hi spwolf
Thanks for that, got new codes and it works fine :)
It’s not obvious that new codes was what was wrong when it happens though, can it check and tell the user that they need new codes?
Matt
-
Hi spwolf
Thanks for that, got new codes and it works fine :)
It’s not obvious that new codes was what was wrong when it happens though, can it check and tell the user that they need new codes?
Matt
there is no way for us to do that right now… which is why it is written on the website several times :-)
-
In beta 7 i have the same problem. I reformated my hard drive and installed beta 6 and then i installed beta 7 and i have to renter my settings again. looks like pa is over writing the settings thats what my installed monitor is saying. When will this be fixed i have a windows 2000 computer. its an annoying part of upgradeing pa with every beta
-
I can confirm this too, all my settings for the previous beta (including the serial number) were lost during the upgrade to the latest beta.
It would be nice if the installer could remember the settings (shell extensions, folders etc.) during the update.
-
Not fix in 7, still had to enter all the reg info.
-
Confirmed here too with beta 7. It would be nice to export settings just so we wouldn’t have to go through this - but, that’s a different issue. ;)
-
Confirmed here too with beta 7. It would be nice to export settings just so we wouldn’t have to go through this - but, that’s a different issue. ;)
we found another bug… it will be now fixed for… b9 :-).
thank you guys - you can always export via regedit.exe and then just execute the .reg file after installation…
-
As others have stated, this is definitely NOT FIXED in Beta 7
-
Ditto!
I have actually designed my own regkey that will upload my Username, Serial aswell as my old prefered settings in order to save time as we are now in Beta 7 and still the settings don’t seem to save after an upgrade.
In some new software programs when upgrading or uninstalling you have the option to keep or delete your current registry settings I would suggest that this might be an idea PA2008 Have or maybe a later release of 2007 Final.
-
@Sir:
Ditto!
I have actually designed my own regkey that will upload my Username, Serial aswell as my old prefered settings in order to save time as we are now in Beta 7 and still the settings don’t seem to save after an upgrade.
In some new software programs when upgrading or uninstalling you have the option to keep or delete your current registry settings I would suggest that this might be an idea PA2008 Have or maybe a later release of 2007 Final.
again, it is an bug :-). It will still be reset in B8, but then it will work fine in B9 or final, whatever comes sooner :-).
-
this is still not fixed and it means i have to change the toobars and settings every install.
-
Did they release beta 9 and I miss it?
-
-
try now guys…
-
It worked for me! :D :D :D
-
-
Fixed in PowerArchiver 2007 10.00.28 Beta 9
-
Just for fun err… testing, I uninstalled PA beta, rebooted, then installed PA 2006 and entered registration code.
Then I tried “upgrading” to Beta 9…
Of course, registration is “lost” - but the timer showed
Days Used : 16 (Out of 30)Not sure where this came from, but I like it - two weeks to get the new/free code seems eminently fair.
Maybe in this specifc case (upgrade of registered version) there should be a text stating that new codes are needed and where to get them?
Even the skin was preserved when switching to classic view :cool:
The only other setting not preserved were the shell extensions - not really surprising.
-
Just for fun err… testing, I uninstalled PA beta, rebooted, then installed PA 2006 and entered registration code.
Then I tried “upgrading” to Beta 9…
Of course, registration is “lost” - but the timer showed
Days Used : 16 (Out of 30)Not sure where this came from, but I like it - two weeks to get the new/free code seems eminently fair.
Maybe in this specifc case (upgrade of registered version) there should be a text stating that new codes are needed and where to get them?
Even the skin was preserved when switching to classic view :cool:
The only other setting not preserved were the shell extensions - not really surprising.
If you just installed PA 2007, it would be at 0. But uninstalling PA 2007 will not reset it to 0 :-)
-
If you just installed PA 2007, it would be at 0. But uninstalling PA 2007 will not reset it to 0 :-)
As I said I don’t think there is a problem it is just that
if I uninstall PA 2007 and install PA 2006 it says:
Days 842 (out of 30) - Expired :DAnd I was used to seeing that - earlier 2007 BETAs also told me that.
Now if I uninstall PA 2007(B9) and install PA 2007(B9) it says:
Days 16 (out of 30)That’s why I mentioned it.
Maybe the 16 days used is just counted from installation of PA 2007 Beta 8 - but as I did enter register code for that I am not sure where it counts from :confused: -
As I said I don’t think there is a problem it is just that
if I uninstall PA 2007 and install PA 2006 it says:
Days 842 (out of 30) - Expired :DAnd I was used to seeing that - earlier 2007 BETAs also told me that.
Now if I uninstall PA 2007(B9) and install PA 2007(B9) it says:
Days 16 (out of 30)That’s why I mentioned it.
Maybe the 16 days used is just counted from installation of PA 2007 Beta 8 - but as I did enter register code for that I am not sure where it counts from :confused:We changed the the date for counting PA 2007 in one of the beta’s, so it counts from then… I am not sure exactly which one was it…
-
Well I was just wondering if a first time upgrade from PA2006 to PA2007 will reset the counter to 0 for PA2007?
There is another “problem” however.
When upgrading from PA 2006 to PA 2007, the entry in Add/Remove programs for PA 2006 is not removed.
So I now have two entries.If I now click to remove PA 2006 - it actually removes the installed PowerArchiver but leaves the entry for PA 2007 in Add/Remove programs :confused:
-
You should uninstall PA 2007 and then PA 2006, and then install PA 2007.
As to the counter, it is relative to when it is installed first on your system, which is why it shows you 16 days… to person who installs it today, it will be 0.
thanks,
-
You should uninstall PA 2007 and then PA 2006, and then install PA 2007.
So “upgrading” from PA2006 to PA2007 is not going to be possible - only clean install (with loss of settings).
-
So “upgrading” from PA2006 to PA2007 is not going to be possible - only clean install (with loss of settings).
unless you want to leave PA 2006 entry in Control Panel…. If thats fine, then upgrading is possible.
-
fixed in latest beta
