XTool - Successor of ZTool

[Razor12911]

give sample and the extractor, and I'll take a look at it.

[KaktoR]

Dragon Age Inquisition (https://drive.google.com/open?id=1QtGK5AxFiDy8flZWod_fwCKh_PdMJ10-)


Skyrim SE (https://drive.google.com/open?id=1nFvuZ8OpHSiGWx5wXKnvPzRnsTqyQH_a)
Skyrim SE BSA extractor (https://www.nexusmods.com/skyrimspecialedition/mods/974/)

[doofoo24]

@Razor12911 what about encrypted game files like fifa/project car/crysis :D:D:D

[Razor12911]

@Razor12911 what about encrypted game files like fifa/project car/crysis :D:D:D

https://fileforums.com/showthread.php?t=102524
https://fileforums.com/showthread.php?t=102461

as for Crysis, if I had an idea as to how it was encrypted, I would have made a tool for it

[doofoo24]

i know the tools for fifa/project car...
i thought the new xtool will work on encrypted files like QuickBMS :o

[Razor12911]

it could, but as of right now I am busy optimising the code and getting rid of old bugs, main focus is more speed and less cpu/mem usage

[darkwolves]

Don't expect good ratio, LZNA is the best compression algo in Oodle family.

yes i know this but some compression is better than no compression at all the way i see it

[elit]

@everyone
I'm now focusing on the main code of XTool 2019, so now it's a good time to mention all the bugs the current xtool has so I can try to avoid as I write the new code from scratch and what new features would you like to be added in the upcoming release.

Perhaps 2 thing's left are lzss and nintendo's yaz0. Very important for some Jap games and especially console roms.
EDIT: also xcompress and endian versatility.

EDIT: Also codecs help is missing, for instance xtool can utilize same :m2, :high, etc. parameters for zlib like ztool does, but I wouldn't know if I was not familiar with ztool from the past.

[amin fear]

Why ZTOOL needs "Visual C++ MSVC**.dll" files for unpacking archives ? is there any workaround for this limitation ?

But XTOOL is standalone & stable.

[deepshit]

Why ZTOOL needs "Visual C++ MSVC**.dll" files for unpacking archives ? is there any workaround for this limitation ?

But XTOOL is standalone & stable.


Xtool needs VC++ 2010.

[Razor12911]

no it doesn't, it's the libraries that come with precompressor that do

[amin fear]

no it doesn't, it's the libraries that come with precompressor that do

This clarification is true , i have tested both XTOOL & ZTOOL on clean fresh operating systems & only ZTOOL needs Visual C++ 2010 & 2013 libs while compressing & decompressing

[IgorKolesnik]

But can I somehow do this to put the folder to check xtool and the files in which the zlib... streams were hoped for example were displayed in a separate list?

[elit]

Hi Razor, I apologize for not having enough time recently to participate despite my promises, but now I have something to share since I am repacking FFXIII series. Looks like ztool is still more reliable choice for now, at least when it comes to zlib. xtool is not detecting/inflating zlib-compressed file from FFXIII at all, it does inflate at deflate :m2 option but even then slightly less than ztool. Ztool on the other hand both zlib(:m1) and deflate(:m2) reliably inflate file, with :m2 even slightly more(but even :m1 inflate 5mb more than xtool :m2). Anyway, here goes screenshots:
25148
25149
25150

This is with v0.12, I don't know if it was fixed already or not. Anyway hope it help & best regards, if I find more during repacks I will post.

EDIT: Noticed yet another xtool thread. Not sure why there are so many for same tool but whatever, so I tried that version with zlib and rzlib options and it does seem to be working. Although cmd command piping is broken in that version and so doesn't work with lzscan's stdio (aka: "cmd | xtool | cmd").

[Razor12911]

EDIT: Noticed yet another xtool thread. Not sure why there are so many for same tool but whatever, so I tried that version with zlib and rzlib options and it does seem to be working. Although cmd command piping is broken in that version and so doesn't work with lzscan's stdio (aka: "cmd | xtool | cmd").

Hi, so does it work now? the New xtool I mean.

As for stdio, well I didn't change anything there so pipes should work because if that was the case then xtool should also not work for Freearc

[elit]

Hi, so does it work now? the New xtool I mean.

As for stdio, well I didn't change anything there so pipes should work because if that was the case then xtool should also not work for Freearc

I can confirm the issue:
25157
25158
On second pic you can see commented(green) line - that was for xtool 0.12 and it would work. This is script from lz_scan which if you need as whole tool to check you can download on this site. On top of it, I can also confirm that unlike v0.12, v1908 will inflate if used on files directly. About 1mb less than ztool, but that's not a big deal now.

So yes, v1908 will inflate unlike v0.12 without needing deflate, but also broke pipes.

[Razor12911]

you have to specify - - for stdio

I only see "xtool.exe precomp:zlib", should be "xtool.exe precomp:zlib - -"

[elit]

you have to specify - - for stdio

I only see "xtool.exe precomp:zlib", should be "xtool.exe precomp:zlib - -"

Those " '|' (xtool) '|' " characters are pipes, that's how you pass data between programs and its is well known standard. Normally, you wouldn't never use '-'-' additionally in such case but I will try something like "cmd | xtool - - | cmd" later and let you know. Again v0.12 and ztool work fine like this.

[elit]

Ok I can confirm that if I use "cmd | xtool precomp:zlib - - | cmd" then it work. Although '- -' should normally not be necessary in this type of syntax, at least it works. Thank you for a great tool.

[Razor12911]

Those " '|' (xtool) '|' " characters are pipes, that's how you pass data between programs and its is well known standard. Normally, you wouldn't never use '-'-' additionally in such case but I will try something like "cmd | xtool - - | cmd" later and let you know. Again v0.12 and ztool work fine like this.

Dude, I know that "|" is for pipe, but - - is for stdio in terms of xtool

The usage for xtool goes like this

xtool command input output
"-" denotes stdin/stdout depending where you put it.

This is how I have written it


if ParamArg[2] = '-' then
Output := THandleStream.Create(GetStdHandle(STD_OUTPUT_HANDL E))
else
Output := TFileStream.Create(ParamArg[2], fmCreate);

Ok I can confirm that if I use "cmd | xtool precomp:zlib - - | cmd" then it work. Although '- -' should normally not be necessary in this type of syntax, at least it works. Thank you for a great tool.

The reason I have added it as "-"

is because what if you can accept input as stdin then the next program requires an existing file
it then becomes something like this

xtool command - output

or if input is a file and output is required as stdout
it becomes
xtool command input -

if pipes are involved it means stdin and stdout takes place which is why it is
xtool command - -

[elit]

Yes I understand and its not a big deal so feel free to leave it as is.
From what I know common practice in apps is to assume both stdin and stdout if both filenames are omitted, while if only one stream is std as you pointed out then '-' have to be used to differentiate.

[devil777]

Uhh bosses is the v9 of xtool is more stable or better or what than other version of the tool...cause many repacker been using this version of the tool

Thanks in advance for the desired answer

[KaktoR]

Uhh bosses is the v9 of xtool is more stable or better or what than other version of the tool...cause many repacker been using this version of the tool

Thanks in advance for the desired answer

https://fileforums.com/showpost.php?p=481383&postcount=484

[FitGirl]

Uhh bosses is the v9 of xtool is more stable or better or what than other version of the tool...cause many repacker been using this version of the tool

Thanks in advance for the desired answer
It's the most stable atm. Xtool 2019 is currently in active development, has bugs and I wouldn't recommend it for daily use or for public repacks. Wait until Razor will fix all major issues.

[devil777]

AtAt first of all thanks mr.Kator for youpc answer indicating reply... and also thanks Mrs.Fitgirl..

[devil777]

Uh sorry to irritate but is v11 of the tool even stable to do things?I mean to unpack archives which has been packed with v9 of xtool

Wishing for an exact answer and thanks in advance

[KaktoR]

Yes.

[doofoo24]

last time i used different xtool for pack/unpack i got error...
better to use the same xtool ver for pack/unpack...

[KaktoR]

I have many archives with xtool 0.9 and i can unpack them with 0.12 without problems.

[doofoo24]

if i remember correctly it was on mass effect 3 i got error during install after checking i noticed that xtool was different ver form the one during packing...
but i don't remember which ver, maybe the opposite of what you did i packed with newer ver and using old ver for unpack...

[yasitha]

I had a problem with
Ghost Recon Wildlands (.Forge files)
i have check it with GFS, then i found the game had lzo streams. But when i try xtool: lzo on game files,
it won't decompress and I don't know how to decompress it.
ANYONE CAN HELP ME PLEASE?

[KaktoR]

Try AFR.

[magicball]

thank you

[Illume]

the headers are placed elsewhere bro. The files you gave me do have signs of lz4hc being used but there are no headers for me to reference for information as to where streams start and where they end. This will be a job for a universal lz4 precompressor but not at the moment because lz4 is a piece of shit when it comes to that department, as you can see in the screenshot I uploaded.

gives two byte header "F2 00" that I have no idea what it means then followed by parts of the original data, "44 44 53 20" which is a header for a dds texture which means lz4hc was indeed used but that's it. no game engine headers located or anything that could help for me to be able to add support.
headers are at the end of file
zenhax.com/viewtopic.php?f=9&t=1663
and pak files are splitted
like:
Textures.pak
Textures_1.pak
Textures_2.pak
it is one big archive

[samer1990]

whe i try to pack the files arc.exe get crash
how to solve this issue :(

[jenning]

help please solve the problem. When using xtool for large files, this error occurs during installation.
I use this method: xtool+srep+delta+lolz
options xtool:
[External compressor:xtool]
header = 0
packcmd = xtool e:precomp:t2:zlib - - <stdin> <stdout>

bat file:
arc.exe a -w.\ -ep1 -dses --dirs -s; -lc- -di -i2 -r -mxtool+srep+delta+lolz data1.bin "packeddata2\*"

xtool v011

https://i1.imageban.ru/out/2019/03/13/8e1215a0bf73996d9f41dab3b81b57d7.jpg


I'm having the same error when using zlib, I have tried all xtool versions x86/x64, all combinations old+new/same versions, compressing with only 1 thread, with different chunk sizes.

Any ideas ?

my compression cmd:
arc a -ep1 -ed -r -w.\ Data\Setup-1.bin -mxprecomp+srep_x64:m3f+lolz:d256m:mtb256:mc1023:mt t1:mt8 "D:\TEST\TESTGAME\*"

my arc.ini:
[External compressor:xprecomp]
header = 0
packcmd = xtool.exe e:precomp:c128mb,t1:zlib $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = xtool.exe d:precomp:t1 $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

[External compressor:srep_x64]
header = 0
packcmd = srep_x64 {options} -s907374182400 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = srep_x64 -d -s $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

[External compressor:lolz]
header = 0
packcmd = "lolz_x64" {options} $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = cls-lolz_x64.exe $$arcpackedfile$$.tmp $$arcdatafile$$.tmp
datafile = $$arcdatafile$$.tmp
packedfile = $$arcpackedfile$$.tmp

[KaktoR]

Try percent instead of threads for xtool

packcmd = xtool.exe e:precomp:c128mb,t50p:zlib $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

From 1 to 100

[logboy666]

Same thing, using xtool v.012 x86 for packing and unpacking

[jenning]

Did not help, same error..

[jenning]

This are my tools and setup, uploading test files too.

[jenning]

Error when unpacking at 17.1%, using tools uploaded on the previous page

https://i.imgur.com/kSERhek.jpg

[KaktoR]

Sims 4, right?

You have to exclude these two files

Game\Bin\Core\QtWebKit4.dll
Game\Bin_LE\Core\QtWebKit4.dll

I wasn't able to unpack this files either. Just include this files into a seperate archive or include to Setup.exe

[jenning]

Would never guess the compressor had problem with this certain files and not due to my configs. Thank you! was trying to fix it whole day...

I have only one issue to solve, the progress bar for lolz_x64 is not working with my old setup. Any suggestions what files / code need updating ? by my own it will probably take me a week to find the issue..

[KaktoR]

XTool 0.12 stuck compression on Anno 1800 latest version (zlib codec).

[PsYcHo_RaGE]

I'm having the same error when using zlib, I have tried all xtool versions x86/x64, all combinations old+new/same versions, compressing with only 1 thread, with different chunk sizes.

Any ideas ?

my compression cmd:
arc a -ep1 -ed -r -w.\ Data\Setup-1.bin -mxprecomp+srep_x64:m3f+lolz:d256m:mtb256:mc1023:mt t1:mt8 "D:\TEST\TESTGAME\*"

my arc.ini:
[External compressor:xprecomp]
header = 0
packcmd = xtool.exe e:precomp:c128mb,t1:zlib $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = xtool.exe d:precomp:t1 $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

[External compressor:srep_x64]
header = 0
packcmd = srep_x64 {options} -s907374182400 $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = srep_x64 -d -s $$arcpackedfile$$.tmp $$arcdatafile$$.tmp

[External compressor:lolz]
header = 0
packcmd = "lolz_x64" {options} $$arcdatafile$$.tmp $$arcpackedfile$$.tmp
unpackcmd = cls-lolz_x64.exe $$arcpackedfile$$.tmp $$arcdatafile$$.tmp
datafile = $$arcdatafile$$.tmp
packedfile = $$arcpackedfile$$.tmp



[External compressor:xzlib]
header = 0
packcmd = xtool.exe e:precomp:c128mb,t80p:zlib $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

[External compressor:srep]
header = 0
packcmd = srep_x64.exe {options} $$arcdatafile$$.tmp $$arcpackedfile$$.tmp

[External compressor:lolz]
header = 0
packcmd = lolz_x64.exe {options} $$arcdatafile$$.tmp $$arcpackedfile$$.tmp


perfect!

[Razor12911]

Can you guys give a list of issues xtool has, I'll try to patch them. Also if possible provide samples.

I'm giving the project another try since it seems like people are still interested in it.

No promises, even with quarantine going on, it should mean that I have time to make changes but then I use this time to sleep (Lazy af these days, not sure why) XD

[KaktoR]

- Big input with oodle codec does not work
> xtool just won't precompress all files
- The same for FC5 lz4hc codec
> File by file works, all files together just stops inflating
- Crilayla codec always will give crc error when unpack is greater then t75p
> t50p works all the time

I think there a some more. I just wrote what I remember this fast :D

[mixtro]

Two games I have experienced issues with xtool:
Darksiders
Red Faction Guerilla Remarstered

I don't remember exactly which files were problematic.

[artag]

sorry but this is a little confusing, what xtool version should i use?

this one:

https://fileforums.com/showthread.php?t=102832

or the 0.12?

This thread seems to have more activity, that's why i'm asking.

Thanks.

[devil777]

Mr.artag, use this version

[artag]

oh thanks!! i was using the other one!!
and another question, what about CriLayla games (bayoneta), the codec is not present on the las version, should i use a previous version or that means that the codec is unstable? thanks!
Edit: oh i just saw i'ts only for 32b

[Razor12911]

Can you guys give a list of issues xtool has, I'll try to patch them. Also if possible provide samples.

I'm giving the project another try since it seems like people are still interested in it.

No promises, even with quarantine going on, it should mean that I have time to make changes but then I use this time to sleep (Lazy af these days, not sure why) XD

Not much to fix then, development will resume sometime in June. I should have plenty of time then.

Edit:
You guys should also make sure you use the program correctly, I downloaded a game the other day and I was wondering why the heck I can't use my PC but turns out 25 threads were enabled, like wtf. RIP my quad core cpu... :o

[Masquerade]

Hi

I'm not really sure how to explain this is such but here goes:

- Using the crilayla codec on XTool v0.12, I am facing decompression issues where XTool seems to crash and sits idle in task manager. I am running a CPU with 16 threads and Xtool is given all 16 of them to play with. Would limiting the threads help at all? I've seen that 16 copies of the crilayla dll is created during installation, I understand this is 1 copy per thread. The game in question is The Wonderful 101 Remastered.

- Other times, using zlib codec, the same issue occurs. This is with both the x86 or x64 version of 0.12.

I'm not sure what to try in order to fix this.

Thank you in advance.

[KaktoR]

Try t2 ot t25p. It works all the time. It's a known issue.

[Masquerade]

Try t2 ot t25p. It works all the time. It's a known issue.

Tried both limits and same crash at the same point in both scenarios, just takes longer to reach that point because the threads are limited.

[devil777]

Hola masquerade.... hope you're doing well

Will you please try Pzlib v3 with m2:x+srep+lolz

It'll be okay... but don't forget to add the "libraries" with the binaries though they are in optional folder.

Both Pzlib v3 and Xtool is the offering by razor12911


But if you find that m2:x (best as razor had told) takes much longer , try m2:t1 or m2:t2

And Pzlib v3 doesn't have any stdin/stdout bug.I know Pzlib is off-topic for xzlib.. but dang that works well

[Hexagon123]

Has issues with some Unity Engine based games like Tin & Kuna, Trollhunters - Defenders of Arcadia, and New Super Lucky's Tale?

I tried using the lz4 codec but it failed.

But some had custom compression on them.

Edit: New XTool works.

[Miki13]

I need a tutorial, I want to learn this :(

[KaktoR]

Could someone tell me what's wrong with this file?

XTool just stop working on this (no cpu/ram load), no matter what settings I use.

This is from Anno 1800

https://i.imgur.com/NBDp2pd.png

[Razor12911]

there must be a single stream that decompresses to more than 2gb.
that ratio is very unusual 11443%

[KaktoR]

I did more tests and the same with ztool.

I think I have to exclude this file from precompressing :D

[Shegorat]

there must be a single stream that decompresses to more than 2gb.
that ratio is very unusual 11443%

Nope. There are 71 valid deflate streams with dynamic huffman

***
Block: 1186: offset=00000000018C6768 last=0 type=2 size=18440 unplen=4208336 hdrsize=39 entropy=5.0482
Block: 1187: offset=00000000018CAF70 last=0 type=2 size=18444 unplen=4226814 hdrsize=14 entropy=3.4551
Block: 1188: offset=00000000018CF77C last=0 type=2 size=18445 unplen=4226814 hdrsize=15 entropy=3.4501
Block: 1189: offset=00000000018D3F89 last=0 type=2 size=18444 unplen=4226814 hdrsize=14 entropy=3.4310
Block: 1190: offset=00000000018D8795 last=0 type=2 size=18444 unplen=4226814 hdrsize=14 entropy=3.4167
Block: 1191: offset=00000000018DCFA1 last=0 type=2 size=18445 unplen=4226814 hdrsize=15 entropy=3.4501
Block: 1192: offset=00000000018E17AE last=0 type=2 size=18444 unplen=4226814 hdrsize=14 entropy=3.4310
Block: 1193: offset=00000000018E5FBA last=0 type=2 size=18455 unplen=4205523 hdrsize=40 entropy=4.0372
Block: 1194: offset=00000000018EA7D1 last=0 type=2 size=18447 unplen=4222705 hdrsize=23 entropy=3.6798
Block: 1195: offset=00000000018EEFE0 last=0 type=2 size=18432 unplen=4195105 hdrsize=36 entropy=3.9656
Block: 1196: offset=00000000018F37E0 last=0 type=2 size=18444 unplen=4226814 hdrsize=14 entropy=3.4410
Block: 1197: offset=00000000018F7FEC last=1 type=2 size=5641 unplen=1048327 hdrsize=77 entropy=4.8571
beg=00000000018C6768, end=00000000018F95F6, blocks=12, size=208526 (0.199 Mb), unplen=47467694 (45.269 Mb)


raw_count=71, rawdata=24207594 (23.086 Mb), outdata=2129222 (2.031 Mb), unpdata=3011528751 (2872.018 Mb)

[78372]

Could someone tell me what's wrong with this file?

XTool just stop working on this (no cpu/ram load), no matter what settings I use.

This is from Anno 1800

https://i.imgur.com/NBDp2pd.png

71 zlib streams with valid headers. Data is very much precompressible.

[Masquerade]

I am having a similar issue with Monster Truck Championship, a UE4 game, no encryption, xtool will stick at 1.0% - ZTool / pZlib will instant crash with error 0xC0000005.

[78372]

I am having a similar issue with Monster Truck Championship, a UE4 game, no encryption, xtool will stick at 1.0% - ZTool / pZlib will instant crash with error 0xC0000005.

Better post a sample

[Masquerade]

Better post a sample

The single pak file of the game is 26GB.

https://steamdb.info/depot/1209361/

[Masquerade]

Getting unarc -12 at 100% when trying to unpack UE4 games, especially new ones. Unpacking is slow up until 100% when it should finish, but returns an error,

Call Of The Sea (although it uses not much compression) errors at 100% and aefer fall doesn't precompress at all (xtool just gets stuck) using v12 x64 variant.

Anything I am doing wrong?

[Hexagon123]

Getting unarc -12 at 100% when trying to unpack UE4 games, especially new ones. Unpacking is slow up until 100% when it should finish, but returns an error,

Call Of The Sea (although it uses not much compression) errors at 100% and aefer fall doesn't precompress at all (xtool just gets stuck) using v12 x64 variant.

Anything I am doing wrong?

The file is a bit uncompresed

[Ele]

Getting unarc -12 at 100% when trying to unpack UE4 games, especially new ones. Unpacking is slow up until 100% when it should finish, but returns an error,

Call Of The Sea (although it uses not much compression) errors at 100% and aefer fall doesn't precompress at all (xtool just gets stuck) using v12 x64 variant.

Anything I am doing wrong?

FreeArc errorlevel -12 means failed CRC check right? Use xdelta if possible.

[Masquerade]

FreeArc errorlevel -12 means failed CRC check right? Use xdelta if possible.
Yes, but this is an installation. At isdone error, the installer clears everything. I'd need to patch the installer to not clear everything, ignore isdone error then complete the patch.

[drsamonline]

Nice thank you

[Cesar82]

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

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

I don't know what the v is for in your packcmd though:
e:precomp:t100p,c128m,v:crilayla

[Cesar82]

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

I don't know what the v is for in your packcmd though:
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]

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

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

[Cesar82]

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]

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]

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]

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

[Prince4]

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 :

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 :

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

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]

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]

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

[JaleSwiftpaw]

Thanks, I've been looking for this.

[Gcr27]

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