-
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.
-
-
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.
Not extracting ZIP file
-
Powerarchiver 9.00.32
I opened a ZIP file in FireFox 0.9.2 ( http://www.hydrairc.com/download.php?directory=files&file=HydraIRC.zip ), Powerarchiver was automatically run. Then I closed FireFox and tried to extract the files to a directory. Nothing happened. The extract dialog disappeared after clicking the “Extract” button. No files were created. No error report ( as we are used from PA, aren’t we ? )
I deleted PA v8.8 last month, but I decided to give another chance to v9.
I blew it… -
Well, I downloaded that file to hard disk - not opening directly from browser.
Then opened in PA and extracted to a subdirectory OK.
Current version of PA on the download page is 9.00.33
Or, if you come to the forums get a test 9.00.34 here (which I’m using):
http://www.powerarchiver.com/forums/showthread.php?t=108 -
this problem is not powerarchiver but a browser problem.
When you clicked the file link with your browser it opened powerarchiver, however when you closed your browser it must have disconected your link and thats why it did not extract.You actually did not download the file otherwise it would have worked
-
Yes, I did download the file. You know, browsers (including FireFox) first download files and then start the program to handle it, not the other way around.
-
Nevertheless, never open files directly from Internet, always save them to your hard drive and then open it. What Firefox did is probably delete the file from its cache when you closed it and then Powerarchiver was not able to extract anything since the file isnt there.
In fact, Internet Explorer wouldnt even let you open the file properly at all.
I agree that PowerArchiver should tell you that the file actually isnt there, we simply didnt take in account that the file might be deleted between the time you open it and the time you extract the file. However - actual file being deleted is not an PA bug but most likely the way your browser handles the files. Since this is the case with most browsers, I definetly reccomend that you should always save the file to the hard drive first.
thanks,
-
The bug is, that the user request something ( Extraction, in this case ) from PA, and PA does not do it, and it doesn’t even bother to tell it to the user ( sorry, that failed ).
And this happens all the time. I guess you took some programming shortcuts, eh ?
-
The bug is, that the user request something ( Extraction, in this case ) from PA, and PA does not do it, and it doesn’t even bother to tell it to the user ( sorry, that failed ).
And this happens all the time. I guess you took some programming shortcuts, eh ?
Didnt I say that PA should have shown an error msg? Yet the fact remains that your file got deleted which is why it couldnt be extracted from - because the file was deleted by your browser not PowerArchiver.
So in the future, save your files directly to the hard drive.
thanks,
-
The bug is, that the user request something ( Extraction, in this case ) from PA, and PA does not do it, and it doesn’t even bother to tell it to the user ( sorry, that failed ).
But that is not the “bug” you reported! The title of your post was
“Not extracting ZIP file”When the Zip file does not exist - not extracting from it can hardly be seen as a bug!
Spwolf:
Related to the error message(s):
If you open an archive in PA - then delete the file via Windows Explorer - then activate TEST in PA you get this message:#####################################################
Testing archive: Testing.zip – 05/08/2004 09:51
#####################################################File not exist!
#####################################################Should be: File does not exist!
:p -
Small spelling mistake will be fixed in next release!
-