I hope that despite my poor control of English, you can understand me.
When compressing a file, by default the extension is included as part of the file name. for example, if the file is name.pdf, the compressed file will be name_pdf.zip.
Is there any way for the extensions not to be included in the compressed file name? As much as I have searched I don’t see such an option.
Thanks for your time
Hello, I used the support form to ask this a couple weeks ago but never received a response. Perhaps here would be better? Here’s the issue:
Powerarchiver 2019 was locking up testing a .7z file so I looked for and found a new version (note- new version didn’t fix this- I ended up using 7-Zip itself. Archive was large and contained a ton of files)
Upon installing it, I was prompted to register it or “continue unregistered” so I logged into the website and used the order recovery option to get my new codes for PA2021. However, after cutting and pasting my name and registration code, upon restart when I click on the help button it still shows as unregistered (it did not show the nag dialog again). I tried two different codes (see below). I also tried installing again using the link in the email but there was no difference. Where do I go from here? Thanks.
Update: After a couple weeks it still hasn’t negged me, but continues to show as unregistered in the (?) area- will this stop working altogether soon?
OS: Windows 10 Pro version 2004
File installed: first used PA 2019 to check for and install update, then used link in email which downloaded powarc200073.exe and installed that.
Codes used: first tried the toolbox/english code in first email, then tried the standard/international code in second email
I’m using Convert Archives on a local folder of .zip files, converting them to .lzh files, and I’m finding that perhaps 1 in 75 files is actually converting and outputting a file. Even then, the .lzh file is incomplete, missing most of the source files.
The progress bars completes OK, say 75/75 files, but only one .lzh file exists in the output folder.
It seems to be the same with different source and output folders on both local and USB disk - I can’t see a pattern.
The files extract and compress (to .lzh) without issue on their own.
Is there a log file I can check please, to see why PA does not like these files as part of the batch conversion?
Thanks very much, Rich.
I’m experiencing very slow extraction speed of multipart RAR files. For the first part the extraction is super fast but when PA reaches the part2.rar the extraction from there on gets super slow. PA needed for a 6,3 GB multipart archive 30 minutes to extract. I tested then with another program and it just took 70 seconds. I had this slow extraction speed with PA for quite a long time and I always thought that is maybe because of a high compression rate that the extraction would take longer. But it seems that only PA gets that slow.
I have lots of multipart archives that are 10+ GB and with PA it would be really time consuming. Is there any solution to this?
I have powerarchiver licenses for powerarchiver standard and toolbox (and also as a result for pro).
I can successfully register powerarchiver with my pro/toolbox codes, and it unlocks the majority of the content/features. However if I try and create a .pa style archive I get the registration popup saying I need PowerArchiver Pro (if I go to help/about I can verify I have the relevant version and it’s registered to me).
Powerarchiver 2021 20.00.73
Windows 10 Education 10.0.19042 Build 19042
When extracting gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz , Powerarchiver wrongly thinks some .exe files have a length of zero:
Once extracted:D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin>dir *.exe Volume in drive D is DATA Volume Serial Number is 0E12-BCA2 Directory of D:\Temp\Powerarchiver\gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf\bin 2020-11-20 07:10 PM 1,391,599 arm-none-linux-gnueabihf-addr2line.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ar.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-as.exe 2020-11-20 07:41 PM 3,030,119 arm-none-linux-gnueabihf-c++.exe 2020-11-20 07:10 PM 1,389,293 arm-none-linux-gnueabihf-c++filt.exe 2020-11-20 07:41 PM 3,027,513 arm-none-linux-gnueabihf-cpp.exe 2020-11-20 07:10 PM 4,040,503 arm-none-linux-gnueabihf-dwp.exe 2020-11-20 07:10 PM 391,769 arm-none-linux-gnueabihf-elfedit.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-g++.exe 2020-11-20 07:41 PM 3,026,926 arm-none-linux-gnueabihf-gcc-10.2.1.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ar.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-nm.exe 2020-11-20 07:41 PM 609,607 arm-none-linux-gnueabihf-gcc-ranlib.exe 2020-11-20 07:41 PM 0 arm-none-linux-gnueabihf-gcc.exe 2020-11-20 07:41 PM 2,165,533 arm-none-linux-gnueabihf-gcov-dump.exe 2020-11-20 07:41 PM 2,343,605 arm-none-linux-gnueabihf-gcov-tool.exe 2020-11-20 07:41 PM 2,450,233 arm-none-linux-gnueabihf-gcov.exe 2020-11-20 07:54 PM 9,605,899 arm-none-linux-gnueabihf-gdb.exe 2020-11-20 07:41 PM 3,028,997 arm-none-linux-gnueabihf-gfortran.exe 2020-11-20 07:10 PM 1,412,943 arm-none-linux-gnueabihf-gprof.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.bfd.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ld.gold.exe 2020-11-20 07:41 PM 25,546,567 arm-none-linux-gnueabihf-lto-dump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-nm.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objcopy.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-objdump.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-ranlib.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-readelf.exe 2020-11-20 07:10 PM 1,393,083 arm-none-linux-gnueabihf-size.exe 2020-11-20 07:10 PM 1,392,464 arm-none-linux-gnueabihf-strings.exe 2020-11-20 07:10 PM 0 arm-none-linux-gnueabihf-strip.exe 32 File(s) 67,465,867 bytes 0 Dir(s) 1,002,422,431,744 bytes free
When the same archive is being extracted from a git bash session (after having installed git 2.30.1 for Windows 64 bit version from git-scm.com), the .exe files are extracted as expected:xz -k -d gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz tar xf gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf.tar cd gcc-arm-10.2-2020.11-mingw-w64-i686-arm-none-linux-gnueabihf/bin ll *.exe -rwxr-xr-x 1 User 197121 1391599 Nov 20 19:10 arm-none-linux-gnueabihf-addr2line.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ar.exe* -rwxr-xr-x 2 User 197121 2028927 Nov 20 19:10 arm-none-linux-gnueabihf-as.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-c++.exe* -rwxr-xr-x 1 User 197121 1389293 Nov 20 19:10 arm-none-linux-gnueabihf-c++filt.exe* -rwxr-xr-x 1 User 197121 3027513 Nov 20 19:41 arm-none-linux-gnueabihf-cpp.exe* -rwxr-xr-x 1 User 197121 4040503 Nov 20 19:10 arm-none-linux-gnueabihf-dwp.exe* -rwxr-xr-x 1 User 197121 391769 Nov 20 19:10 arm-none-linux-gnueabihf-elfedit.exe* -rwxr-xr-x 2 User 197121 3030119 Nov 20 19:41 arm-none-linux-gnueabihf-g++.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-10.2.1.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ar.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-nm.exe* -rwxr-xr-x 1 User 197121 609607 Nov 20 19:41 arm-none-linux-gnueabihf-gcc-ranlib.exe* -rwxr-xr-x 2 User 197121 3026926 Nov 20 19:41 arm-none-linux-gnueabihf-gcc.exe* -rwxr-xr-x 1 User 197121 2165533 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-dump.exe* -rwxr-xr-x 1 User 197121 2343605 Nov 20 19:41 arm-none-linux-gnueabihf-gcov-tool.exe* -rwxr-xr-x 1 User 197121 2450233 Nov 20 19:41 arm-none-linux-gnueabihf-gcov.exe* -rwxr-xr-x 1 User 197121 9605899 Nov 20 19:54 arm-none-linux-gnueabihf-gdb.exe* -rwxr-xr-x 1 User 197121 3028997 Nov 20 19:41 arm-none-linux-gnueabihf-gfortran.exe* -rwxr-xr-x 1 User 197121 1412943 Nov 20 19:10 arm-none-linux-gnueabihf-gprof.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.bfd.exe* -rwxr-xr-x 4 User 197121 2572182 Nov 20 19:10 arm-none-linux-gnueabihf-ld.exe* -rwxr-xr-x 2 User 197121 4550029 Nov 20 19:10 arm-none-linux-gnueabihf-ld.gold.exe* -rwxr-xr-x 1 User 197121 25546567 Nov 20 19:41 arm-none-linux-gnueabihf-lto-dump.exe* -rwxr-xr-x 2 User 197121 1404945 Nov 20 19:10 arm-none-linux-gnueabihf-nm.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-objcopy.exe* -rwxr-xr-x 2 User 197121 1991350 Nov 20 19:10 arm-none-linux-gnueabihf-objdump.exe* -rwxr-xr-x 2 User 197121 1421598 Nov 20 19:10 arm-none-linux-gnueabihf-ranlib.exe* -rwxr-xr-x 2 User 197121 1163376 Nov 20 19:10 arm-none-linux-gnueabihf-readelf.exe* -rwxr-xr-x 1 User 197121 1393083 Nov 20 19:10 arm-none-linux-gnueabihf-size.exe* -rwxr-xr-x 1 User 197121 1392464 Nov 20 19:10 arm-none-linux-gnueabihf-strings.exe* -rwxr-xr-x 2 User 197121 1531656 Nov 20 19:10 arm-none-linux-gnueabihf-strip.exe*
The same archive file does extract properly under a native Linux Ubuntu 20.04 system, or under Windows 10 using the WSL2 Linux subsystem using xz and tar.
I just saw, that on the Website, PowerArchiver 2021 20.00.73 is advertised as latest version. (Actually, the downloaded version says, it’s 20.00.70 in the about dialog)
But it still comes with the “red icon set” for preview versions and has some known unfixed bugs, as I read here.
Is it sufficiently stable to be used on production systems?
Hi I recently bought PowerArchiver and found some bugs and issues that I hit testing some of the features out.
If you are doing a backup and on the compression options screen its default is compression format is PA with no option to change disk spanning. If you change to 7-zip you can change disk spanning. If you change the disk spanning then move back to PA format the field for disk spanning disables but the option stays set to what you changed it to. When you do a backup it will use PA with files spanning but PowerArchiver says that its not a valid format when you open it. If PA can’t really do file spanning then this screen is allowing it.
I have attached an image where the progress bar is in the middle of the CD/DVD/BD Tools screen.
I have a 7-Zip file I created using the backup tools doing an increment backup. It opens and extracts just fine but if you using the Test option PowerArchiver locks up. Link to file: Backup-2021-02-05-20-35-36 TEST LOCKUP.7z
On any Zip/PA/7-Zip process the pause and cancel buttons do not work. You have to hard kill the entire application to get out.
There would be many of us with Intel Processors.
and they have their own optimized zlib algorithm, which can result in more efficiency if used combined with their hardware processor.
Can we get the same Functionality Under Hardware Acceleration Feature?
Zlib is not the only feature that intel has included with their processor, there’s many, which if combined can result in efficient and better compression ratios.
After the batch archiving is complete, and if I click on whitespace of the PA app, I get this error.
I did check for ongoing process and ensured no archives were corrupt, It seems like activity did complete successfully but the error is shown for no reason, and only after clicking the whitespace.
Please see if this can be removed.
I’m using the Kaspersky Total Security.
I have configured PA as exclusion as followed:
and also is set us trusted application
PA Trusted Application.png
My Antivirus likes to scan for everything, and it’s safeguarding behavior is to prevent the access to the file until the file is properly scanned for.
PA when losses the access to file, it is stuck, consumes Resources, and never completes the process or throws any error
PAStarter should also work as PAMonitor:
There should be a monitoring process, at least if I’m using queuing feature, that should check for never ending compression processes and terminate them so the queue can be little bit automated.
There should be multiple attempts at retrying if PA loses access to or is denied, instead of having to see process was stuck for longer duration.
Or, better, save the parameters I used for keeping the files in compression, and automatically restart the whole compression process after termination the same, of same folders and files set, this should happen in case if compression was stuck.
If you use Queue Feature, you are not saving on space, you are just squeezing less.
I did test the same on multiple files, and of different types.
It does have large difference for each large file you are trying to squeeze.
Folders with multiple files, just have no benefits if you use Queue Feature
I am using the portable version of PA2021. After switching from build 58 to 73 I have problems with the color-scheme:
While 58 behaves like expected and showed everything in light or dark colors according to the settings, 73 always shows the lower part of the window in dark colors, no matter whether I select automatic, light or dark.
This happens on a clean installation of 73 as well as on an update from build 58. I have attached two images generated on the same machine at the same time with the same settings. The upper shows build 73, the lower 58. Is it a bug or some changed setting I miss?
Thanks for help!
I currently own the PowerArchiver Select - lifetime free upgrades and support for PowerArchiver Toolbox English license.
This license is active on 1 device. Does the license allow me to activate PowerArchiver on a second device that I own? Or do I need a separate license for that?
Thank you ! :)
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.
Thanks for the great program- this is really the only issue I have with it (and it worked fine in PA2009).
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.
Oops, I am actually using RC2. I will try RC3 to see if the issue is solved.
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.
did you try unchecking “use oem…” ? Any difference.
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.
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 settings
In 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.
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!
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:
see if that works properly.
I have tested RC3 too, and seems like it works fine - please let us know when you have an chance. thanks!