thanks for your help in getting my PowerArchiver CommandLine license (Re: License Code Not Working / Missing) and sorry for my late reply. I do check my spam folder regularly and couldn’t find a mail from support. Also, there was no mail in my backups or any mention of it in my email logs.
I have a question regarding my licenses in the hope you are able to help me:
While my account lists “PowerArchiver Select - lifetime free upgrades and support for PowerArchiver Toolbox English - Count 2”, this does not apply for PACL, which was included with my purchase. My account shows only PowerArchiver Select - 12 months of upgrades and support for PowerArchiver Command Line - Single User License.
Since PACL was included with PowerArchiver Toolbox, shouldn’t PACL also come with a lifetime license for 2 PCs?
Thanks for your help in advance.
PACL 9.00 Beta 2
What’s New since version PACL 7:Updated to PowerArchiver 2017 engine Fully unicode interface RAR v5 (v4) support PAE2 support
Latest format support and all the various engine updates done in PA 2017.
Full support for .PA format with many different options and switches.
Due to the support of new PA format and all the changes needed for that support, we decided to move up version number to PACL 9. This is purely cosmetical - companies who purchased PACL8, have PACL9 now added to their orders. Users who have free upgrades for PACL8, now have PACL9 added as free upgrade (Business users with active select (pro/tbx), all personal users (pro/tbx).
Since we are finalizing PA 2017, we can also now spend a lot more time on PACL9.
Please check your bugs, and check .PA support as well.
Thank you! @Alpha-Testers
My OS: Windows XP Home Edition, SP3
The version number and date of the program: PowerArchiver Command Line v9.00b [Feb 23 2019]
The program not extracts one self-extracting file.
How to reproduce the problem
Download the SFX file by link: install.exepaext32 -o+ -p"install" "install.exe"
Copy the “install.exe” file into the same location as the program is located.
Go to the DOS prompt. Make your PACL location the default drive.
If it is on the E drive enter the command E: and press enter. Replace “E:” with the appropriate drive letter.
Enter command cd e:<path name> to go to the location where the program resides.
As a result, the “install” directory will not be created and no
files will be extracted.
The “install.exe” file may be damaged but if you use a program such as 7-Zip or PeaZip to extract the files, the extraction process is successful. I want the PACL to also unpack such a file.
This problem is very critical for me. I often come across this. I do not want to resort to using other compression program.
there’s a problem with PAComp and file names with a leading ".\ ".
That’s nowadays a problem, since PowerShell auto complete will complete a file test.zip in the current directory to .\test.zip.
The first command reports “All OK”, but test.7z is not created.
The second command reports an error, but the error message isn’t helpful at all. VSS doesn’t help anything if a program fails to write to a file. It’s for reading locked files… And the problematic file isn’t mentioned at all. By the way, there’s a typo, it should be “open”, not “opet”.
Only the third command (without ".\ ") works as expected.
The problem exists in the x86 and x64 version, it doesn’t matter if the archive already exists (updating) or not (creating a new archive).
PACL 8.00 Beta 1
Whats New:Updated to PowerArchiver 2016 engine Fully unicode interface RAR v5 (v4) support PAE2 support Latest format support such as improved ZIPX, ISO, etc, etc, etc.
Please test it against your existing scripts and let us know. There will be some features added in future release as well as more testing.
This is first release, please test. Thank you!
I’ve made changes to fix some problems with PAConv.bat:
1. Replaced the “” by () in the first two lines, so that it’ll work with command line arguments in quotation marksif (%1)==() goto help if (%2)==() goto help SET PATMPDIR=%TEMP%\$PATEMP$.%time::=% if exist "%PATMPDIR%" rmdir /s /q "%PATMPDIR%" mkdir "%PATMPDIR%" paext -e -d -p"%PATMPDIR%" "%~1" echo. pacomp -a -r -p -w "%~2" "%PATMPDIR%\*.*" echo. rmdir /s /q "%PATMPDIR%" SET PATMPDIR=
2. Replaced deltree with rmdir, since deltree is unknown at least in Windows XP and later
3. Also replaced the del command, which left an empty $PATEMP$ directory with rmdir
4. Changed $PATEMP$ to “%TEMP%$PATEMP$.%time::=%”, so that no write privileges are needed in the current directory as the users Temp directory is used and that more operations will work simultaneous, as long as they are not started at the very same time.
5. Changed %n to “%~n” to allow parameters with spaces and quotation marks
I spent many hours trying to figure out how to use PACOMP to add about 50 Gb to a spanned 7z archive with AES256 encryption, and have yet to be successful.
I’ve tried every combination of switches I can think of, with no success. Can someone offer a combination of switches that is known to work for this kind of task?
All I have been able to make is a set of spanned files that PA cannot open.
I am trying to understand what is default encryption method for PACOMP -fips command?
And what is the difference if you specify encryption method using e[0,1,2] command?
Using only FIPS:
pacomp -a -ssecret -fips -p stuff.bh “c:\my stuff*.*”
FIPS combined with e2
pacomp -a -ssecret -fips -e2 -p stuff.bh “c:\my stuff*.*”
I have archive that holds password protected, encrypted data which is created using something like this:C:\Temp\ZipTest>pacomp -a -spassword -fips -e2 archive.zip "C:\Temp\ZipTest" -x"C:\Temp\ZipTest\ReadMe.txt"
Then I add regular file into that archive which is not encrypted and not password protected. “ReamMe.txt” sort of file. Using command below.C:\Temp\ZipTest>pacomp -a archive.zip "C:\Temp\ZipTest\ReadMe.txt"
Now when I extract this archive using:paext -spassword -p"C:\ZipTest\Temp" archive.zip
Everything extracts correctly except for ReadMe.txt file. File is present but content is empty.error: extracting: ReadMe.txt --> CRC ERROR! [100%]
I get following
How can I extract archive without corruption ReadMe.txt file?
Pacl pacomp command line stops
I am using pacomp to compress a large archive. After the fourth file, pacomp silently stops, and the ‘.zip’ file it creates is invalid. The size of the archive is 1.5GB. Are there ways to diagnose the problem? Is there a filesize limit on the archive?
what is the size of files being archived? PACL has limits there…
The size of the files are:
file1 - 678,545 KB
file2 - 156,753 KB
file3 - 2,472,081 KB
file4 - 559,505 KB
file5 - 265 KB
file6 - 327,377 KB
file7 - 4,682,257 KB
file225 - 615,057 KB
Total - approx 245 GB
Winzip successfully produced a zip file of 99 GB. pacomp produced an invalid zip file of size 1.5GB and stopped on the fifth file above.
Easy troubleshooting - PACL curretly has 2/4 GB limit.
However, new version of PACL is coming out this week, so please test it out and see if it works properly.
I would be absolutely interested in testing higher limits, as well as the planned Unicode support. How do I pick up the latest release? Thanks.
TBGBe last edited by
When it is available (spwolf says this week) it will on the PA download page.
Let us know how it works…