DiskSpan GUI

[Cesar82]

Originally Posted by Fak Eid

I use it differently actually. I extracted everything outside so no one has ever make changes in the script. If you want to use any decompression just update ToolsDefine.iss
Although the changes are old and this is just an alpha as I said I use it for myself.

Here's an example: https://fileforums.com/showpost.php?...2&postcount=52
Or, you can check the last third picture.

Another example: https://fileforums.com/showpost.php?...2&postcount=50
Simple example: https://fileforums.com/showpost.php?...1&postcount=28

All Stuff in 'Game' folder.

Nice installer...

But that's what the DiskSpan GUI tries to avoid.
Try to avoid incompatibility of compression and unpacking tools.
You cannot use one version of compressor to compress (in this case, those used by DiskSpan GUI) and another version to decompress.
Example: Your MTX64.exe from the first post is 5.0.0.3 (64-bit).
DiskSpan GUI compresses using MTX64.exe v0.1 (64-bit) which is a remake of the old MTX project.
If you use an MTX method like razor_mtx, even if everything else is compatible, the extraction will fail because the version of the tool is different and often (this is one case) the commands are different.

You should always use the same version-compatible tools for compression and decompression.
The "DiskSpan GUI" generates Setup.dll containing all compatible files, even if you don't understand anything about compression.
Yes, you can extract Setup.dll and merge it into your installer using the TOOLS button ("Setup DLL" tab).
There you can even create a DLL setup before compressing using the "Maker" subtab, if you are already sure which method you are going to use.

If you noticed, in the last DSG module, it already supports including compressors in a folder that will be automatically included in your setup.exe, requiring only external Records.ini (if setup.dll exists next to setup.exe, the compressors from Setup.dll).
You can also put records.ini in the folder before compressing setup.exe if you don't want anything external, but you will need to compress the game first to generate Records.ini or write it manually.

[Fak Eid]

Originally Posted by Cesar82

Nice installer...

But that's what the DiskSpan GUI tries to avoid.
Try to avoid incompatibility of compression and unpacking tools.
You cannot use one version of compressor to compress (in this case, those used by DiskSpan GUI) and another version to decompress.
Example: Your MTX64.exe from the first post is 5.0.0.3 (64-bit).
DiskSpan GUI compresses using MTX64.exe v0.1 (64-bit) which is a remake of the old MTX project.
If you use an MTX method like razor_mtx, even if everything else is compatible, the extraction will fail because the version of the tool is different and often (this is one case) the commands are different.

You should always use the same version-compatible tools for compression and decompression.
The "DiskSpan GUI" generates Setup.dll containing all compatible files, even if you don't understand anything about compression.
Yes, you can extract Setup.dll and merge it into your installer using the TOOLS button ("Setup DLL" tab).
There you can even create a DLL setup before compressing using the "Maker" subtab, if you are already sure which method you are going to use.

If you noticed, in the last DSG module, it already supports including compressors in a folder that will be automatically included in your setup.exe, requiring only external Records.ini (if setup.dll exists next to setup.exe, the compressors from Setup.dll).
You can also put records.ini in the folder before compressing setup.exe if you don't want anything external, but you will need to compress the game first to generate Records.ini or write it manually.

Agreed and acknowledged the 'MTX' point but as I said it is still alpha and I still do not have it all compression method comptaible. The ones created are just what I've used so far. Or use plugins for some game (like w3, Ghost of Tsushima, Starfield, etc.) and then remove. In this way, I keep my Setup.exe from overburdened with all the unnecessary files. DSG is by far the most useful tool for compression for me and the support is great too. If someone understands how to use it, it's a boon.

[Cesar82]

Originally Posted by Fak Eid

Agreed and acknowledged the 'MTX' point but as I said it is still alpha and I still do not have it all compression method comptaible. The ones created are just what I've used so far. Or use plugins for some game (like w3, Ghost of Tsushima, Starfield, etc.) and then remove. In this way, I keep my Setup.exe from overburdened with all the unnecessary files. DSG is by far the most useful tool for compression for me and the support is great too. If someone understands how to use it, it's a boon.

XTool is also a different version that is in your installer "[OG] RGT Repack" (I haven't analyzed the others) of the xtool present in currend version of the DSG.
In your installer contain xtool v0.7.9 (HOTIFIX 1), so it would be necessary to use DSG plus 2.0.1.9 to maintain compatibility.
The current DiskSpan GUI uses version 0.87 of XTOOL and this version will certainly be the version that will be maintained from now on because now XTool is no longer available to all users, and even if there is an update to XTool, only users with a paid account will be able to have it. access to it.
If a user wants to use a new version of XTool and wants to use it for themselves, as long as they know the changes to any xtool parameter, it can possibly be changed in DSG_Methods.ini to support new codecs, or parameters of the new xtool.
So far I don't think we have any more updates (DSG stays up to date with XTOOL)...
But if there is an update that requires changes that cannot be made directly in DSG_Methods.ini, send me the xtool.exe or send me the necessary information and I will include the DSG to support the new XTOOL functions/parameters.

As for your installer not to be full of compressors that will not be used, that's why DSG uses Setup.dll. If you only include the Setup.dll files in your installer it will only contain the files needed to unpack your game.
Setup.DLL only contains the files necessary to decompress the conversion that generated Setup.dll. If you try to use the same setup.dll with other methods that use other compressors, the extraction will fail.

[Fak Eid]

Originally Posted by Cesar82

XTool is also a different version that is in your installer "[OG] RGT Repack" (I haven't analyzed the others) of the xtool present in currend version of the DSG.
In your installer contain xtool v0.7.9 (HOTIFIX 1), so it would be necessary to use DSG plus 2.0.1.9 to maintain compatibility.
The current DiskSpan GUI uses version 0.87 of XTOOL and this version will certainly be the version that will be maintained from now on because now XTool is no longer available to all users, and even if there is an update to XTool, only users with a paid account will be able to have it. access to it.
If a user wants to use a new version of XTool and wants to use it for themselves, as long as they know the changes to any xtool parameter, it can possibly be changed in DSG_Methods.ini to support new codecs, or parameters of the new xtool.
So far I don't think we have any more updates (DSG stays up to date with XTOOL)...
But if there is an update that requires changes that cannot be made directly in DSG_Methods.ini, send me the xtool.exe or send me the necessary information and I will include the DSG to support the new XTOOL functions/parameters.

As for your installer not to be full of compressors that will not be used, that's why DSG uses Setup.dll. If you only include the Setup.dll files in your installer it will only contain the files needed to unpack your game.
Setup.DLL only contains the files necessary to decompress the conversion that generated Setup.dll. If you try to use the same setup.dll with other methods that use other compressors, the extraction will fail.

Thanks for the info. I'll put the latest version of Xtool.exe in my installer. As for other compression method the idea is very simple, include only the files in the Script.iss, required for decompression. Then, there was a problem that I had to make an update in the script to import and extract the file. I even wrote a .bat for it, but things were getting complicated.

So that's why instead I kept all the files and imported based on the tool definition. The setup.dll merging with records.ini, I'm not aware of as I only do this part time and have lost track of updates long ago. If there's a video of your explanation, I'll surely watch and write code to enhance FMX even more. If our ideas align, maybe we can collab too.