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.
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
there were some security issues fixed in 7zip:
As it seems, that PowerArchiver and PACL use the 7zip libraries, could you please update them to the latest version?
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.
a) PA always issues a UAC prompt to do this!
b) PA always says there are many errors in PA files.
Automated install and gdiplus.dll
I’m trying to come out with an automated setup.
Now that I FINALLY found the right MSI options and properties to use, I stumbled upon the gdiplus.dll problem for Win9x/Me/2k machines.
I either run powarc1011fr.exe or powarc1011fr.msi with the following parameters: /qb AI_DESKTOP_SH=“” ADDSTART=“” SHOWCONF=“” ENABLEQUEUE=“”
The MSI installer goes through the installation process, but it won’t take care of the gdiplus.dll requirement, and trying to use PA will lead to a “missing DLL” message. :(
The EXE installer correctly detects the DLL is missing, but then displays a dialog box, so it won’t run unattended…
And this is a hell of a DLL: in WinXP/2003/Vista gdiplus.dll is buried deep in the WinSxS subsystem and it’s hard to check for; in Win9x/Me/2k it’s supposed to be installed in the program directory of EVERY application that depends on it.
I’ll try to work around this by checking wether the %windir%\WinSxS directory exists and copying the file otherwise, but this should clearly be done by the installer !
you can simply download the SFX from the installer requirement and then install SFX prior or after PA 2007 installation.
Checking for requirements is feature of .exe installed (which is MSI as well).
additionally, if you email us via support form, you can get more info and faster than on forums….
Hmm, yes I can do that.
However, installing gdiplus.dll on XP/Vista goes against Microsoft’s recommandations, and it’s even a violation of their EULA (“You may distribute gdiplus.dll solely for use with Windows 2000, Windows Millennium Edition, Windows NT 4.0 and Windows 98”).
Well, I put the following line in my install script:
if not exist %windir%\WinSxS gdiplus_dnld.exe /s ```I'll stick to this for now, but I really think this should be handled by the MSI installer. Sure, the EXE installer is based on MSI as well, but checking is done in the wrapper part, not by the MSI itself. :P
Sorry for not going straight to the support, I did not notice the form.
At least in our MSI Installer, we can not include prerequsites without boot strapper (exe). Even then, would you want each one to be download from the net? That would be too much extra work.
Your solution is reccomended one.
When having setup issues, it is usually much better to contact support since most people on forums are private users that dont have access to advanced installation docs (that you should have gotten).