FileForums - LOLZ Unpacking problem

FileForums (https://fileforums.com/index.php)

- Conversion Tutorials (https://fileforums.com/forumdisplay.php?f=55)

- - LOLZ Unpacking problem (https://fileforums.com/showthread.php?t=104164)

LOLZ Unpacking problem

I can pack LOLZ.

Problem is:

When I unpack it, it calculates, but nothing is in the directory.

What does the Arc.ini have to look like so that you can unpack with lolz?

You need cls.ini and

Quote:

[lolz]
Bufsize=512k
transfer_ReadBufSize=512k
transfer_WriteBufSize=512k
MaxThreadsUsage=100%
MaxMemoryUsage=75%-10m

+
CLS-LOLZ.dll
cls-lolz_x64.exe
cls-lolz_x86.exe

Unfortunately, unpacking my xxx.bin, which was packed with Arc and Srep + LOLZ, does not work.

I use Tiny-Toolz as a GUI.

The entries for LOLZ in the Arc.ini are:

[External compressor:lolz]

header = 0
packcmd = "lz\lolz_x64.exe" -mt4 -mc256 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = "lz\lolz_x64.exe" -mt4 -mc256 $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

[External compressor:lolzi]

header = 0
packcmd = "lz\lolz2_x64.exe" {options} $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = "lz\lolz2_x64.exe" {options} $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

I have now created a file with the name as specified, but unfortunately Unarc does not unzip my bin. A directory is created in the unpacking directory, but it is empty.

There's a bug somewhere. But which one.

OK.

And how do you work with the CLS version and Arc?

Would someone help me a little?

You need CLS-LOLZ.dll + cls-lolz_x64.exe + CLS.ini with above content.

You don't need lolz in arc.ini for unpacking.

Now I have to.

Would someone please make these files available to me and then tell me how I can use them via Arc?

Quote:

Originally Posted by biotec2k8 (Post 490679)

Now I have to.

Would someone please make these files available to me and then tell me how I can use them via Arc?

Here,

Very good. Thanks alot.

Now I can understand how unpacking and packing works properly.

It has been written that SREP + LOLZ is a very effective combination. But does the script unpack even if I mix SREP while packing?
>> if I include srep, then I also have to use the cls-srep.exe and a cls-srep.dll and make the appropriate entries in the csl.ini, right?

I can Pack a Drawer with LOLZ an Srep+LOLZ. All Clear. Output Files writing correct.
The next Problem is:

When I run the unpack.bat from lolz, I get a read mapping error. And then Arc breaks off.

When unpacking the srep + lolz file, Arc tells me that it would not recognize the compression.

I think there is an error in the ini file in both menthodes.

Quote:

Originally Posted by biotec2k8 (Post 490683)

To decompress "Srep + Lolz", you can use this as follows.

Code:

CLS.ini



[Srep]

Bufsize=24m

transfer_ReadBufSize=512k

transfer_WriteBufSize=512k

Memory=80%-512m

TempPath={app}



[lolz]

Bufsize=512k

transfer_ReadBufSize=512k

transfer_WriteBufSize=512k

MaxThreadsUsage=75%

MaxMemoryUsage=75%

ldmfTempPath={app}

ldmfMaxMemoryUsage=32m

ldmfDeleteTmp=0

It's common for a ###.bat file to have a decompression error for cle-lolz.dll. This's because cls-lolz_x64.exe creates temp files in the Windows temp directory. Therefore, for whatever reason, it requires the permission of the administrator.

So, run the Unpack.bat file as an administrator, then it will be correct. (tip from @Masquerade)

Yes, Working. Thanks

Is there actually the possibility to pack LOLZ via GUI and to unpack it again?

Found from Krinkels forum its attached file, from WinXP users: lolz uWinXP.rar

Win XP compatible compressors?

Quote:

Originally Posted by KaktoR (Post 490644)

You need CLS-LOLZ.dll + cls-lolz_x64.exe + CLS.ini with above content.

You don't need lolz in arc.ini for unpacking.

My code working from XP SP3 use Tiny Compressor v0.2 or 1.4 created masked compressed archives.

Example is compression schemes:

v1: "xZlib+srep+lzma:176mb:normal:bt4:273:mc1000000000 :lc8"
v2: "xZlib+srep+lolz:dtb1:dtw1:dto1:dtd1:mtt1:mt4:d64m :fba4096:mc1023"

arc.ini:

Code:

[External compressor:xZLib]

header    = 0

unpackcmd = "XT" d:precomp:t50p,t4:zlib - - <stdin> <stdout>



[External compressor:srep]

header    = 0

unpackcmd = "srep" -d <stdin> <stdout>



[External compressor:lolz]

header    = 0

unpackcmd = "cls-lolz_x86" {options} $$arcpackedfile$$.tmp $$arcdatafile$$.tmp



[External compressor:precomp]

header    = 0

unpackcmd = "{compressor}" -o$$arcdatafile$$.tmp -r $$arcpackedfile$$.tmp

cls.ini:

Code:

[Srep]

Bufsize=24m

transfer_ReadBufSize=512k

transfer_WriteBufSize=512k

Memory=25%

TempPath=.\



[lolz]

Bufsize=512k

transfer_ReadBufSize=512k

transfer_WriteBufSize=512k

MaxThreadsUsage=75%

MaxMemoryUsage=25%

TempPath=.\

ldmfMaxMemoryUsage=32m

ldmfDeleteTmp=0



[Precomp]

Memory=128m

TempPath=.\

Any help from limitate biggest memory footprint from decompression?? (From old PC's. My 2.94GB's archive with v1 compression methods eats 1.2-1.25GBs memory footprint. 1GB RAM available from the very old PC. Targeting reduction to max. 512+ MB's from decompression. Use cls-ini or Arc.ini with extra parameters?? (Any info: The archive, compressed 9.41GB's *.ACE files to 23.1GB's data exploded with xtool and chrunched to 8.5GB+ with srep and compressed with lzma methods to lower than 3GB's size.) Use v2 compression schema archive creating in progress. (Use laptop with 8GB's RAM and Pentium B960 2.2Ghz CPU) The 9.4GB's data will compress by SREP+LZMA methods 4.8+ GB's archive. Nice difference.

Example from: Arc.exe: -ld64m and XT.exe: Add the -dm1 switch and srep.exe: Added -ia- and/or -mem25p switches? Its works?

I tried FreeArc once. Unfortunately it doesn't work there like that. I get the read mapping error there also when compressing.

The solution was just an extra BAT. It then turns the directory into a CAB file and if you want to unpack it, you have to unpack it with an Unpack.bat. And I have to run this Unpack.bat as an admin. Otherwise I get an error there too.