PDA

View Full Version : LOLZ Unpacking problem


biotec2k8
28-02-2021, 11:44
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?

dixen
28-02-2021, 12:59
You need cls.ini and

[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

biotec2k8
28-02-2021, 14:51
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.

Masquerade
28-02-2021, 23:57
You need cls-lolz.

biotec2k8
01-03-2021, 01:32
OK.

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

Would someone help me a little?

KaktoR
01-03-2021, 03:03
You need CLS-LOLZ.dll + cls-lolz_x64.exe + CLS.ini with above content.

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

biotec2k8
02-03-2021, 01:07
Now I have to.

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

Ele
02-03-2021, 05:11
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,

biotec2k8
02-03-2021, 10:28
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.

Ele
02-03-2021, 13:17
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.

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

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)

biotec2k8
07-03-2021, 02:31
Yes, Working. Thanks

biotec2k8
12-03-2021, 08:15
Is there actually the possibility to pack LOLZ via GUI and to unpack it again?

kj911
25-04-2021, 08:00
Found from Krinkels forum its attached file, from WinXP users: lolz uWinXP.rar (https://krinkels.org/attachments/lolz-uwinxp-rar.5264/)

Win XP compatible compressors?

kj911
27-04-2021, 11:06
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:

[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:

[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?

biotec2k8
30-04-2021, 02:10
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.

Masquerade
30-04-2021, 08:06
biotec2k8
Read mapping error comes in decompression when you don't have admin elevation.

Run decompressor as admin, and problem goes away. :D

biotec2k8
02-05-2021, 03:04
I know ... ^^ ... but nothing with freearc ... unfortunately

kj911
14-11-2021, 06:57
Aaaarrghh! Created LOLZ packed ARC archive with following switches and don't decompresseable! Its the best results from my game recompression. This errors use the oh14 switch or gm01 or lm4? CLS.ini issue?? (Any file its works.) LOLZ-bug?

The test package: https://www.mediafire.com/file/j5z148wuxn32w66/Data1.bin/file

ERROR: general (de)compression error in lolz:dt:dtb1:dtw1:dtm1:dto1:dtd1:mtt1:mt4:d128m:tt 32:oh14:gm01:lm4:fba4096:mc1023

The switches posted in the topic (https://fileforums.com/showpost.php?p=494890&postcount=2647)

Any tips from fixing??

UPDATE: Tested more switches combination use gm01:lm4:oh12/14 trio. Found the bug! Use lm0 its works! Use lm1/2/3/4 with or without oh12/14 and gm01 switches crashing now!! Tested some cls.ini conmmands, not good. Tested any cls-lolz.dll file, its no good.

Doooh! 2.80GB size better than 2.92GB and require more 30+ MB gain from fit the DVD5 size the game.
Will hope find correct and best results.

The my not decompresseable package send to member ProFrager from testing and searching error.

LOLZ v21a7 its better compression than v22c4b???

kj911
07-03-2023, 08:43
Any idea tricking this "cls-lolz" usage from virtual file system?? (Enigma VBOX)

All three files (cls-lolz.dll and two EXE) packed in to FreeArc SFX file, within any decompressors, not fully working. (cls-srep+Xtool)

Execute modded SFX'ed archive, run x86 OS, its works! (WinXP and probably works from newest 32bit OS) Executed Win7 SP1 x64 OS, not works! Its says, classic, "Failed to start cls-lolz_x64.exe" error message. The cls-lolz_x64.exe file its presents from embedded EXE file. Separately copy the real file to located in SFX EXE from to one directory, its ok!

Virtual registry systems not tested in last time, from the testing Can't read mapping error. (Adding the fix (https://fileforums.com/showthread.php?p=471133&highlight=read+mapping#post471133).)

UPD: This virtual registry based fix, probably works, solve Run As admin methods, from executing. (Says qoute, from running or not the EXE file, see more info from UPDATE2 sections from post.)

FreeArc internals (exe, tta, delta, lzma and more..)
Xtool 0.12 (zlib only, zlib1.dlll and two raf/hif dll's injected.)*
SREP (with limitations! Used ProFrager's v0.3.3 cls-srep.dll)
MSC (with TAK audio, DXT optimization, MP3, BMF-based BMP/DDS not tested.)
LOLZ (cls-based and works x86 ONLY! Fixing tricks??) or DLZ (this cls-filter based.)

Usage? copy /b freearc.sfx.exe + anyarchive.arc sfxtest.exe

*Named in xtool "xZLib" ! Not, 'zL' or 'Zl', this 'ZL' !

UPDATE2: Attachments updated. (This LOLZ variants, EVB and EXE file.) These registry tricks, not properly handle, running the any EXE files to elevated admin process! Its one works methods from last time, these classic selects "RunAs Admin" options from right-click menu. The "Failed to start cls-lolz_x64.exe" error, its finely easily fixed. The x64 exe removed from EXE package and manuallly edite "cls-lolz.dll" file any Hex Editor... Open the dll in editor and fin these strings "_x64" replaced to "_x86" and save it.

The registry values from Win7 SP1....

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Policies\System]
"ConsentPromptBehaviorAdmin"=dword:00000005
"ConsentPromptBehaviorUser"=dword:00000003
"EnableInstallerDetection"=dword:00000001
"EnableLUA"=dword:00000001
"EnableSecureUIAPaths"=dword:00000001
"EnableUIADesktopToggle"=dword:00000000
"EnableVirtualization"=dword:00000001
"PromptOnSecureDesktop"=dword:00000001
"ValidateAdminCodeSignatures"=dword:00000000
"dontdisplaylastusername"=dword:00000000
"legalnoticecaption"=""
"legalnoticetext"=""
"scforceoption"=dword:00000000
"shutdownwithoutlogon"=dword:00000001
"undockwithoutlogon"=dword:00000001
"FilterAdministratorToken"=dword:00000000

All changed to "0" excepts, scforce.., shutd.., undock.. settings, not work and resolve run the EXE files with elevated admin process.