DiskSpan GUI

[Cesar82]

Originally Posted by Gummy Bear

Hi, I don't understand what's wrong, I compress any file using xtool+srep+lolz, and it gives this error, I can't figure out how to fix it.

This error occurs because your installer is using the "IsArcEx.dll" library that is integrated inside FMXInno.dll or externally. DiskSpan GUI has been prepared to work with IsDone.dll.
You can include IsDonel.dll in your project and use the IsDone functions to do the unpacking.
Along with DiskSpan GUI you find an example with "DSG_Module.iss". You can integrate this module into your script by replacing the IsArcEx functions.

Originally Posted by audiofeel

In my opinion, DiskSpanGui lacks a checkbox - "do everything for another unpacker and do not hide everything in setup.dll ". Then any user can compress the archive in this program and transfer all the necessary dll and ini files to his installer without incident. "FMXInno" is gaining popularity and there will be even more questions and problems with this program "DiskSpanGui".

DiskSpan GUI is designed to work only with "IsDone.dll" (not "IsArcEx.dll").
The reason is that some functions used in "DiskSpan GUI", such as Z-Zip and RAR compression and Patch mode cannot be unpacked by "IsArcEx.dll".
BLACKFIRE69 chose not to include in its "IsArcEx.dll" library (whether the version integrated with FMXInno.dll or an external library) functions equivalent to IS7ZipExtract, ISRarExtract and ISxDeltaExtract contained in "IsDone.dll".
I personally find this additional feature very useful, because with IS7ZipExtract we can just create an additional file manually in 7-Zip or RAR using one of the WinRAR or 7-zip programs at any time after compression, and just add a section to "Records.ini ", as long as you have not merged "Records.ini" into "Setup.dll" or integrated into "Setup.exe", and include the information from the new 7-Zip/RAR file. Example: You want to include an extra addon to your installation, with optional installation, you would just compress it with WinRar and play it on the last disk by making the config in Records.ini and you could also define a task for it in Records.ini, so you could check this task in your installer.
In any case, the DiskSpan GUI module is there for you to integrate into your installers without much effort.
The idea of ​​putting a checkbox to not generate Setup.dll and keeping the files in a folder on Disk 1 could be an option for the next DSG. The problem would be the division of disks which should subtract the size of all compressors in the folder so that when including them in Setup.exe it can be subtracted (If the reserved size is not defined on disk 1, if it reserves space, already include the total size) .

NOTES:
Somewhere in the FMXInno thread there were 2 example scripts using InnoFmx.dll and containing DiskSpan GUI support (previous version of DSG), but I think BLACKFIRE69 may have removed the post.

Originally Posted by homerliew

Hello! Version 2.0.2.0 of Diskspan GUI has too much vertical window size and won't fit on my screen, I have to enable Keep on top to see everything pass my taskbar but the problem still exists in the Tools tab because it doesn't stay on top of the taskbar inside Tools tab.

I use a 15.6" laptop with 2560x1440 resolution. The screen is just too small for its resolution, allow adjusting the window size will help. v2.0.1.9 had no issues btw.

You must be using some Windows desktop enlargement scale above 125%.
The maximum supported for creating the DSG interface is 125% scaling at 1440p or 100% at 1080p.
For lower resolutions, unfortunately the DSG cannot be drawn correctly.
The DSG 2.0.1.9 version had a slightly smaller interface than the current one, that is, 636x734 pixels, so it was displayed correctly for you.
The current version of DSG 2.0.2.0 has dimensions of 693x814 pixels because it was necessary to include new EDITs in the DEVELOPER mode area to meet the new supported configurations, so now in this new version your monitor area stands out when using resolutions below 1080p or for those using scales above 125% at 1440p resolutions.
I'll see if I can find a way to reduce the size of the DSG interface in the next version, but I can't promise anything because the DSG is developed in Inno Setup, and Inno Setup doesn't offer many customization options for design objects.

[Gummy Bear]

Originally Posted by Cesar82

This error occurs because your installer is using the "IsArcEx.dll" library that is integrated inside FMXInno.dll or externally. DiskSpan GUI has been prepared to work with IsDone.dll.
You can include IsDonel.dll in your project and use the IsDone functions to do the unpacking.
Along with DiskSpan GUI you find an example with "DSG_Module.iss". You can integrate this module into your script by replacing the IsArcEx functions.


DiskSpan GUI is designed to work only with "IsDone.dll" (not "IsArcEx.dll").
The reason is that some functions used in "DiskSpan GUI", such as Z-Zip and RAR compression and Patch mode cannot be unpacked by "IsArcEx.dll".
BLACKFIRE69 chose not to include in its "IsArcEx.dll" library (whether the version integrated with FMXInno.dll or an external library) functions equivalent to IS7ZipExtract, ISRarExtract and ISxDeltaExtract contained in "IsDone.dll".
I personally find this additional feature very useful, because with IS7ZipExtract we can just create an additional file manually in 7-Zip or RAR using one of the WinRAR or 7-zip programs at any time after compression, and just add a section to "Records.ini ", as long as you have not merged "Records.ini" into "Setup.dll" or integrated into "Setup.exe", and include the information from the new 7-Zip/RAR file. Example: You want to include an extra addon to your installation, with optional installation, you would just compress it with WinRar and play it on the last disk by making the config in Records.ini and you could also define a task for it in Records.ini, so you could check this task in your installer.
In any case, the DiskSpan GUI module is there for you to integrate into your installers without much effort.
The idea of ​​putting a checkbox to not generate Setup.dll and keeping the files in a folder on Disk 1 could be an option for the next DSG. The problem would be the division of disks which should subtract the size of all compressors in the folder so that when including them in Setup.exe it can be subtracted (If the reserved size is not defined on disk 1, if it reserves space, already include the total size) .

