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
Additional paths named backslash created
-
PACOMP included files beginning with a period, in an archive, however any path that was empty had an additional path created in the archive, that was not on the local system.
These additional paths all had a backslash character as the path name.
PowerArchiver Command Line 4.01
-
try with PACL 5.0 Beta 1 please…
thanks
-
PACOMP …[snip]… added the paths beginning with a backslash.
The archives are TAR.GZ
Tried with PACL 5.00 beta 1.
Folder test has one file, three sub folders (two empty)a) pacomp -a -r files.tar.gz C:\test*.*
- did not store any path information even for the files in the sub-folder (hence nothing for the empty folders) :confused:
b)a) pacomp -a -r -P files2.tar.gz C:\test*.*
- stored full paths (including empty folders), but did not see the extra backslash reported (using both PowerArchiver and paext to list contents of archive).
-
try with PACL 5.0 Beta 1 please…
It didn’t even add any files beginning with a period at all, just a heap of empty paths.
-
Tried with PACL 5.00 beta 1.
Folder test has one file, three sub folders (two empty)a) pacomp -a -r files.tar.gz C:\test*.*
- did not store any path information even for the files in the sub-folder (hence nothing for the empty folders) :confused:
b)a) pacomp -a -r -P files2.tar.gz C:\test*.*
- stored full paths (including empty folders), but did not see the extra backslash reported (using both PowerArchiver and paext to list contents of archive).
-p is for relative path, -P is for full path…
-
It didn’t even add any files beginning with a period at all, just a heap of empty paths.
yeah, it doesnt like it since you cant create those in Windows… we will see what can we do.
-
yeah, it doesnt like it since you cant create those in Windows… we will see what can we do.
That is not correct.
I can create a file, in Windows, beginning with a period, using …
Crimson Editor
Notepad
Wordpad
OpenOffice writer
edit (command line editor).I could also think of a number of other programs on Windows, that can “save as”, and make the filename begin with a period.
-
That is not correct.
I can create a file, in Windows, beginning with a period, using …
Crimson Editor
Notepad
Wordpad
OpenOffice writer
edit (command line editor).I could also think of a number of other programs on Windows, that can “save as”, and make the filename begin with a period.
sure, but not in windows explorer….
In any case, i already said we will take an look at it.
-
sure, but not in windows explorer….
Who creates files in Explorer ? It can only create an ‘empty’ file anyway.
If a file beginning with a period needs to be created, then obviously it would be created with an editor, and there are many that can create a file (with content), in Windows, that begin with a period. ;)
-
Who creates files in Explorer ? It can only create an ‘empty’ file anyway.
If a file beginning with a period needs to be created, then obviously it would be created with an editor, and there are many that can create a file (with content), in Windows, that begin with a period. ;)
do you want this done or not? It doesnt seem so…
Want to hear some nice words for working over the weekend…
:-)
-
-p is for relative path, -P is for full path…
I know you know I know that :p
Relative path should still save the Sub-folder names.Note: Just noticed I missed it out, but I did have -p in first test.