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
Problem with large, spanned, encrypted, 7z archive.
-
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.
-
We will test this out, 2-3 days ago someone reported an issue with large 7zip spanned archives…. thanks.
-
I should have given you more information in my first post, so I’ll try to do that here.
I have a batch script that includes the following command:
pacomp -a -P -g -cz -ca -$“%TEMP%” -v%CHUNKSZ% -x@%EXCFILE% -l"%BULOG%\PA_%MON%%DAY%%TM%Log.txt" "%BUTEMP%%MON%%DAY%%TM%.7z" @"%SCRIPTPATH%%BULOG%%MON%%DAY%_%TM%.txt"
The same command with the variables defined appears as (example):
pacomp -a -P -g -cz -ca -$C:\WINDOWS\Temp -v100M -x@exclude.txt -l"BackupLogs\PA_12_03_0453PM_Log.txt" “Z:\BackupTemp\12_03_0453PM.7z” @C:\Users\User\Documents\SystemScripts\BackupLogs\12_03_0453PM.txt"
During the testing of this command, I did not specify any encryption. The archive files were going to be encrypted by Windows native CIPHER (EFS), and then copied to another host using ROBOCOPY /EFSRAW.
The @list argument at the end of the command line is a text file that is generated with other tools throughout the day. It’s essentially a file that contains a list of thousands of lines, each line a fully defined path name without quotes. For example, one entry in the list would be:
C:\Users\User ABC From Unit 123\Documents\FileName.pdf
I also tried:
pacomp -a -P -v50M
pacomp -a -v100M
pacomp -c2 -P -v100M
pacomp -a -P -g -v100M
pacomp -a -P -g -c2 -e2 -v100MIn each case, PACOMP would run for about twenty minutes, using all the CPU it could, then either terminate without any error, or produce a generic error that I didn’t write down and terminate. In every case, it never created any archive files. The only thing it created was most of the header of the log file.
I then tried to use PA 2013 Pro to do the same thing to see if it would work. From the Home tab, I created a New archive with the following options:
Type: 7-zip
Action: Add
Method: Optimize
Compression: Maximum
Encryption: AES 256
Encrypt Filenames: Yes
File Paths: Store Full Paths
Include Subfolders: Yes
Include System and Hidden Files: No
Create Solid Archive: Yes
Encrypt Archive: No
Multiple Disk Spanning: Custom
Volume Size: 100000
VSCS: SmartI selected the same folders for archiving as was specified for PACOMP. The amount of data this represents is about 50 gigabytes. PA Pro ran for about an hour, and it produced 256 (.000-.255 - interesting coincidence, or is this a limit?) volumes and completed successfully. However, when I attempted to open the archive, PA Pro indicated that it could not open the file because it was invalid or something like that. Again, I didn’t write it down.
This is from my memory, so it might not be perfectly accurate. If there’s any testing or diagnostic information you would like me to provide, just let me know.
Oh, and I’m running this on Windows 8.1 Professional 64-bit.
-
We were able to confirm this issue and it has been logged in.
Thanks for the details :) -
Latest version v8 Beta 1 can do the job!
-
Latest version v8 Beta 1 can do the job!
let us know if you find anything else. Thanks!