-
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
PA 11.xx and 12.xx crashes Nero Burning ROM
-
I have had a problem for some time now with PA 2010 (any version of 11.xx) and 2011 (any version of 12.xx) where Nero Burning ROM 10 and 11 crash if I have “Use Explorer Shell Extensions” checked in either PA 2010 or PA 2011. If I uncheck this option in PA 2010 or PA 2011 then Nero doesn’t crash. The crash usually occurs when I drag and drop from the source window pane in Nero to the destination window in Nero. Sometimes Nero crashes after I choose DVD boot ROM and then click on the “New” button in Nero to continue. The error message that pops up says “Nero Burning ROM has stopped working…, check for online solution or close the program”.
I have tried and verified this on two different computers using two different operating systems (XP and Win7 x64) and I get the same results. I have also re-imaged my hard drive and installed a minimal system of XP SP3 and then Win7 SP1 x64 to eliminate any other possible programs influencing this crash and even with either OS installed with only the MS updates I still get the crash in Nero 10 and 11 when I use either PA 2010 or PA 2011 without unchecking " Use Explorer Shell Extensions".
However, if I use PA 10.22 then both versions of Nero (10 and 11) work fine. But any version of PA 11.xx or PA 12.xx cause Nero 10 and 11 to crash if I don’t uncheck “Use Explorer Shell Extensions”.
Anyone have any ideas on how to fix this? Thanks
-
According to a posting on Nero forums, there is a problem with “shell extensions” (from various utilites)
http://forum.my.nero.com/index.php?showtopic=12061@Nero:
In some cases, if Nero BurningROM crashes while using the file browser, the crash may be caused by installed shell extensions from 3rd parties.
Just try to add files from your Windows Explorer to thecompilation instead of using the Nero File Browser. If this works then most likely such an extension is causing the problem.If that works, then you have a workaround whilst the actual problem is investigated.
if I use PA 10.22 then both versions of Nero (10 and 11) work fine.
That is interesting and may provide PA support with some clues.
Kudos for doing all that checking/testing by the way :cool:
-
According to a posting on Nero forums, there is a problem with “shell extensions” (from various utilites)
http://forum.my.nero.com/index.php?showtopic=12061Quote:
Originally Posted by Nero
In some cases, if Nero Burning ROM crashes while using the file browser, the crash may be caused by installed shell extensions from 3rd parties.
Just try to add files from your Windows Explorer to the compilation instead of using the Nero File Browser. If this works then most likely such an extension is causing the problem.If that works, then you have a workaround whilst the actual problem is investigated.
Quote:
Originally Posted by peeco
if I use PA 10.22 then both versions of Nero (10 and 11) work fine.
That is interesting and may provide PA support with some clues.Thanks for getting back to me so quickly!
I just tried using the Windows Explorer instead of the Nero File Explorer and I was able to drag and drop. However, there are times when Nero will crash even before I get to the Nero File Browser. Occasionally it crashes when I just select DVD Boot and select “New”. Selecting “New” should bring me to the Nero File Browser but It crashes as soon as I click on the “New” Button. I realize that this still doesn’t rule out third party extension problems. But….
A short time ago I installed Windows 7 SP1 fresh from my ISO. After the installation I just installed Nero Burning ROM 10 and then PA 2011. I didn’t install any other programs, nor did I install any drivers or any MS Updates. So the Windows 7 SP1 installation consisted of Windows 7 SP1 x64, Nero 10 and PA 2011 and nothing else. And when I ran Nero it did crash often. I think should rule out any installed shell extensions from third parties being the potential culprit since there where none installed. ;)
Kudos for doing all that checking/testing by the way
:cool:You’re welcome.
I can easily re-image my system for Windows 7 SP1 x86 or x64 and also for XP x86 (no vista…yuck!). So if you want me to try a particular OS installation for you then let me know what you would like installed and tested and I will do my best. I have Nero 6, 7, 8, 9, 10 and 11 and PA 10.22, 11.xx, 12.xx. BTW, Nero 6 works fine with PA 2010 and PA 2012 (never crashes). I haven’t tried Nero 7, 8 or 9. Also, the Free version of PA (PowerArchiver 2010 Free 11.63.12) also crashes Nero 10 and 11.
FYI, I just tried the new PA 2012 beta 1 this afternoon and it also crashed Nero 10 if I have “Use Explorer Shell Extensions” checked.
Hope this information helps. :)
-
If it’s a problem between PowerArchiver shell extensions and Nero, I would expect it to happen with 2012 beta as well, but the clarification is good.
Just to clarify - PowerArchiver would be one of those “3rd parties” that does install shell extensions.
I wasn’t implying that there was yet another utility involved.
Also, I’m not saying that PowerArchiver is at fault here. It could be a problem in Nero that is “found” by ANY utility using “particular” shell extensions - that’s implied by the post from their forum.At least you have two (clumsy) workarounds -
a) use Win file explorer with Nero
b) disable PA shell extensionsUntil a solution is found.
Now it’s up to the PA devs to investigate further.
(look for responses from spwolf, mili or ivan).
The rest of us are customers like you. -
Thanks Terry, I will be watching.
-
Top Notch Feedback Peeco!
Terry’s on the ball as always :) -
Thanks Terry, I will be watching.
please check with pa 2012 beta 3 and lets see what happens. thanks!
-
please check with pa 2012 beta 3 and lets see what happens. thanks!
spwolf, I tested pa 2012 beta 3 with Nero 10 and Nero 11. In Nero 10, before I updated it with the latest updates, I was able to create a new compilation and drag and drop files and folders using the Nero file browser much better than with pa 11 and pa 12. Nero 10 still eventually crashed but it was after I opened and dragged numerous files and folders into the new compilation. With pa 11.xx and 12.xx often Nero 10 would crash upon opening Nero 10 and if Nero 10 did open then it would crash after opening just a couple of folders in the Nero file browser.
Now, here comes the interesting part. When I updated Nero 10 to the latest updates then it crashed more frequently. In the numerous times that I opened Nero 10 before the update it never crashed like it does with pa 11.xx and pa 12.xx. However, after the Nero 10 update Nero crashes about one out of every 3 or 4 times you open it. I don’t know if it will help, but my version of Nero 10 before the update is: 10.6.10600, and after the update is: 10.6.10700.
I then uninstalled Nero 10 and installed Nero 11 and Nero 11 crashed about as frequently with pa 2012 beta 3 as it does with pa 11.xx and pa 12.xx.
Once again, when I uncheck “Use Explorer Shell Extensions” in pa 2012 beta 3 Nero 10 and 11 work fine (no crashes).
Hope the information helps.
-
This issue has been logged in for a bit now.
I’ve reproduced the issue as you’ve mentioned it using Nero11 and PA 2012 Beta 3 and have added it to the logged in report. It will definitely help in locating the problem.Thanks for taking the time to let us know!
-
Please check this version and let us know if it fixes your issue:
http://dl.powerarchiver.com/2012/powarc1300rc1.exethanks!
-
Please check this version and let us know if it fixes your issue:
http://dl.powerarchiver.com/2012/powarc1300rc1.exethanks!
Success! I have run three separate compilations using Nero 11 and pa 13 rc1 and I tried my best to get Nero to crash but I could not. So, at this point it seems that rc1 has solved the Nero 11 crash issue when using the Nero file browser.
I have not tried Nero 10 yet with pa 13 rc1 but I will by Monday. I will let you know of the results.
If for some reason Nero 10 or 11 crashes in the future then I will let you know.
A BIG thanks for fixing this! Much appreciated. :D
-
cool… btw, Nero 11 install has to be the worst thing i have experienced in quite an while :-)
-
cool… btw, Nero 11 install has to be the worst thing i have experienced in quite an while :-)
I actually use Nero 10 but I installed the Nero 11 trial version to test pa. I have heard that Nero 11 installation has not been a pleasant experience for some. Nero 10 isn’t much better. I haven’t upgraded since I see no reason to. It seems that Nero is getting worse and worse while pa keeps getting better! :D
BTW, I just installed Nero 10 and updated it and went through some simulated compilations to see if I could get it to crash and I couldn’t. So, it appears that Nero 10 works well with pa 13 rc1 as does Nero 11.
Good job to all! :)
-
I actually use Nero 10 but I installed the Nero 11 trial version to test pa. I have heard that Nero 11 installation has not been a pleasant experience for some. Nero 10 isn’t much better. I haven’t upgraded since I see no reason to. It seems that Nero is getting worse and worse while pa keeps getting better! :D
BTW, I just installed Nero 10 and updated it and went through some simulated compilations to see if I could get it to crash and I couldn’t. So, it appears that Nero 10 works well with pa 13 rc1 as does Nero 11.
Good job to all! :)
it didnt misbehave, just too much stuff… 350 MB Trial, that installs for loong time. Reminded me of Windows installation :-)
-
it didnt misbehave, just too much stuff… 350 MB Trial, that installs for loong time. Reminded me of Windows installation :-)
Yea, that is what I was referring to also when I said it is getting worse and worse. I also was referring to it being bloated. That is why I only install Nero Burning ROM and not the multimedia package (though I have a license for it). I should have been more specific.
Again, thanks for fixing pa so that it now works with Nero.
