-
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
-
Just uncompressed a RAR file that has a folder within, PA created the folder but the files inside are not being saved into folder because directory separator is a BACKSLASH (Windows style) instead of SLASH (macOS).Screenshot_2022-05-12_09-59-08.jpg
-
Hello,
When clicking on the main ribbon for a new version I get a script error message.
Actual version: 21.00.15 - French version
OS: W10 21H2 19044.1645Best regards
WilfridPS: Keep building such good software
-
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.de9b4a2d-07e7-4323-a5a3-1b91e73dafc0-image.png
-
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.b606f084-9d96-461e-b93b-6ba9310a0f6c-image.png
-
PowerArchiver 2022 - Final Version - 21.00.15
Download:
https://powerarchiverdl.cachefly.net/2022/powarc210015.exeInformation about PowerArchiver 2022 - 21.00.15:
https://www.powerarchiver.com/2022/04/05/welcome-to-owerarchiver-2022/Thanks everyone for your assistance!
-
Hi,
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,
Karsten -
-
-
-
-
-
Hi,
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?
-
Hi,
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.7989017c-3cd2-4a99-a1f6-06ce62329dec-image.png
“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
89843f23-ad89-45bf-92bc-406b1a11dfc9-image.pngcc40877b-d8d0-404c-b7f8-d5ae0a1ee445-image.png
-
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.
Suggestions, please.
I think PA just blue screened my Vista x64 SP1 PC
-
Had been using default classic skin for a longtime so I decided to change it to the modern skin. Didn’t like the skin so I proceeded to go to the skins options and there were two others listed MyPA and Longhorn. Changed to Longhorn and PA suddenly crashed. Any attempt to reopen PA just caused an instant “This app stopped working” message from Vista. I then decided to go to the PA program directory and delete those two skins hoping that would cause PA to revert to default skin. As I was clicking through the directories, I noticed that my sound as screwed up as in static filled and the “click” sound effect was instead the “stop” or “crash” sound effect instead. Figured it was time for a reboot so I went to the start menu and selected to restart the PC. Within 20 seconds I got a blue screen. Powered down the PC and cold booted it and got a windows recovered from a serious error message. Immediately deleted those two skins and got PA to start again, but this was very troubling. This Vista install isn’t 3 months old and I had no issues up until this point. Using latest PA 2007 build, btw.
****** I tried to repro on an XP PC and although I didn’t get it to crash, there are definite problems with those two skins. If you switch back and forth between them, they will glitch up. It will for example show the MyPA skin even though it clearly shows Longhorn skin as being checked. Those skins should be removed from the installer if they’re not going to be updated. TBO, neither one of them are that great, especially LH.
-
Thanks Denzilla,
Im sure one of the developers will get back to you with regards to this issue. In the mean while can you provide a bit more information of your system specs of which this issue occured. ie, CPU, RAM, Vista Version ie Ultimate, Home etc… also if possible any programs that were runing as well.
Can any other users who own Vista try and replicate this and report it please? This will allow PA to gain an idea to the overall impact to other users.
-
I’m unable to reproduce this on vista x86.
-
Just tried it on Vista home premium 32 bit and could not reproduce.
What version of PA are you using ? as there was a problem with these skins in an earlier version as posted HERE
-
I could be a specific problem with Vista x64, SP1 or a combination of the two. My hardware:
Asus M2N-X motherboard
A64 X2 4400+
2GB Corsair VS DDR-667
Sapphire Radeon HD 3450 PCI-E
Seagate 250GB SATA II
Vista x64 w/SP1I had no other apps open at the time other than a few things in the systray (KAV7, APC powerchute, ATI control panel)
-
I could be a specific problem with Vista x64, SP1 or a combination of the two. My hardware:
Asus M2N-X motherboard
A64 X2 4400+
2GB Corsair VS DDR-667
Sapphire Radeon HD 3450 PCI-E
Seagate 250GB SATA II
Vista x64 w/SP1I had no other apps open at the time other than a few things in the systray (KAV7, APC powerchute, ATI control panel)
skins should not be used in x64… it is our error, it was supposed to be disabled when it detects x64.
so as an workaround, dont use skins in x64 :-).
-
skins should not be used in x64… it is our error, it was supposed to be disabled when it detects x64.
so as an workaround, dont use skins in x64 :-).
Just glad to hear there was an actual reason for the blue screen. Its actually the first blue screen I ever had. Seen them on other people’s systems, but never my own. Rather scary :p