-
Converting an archive to .zip (using both the “Deflate (.zip, compatible)” and “Store” compression methods) always creates a .zipx file instead.
pa-convert-zip-1.jpg
pa-convert-zip-2.jpgUsing the “Store” method sometimes creates a .zip file; I have seen it happen just now, but I cannot reproduce it.
-
Good morning,
I have been using all compression programs for over 20 years, I have always found Winrar very easy to use when I create a self-extracting archive, even 7-zip is simple, “right click” and “create self-extracting archive”, because on powerarchiver it must be like this confused ?
It doesn’t just create the archive, it opens a page where I have to select the file again, what kind of archive, which folder to create it, etc … you should learn from your competitors how to make life easier! -
Hi,
So refer this screenshot:
image_2020-12-30_115129.png
The properties panel that you see, is what I tried to compress, using PA, with following settigs:
Extreme Strong optimize
https://forums.powerarchiver.com/assets/uploads/files/1609079025475-image_2020-12-27_195344.pngThe process was stuck at 0% with no progress for over 8 Hours:
PA.png
Then the usual, clicking will make it go not responding.
So, I could not get the files compressed using PA.
I tried 7zip, and it worked, so that’s 1 issue.
PA shows incorrect original(before compression) size of total contents.
Refer the first screenshot.
folder’s size is shown correctly in 7ZIP
but not in powerarc.this happens with every archive, whether they are compressed in PA or not, whether it has only 1 file, or multiple files inside multiple directory.
Neither does the archive property panel shows original content’s size.
-
Hi,
So my rig is as below:
CPU: Intel® Core™ i7-4720HQ CPU @ 2.60GHz (Turbo 3.7GHz)
RAM: 16 Gigs DDR3
Samsung SSD 860 EVO
Windows 10 pro for workstations x64, freshly installed on 22nd Dec 2020, and updated.
PA freshly downloaded on same day, so it’s 2021 x.x.62 versionPA Stuck.png
Issue and reproduction:
If you start a compression, and if it’s mid way anywhere or even started, and you try to cancel it, the window will get stuck there, another click or key press will make the window not responding, then, and more will make windows to collect logs for crash, and the process will be terminated by windowsOn the other hand.
If the process is mid way, and if you try to pause it, the compression, CPU utilization, RAM usage will stay/increase as if the compression if still going on, the whole process will take it’s course, instead of doing what we clicked on.
So, both pause and cancel buttons are useless.
-
I recently installed PA 2021. But the PowerArchiver Starter, for my backups, keeps running at high CPU usage, I have to keep killing it, its running about 46% constantly.
I have Windows 10 Pro, 20H2, build 19042.662
Any ideas would be helpful.
Thanks
-
Just installed 2021 v20.00.63
Now, when I add to queue, with or without using always use queue.
The powerarc starter opens up in notification bar.
and that’s it, no matter how many files I add to queue, no compression will start.
I also cannot double click or right click the icon.
If i end task for this, and disable queuing, compression works fine, just that I have to manually start individual tasks.
it’s quite ironic that you guys took whole year to fix one issue, in this versions, which completely broke the queuing feature.
Did you guys test it before releasing?
-
Hi,
You can obtain the original file from here:
https://pcsupport.lenovo.com/in/en/products/laptops-and-netbooks/lenovo-y-series-laptops/y50-70-notebook-lenovo/80ej/59428436/cb32343883/downloads/driver-list/component?name=Power%20Management
For Lenovo Y50-70 win 7 x64 bit, power management, get lenovo energy management
Run the exe it will extract the installable drivers to C:\drivers
I tried to compress the whole folder using PA using following parameters:
Extreme, strong optimize.
image_2020-12-27_195344.pngThis resulted in negative compression.
However same file is compressed by 7zip alpha, with positive compression:
PA Negative compression.png
I understand that there are different algorithms, parameters used, and totally different software with unique sets of logics programmed, but see if compression algo can be optimized for such files.
-
Over the last few months, I’ve been trying to track down the cause of a hanging bug in PA.
I have found a reliable test case (on my computer at least).I am trying to extract the folders/files from: https://github.com/codereader/DarkRadiant/releases/download/2.9.0/windeps.7z
By selecting both folders, then dragging over to a Windows Explorer window on another HDD.
I’m not sure what causes this but this just doesn’t do anything, progress bar appears, but nothing happens.
PA shows about 5% CPU utilization and I’ve left this going all night and it never does anything.
It doesn’t always happen, but this morning this is reliably failing for me.
The folder I’m dragging to is under Git source control, but this also happens when dragging into other folders also, but not always, sometimes it works.If I do a regular extraction and use the dialog box to select the location to extract to, that always works.
Windows 10 64bit Pro 20H2 (19042.630)
Ryzen 3900X
Anti Virus is built in Windows Security only.I captured a dump of the running process if that helps: https://drive.google.com/file/d/1WLzHG_fOAMtzGMMFLHlIElnQXhsoPyYd/view?usp=sharing
-
I have just installed 2021, but seems to have similar issues to 2019. If you move the app between differen monitors (with different resolutions) the app does not automatically adjust accordingly, so on one monitor I have the app is too big for the screen, whereas on another monitor it only takes up a small fraction of the screen.
This was worse with 2019, where the fonts were totally screwed up, making the app unusable. This seems better in 2021, but still not working properly. -
Hi.
I have noticed after updating PowerArchiver through PatchBeam to 20.00.63, after the installer finished and I recheck for updates, it still tells me that I have version 20.00.62 installed and prompts to download 20.00.63 again.
This also happens when I install from the offline setup file powarc200063.exe ( https://powerarchiverdl.cachefly.net/2021/powarc200063.exe ). It still installs version 20.00.62 and the process goes over and over again.
Also, in PowerArchiver About screen I see version 20.00.62 but in Programs and Features in Windows 10, version 20.00.63 is displayed as being installed.
Can someone check and see if they experience similar behavior?
Thank you!
-
When I double click on a file within an archive the file gets temporarily extracted to being opened with the external program. When I now go back to the windows explorer and want to open another archive while the file from the first archive is still being extraceted, a new window of power archiver opens and immediatly closes. It opens and closes the new window repeatedly until the extraction of the file from the first archive is completed.
I use the option that power archiver opens a new tab when another archive is opened.
This happend with version 20.00.60. I wanted to update it to 20.00.63 as shown in the update window but it just updates to 20.00.62. It still shows that 20.00.63 is available but never seem to update to that version. The bug still exists though.
-
I have some large zip files (~ 40 MB) with a lot of html files. When I double click on one of them in the archive, it takes a long time (eg 20 sec) for the file to be extracted and opened in the browser.
I am using version 19.00.59.
I discovered that the root cause of the problem is that all the files in the archive are extracted to the temporary dir before the selected file is launched.
It does not appear to happen with other file types (such as pdf) nor when dragging a html file into the browser.
I think I recall this issue being raised by someone else, but could not find it.
-
On PowerArchiver 2021 (20.00.60) and windows 10, Both options in the windows explorer shell extension, “Compress to …zip” and “Compress to …zipx” create a .zipx file. ¿Its this intended?
-
My slow ring still reads as 19.00.59… will it ever offer an update to 2021 or is that something I must do manually?
-
Hello there,
I was installing-uninstalling and reinstalling PA 2021 due to another bug when I noticed a minor popup “bug” if it is considered a bug, regarding application association with recommended formats.
During PA installation you get to choose those options
Installation 1.pngI have ticked Associate PA with recommended formats
Installation completes and when you open PA the defult theme is Windows Ribbon.
When I changed it to Classic Theme, PA restarts for changes to take effect and then I get the below popup (Sorry I have a greek system)
It asks: Do you want PA to associate with recommended formats now?
Options: Associate for all users and Never show again.
Popup 2.pngI could swear that once I was changing themes and icons all the time to see which one I prefered and also toggling PA.exe to run as admin and windows compatibility mode and got this popup twice or tripple times.
Well this one does not bother me at all, I just posted it for the records if needed! -
If I the Configuration > View > Standard > Disable Tabs option is checked, when double clicking inside archives on files supported by the internal viewer (PDF, JPEG etc.) they are opened in associated application rather than on a new tab in PA internal viewer, which is expected behavior.
Next, if the Configuration > Miscellaneous > General > Reuse PA Windows is unchecked, when double clicking on archives associated with PA in Explorer they are opened in new PA instance when there is another one already running, which is expected behavior.
But when Configuration > View > Standard > Disable Tabs option is checked AND Configuration > Miscellaneous > General > Reuse PA Windows is unchecked, when double clicking inside archives on archive files they are opened in the same instance of PA with no way to get back to the parent archive. I would expect, that when the user doesn’t want to use tabs AND want to use multiple PA instances, that in such case double clicking on archive located inside another archive, the second one would open in a new PA window. -
I’ve made the sections of the output bold to indicate where the typo is.
Version 7 output
Commands:a : add files to archive (default)
u : update files to archive
h : freshen files in archive
m : move files to archive (files only)
d : delete files from archiver : recurse subfolders
Version 9 output…
p|P : store relative Pathnames|store full Pathnames
PP : store full Pathnames including drive
c[0,1,2,10,11,13,15,17,19,l,p,w,b,d,z] : set compression level
(0 - store; 1 - normal ; 2 - maximal)
(10 - store, 11 - super fast, 13 - fast, 15 - normal, 17 - max, 19 - ultra
(l - use LZMA, p - use PPMd, w - use WavPack, b - use BZIP2, d - use Deflate
(z - use optimized compression method based on file exstension)
g : create Solid archive (7Z format only)
Commands:a : add files to archive (default)
u : update files to archive
h : freshen files in archive
m : move files to archive (files only)
d : delete files from archiver : recurse subfolders
P : store full Pathnames
PP : store full Pathnames including drive
p : store relative Pathnames
c[0,1,2,10,11,12,13,14,15,16,17,18,19,u,l,p,w,b,d,z] : set compression level
(0 - store; 1 - normal ; 2 - maximal)
(10 - store, 11 - super fast, 13 - fast, 15 - normal, 17 - max, 19 - ultra
(l - use LZMA, p - use PPMd, w - use WavPack, b - use BZIP2, d - use Deflate
(o - use LZMA2
(u - use pLZMA4, f - use ZSTD, k - use PPMd_sh, e - use Deflate64
(z - use optimized strong compression method based on file exstension)
(x - use optimized fast compression method based on file exstension)
(m<filters|methods> - use custom set of filters and methods for .PA archive
y[r|b|d|x|p|d] - filters reflate, bcj2, x64flt, rep, delta
ypc<size> - custom rep c size
ypm<size> - custom rep mem size
yrx<size> - custom reflate zlib level (1-9)
yt{x} - number of threads
ya - debug mode
mt : set multithreading on
g : create Solid archive (7Z format only) -
I’ve found a bug when extracting files from a 7ZIP file, specifically when you tell PowerArchiver to extract only some files and folders from it. This is where the bug exists. You can tell PowerArchiver to extract only certain files but then it proceeds to extract the whole file and not just what you wanted.
-
Sorry if I’m asking this in the wrong place.
Can Powerarchiver create images of entire drives (e.g. C: system drive) to create drive image backups?
Thanks,
Tim
Rar file extracting ISO at 100% ISO
-
When extracting a ISO normaly you see the iso file while it is extracting and at the end just click it but mine just disappears after extraction no warning.
-
Sorry, but I have no idea what your problem is.
Can you give a “step by step” description of what you are doing - trying to do?A link to the rar/iso file would also help.
Also, which version of PA and which OS would be useful.
-
Windows Xp SP1 the problem is simple really when it extracts from the rar file the ISO disappears at 100% so i get no extracted file i have used current BETA’s and old versions the same thing.
-
Does it happen on all rar files or just one?
-
Does it happen on all rar files or just one?
All files over 1gb which is strange because i have 20gb free.
-
Over 1GB is a strange size limitation - and not easy to find for doing quick tests.
(2GB would make more sense - e.g. 16 bit limitations).Do you mean that you have a single rar archive (not split) which is over 1GB containing a single ISO file?
Or is the ISO file itself over 1GB ?Is the problem only with ISO files inside RAR…
or any RAR archive which is over 1GB…
or only when RAR archive contains a file which is over 1GB?Do you know how the RAR was created (which version of RAR)?
Exactly how are you trying to extract it in PA 9.5 beta 7?
-
Confirmed. I created a file FILE.ZIP using b7 and it was 1.2Gb, and then I try to extract it using b7, it extracted the content to… nowhere humm. The extacted folder and content is not to be found :)
-
@yop:
Confirmed. I created a file FILE.ZIP using b7 and it was 1.2Gb, and then I try to extract it using b7, it extracted the content to… nowhere humm. The extacted folder and content is not to be found :)
Sorry, NOT confirmed here. :confused:
I tried with a Zip of a DVD - zip filesize 4.04 GB (4,345,357,872 bytes)
Then tried a zip containing two movie files - zip filesize 1.66 GB (1,784,405,346 bytes)
Then tried a ZIP file of 980MB.All extracted with no problems in PA 9.5 beta 7.
Note: there was a “known” problem with PA not showing error message on insufficient disk space when using ZIP format, but this was fixed in PA 9.5 beta 7.
However, Atonement said he has 20 GB free (and is using RAR anyway) :confused: -
I created a zip file (1.5GB-named test.zip) using Beta 7. I was able to unzip without any problems. I also tested the archive and it tested fine. I created 758MB (330files) archive and it also checked out fine.
-
All files over 1gb which is strange because i have 20gb free.
I do not have a 1GB iso file. However I do have one 340MB iso.
So I made copies.4 iso files -> RAR 1.29 GB (1,386,471,671 bytes)
“Extract to folder” via shell (using PA 9.5 beta 7)
No problems encountered.My drive C: only has 1.5 GB free but my “working” drive D: has 20GB free - (Note: I activated PA “use current folder as temp” to avoid possible free disk space problem on Drive C:).
-
The problem was extracted it was 4gb and i was on my fat32 formated drive so i just converted back to NTSF( something like that)
-
OK
Thanks for coming back and telling us. -
Explains why we couldn’t reproduce it. :)
-
But there’s still a bug here - an error message should be displayed.
-
But there’s still a bug here - an error message should be displayed.
Yes, but the problem is that Windows cannot handle files of this size.
So the error message should be from Windows - not PowerArchiver. -
I’m not 100% sure, but I believe that what happens is that when a program tries to write past the 4GB file limit on a FAT32 partition the API returns an ERROR_DISK_FULL result to the calling program.
This often leads to a confusing error message (since there can be more than 4GB available on the partition), so PA may want to present it as “The disk is full or the file is too large for the destination file system.” Or something.
But in any case, it should not fail silently.
(edited)
-
We will check it out later on, thanks for clarification, although in reality move to NTFS people!!!
:-)
