For example:
Download this ZIP file: http://dslstats.me.uk/files/dslstats32W-6.5.zip
Everything in the ZIP file is in a directory “dslstats32W-6.5”.
However when I extract using right click “Extract Here” the name of the directory created is “2W-6.5” !
I am running PA 22.00.09 on Windows 11. I have seen the same happen with some other kinds of archive too.
Hello!
Is there currently no portable version of PA2023 available?
(When) do you plan to release one?
Thanks!
If I compress a folder to a .pa using right click, Compress to folder.pa and use the new Windows 11 menu then the Options, Configuration, Miscellaneous, Use normal relative path setting is always enabled.
But I like this option disabled so I have to use the old style menu in order to get PA to compress a folder in the way I wish.
Just tried using the Modern (Windows 10) Icon set and seeing a few missing icons in both PowerArchiver Burner and PowerArchiver Encryption screens . They are all there in the Minimalistik icon set and the only difference I can see is the former is blue and the latter grey. In version 22.00.9
powerarc_2023-09-18_17-00-19.png
powerarc_2023-09-18_17-01-05.png
PA 22.00.09
344c6c52-f03f-407b-ad76-8130b31936bb-image.png
PA 22.00.09 shows a nag screen, when I try to open some setting windows. I have already PA 2023 Toolbox and PA shows, that it’s licensed in the info dialog.
a860bd81-3e71-4ce0-9988-74cd4189d43e-image.png
0836bc83-8046-4a91-bc7b-68bd231100a3-image.png
PA 22.00.09
Some labels in the help toolbar are not translated:
b3c1f5c4-b73d-49d8-9ed0-56294840838c-image.png
I’m looking forward to deploying PowerArchiver 2023 to my users. Can you tell us when the MSI will be available for download and distribution?
Thanks.
Hi there,
there were some security issues fixed in 7zip:
https://www.zerodayinitiative.com/advisories/ZDI-23-1165/
https://www.zerodayinitiative.com/advisories/ZDI-23-1164/
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
Hi,
From where I get PAVD2023.EXE? PowerArchiver 2023 tries to open it.
But it seems, it tries to download PAVD2021.EXE.
Thanks
I noticed that the version of ZPAQ used is older than the latest released 7.15 https://mattmahoney.net/dc/zpaq.html also there seems to be a newer fork that adds several features https://github.com/fcorbelli/zpaqfranz
It would be useful to implement this latest version (it also maintains the same syntax and behavior as the latest official release if used the -715 flag) and add when opening a zpaq file a choice of the version of the files to show (e.g. as dummy folders represented the various versions present). Since any previous changes are stored with this format, it is possible to extract a snapshot of a certain date/version.
If I open a password-protected zipper file (created with WinRAR but I think that’s irrelevant), open it with PowerArchiver and run “Remove Encryption” on the same file, then reopen it and add a password with “Encrypt Archive,” the resulting archive will be protected with the old ZipCrypto algorithm and not AES as indicated.
(this can be verified, for example, by trying to open the archive files with Windows Explorer, which does not support the AES algorithm)
PA 21.00.18 running on Windows 7 64 bit.
I made a big .PA file and thought I’d check it was made correctly with Menu / Actions / Test.
Discovered:
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
PABACKUP.EXE Crashes
-
Hello,
Lately I’ve been experiencing application crashes with with PABACKUP.EXE. Here is the Event information offered by the Windows Application Log (let me know if you need more details):
Faulting application name: PABACKUP.EXE, version: 12.0.24.1, time stamp: 0x2a425e19
Faulting module name: PABACKUP.EXE, version: 12.0.24.1, time stamp: 0x2a425e19
Exception code: 0xc0000005
Fault offset: 0x000041da
Faulting process id: 0xcd4
Faulting application start time: 0x01cc5fb1ffa1369e
Faulting application path: C:\Program Files (x86)\PowerArchiver\PABACKUP.EXE
Faulting module path: C:\Program Files (x86)\PowerArchiver\PABACKUP.EXE
Report Id: 3d59a85f-cba5-11e0-bbed-7071bce3eb99This started happening under version 11.71 and continued after I upgraded to version 12. I have even uninstalled version 12 and re-installed from scratch.
I’m running Windows 7 64-bit and I launch my PA backup jobs using Splinterware’s System Scheduler 4.17.
In System Scheduler I use the Sequence of Events scheduling type in order to launch multiple backup jobs sequentially (I switched to this method when the PA Queue feature proved too problematic with frequent failures).
Thanks in advance for any help with this.
-
You will most likely be asked by the devs if you have the same problem if you don’t use “Splinterware’s System Scheduler 4.17” So it would probably help them to know that.
-
Hi Joe,
I’ve installed splinterware system scheduler and scheduled a pbs script there to be run.
Once the selected time came up, the script ran and created my backup with no issues.Does this error occur for you with all pbs scripts or just one?
If you can, please send us a sample script which does not work for you along with a screenshot of the settings for that scheduled event/script in Splinterware System Scheduler.You can send it to support at conexware dot com
Thanks!
-
Hi Mili,
Thanks for your reply and thanks for your help.
This issue is becoming a real brain teaser as I am pouring over the Windows event log to find anything that could cause this crash.
Just like you, I can’t duplicate the crash at will. System Scheduler is not the culprit here, as it does exactly what it is supposed to do. As a matter of fact, it ran successfully at 2:30am this morning - no crash this time.
I am currently looking at the possibility of some sort of conflict with VSS. The VSS service stops due to idle timeout and perhaps that causes a problem when PABACKUP.EXE starts.
I was hoping the crash information provided through the event log might help you pinpoint some sort of problem area. If that is not the case then there is not much else you can do at this juncture.
I will keep plugging away at this and will provide updates here.
If you have any thoughts on the VSS angle please let me know.
Thanks!
-
VSS was not used with PA 2010 though, so it should be not influencing factor with the issue.
Did you try using different compression? What are other PBS settings, for instance are always new files created, or is old backup file updated?
-
is there another process running in the background when pa backup is used.
does differnt backup scrips work ok?
when did you create the backup script i mean what version of pa was the backup script made in.
-
I’m closing this thread. Thank you to all for your replies. :)
As it turns out the System Scheduler utility has failed to properly execute an automatic Windows login, so when PABACKUP is scheduled no user is logged in, causing PABACKUP to crash (perhaps not very elegant programming!).
Before I run all of my backup scripts, I schedule a series of housekeeping activities (closing applications, running CCleaner) followed by a system restart. System scheduler has a setting to automatically initiate a Windows auto logon and this works well in Windows XP, but has stopped working in Windows 7.
I’ve had to find a different way to initiate a forced Windows auto login (I’m not relying on System Scheduler for this any more). Problem solved.
Thanks again. :)
