PrecompX v2.0.0.1
 

What's new

• Added detection mode.
• Users can select either PrecompX for decompression, or the CLS Library.
• Some improvements.

Commands:
a = Compress
x = Decompress

Options:
-c# = Chunk Size [Compression Only]
-t# = Threads (as a number or as a percentage)
-method = Detection Method [Compression Only]

Detection Methods:
Usage:
PrecompX.exe a -c# -t# -method - - <stdin> <stdout>
PrecompX.exe x -t# - - <stdin> <stdout>

Arc.ini:

For Compression:
arc.ini
PrecompX.exe
precomp32.exe
precomp64.exe

For Decompression:
arc.ini
PrecompX.exe
precomp32.exe
precomp64.exe

or the CLS library for decompress

cls.ini
cls-precompx.dll
cls-precomp_x64.exe
cls-precomp_x86.exe


check the first post...

Great tool. Thanks for your hard work. I want to ask something:

Normally Precomp.exe first decompress given file, then compress it with BZip2. We can use -cn syntax and block it. So we can compress it further with lzma or another compressor. Can we use -cn syntax in PrecompX? Or any other way so precomp must not compress file?

PrecompX already uses "-cn". ;)

if you want to deal with more options, try mine cls-precomp.dll (multithreaded). so i have given you the facility with it to change the options used in Precomp.

cls-precomp - any version (Multithreaded)

Hi friend
Precomp can compress zlib streams like xtools and ztools. Also it can compress the .png or .jpeg files by the help of packjpg.dll file. It can compress zip and gif files. More effective tool 🤗

I am wondering about bzip2. You can give the link for it. Also give some examples, how to use it?

This cant be right, if it takes 4h to recompress 17gb with z/x-tool you must be doing something wrong. Probably invoking some obscure and completely unnecessary brute mode etc. Compare with similar settings, x/z-tool also have its own options and for 99% time all you need is either :m1, or :m2 - aka :high. Thats it. I can get at least around ~20mb/s on m2/high, tool is extremely fast and have no reason to drag like your results show.

^
I think this is one of the games for which xtool has problems because of odd streams or something like that, if I remember correctly.

And one other thing. For to me unknown reasons many of you use wrong terms regarding data inflation, calling it compression and leading to confusions. When you compress data as a whole, you are in fact decompressing those streams in the process, that particular part is *not* compression but actually decompression. To avoid confusion with global data compression, call it inflation. You are inflating the data within global compression process - as a preprocess.

This is confusing because then you have inflator tool with parameters like "compress" and "decompress", guess which flag is used when, exactly opposite as when it should. It should be "e" or "c" during global data unpacking, and "d" during global compression, because that is what is actually happening. Tool is its own entity/command, working on its own and is not superwising rest of the chain in the process and doesnt know about it, it just push the data through the pipe.

Major issue was founded friend. I am using 4 thread pc to repack. Decompression on 4 thread pc or lower pc works well. But higher thread pcs are showing this error like unarc.dll error code: -1. Also no use the -hp to encrypt the file.This error comes with Cls and precomp

https://i.ibb.co/sRT0h02/unknown.png

I am trying with t4 or threads=100%, But it still shows a error

this will happen when you use more than the threads used in the compression. so make sure the threads used for decompression are less than or equal to the threads you used in the compression.

ex:
set compression threads = t4
and
decompression threads = t4

then your problem will be solved.

Cls decompression error
 

Sometimes the inflated or deflated streams higher than 1 Gb per thread. Example like 128Mb=>1 Gb. At the moment the cls decompression was freezed without showing any errors. Please fix this errors

Somehow you can place TEMP, or rather PrecompX_temp in another area, for example, on a virtual hdd in RAM.