The 4.5 format allows “large archives”.
This is used when :-
A) Number of data files/folders >65500 (approx)
B) Size of data files before compression >4GB
C) Size of zip file after compression >4GB

So if your zip file is only 100MB, I doubt B) or C) apply.
Only you know if A) applies to these zip file(s) :D

I can only guess at possible differences that are NOT really errors in PAEXT or PowerArchiver.

If you know how to create one of these zip files or if you provide an example zip with the problem (e.g. url to access a “bad” zip file) then it could be checked by PACL/PowerArchiver devs. If not, all we can do is guess.

Nope.
PACL doesn’t support 7-zip at all.

http://www.powerarchiver.com/forums/showthread.php?t=219

@hlb:

I am using PACL version 4.01 with Windows XP Professional.

I am in the process of testing PACL 4.01 (PACOMP.EXE) and have discovered that the -q (quiet) switch does not work as expected. I have a work around by using the -l"nul" switch to send the output to the nul device. This also prevents the console bell from ringing. It does not however prevent the PACL program banner from appearing. Alternately, I can also redirect the output to a log file as well. In my humble opinion, the -q (quiet) switch should not only work, but it should also prevent the PACL program banner from appearing as well. I.E. -q (quiet) should mean just that. The -q (quiet) switch would likely be used from the scheduler when performing archival tasks and you would not want or need any console output whatsoever.

Thanks much.

HLB

Hi,

what -quiet switch means in this case is that PACL will not ask you anything during its work.

regards,

While evaluating the PACL 4.01 tools, I tried to zip a directory tree that contained numerous empty subdirectories. With two exceptions (test\test8\test6 and test\test9\test6), PACOMP did not place any empty directories into the ZIP file.

I created the attached file testpa.zip with the following command:
pacomp.exe -a -r -P testpa.zip test*

For comparison, I created the attached file testwz.zip with WinZip using the command:
wzzip -aPr testwz.zip test*
attachment_t_1052_0_testpa.zip
attachment_t_1052_1_testwz.zip

Have a look at PKZIP: http://pkzip.com/products/enterprise/unix/server/pkz/features.php

Powerarc is not the command line utility - it is the Windows (GUI) program!

For command line working use the PACL suite - extraction uses PAEXT.

Thanks a lot!

Have you tried extracting .tar.gz archive on Unix from / directory . This will extract file dir/test.c to /dir/test.c.

Using the following with WinZip commandline interface works:

call wzzip.exe -mu -ex -r -P %KATALOG%%year%%month%-%server%.zip E:\Logfiles\Http%server%\ex%year%%month%*.log

Using this command with PACL 4.0 does not work:

call pacomp.exe" -u -m -c2 -r -P -v1024M %KATALOG%\SP%year%%month%-%server%.zip E:\Logfiles\Http%server%\ex%year%%month%*.log

Using PACL i wanted the ZIP created to span in 1 GB chunks.

The result is that when using PACL it looks fine but no ZIP is created and the source files is deleted.

/URban

Is there a switch (undocumented) or some other method by which I can prevent PACL from deleting and recreating an archive if one already exists with the same name? Presently PACL doesn’t even prompt to delete, it just does it before creating the archive.

I would rather not find that I need to use an IF statement to check the existance of the file.

No, but all the work will be transparent (without any windows). Plus, you will have enought options to set in Outlook Options dialog.

Hi,
First of all, thanks for your answer !

we are going to take the problem by another way.
I am writting a program which terminate with compressing files in a subfolder I create in a folder the user choose.
I want to be able to let the user choose the program he want to compress : WinZip, WinRar, PowerArchiver, …/…
even I have to adapt my Test.bat.

If, for example, the user choose the folder C:\Dir01\Dir02 to work,
I create a subfolder Dir03,
where I write the Test.bat which call pacomp (with his full path -in the path or not-)
and where I write Test.txt which list the files I need to compress, assuming the root directory is Dir02.
So, Test.txt look like this :
File01.txt
File02.txt
Dir03\File03.txt
WinZip and WinRar works correctly, like I wait they must do
so in the Test.zip I get
Name__________________________________Path
File01.txt____________________________
File02.txt____________________________
File03.txt____________________________Dir03\

PaComp do not work like this, and more :
I reproduce the test you do :
working with Test.txt, Test.bat in the same folder as File01.txt
in the Test.zip I get this :
Name__________________________________Path
File03.txt____________________________Dir03
File01.txt____________________________Dir01\Dir02
File02.txt____________________________Dir01\Dir02\

and of course, when I unzip Test.zip, it create a folder Dir03 and a folder Dir01 with a subfolder Dir02
so I thing there is a bug in the command -p.

May be I do not use PaComp like it should be use, but I know exactly what I want to do
and I do not find the way PaComp can do it.

If you have a suggestion you are welcome.
Or may be review the -p command…

Thank you TBGBe!

My program wasn’t generating the “if exist *.zip” in the batch file. I added that and it works like a charm! I appreciate your assistance!

See http://www.powerarchiver.com/forums/showthread.php?t=100
and IVAN’s response for a BATCH file workaround.

The command -m is “move files to archive [files only]”
See MANUAL.TXT for PACL.

I don’t know of an PACL option/command to delete folders.
(
If you are careful and brave, create a batch file with :-
pacomp -m -c2 -w -p -r c:\to_burn\ArchiveSink.zip “c:\temp*.*”
RMDIR /S C:\TEMP
)

Archives >4GB are not (yet) supported.
See http://www.powerarchiver.com/forums/showthread.php?t=194

Right now - there is no way. -k options is only if you are updating already existing archive.

We will take care of this feature for next version.

Thanks!

The issue will be fixed in next release - 4.00 BETA 2.

We have added one more check for next version (4.00 BETA 2) - now even if you use quotes it will work.

Thanks!

The issue will be fixed in next release - 4.00 BETA 2!

Definetelly not for 4.0.

We shall see later - currenty PACL is very usefull because it doesn’t need any DLLs to work with most archives. If we shall do on some big engine changes then probably we should have to distribute DLLs for some formats and then it becames more complicated for users who use PACL in their own programs for some operations.

@iwod:

PACL and PA?

Apart from the missing interface of cause. So in Theory everything done with PA can be done with PACL?

It is separate tool really, everything is completly new/different than PA. PA has many more tools and options, while PACL has some features that are specific to command line… Both are advanced in their own right.

thanks,