-
PA 2023 22.00.08
Long time no seeing. So I start up the new year with a first problem : the virtual driver cannot be installed. Reason : it is missing in the Fast Ring PatchBeam Update Service…
Virtual driver PA 2023-01-28 152607.png
It seems a standard problem with new releases :-)
Can I have a link or can it be fixed. Thank you. CU later -
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.
PowerArchiver creates @LongLink in Archives ?
-
Hi,
everytime i want to unpack a Backup Archiv of my Website (including Mambo CMS or PostNuke) with PowerArchive i get a error.
Example :
If there is a Link in the Archive that is very long PowerArchiver can´t handel and unpack the whole Archive. He stops and creats a File named @LongLink.
If i open it with a Editor i see in it
./postnuke/pnTemp/pnRender_compiled/Xanthia^SeaBreeze^eng^%%52^52C^52C3DF3D%%xanthiaadminmenu.htm.php
as Example.
How can that be ? With WinRAR it isn´t a Problem.
It can´t be a Problem of my Backuparchiv. It also happens with the original Archives like PostNuke-0.750.zip or the one from Mambo CMS.
-
PowerArchiver does not support TAR archives with longlinks, which is what does not work. Basically, @longlink is used to make TAR files with filename+pathname bigger than 100 characters.
We will introduce this in one of the future revisions of PowerArchiver, I hope.
regards,
-
This Error does not only appera at *.tar Archives. It apperas at *.zip and *.rar Archives too.
So i have to use WinRAR for such Archives ?? That has to be a Joke ! :(
-
I dont know what exactly are you reffering to, but longlinks only exist in TAR archives, they do not exist in RAR or ZIP archives. PowerArchiver will work perfectly fine with both zip and rar archives…
regards,
-
It can´t be a Problem of my Backuparchiv. It also happens with the original Archives like PostNuke-0.750.zip
I just downloaded PostNuke Phoenix 0.750 Gold (.zip) from
http://downloads.postnuke.com/pafiledb.php?action=category&id=45This was unzipped by PA 9.02.01 with no errors on Win98.
-
Again - ZIP does not make @LongLink files, only certain TAR utilities make them for the purpose of extending TAR path+filename lenght above 100 characters. Those files are actually included in the TAR file, so they exist there. PA currently does not support them and hence it does not read them (again in TAR files only).
Only reason for them existing in ZIP file would be that someone converted TAR file or compressed them as well as rest of the files…
-
My only question is : When will it support them ? All others do it (winzip, winrar etc.) … it´s so frustrating.
-
Hello ?
I payed Money for this Software - can the Support answer please ??
Every OpenSource Archiver can handle this and i didn´t see why the one i buyed can´t .
Hope my english isn´t to bad. If so - is anyone here that can speak german ?
-
Hello ?
I payed Money for this Software - can the Support answer please ??
Every OpenSource Archiver can handle this and i didn´t see why the one i buyed can´t .
Hope my english isn´t to bad. If so - is anyone here that can speak german ?
We already said it will be done in one of the future revisions - and also that it only happens with TAR archives, not zip archives.
You english is just fine… Hopefully we will be able to include it in 9.2 release!
-
Thank you for your Answer. :D
This sounds better :Hopefully we will be able to include it in 9.2 release!
as before :
We will introduce this in one of the future revisions of PowerArchiver, I hope.
;)
-
Well, it is pretty much the only “big” problem with PowerArchiver and is out of our hands so we will put it back into our hands and solve it - but it takes time…
thanks,
-
Yeah but only for understanding - can you describe me in simple Words why the free TUGZip and ZipGenius can handle it ?
-
Yeah but only for understanding - can you describe me in simple Words why the free TUGZip and ZipGenius can handle it ?
Because they use different TAR components that we dont use?
-
Any updates on a fix for this problem yet?
-
Yes, as we already announced few times ago, this bug will be fixed for 9.1. Version 9.1 will be avilable in the beginning of the next week.
