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 errors
Is 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.
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.
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.
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
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 gives gpf
When power archiver runs backup script from task mgr it gives 3 gpf windows for unknown and powarc.exe. It is set on gzip tar. I have edited it repeatedly. When I goto the menu from pa and runit w/ the editor it will run. Worked fine before upgrade. This happened in previous versions. I believe it was related to it getting file type wrong. Since it doesn’t give too much info hard to say. This is on w98 so no real dump.
What version of PA are you using?
PA 9.00.33 / Win98
Cannot reproduce this.
Note: Just testing so only used Run Once option?
PBS file attached (just renamed to txt for attaching).
Latest version PA. On win98 original w/ updates. Runs fine from wizard, but tries to run from task manager and gpf. Don’t have anything unusual running at time. Only kerio fw. It did this before in on version. Then ran fine. This no install broke it I guess. I will try to down grade to last version I had.
Can you please check what is the actual version number in About menu?
Sorry about that. Maybe not latest, but just downloaded it. 9.00.31. Thanks.
Just updated. Here is something else I am seeing. When I go from in pa and edit/run the script I have to go and change it to gzipped tar then file name changes(filename.tar.gz) and I can run it fine, but the filename and gzip settings refuse to stick which may be causing the error. Even when I choose save as default if I open the script it goes back to .tar and the regular tar settings.
With the update it finally stuck in pa when editing, but when I run *.pbs script from taskmgr it now gpfs in powerarc.exe. With run once set. How odd. The task is set as c:\path\script.pbs should I change that to make it run better. It may be a previous pa install in the reg somewhere that is messing it up.
I don’t know…weird. zip runs fine, but gzip gives gpf. Checked registry couldn’t find anything that jumped at me.
Sorry, missed your reply (not ignoring you).
zip runs fine, but gzip gives gpf.
Still cannot reproduce this.
Some things to consider:-
Can you activate DR Watson trace ( may help when nothing else is running).
Do you know at which point it gpf’s
a) Building Filelist
b) Compressing TAR
I don’t know kerio fw, does it have an Anti-Virus check/scan which “might” influence this?
Do you have other tasks running (e.g. Disk Cleanup) which might be deleting the Temp directory?
Don’t sweat it. I was just using zip for now. Hadn’t had time to fool with it, but maybe this weekend. Since it doesn’t say. I don’t know when it happens, but it is right when it starts to run. It seems to load then gpf. Active desktop is disabled. I am using 5.5 IE. on this sys. 6.0 on win98 can get clunky. (use FF mostly anyway) I tried using dbugview and didn’t get anything. I did hit on something that has happened before tho. I went back and did a new script adding a folder at a time. I got a few folders added and it was fine. I think it was the my docs folder. Once before I had another desktop folder that triggered this. Might be related to size w/ in the desktop folder or recursive folders, as well. Just thought that the fact that it ran fine w/in PA, but not from taskmgr was odd and w/ tar gzip. I am going to add back all folders incrementally and see if I can isolate it. Kerio has no AV I unloaded other processes, as well. Including w/o AV. Didn’t change anything tho…just upgraded PA. I will let you know what it does.
It appears to gpf’s when it is compiling a filelist. However, nothing is open or running. I tried it this way.
gpf’s when it is compiling a filelist.
That points to a problem in TAR module. I would check filenames, path/filename lengths and things like non-english characters (Unicode support is not good on Win98).
Active desktop is disabled. I am using 5.5 IE. on this sys. 6.0 on win98 can get clunky.
We have some differences. I have active desktop enabled (only for Background JPG).
I have IE 6 - only because it includes OS updates.
I also upgraded OS via the MS update/security CD.
use FF mostly anyway
I use Opera :cool: - but do have FF installed :p
That is for another forum though :D
Edit: You did upgrade PA with 9.00.35 ?
Yep, here’s the deal. A particularly long shared file path looks to be the problem w/ tar. Removed that: it ran fine. It ran fine before and from w/in PA. Just not from .pbs. I don’t have time stamp or other options selected. I will try 9.00.35 later and see if it works okay. Thanks guys. I have been sending you business. :D
Maybe save yourself some testing effort (wait for 9.1):
can you please send me that PBS you had problems with and full filename of file that caused problems?