From within PA on the extract popup, buttons are hidden, I must resize the window to get access to the OK/Cancel buttons. Tried on the default notebook screen (Macbook M1 Max 14") as well as on my external monitor (4k).Screenshot_2022-05-12_10-02-10.jpg
Ho già contattato il supporto con il modulo presente qui https://www.powerarchiver.com/it/contact/ da settimane ma non ho ricevuto riscontro e ora che ho aggiornato alla versione 21.00.15 ho notato che il problema persiste.
Quando clicco PDF Encrypt & Sign nel tab Crittografia appare la schemata riportata sotto come se mancassero le funzionalità.
I’ve already contacted support with the form here https://www.powerarchiver.com/it/contact/ weeks ago but I haven’t received any feedback and now that I’ve updated to version 21.00.15 I’ve noticed that the problem persists.
When I click on PDF Encrypt & Sign in the Encryption tab the schematic below appears as if the functionality is missing.
I have tried to burn a DVD with PowerArchiver 2022 Final, but it didn’t work because PA didn’t found the external DVD-Burner.
I have tried several burners from Sony, LG, Dell.
I have connected the burners with several USB-Ports but unfortunately without any success.
With other burning software, e. g. Nero, all burner worked perfect on each USB-Port.
The same problem occured with PA2018 and it was solved with an update, but I don’t remember the detailed software version.
Could you check the possibility of an bug, please?
Thank you for your support in advance!
Quando creo un archivio zip con un altro programma ad esempio Winrar se apro il file con Winrar vi sono visualizzati anche le date originali di Accesso e Creazione.
Se ottimizzo quel file zip con la funzione Ottimizza archivio di PowerArchivier (o creo un nuovo archivio) il file risultate non ha più le date originali di Accesso e Creazione.
C’è una opzione per preservare questi dati? (Non l’ho trovata nelle impostazioni del programma e ho già abilitato le opzioni “salva info complete cartella” presente in “Profili di compressione”)
When I create a ZIP archive with another program such as Winrar, if I open the file with Winrar, the original Access and Creation dates are also displayed.
If I optimize that zipper file with the Optimize Archive function of PowerArchivier (or create a new archive) the resulting file no longer has the original Access and Creation dates.
Is there an option to preserve this data? (I haven’t found it in the program settings and I have already enabled the “save complete folder info” options in “Compression Profiles”)
Upgraded from 2021 to 2022. Selecting ‘backup’ no scripts are showed. Only after editing and saving an existing script (explorer) it shows up in the PA backup folder.
So is the ‘backup’ icon to open the Backup screen only for creating ‘new’ ones. This means that you have to open ALL your old pbs files and to save them again… not user friendly.
No way to improve this ? Thank you.
PowerArchiver 2022 - Final Version - 21.00.15
Information about PowerArchiver 2022 - 21.00.15:
Thanks everyone for your assistance!
I have a 31" 4K screen with 3840x2160 pixel, which PA is able to handle - except of a scaling other than 100%.Access violation at address 0000000..DF47A4 in module 'powerarc.exe'. Schreiben of address 0000...00330.
When changing scaling for this screen to 125%, starting PA brings the following exception:
After closing this message, PA seems to work fine.
PA version 21.00.15 (03/2022) 64bit (tested with Win 10 and after upgrade Win 11)
Is there any chance to avoid this access violation or this message?
Thanks and regards,
the new Windows 11 context menu is not localized in PA 21.00.13.
While the classic context menu is localized, when it’s opened on a file on my desktop, it’s English, when it’s opened from a file on my C drive.
@Mili Are there updated localization files available?
I thought, I’ll give it a try and upgrade my PA 2018 Toolbox on my production machine to PA 2021 (20.10.03)Sending registration codes in your order recovery doesn’t seem to work at the moment (I also checked my junk folder), online activation works Using registry to disable modules (for example HKLM\SOFTWARE\PowerArchiverInt\General\DisableBurning) doesn’t work as expected with modern ui. The module is visible, but I’ll get the trial nag, if I try to open it. It’s almost fine in classic and ribbon mode.
“DisableClouds” and “DisableExplorer” seem not to be respected at all, while the classic UI seems to respect the setting to disable any other unused module:In settings I won’t be able to access the SmartAI settings and the settings for the internal editor if the FTP module is disabled
PA Queue does not compress file optimally with same parameters if used in Queue mode.
Being able to save advanced option, and set a default profile and archive type for compression so I can save clicks.
The above two are majorly affecting my efficiency with archiving stuff with PA 20.10.03.
Can someone confirm if they are resolved with the 2022 RC1?
I’m running W10 Pro on an HP i-7 machine with now 32gb of RAM. The system drive is an SSD.
In the course of sorting out some inconsistencies in a couple of my .pbs jobs, I’ve been paying close attention to the system CPU resource and power consumption of PA Starter, as shown by the various resource management tools. I’ve also been trying to identify why my system seems rather sluggish despite some extensive tuning for speed etc.
When I have enabled Starter as a start-up programme, to use the PA Queue facility, I see that Starter consistently uses between 10-13% of CPU, with High Power consumption indicated. It runs, consuming this resource, irrespective of what may be happening with PA and any pbs script jobs.
I can understand a need to use a good chunk of CPU when Starter is actually handling PA jobs, but it shouldn’t sit and consume this amount when it really isn’t doing anything but wait for a job to start and for which it is needed.
Perhaps I’ve missed a way of lessening Starter’s impact, but in the meantime I’ve adjusted my set-up to running PA without it.
SOLVED Open with... broken for filenames with spaces
Hi, long-time user of PowerArchiver here.
I noticed that some time ago the “Open with…” functionality broke for files with spaces in the name. Tested with latest PA2017 (64bit) on Win7.
The issue is that the argument isn’t passed as a single string to tools, so for instance trying to file “My Text File.txt” using “Open with…” a tool located at C:\Program Files\Tool\My_Tool.exe will try to open the following files:
Basically, the file name needs to be enclosed in double quotes for this to not happen, so tools are called “%TOOL_LOCATION%” “FILE_LOCATION%”, e.g. “C:\Program Files\Tool\My_Tool.exe” “%TEMP%_PAnnn\My Text File.txt”
Thanks in advance,
Thanks for the details.
I’ve attempted the “Open With” function on file with spaces.txt and it opened properly in notepad.
Which Tool are you using so that we may test with it and also, are you getting an error message when attempting to use the “open with” function on filenames with spaces and mentioned tool?
Also, which format are the archives in? I have tested with .zip and .pa
Let us know and we will look into it.
Notepad is a bad test case, as it by default attempts to open multiple command line arguments as a single file.
I personally experience the problem with applications that allow multiple files to be put on command line. Notepad++ will actually guess, so not a good test case. I notice this with 010 Editor (a hex editor) when I examine zipped binaries that have spaces in their names.
I tested .zip and .7z and both had the same issues. I doubt it’s related to the file format as this seems purely a PowerArchiver UI/logic issue.
For testing you can replicate the issue with the following batch file and zip file:
I just noticed that the error does not occur when initially selecting “Open with…” --> “Choose Program…” – probably because Windows handles the arguments correctly. The error only occurs when using the shortcut that is generated afterwards directly in the “Open with…” menu.
Initially, “Open with…” --> “Choose Program…” will show the correct and expected result:
Using the generated shortcut it will show that the argument was not enclosed in double quotes:
This should illustrate the bug enough to reproduce and hopefully fit it.
many many thanks for the details @FreakRob
we have reproduced and have logged the issue in.
we appreciate the assistance!
@FreakRob Thank you for your report. Please check latest release:
It should work now. Please let us know. Thank you!
@spwolf I just tried it and it works. Many thanks!
@FreakRob thanks a lot. 2 more bugs and free license or extension, just a reminder!