XTool - Successor of ZTool

[Razor12911]

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

[amin fear]

Originally Posted by Razor12911

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:
1.png
2.png
3.png

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]

Originally Posted by elit

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]

Originally Posted by Razor12911

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:
err.png
err2.png
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]

Originally Posted by Razor12911

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]

Originally Posted by elit

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_HANDLE))
  else
    Output := TFileStream.Create(ParamArg[2], fmCreate);

Originally Posted by 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.

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]

Originally Posted by 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

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

[FitGirl]

Originally Posted by 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

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..