NOTES:
Somewhere in the FMXInno thread there were 2 example scripts using InnoFmx.dll and containing DiskSpan GUI support (previous version of DSG), but I think BLACKFIRE69 may have removed the post.


You must be using some Windows desktop enlargement scale above 125%.
The maximum supported for creating the DSG interface is 125% scaling at 1440p or 100% at 1080p.
For lower resolutions, unfortunately the DSG cannot be drawn correctly.
The DSG 2.0.1.9 version had a slightly smaller interface than the current one, that is, 636x734 pixels, so it was displayed correctly for you.
The current version of DSG 2.0.2.0 has dimensions of 693x814 pixels because it was necessary to include new EDITs in the DEVELOPER mode area to meet the new supported configurations, so now in this new version your monitor area stands out when using resolutions below 1080p or for those using scales above 125% at 1440p resolutions.
I'll see if I can find a way to reduce the size of the DSG interface in the next version, but I can't promise anything because the DSG is developed in Inno Setup, and Inno Setup doesn't offer many customization options for design objects.

If I use lolz + srep, it decompresses fine, the problem is with xtool.

[Fak Eid]

Originally Posted by Gummy Bear

If I use lolz + srep, it decompresses fine, the problem is with xtool.

DM me. We can talk this private and I can sort this out. I use a modified version of this installer and know the code.

[KaktoR]

Originally Posted by Cesar82

The maximum supported for creating the DSG interface is 125% scaling at 1440p or 100% at 1080p.

125% on 1080p aswell. So the max scaling you can use is 125% for 1080p and 1440p.

[KaktoR]

All you need to make FMX compatible with DSG is inside the folder "_ISDone Script Example (DiskSpan_GUI)" (script wise).

[Fak Eid]

Originally Posted by KaktoR

All you need to make FMX compatible with DSG is inside the folder "_ISDone Script Example (DiskSpan_GUI)" (script wise).

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.

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

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

I made some changes here for you.
Now you can just add the Setup.dll generated by DiskSpan GUI during compression into the "Decomp" folder and the compressors present in Setup.dll will be added to your Setup.exe during compilation.

I added a test in InitializeSetup (DEBUG_2), if you want to check when starting the installer you can remove the slashes before "//#define DEBUG_2" (These lines can be deleted if you want).
The decompressors will be unpacked during the beginning of the installation.

[CrownRepack]

Originally Posted by Cesar82

I made some changes here for you.
Now you can just add the Setup.dll generated by DiskSpan GUI during compression into the "Decomp" folder and the compressors present in Setup.dll will be added to your Setup.exe during compilation.

I added a test in InitializeSetup (DEBUG_2), if you want to check when starting the installer you can remove the slashes before "//#define DEBUG_2" (These lines can be deleted if you want).
The decompressors will be unpacked during the beginning of the installation.

Hi Cesar, can you please add the function to Vesta Installer aswell?
The one created by audiofeel.

[Cesar82]

Originally Posted by CrownRepack

Hi Cesar, can you please add the function to Vesta Installer aswell?
The one created by audiofeel.

If you want something similar to the modified installer file I posted before, download the attached file.
This will just unpack the decompressor files from within "Setup.dll" and include them in your installer.
But you will always need to update "Setup.dll" in the "Decomp" folder according to the compression done before compiling Setup.exe.

IMPORTANT:
Always use the "UNLIMITED" tab of the DiskSpan GUI to make your conversion...
The installer does not have the IsDone module/functiond, so it is not possible to use disk spanning features like DiskSpan or SPLIT mode.

ADITIONAL:
I also attached here the modified version of the popular installer "OpenSetup" that audiofeel requested for the PM.

[kj911]

Is it possible to integrate the "disk spanning" function/files in "DiskSpanGUI" under the "Tiny Compressor v1.4" or plain "FreeARC" solutions??

I think that a created archive much larger than 4+ GB is no longer an easy way to slice it into volumes of any size using the "diskspan" method?

Eg: 7GB --> (added with the diskspan:4400mb:4440mb method, the original compression.) we would then get a 4400MB first volume and a ~2769MB second volume files.

[homerliew]

Thank you for the answers regarding Window Size. I dropped my Desktop Scaling down to 150% from 175% which is the recommended setting for my laptop, no more issues. Texts are smaller now though.

[CrownRepack]

Fak Eid, this method by Cesar solved my issue, all i need is to add the Setup.dll of the compression in the Decomp and now its working fine, and i'm scratching my head with all the fail attempts like for 3 days, thanks Cesar82 , Fak Eid and audiofeel, you guys are my king!