I’m trying to backup the complete contents of a directory using:
pacomp64 -parcz T:\BACKUP.PA C:\STUFF
The contents of subdirectories of C:\STUFF isn’t getting backed up!
The sub directories are just stored as empty directories!
How do I achieve this ; show me a command line example !
Hello @Mili,
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.
Version:
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 supportLatest format support and all the various engine updates done in PA 2017.
Full support for .PA format with many different options and switches.
Download:
http://dl.powerarchiver.com/2017/PACL900-170429.EXE
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
PA Team
ConeXware, Inc.
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.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.
Enter command:
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.
… Michael
Hi,
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.
0_1524826660985_pacomp.png
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).
would be nice to have czip support
Version:
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.Download:
http://dl.powerarchiver.com/2016/pacl800b1.exe
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 am Having Appcrash mid problem in my Pc.
Hi,
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 marks
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
Explanation of -c
-
Hi,
c[0,1,2,10,11,13,15,17,19,l,p,w,b,d,z] : set compression level (0 - store; 1 - normal ; 2 - maximal) (10 - store, 11 - super fast, 13 - fast, 15 - normal, 17 - max, 19 - ultra (l - use LZMA, p - use PPMd, w - use WavPack, b - use BZIP2, d - use Deflate (z - use optimized compression method based on file exstension)Can you confirm whether these are cumulative or whether you can only have one option?
For example: Can I have 2-maximal compression using d-Deflate? If so would the format be “-c2,d”?
Thanks.
-
Does no one know the answer to this? Mods? Anyone?
-
i thought i answered, just put them separate as -c2 -cd and it will work fine… you can test and check compression method afterwards
-
Thanks for the syntax, appreciated.
So looking at the options:
(0 - store; 1 - normal ; 2 - maximal)
This is type of compression not related to speed?
(10 - store, 11 - super fast, 13 - fast, 15 - normal, 17 - max, 19 - ultra)
This is compression based on speed?
(l - use LZMA, p - use PPMd, w - use WavPack, b - use BZIP2, d - use Deflate, z - use optimized compression method based on file extension)
This is the compression method used.
-
0,1,2,10,11,13,15,17,19 are all the same… 0/1/2 are there for backwards compatibility as we added more of them in PACL 6.x I believe but didnt want to break anyone’s script.
They are are compression/speed related. Strong the compression, lower the speed… faster the speed, lower the compression :-)
-
OK that’s understood - thanks. So, finally, is there anywhere which describes the benefits of the compression methods? Is it, again, down to speed or compression for the various methods?
-
OK that’s understood - thanks. So, finally, is there anywhere which describes the benefits of the compression methods? Is it, again, down to speed or compression for the various methods?
maybe we should have something on our wiki? :-)
-
deflate - default and compatible with all other zip utilities. Great speed, low compression.
lzma - only compatible with utilities that support lzma method (zipx/lzma).
ppmd - great for text files (zipx)
wavpack - only for wav files (zipx)Optimized tries to guess which one is best to use based on stenght selected and extension of the files.
-
Great - thanks for that. You have a PACL wiki?
-
nope…only PA:
http://wiki.powerarchiver.com/en:help:welcome?redirect=1should we?
-
Ah OK - already been through that one… :-)
-
should we?
-
Possibly. I think the information sent out with PACL (manual.txt) is very minimal. It might have been fine for version 4 when the functionality was much less but there’s too much guess work in using the options and how the options interact with each other.
e.g. “0 start as a low priority process”. OK, that’s fine, but then what? What causes the process to change priority? Is it up to the user to change the priority? Will it change priority automatically when the machine is less busy or more busy?
There’s not enough detials for the type of computer-literate user who will be using PACL. Maybe it just needs more detailed documentation.
-
it wont change priority, it will be started as lowest possible priority - started as in run as low priority…
-
we could convert manual.txt to wiki and then improve….
-
it wont change priority, it will be started as lowest possible priority - started as in run as low priority…
I understand that (maybe a bad example from me) but having compression options “0 - store” and “10 - store” without the “backwards compatibility” explanation you gave above is confusing.
manual.txt, wiki, pdf - doesn’t really matter how you present it so long as the information is available. It wouldn’t take much but it’s up to you on whether you think it’s worth it.
-
I understand that (maybe a bad example from me) but having compression options “0 - store” and “10 - store” without the “backwards compatibility” explanation you gave above is confusing.
manual.txt, wiki, pdf - doesn’t really matter how you present it so long as the information is available. It wouldn’t take much but it’s up to you on whether you think it’s worth it.
it is always worth it if our users request it :-)
-
so… what do we need to improve?
http://wiki.powerarchiver.com/en:help:pa_command_line_manual_pacl -
You’ve been busy :) Nice!
OK, it looks like you used the text from manual.txt as the basis of the wiki. Initially, I’d like to see a short explanation of each command and it’s capabilities\requirements at the top of the wiki so it’s the first thing you see in the wiki - sort of an expanded whatsnew.txt for each command - with links to the syntax of each command. Is there a reason why PAEXT is first. I’d have thought you compress then uncompress so PACOMP followed by PAEXT maybe?
(These are just my thoughts so anyone else please sound-off).
-
This post is deleted!