-
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.
Problems with unicode zip in PA 2010 RC
-
I am using Power Archiver 2010 RC3 and I have a problem displaying Unicode for zip files. 7z and Rar files seem to be okay. I am using Windows 7 RC.
I have attached several zip files to show what I am talking about:
Test1_(7-zip).zip - [i]A zip file compressed by 7-Zip[/i] Test1_(PA).zip - [i]A zip file compressed by Power Archiver[/i] Test1_(PA).7z - [i]A 7z file compressed by Power Archiver[/i] Test2_(7-zip).zip - [i]A zip file compressed by 7-Zip[/i] Test2_(PA).7z - [i]A 7z file compressed by Power Archiver[/i]I have also posted screenshots of what Power Archiver displays when it opens and extracts the said files.
http://www.picamatic.com/view/3985786_Test_1_Results/
http://www.picamatic.com/view/3985787_Test_2_Results/Thanks for the great program- this is really the only issue I have with it (and it worked fine in PA2009).
attachment_t_3858_0_test1_-7-zip.zip
attachment_t_3858_1_test1_-pa.7z
attachment_t_3858_2_test1_-pa.zip
attachment_t_3858_3_test2_-7-zip.zip
attachment_t_3858_4_test2_-pa.7z -
One more thing - I want to add the original folders and the extracted files (extracted by Power Archiver) to give you a clearer picture.
They are inside a .7z file, so the Unicode (and corrupted Unicode) should stay intact.
Edit:
Oops, I am actually using RC2. I will try RC3 to see if the issue is solved.Edit2:
No, the results are still the same.In addition, checking or unchecking “Use OEM” and “Force Unicode in Zip” or any combination of the two does not seem to make a difference for the specified files.
attachment_p_18973_0_test_folders_and_extracted_folders.7z -
did you try unchecking “use oem…” ? Any difference.
two things:
1. excellent report :).
2. always open new threads as it is easier for us to track problems.thanks a lot!
-
No, nothing in the configuration menu was able to fix my problem. I will check 2010 RC2 on Windows XP to see if it works, since I am certain 2009 works on XP.
-
OK I’m back. I did a few tests.
First I changed my regional setting back to US from Japanese in Windows 7. I was able to archive and extract unicode files perfectly. However, when I tried to display or extract the zip file I had created earlier (while in Japanese regional setting), I was unable to. Even with 7-Zip, the unicode was corrupted.
(See Comparisons)I have uploaded two zip files: [u]Test1 (7-zip) JP.zip[/u] - Archived while in Japanese regional settings (in regional settings in Windows 7 control panel) [u]Test1 (7-zip) US.zip[/u] - Archived in US settingsIn XP, extracting “Test1 (7-zip) JP.zip” with PA2010 gave unusual results where the file extensions were corrupted, while the names retained some unicode (see pic). I was able to extract “Test1 (7-zip) US.zip” perfectly fine.
I uninstalled 2010 and installed PA2009 (11.03).
While in Japanese regional setting on XP, I was able to display/extract unicode files with PA2009. “Test1 (7-zip) JP” extracted and the unicode filenames were correct. “Test1 (7-zip) US” extracted but the unicode filenames were converted to Japanese letters (checking/unchecking “OEM conversion” did not make a difference). PA2009 could not display any unicode (See pic)
Extracting a unicode directory (“Test2 (PA) JP XP.zip”) resulted in an error (see pic).
–------
What I get from this is that if you both compress and extract archives while in US regional settings, you will be fine. However, if you download files from other parts of the world, unicode may not display correctly. With PA2009, most unicode did display correctly in any circumstances. There are only problems if it can’t read the directory.
attachment_p_18976_0_test1-7-zip-jp.zip
attachment_p_18976_1_test1-7-zip-us.zip
attachment_p_18976_2_test2-pa-jp-xp.zip -
I believe problem is that it is not saving them in Unicode at all :).
You see PA tries to determine when to use ANSI and when to use Unicode - it tries to use ANSI when possible because Unicode is not supported in most archivers, and Unicode when ANSI is not possible.
It seems that something is wrong there - devs will take an look… thanks a lot! Perfect timing too!
-
Hello,
Thanks for the detailed info.
First of all I am using USA as my regional setting.
I am sure some of issues from first post were solved in RC3 because we were working on it.Test1 (7zip).zip was definetelly created wronly by 7ZIP (other utilities show same errors or wrong filenames).
test1 (PA).zip has wrong characters but I was able to create it using right click on Test1 folder and choosing “Compress to test1.zip” correct file.
Test2 all procedures - including creating a test2.zip from shell using PA (Compress to test2.zip) worked fine.
So all issues should work fine. test1 created with 7z is wrong in any way.
Can you try creating some archives using those files from main interface - not shell extensions?
-
Please check this release:
http://www.powerarchiver.com/test/alpha115/powarc1150rc3.exesee if that works properly.
thanks!
-
I have tested RC3 too, and seems like it works fine - please let us know when you have an chance. thanks!
