-
How do I achieve this ; show me a command line example !
-
Version:
PACL 9.00 Beta 2What’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.EXEDue 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
paext32 -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.
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 1Whats 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.exePlease 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
if (%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 -
Why cant i edit my profile details? in my account
-
PACL 8.0.
What new features do you guys want from it?
Current list for 8.0
RAR 5.x support. Latest ZIP/ZIPX engine with even better performance. Updated rest of engines with latest support for all file formats.Possibly:
New PAF format testing.Other things like better logs or what else do we need?
-
Is it possible to encrypt file names as well as archive itself using pacl?
I know you can do this using Power Archiver but not sure about pacl.
-
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.
-
Hi
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*.*” -
How can I add comment to archive using pacl pacomp?
-
Hi All
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.zipEverything extracts correctly except for ReadMe.txt file. File is present but content is empty.
error: extracting: ReadMe.txt --> CRC ERROR! [100%]
I get followingHow can I extract archive without corruption ReadMe.txt file?
-
Does PA (preferably the CL version) have the facility to archive files based on an age?
(I want to be able to move a quantity of files out of a folder and into an archive if (and only if) they’re over 35 days old.
I have an ancient copy of ARJ that can do this (via the -odb switch) but I’d like to use PA, and can’t work out if it’s possible.
-
Hi in pacomp.vbs by Micke how to preserve the folders structure of the files to compress.:confused: because just compress the files not the folder structure of each file.
thanks
'******************************************************************* '* PACOMP.vbs '* @author: Micke '* @hist 2010-02-26 CREATED:Script for compress multiple file types '* @hist 2010-03-01 BUGFIX: Space in path or filename resulted in '* no archive was created. '* '* Script for compress multiple file types '* '* Usage: cscript PACOMP.vbs ArchiveName.extension DrivePath '* Example1: cscript PACOMP.vbs C:\Temp\MyArchive.zip D: '* Example2: cscript PACOMP.vbs C:\Temp\MyArchive.zip D:\Temp '* '******************************************************************* Option Explicit 'Variables Dim FSO, objDir, aList, FileExtension, ArchiveName, DrivePath Dim aFile, aItem, strCompressionString, WshShell 'Constants (Change path to your own enviroment) Const PACOMP = "C:\Programs\PACL\PACOMP.exe" 'Check number of arguments If WScript.Arguments.Count <> 2 Then WScript.Echo "Usage: cscript PACOMP.vbs ArchiveName.extension DrivePath" WScript.Echo "Example 1: cscript PACOMP.vbs C:\Temp\MyArchive.zip D:" WScript.Echo "Example 2: cscript PACOMP.vbs C:\Temp\MyArchive.zip D:\Temp" WScript.Quit End If 'Create the FileSystemObject Set FSO = CreateObject("Scripting.FileSystemObject") 'Create the ShellObject Set WshShell = CreateObject("WScript.Shell") 'Get data from the Arguments ArchiveName = WScript.Arguments.Item(0) DrivePath = WScript.Arguments.Item(1) 'Get the Folders for the DrivePath Set objDir = FSO.GetFolder(DrivePath) 'Create a Array with Fileextensions for the archive, change to your enviroment aList = Array("png", "jpg", "avi") 'Search through the folders SearchFolders(objDir) 'Sub for Searching recursive in Folders Sub SearchFolders(pstrCurrentPath) For Each aFile In pstrCurrentPath.Files For Each FileExtension In aList If FileExtension = LCase(Right(CStr(aFile.Name), 3)) Then AddFileToArchive aFile.Path End If Next Next For Each aItem In pstrCurrentPath.SubFolders SearchFolders(aItem) Next End Sub Sub AddFileToArchive(pstrFileName) 'Create the string with parameters for PACOMP strCompressionString = PACOMP & " -a -P " & Chr(34) & ArchiveName & Chr(34) & " " & Chr(34) & pstrFileName & Chr(34) WScript.Echo strCompressionString WshShell.Run strCompressionString, 0, True End Sub
What's the difference between the evaluation and the registered version of PACL 6.01?
-
Hi!
In the page for PACL it says the following thing about the evaluation version.Without a registration key, PACL will display a notice before each command.
Maybe I’m doing something wrong here, but I can’t see any difference between the registered and the evaluation version of PACL 6.01. I don’t get any notice before each command in the evaluation version, but maybe I have missed something here.
I’m using Windows XP with SP3
Kind Regards
Micke -
I can’t remember for sure, but I think it is the wording of the output “header” - just states “registered” or “evaluation”.
P.S. why have you not input the reg code?
-
P.S. why have you not input the reg code?
I have entered the reg code and registered the application. I just noticed that I couldn’t see any difference when I used the registered version compared to the evaluation version.
Kind Regards
Micke -
only difference is in header, it says unregistered/registered.
-
only difference is in header, it says unregistered/registered.
Thanks, that explains why I didn’t see any difference between the evaluation version and the registered version. The reason for starting this thread was because I thought something was wrong when I couldn’t see any difference between the two versions. Now when I have the answer I have some opinion about it. You don’t have to agree with me, but I still want to share them with you.
Personally I would have expected some limitations in the evaluation version of PACL that still allowed the user to evaluate the program to see if it works as expected and will fill the need the user have for such a program.
Example of limitation could be a small message after running each command like This is day 1 of your 30 days evaluation, press ENTER to continue
For a user like me that uses batch or scripts in combination with PACL this would be a limitation, but I would still be able to evaluate the program even with this annoying message. After registry the program, the message would disappear.
The advantage for the user with this is that the user will get a feeling of getting something for the money the program costs.
One of the critical question is: Why should a user buy the program for $7.95 instead of continue using the evaluation version
One answer could be a personal satisfaction of supporting developing of good software, but I reality the user gets no extra functionality at all by registry the program. The functionality is the same and the message is the same after each command except for in the registered version it says Registered to: Name and the evaluation version says Shareware version.
I think that coneXware will loose potential buyers of this software because of having too generous functionality in the evaluation version of PACL. If you disagree with me about this, ask yourself how many people would have bought PowerArchiver if the nag screen wasn’t visible in the unregistered version of the program. Some people would have bought the program, but I don’t think it would have been as many as there’s today.
The nag screen have a purpose of encourage people to buy the program I don’t see any reason for having a corresponding message in PACL with a pause after each command that the user would have to press the ENTER button to continue.
This message is already far to long :) but I have one more thing to say. I’m very satisfied with PACL and the more I use it, the more I like it. If the current small difference in the evaluation and the registered version is working as expected, it’s ok for me. I will continue use the program and also looking forward future versions of it.
Kind Regards
Micke
