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
PACL v6.01 - command prompt corrupted when used with '-unicode' switch?
-
Hi,
Summary: Powerarchiver with ‘-unicode’ mode is corrupting the environment and no batch files could be executed after PA run
How to reproduce:
1. I have a .bat file C:\test.bat which has the following content@echo off
echo Test > C:\testout.txt2. I open a command prompt and run c:\test.bat. C:\testout.txt is created.
3. delete the file
4. run PACL in unicode mode in the same command shell as below:
D:\ConeXware\PowerArchive\6.01\PAEXT.exe -q -c -v -r -spassoword -unicode d:\archive.tar.Z
- this lists the archive.
5. now run c:\test.bat in the same command prompt
- c:\testout.txt is not created
This is the issue! Even though C:\test.bat returns a success, batch file is actually not executed. This issue does not occur if -unicode switch is not used.
What would be the workaround for this? We are the registered users of PACL and recently upgraded to PACL6.01. Please reply at the earliest as this issue is affecting release of our product.
Thanks,
Jithesh -
Hi!
D:\ConeXware\PowerArchive\6.01\PAEXT.exe -q -c -v -r -spassoword -unicode d:\archive.tar.Z
- this lists the archive.
5. now run c:\test.bat in the same command prompt
- c:\testout.txt is not created
The same thing happends for me. One interesting thing is that after I have list the archive I can’t even use the dir command in CMD.
C:\PACL>dir Volume in drive C is System Volume Serial Number is 3466-FC25 Directory of C:\PACL 2010-06-04 08:35 <dir> . 2010-06-04 08:35 <dir> .. The system cannot write to the specified device. C:\PACL> If it can't write to the specified device then it explains why the txt file isn't created. I don't know why this happends, but I can confirm that I got the same error as you have. Kind Regards Micke</dir> </dir>
-
Did you start cmd.exe with /u switch? Without it, cmd.exe is not running with unicode support, so then PACL can not use unicode either.
-
Hi!
I have tested it with the /u switch and now the bat file write the informaton correct to the textfile.I still get the same error when running the dir comand after list the contents of the archive. It works if I use the dir /w, but only dir gets the same error message. It’s not important to me since it works when I use the dir /w instead.
Thanks spwolf for the help.
Kind Regards
Micke -
I tried opening with /u switch but that didnt work either. C:\testout.txt is not created when running the batch file after running paext.exe with ‘-unicode’ in the command prompt opened with /U switch.
@Micke: ‘dir’ command is always working regardless of -unicode switch for me. No issues with dir command at my side. Please check if it is because of write permission for PACL in a particular directory.
Thanks,
Jithesh -
I tried opening with /u switch but that didnt work either. C:\testout.txt is not created when running the batch file after running paext.exe with ‘-unicode’ in the command prompt opened with /U switch.
Have you tried change the path to where the testout.txt is created? Instead of writning to the root of C: try write to a subfolder instead.
I have tested this on Windows 7 and it’s working for me when I open a cmd window using the /u switch like this:
cmd /u
The difference for me is that I write the testout.txt to C:\Programs\Test which is a folder I have write access to.
@Micke: ‘dir’ command is always working regardless of -unicode switch for me. No issues with dir command at my side. Please check if it is because of write permission for PACL in a particular directory.
Thanks for the information, I don’t know why I get this problem with the dir command, but I know I have write access to the folder, because the textfile is created even after running PAEXT.
My only suggestion to you is that you try change the path in the bat folder to a subfolder instead of the root folder.
Kind Regards
Micke