FileForums

FileForums (https://fileforums.com/index.php)
-   Conversion Tutorials (https://fileforums.com/forumdisplay.php?f=55)
-   -   XTool - Successor of ZTool (https://fileforums.com/showthread.php?t=101729)

drsamonline 10-12-2020 22:21

Nice thank you

Cesar82 19-01-2021 20:51

Could someone tell me if to use the "crilayla" method I need to insert a library in addition to "CriLayla.dll" next to XTool.exe (32 bits).
I mean if I configure Arc.ini in this way I need to have in the "CriLayla " folder plus any files besides "CriLayla.dll" and "XTool.exe" (32-bits)?
Code:

[External compressor:xcrilayla]
header    = 0
packcmd  = "CriLayla\XTool.exe" e:precomp:t100p,c128m,v:crilayla - - <stdin> <stdout>
unpackcmd = "CriLayla\XTool.exe" d:precomp:t50p - - <stdin> <stdout>


Masquerade 19-01-2021 23:43

@Cesar
That is all you need: xtool x86 + crilayla.dll

I don't know what the v is for in your packcmd though:
Code:

e:precomp:t100p,c128m,v:crilayla

Cesar82 21-01-2021 13:06

Quote:

Originally Posted by Masquerade (Post 489929)
@Cesar
That is all you need: xtool x86 + crilayla.dll

I don't know what the v is for in your packcmd though:
Code:

e:precomp:t100p,c128m,v:crilayla

I have no idea of this "v" as a parameter.
I looked at the older sources codes and since version "CIUv2 v2.0.3.9 U15.2 (2018-10-28) in "UltraARC 2900 R6" (modifyed by Simorq) has this parameter "v" in crilayla method.
Until the version "UltraArc 2900 R5" (CIUv2 v2.0.3.9 U15.1 (2018-10-06)) there was no such parameter "v" in the cirilayla command (Only: XTool e: precomp:t100p:crilayla - - <stdin> <stdout>)
In the image you can see which original parameter has been replaced.
If anyone knows what this parameter "v" refers to please post it here.
https://i.imgur.com/5CCe7jk.png

KaktoR 21-01-2021 13:50

v is for verify if I remember correctly. Simorq posted somewhere over here about this (or someone other).

Edit: https://fileforums.com/showpost.php?...&postcount=380
Edit 2: https://fileforums.com/showpost.php?...&postcount=377
...

Cesar82 22-01-2021 10:38

1) Can anyone tell me for sure if the zstd codec works with old 32-bit XTool?
Putting 32-bit libzstd.dll together with XTool v012 (or earlier) and running XTool displays the message "zstd: not loaded" (see image).
With the 64-bit version (using the x64 libraries) the zstd codec is loaded normally.

2) The image also says that "oodle" has not been loaded and the library "oo2core_5_win32.dll" is together with XTool, this is normal, or does it not support Oodle in the 32-bit version despite Razor12911 having shared the library in the x86 folder?

https://i.imgur.com/4DizJDP.png

Razor12911 22-01-2021 10:44

The 32-bit libzstd from this xtool package requires libgcc_s_dw2-1.dll, think of it as programs requiring Visual C++ Runtime libraries, but this one requires one from gcc compiler, not sure why.

Try finding the matching pair from here
https://github.com/facebook/zstd/releases

Cesar82 22-01-2021 11:44

Quote:

Originally Posted by Razor12911 (Post 490005)
The 32-bit libzstd from this xtool package requires libgcc_s_dw2-1.dll, think of it as programs requiring Visual C++ Runtime libraries, but this one requires one from gcc compiler, not sure why.

Try finding the matching pair from here
https://github.com/facebook/zstd/releases

I looked for everything on the link page and didn't find it.
I don't even know the version of libzstd.dll that the old XTool used.
However I found the library informed at:https://pt.dll-files.com/libgcc_s_dw2-1.dll.html
Both link files allowed to load the codec. I tested it and it worked perfectly zstd with StarWars BF2 (Ratio 129.47%)

@Razor12911, does the oodle method need anything to load with old XTool or does it not support oodle in 32-bit version?

KaktoR 22-01-2021 11:52

@Cesar
I suggest to not use oodle with old xtool at all due to bugs.

Prince4 07-04-2021 04:35

Hi all, i've been away from this stuff for quite some time, but i just wanted to get back into this, so i'm trying to run XTool with Freearc but everytime freearc runs it crashes instantly with XTool, can someone help me out as to why is this happening?

Other methods are working fine (Precomp,PZLib,SRep,Delta,Lolz)

These are the parameters :

Code:

Arc_mar14.exe a -ep1 --dirs -r --archive-comment="%comment%" --workdir=C:\_Out\$$work_dir$$\ -mxtool+srep+lzma:a1:mfbt4:d256m:fb128:mc2000 "C:\_Out\Setup-XT+S+L%1.Rpk" "%dir%\*"
Here is my Arc.ini :

Code:

[External compressor:xtool]
header    = 0
packcmd  = xtool.exe precomp -mzlib -c32mb -t100p --dbase - - <stdin> <stdout>
unpackcmd = xtool.exe decode -t50p - - <stdin> <stdout>

[External compressor:srep]
header = 0
packcmd  = srep64 -m5f $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = srep64 -d -s $$arcpackedfile$$.tmp $$arcdatafile$$.tmp


Masquerade 07-04-2021 09:52

Prince4

Your issue lies in the packcmd, xtool in this topic does not support --dbase parameter.

I think you may be confused with new XTool, which can be found in this topic: https://www.fileforums.com/showthread.php?t=102832

Prince4 07-04-2021 22:31

Quote:

Originally Posted by Masquerade (Post 491239)
Prince4
Your issue lies in the packcmd, xtool in this topic does not support --dbase parameter.
I think you may be confused with new XTool, which can be found in this topic: https://www.fileforums.com/showthread.php?t=102832

Ah i am using that version (0.3.9), i just posted on the wrong thread. But i can verify that program does have that option.

Also just tested, i added "=temp.db" in that option on the packcmd and the compression started but crashed in srep (bad media=?) at 0.2% where FArc is supposed to make a zip file. I'm using SRep 0.393a.

sanniasajive 05-11-2021 17:15

thank you razor, you made my life much simpler!!

JaleSwiftpaw 03-05-2022 12:11

Thanks, I've been looking for this.

Gcr27 22-04-2023 18:16

hello my game use a zlib compression files cart fury champioship racing ps2 have a program or software to decompress files wms,zif files format


All times are GMT -7. The time now is 17:28.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
FileForums @ https://fileforums.com