FileForums
Page 10 of 14 « First 89 10 1112 Last »
Show 40 post(s) from this thread on one page

FileForums (https://fileforums.com/index.php)
-   Conversion Tutorials (https://fileforums.com/forumdisplay.php?f=55)
-   -   DiskSpan GUI (https://fileforums.com/showthread.php?t=104507)

Cesar82 07-06-2024 10:38
Quote:
Originally Posted by audiofeel (Post 504727)
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".
Do you think DSG is hiding something from you, no, it stores the compressors in an ARC file with method "-m3" (Yes, it could be zip/7-zip/RAR, but the unpacking speed of the compressors would be harmed). This way you can replace your executable without needing to change anything else.
Example: I can take a conversion created in CIU and replace Setup.exe with one created by ASIS by other user that will continue to work, without me knowing which method was used to compress.
See for yourself...

How many times have you contributed compression information, more precisely configurations to be added to the DSG database?
If it weren't for @KakoR, who spends hours and hours carrying out tests, obtaining the best methods for each game and creating configurations, we wouldn't have any preconfiguration of methods in the DATABASE.
So be grateful for what you have, if you don't want to use DSG, don't use it.

Remembering that it is very important that you share information to the database, especially about games that are not there yet.
To share information to the new database is very simple.
After configuring your method for a game in DEVELOPER mode, just hold down the "CTRL+SHIFT" keys on your keyboard and click the "Save" button (without releasing the "CTRL+SHIFT" keys) and click OK in the dialog box that will be displayed.
The information from the database will be copied to the clipboard, so you just paste it into your collaboration post here on the DSG thead.
But only send information after testing and obtaining the best compression ratio, there is no point in sending srep+LOLZ_ULTRA for everything without test (Not everything is srep + lolz.. :D).

Cesar82 07-06-2024 10:57
Quote:
Originally Posted by Fak Eid (Post 504736)
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.

Gummy Bear 07-06-2024 11:51
Quote:
Originally Posted by Cesar82 (Post 504735)
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 07-06-2024 11:56
Quote:
Originally Posted by Cesar82 (Post 504738)
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.

Fak Eid 07-06-2024 12:00
Quote:
Originally Posted by Gummy Bear (Post 504740)
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.

Cesar82 07-06-2024 12:29
Quote:
Originally Posted by Fak Eid (Post 504741)
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.

kj911 07-06-2024 13:17
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.

Fak Eid 07-06-2024 13:19
Quote:
Originally Posted by Cesar82 (Post 504745)
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.

KaktoR 07-06-2024 13:21
Quote:
Originally Posted by Cesar82 (Post 504735)
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.

Cesar82 07-06-2024 21:59
1 Attachment(s)
Quote:
Originally Posted by Fak Eid (Post 504736)
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.

homerliew 07-06-2024 22:33
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 08-06-2024 09:53
Quote:
Originally Posted by Cesar82 (Post 504754)
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 08-06-2024 12:56
2 Attachment(s)
Quote:
Originally Posted by CrownRepack (Post 504768)
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.

CrownRepack 09-06-2024 08:05
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!

Fak Eid 17-06-2024 05:10
One ridiculous requirement for Setup.dll
 
Hi Cesar82,

I'm currently working on a repack and would request to either know, or if you could create this feature for DSG?

Scenario: The following compression were not done via DSG. So,
I had Data-01 compressed using mzlib+srep+lolz
I had Data-02 compressed using bk2.
I had Data-03 compressed using kraken.

Now I want to decompress this data. I want the Setup.dll to include files required for decompression which would include oodle, bk2, mzlib, srep and lolz files. So, I go to DSG and select the methods and create the Setup.dll. Is it possible?

Let me know if you want me to refine the requirement more or help you understand.

KaktoR 17-06-2024 05:28
It works as long as names in arc.ini are the same.

Cesar82 17-06-2024 06:02
Quote:
Originally Posted by Fak Eid (Post 504815)
Hi Cesar82,

I'm currently working on a repack and would request to either know, or if you could create this feature for DSG?

Scenario: The following compression were not done via DSG. So,
I had Data-01 compressed using mzlib+srep+lolz
I had Data-02 compressed using bk2.
I had Data-03 compressed using kraken.

Now I want to decompress this data. I want the Setup.dll to include files required for decompression which would include oodle, bk2, mzlib, srep and lolz files. So, I go to DSG and select the methods and create the Setup.dll. Is it possible?

Let me know if you want me to refine the requirement more or help you understand.
It's possible, but you'll need to change some things manually.
Firstly, do you need to review the kraken method (Would it be xtool:mkraken)?

Then you will need to access the group of tools in the DSG's TOOLS button in the "Setup DLL" tab.
The correct thing to do is first of all to open your Data#.bin with FreeArc and go to "INFO" > "Solid Blocks" tab to know exactly the name of the methods used.
Within the "Setup DLL" tab of the DSG, access the "Maker" sub-tab and paste the methods one on each line.
You must know which oodle library is required for your compression, so inform the library using a value ":3" ... ":9" or use the specific version for the library using ":core_x.x.x".

Example:
Code:
xtool:mzlib+srep+lolz
xtool:bk2
xtool:mkraken:core_2.9.2
You can uncheck the split and diskspan checkboxes at the bottom of the window if you

The "srep" method will automatically be converted to "srep_new:393c", so it will be necessary to extract Setup.dll (Unpacker sub-tab) after using "Maker" and rename the CLS by removing "_NEW" in the 3 files relating to srep and compressing again Setup.dll ("Packer" subtab).

EDIT:
For some reason the plugin's INI file wasn't added here for me in my testing.
Then simulate a compression to create setup.dll and then unpack it and rename the srep files if necessary and recompress setup.dll

Fak Eid 17-06-2024 06:04
Quote:
Originally Posted by KaktoR (Post 504816)
It works as long as names in arc.ini are the same.
This requirement is for making DSG compatible with all type of FMX installer. Not file extraction.

Quote:
Originally Posted by Cesar82 (Post 504817)
It's possible, but you'll need to change some things manually.
Cool, yes this is what I want. Thank you for your help. I'd appreciate if we could do it by clicking on Checkboxes, just like we do it for compression but anyways, this works for me now.
Thank you soo much.

sajmon83 18-06-2024 09:37
Hey Cesar82, I noticed that the components are not working. After setting and saving, they are not saved to the DSG_Settings.ini file at all

Cesar82 18-06-2024 19:04
1 Attachment(s)
Quote:
Originally Posted by sajmon83 (Post 504828)
Hey Cesar82, I noticed that the components are not working. After setting and saving, they are not saved to the DSG_Settings.ini file at all
It is necessary to have configured at least 2 game tabs for the components to be validated.
Here it is working (See the attached video).

INFO:
- Components are intended for creating game collections, not addons for a single game. To do this, the tasks function is used.
- In the next version it will support components, even if there is only one game.

sajmon83 18-06-2024 19:56
Oh I didn't know that. And I tried using components for Data 1, Data 2 ... Now everything is clear

demon964 19-06-2024 09:26
https://i.imgur.com/gNOqwsG.png

which one compress best?

Cesar82 19-06-2024 10:31
Quote:
Originally Posted by sajmon83 (Post 504837)
Oh I didn't know that. And I tried using components for Data 1, Data 2 ... Now everything is clear
The idea behind the creation of DiskSpan GUI started with modifications of a .bat file called DiskSpan.bat that worked only with the CIU installer that has components only for collections of 2 or more games.
So when I created the GUI version of the program, these aspects were maintained.
The original idea was just to be used together with CIU, but it was later extended to be used in other installers, then the Tasks feature was added which allows you to install additional files.

Cesar82 19-06-2024 10:37
Quote:
Originally Posted by demon964 (Post 504849)
https://i.imgur.com/gNOqwsG.png

which one compress best?
I think it all depends on the "type of file/game" you are compressing. But in relation to the final method, despite having a much longer compression time, the methods that offer LOLZ as a final compressor will have a better compression ratio, but the time spent is not always necessary due to a sometimes insignificant gain in the final ratio. .

nxllxvxxd 23-06-2024 12:49
Is there anyway to port over the extraction to Inno Setup in order to make a custom installer just with the preexisting archives

Cesar82 23-06-2024 17:57
Quote:
Originally Posted by nxllxvxxd (Post 504891)
Is there anyway to port over the extraction to Inno Setup in order to make a custom installer just with the preexisting archives
What do you mean, port over the extraction to Inno Setup?

nxllxvxxd 23-06-2024 22:08
Quote:
Originally Posted by Cesar82 (Post 504892)
What do you mean, port over the extraction to Inno Setup?
Yes I understand the extraction of Setup.DLL and everything like that, needing to have the right decompressors ect. I just don't like get how to necessarily port those functions into Inno.

I'm testing with a archive I created with precomp+srep+lzma (there are going to be mutiple types depending on filetype). It decompresses perfectly within diskspangui I just don't know how to move that function over to Inno setup to work with my setup file

Sorry if I sound kinda dumb about this I am trying my hand at making a little bit more intensive repacks, I've made simple ones with inno itself before doing the compression and everything but never really messed with it

Lord.Freddy 23-06-2024 22:29
Quote:
Originally Posted by nxllxvxxd (Post 504893)
Yes I understand the extraction of Setup.DLL and everything like that, needing to have the right decompressors ect. I just don't like get how to necessarily port those functions into Inno.

I'm testing with a archive I created with precomp+srep+lzma (there are going to be mutiple types depending on filetype). It decompresses perfectly within diskspangui I just don't know how to move that function over to Inno setup to work with my setup file
Do you want to learn how to extract an archive created by DSG using Inno Setup? If so, follow these steps:

1. Download DSG: When you download DSG, you'll find a folder named "_ISDone Script Example (DiskSpan_GUI)."

2. Example Implementation: Inside this folder, you'll discover an example of how to implement the necessary functions for extracting archives created by DSG.

3. Additional Examples: For more examples, explore the 'Light Installer Script' thread.

nxllxvxxd 23-06-2024 22:47
Quote:
Originally Posted by Lord.Freddy (Post 504894)
Do you want to learn how to extract an archive created by DSG using Inno Setup? If so, follow these steps:

1. Download DSG: When you download DSG, you'll find a folder named "_ISDone Script Example (DiskSpan_GUI)."

2. Example Implementation: Inside this folder, you'll discover an example of how to implement the necessary functions for extracting archives created by DSG.
EDIT: Yes that is what I am looking to achieve. I want to compress with DSG and to decompress with inno. I'm trying my hand at making more intensive repacks a la FitGirl

I've read through these and can't lie that I am a bit confused as to which to look at seeing as there are two isdone scripts, I can't really tell what is going on, is the one inside of Script Example the one I want to look at or the one at the top of the _ISDone_ dir?

Again sorry for stupid questions I'm completely lost would not be asking if I didn't have to

Fak Eid 23-06-2024 23:28
Blackfire already shared a better replica for whole Firgirl repack on FMXInno forum

Cesar82 24-06-2024 08:14
1 Attachment(s)
Quote:
Originally Posted by nxllxvxxd (Post 504896)
EDIT: Yes that is what I am looking to achieve. I want to compress with DSG and to decompress with inno. I'm trying my hand at making more intensive repacks a la FitGirl

I've read through these and can't lie that I am a bit confused as to which to look at seeing as there are two isdone scripts, I can't really tell what is going on, is the one inside of Script Example the one I want to look at or the one at the top of the _ISDone_ dir?

Again sorry for stupid questions I'm completely lost would not be asking if I didn't have to
The examples within the "Script Example (DSG_Module)" subfolder are examples using an external module (DSG_Module.iss) that is easier for you to adapt in any Inno Setup script that uses IsDone.dll.
The ISDone_Example.iss example in the main folder is more complex and more difficult to adapt to another script (because it contains all the code in the same script).
Both examples have the same purpose, but the main folder example also has hash checking that is not included in the example with DSG_Module.iss.

INFO:
I am sharing an update to the examples using DSG_Module.iss as an attachment.
Fixed a bug in the previous version where uninstallation did not remove files from the installation folder.

LILU 09-07-2024 01:52
Hello. I use DiskSpan GUI 2.0.2.0 64 bit . After compression ( for example xtool:c32mb:t80p:mkraken+lolz:d35:mtt1:mt12:fba409 6:mc2) script (ISDone_Example.iss) does not unpack the archive (Error writing to disk). What and where should be thrown (files, folders) to unpack the archive correctly?

wareck 19-07-2024 20:23
hello
I found a very small bug in the last release (64bit mode, I do not use 32bit)

If you start to compress then click on abord, then retry, diskpan can't restart
I need to exit and start again

(sometime during test, I do this kind of think several time to find the best compression method)

Best regards

Cesar82 21-07-2024 11:28
1 Attachment(s)
Quote:
Originally Posted by wareck (Post 505068)
hello
I found a very small bug in the last release (64bit mode, I do not use 32bit)

If you start to compress then click on abord, then retry, diskpan can't restart
I need to exit and start again

(sometime during test, I do this kind of think several time to find the best compression method)

Best regards
There are no errors here.
see the attached video.

wareck 26-07-2024 23:55
I found the issue
It's when I use parallel tool, like mpz_mtx.
when I click on abort , there is some threads still running.
Because of that, temporay folder and archive are still in use.
So when I click on retry, diskspan can't delete conversion temporay file and make some error code.

I just need to check is there is no anymore process still runing...
was my bad

thanks !
best regards

pcblizzard 27-07-2024 00:41
Quote:
Originally Posted by Cesar82 (Post 500675)
[...]
Code:
- Added support for boolean operators in the edit boxes Components, Tasks and Languages (Script "ISDone_Example.iss" updated).
  >> The values of these edit boxes will be written to the keys in "Records.ini" file: Component=, Task=, Language=.
  >> Now be possible use the "|" (OR character), or the "&" (AND character), or the "!" (NOT caracter), and you can also use "(" and ")" to determine the parse order of the expression.
  >> It is not necessary to duplicate the "|" or "&" characters as in C programming, even the DiskSpan GUI iterface blocks this action.
  >> For compatibility it is also possible to use the old separator character "," (Comma) as it will be interpreted as "|" (OR operator), and you can also use the "+" character like "&" (AND operator). 
    Component=1,3    //return true if component 1 or 3 checked.
    Component=2+4    //return true if component 2 and 4 checked.
    Component=!(2+4)  //return true if component 2 and 4 unchecked.
    Component=!1,!3  //return true if component 1 or 3 unchecked.
    Task=1&2&!4      //return true if task 1 and 2 checked and task 4 unchecked.
    Task=!1&2&|4      //return true if task 1 unchecked and 2 checked or task 4 checked.
    Task=(2|3)|!(3&5) //return true if task 2 or 3 checked or task 3 or 5 unchecked (even if not checked 3 and 5).
    Language=!ES|!DE  //return true if the installer is not running in ES language and not in DE language.
    Language=EN|PL    //return true if the installer is running in EN or PL language (same as Language=EN,PL).
[...]
Has the feature ‘Component=1,3’ been removed? As soon as I exit DiskSpan GUI (I have saved the settings I made) and restart DiskSpan GUI in dev mode, the setting I made previously is missing (in this case ‘1,2,3,4’ - in ‘Tasks’, for example, the entry ‘1,2,3,4’ remains after a restart).

I noticed this in version 2.0.1.7 and in the latest version (2.0.2.0).


KR pcblizzard

Cesar82 27-07-2024 09:28
1 Attachment(s)
Quote:
Originally Posted by pcblizzard (Post 505114)
Has the feature ‘Component=1,3’ been removed? As soon as I exit DiskSpan GUI (I have saved the settings I made) and restart DiskSpan GUI in dev mode, the setting I made previously is missing (in this case ‘1,2,3,4’ - in ‘Tasks’, for example, the entry ‘1,2,3,4’ remains after a restart).

I noticed this in version 2.0.1.7 and in the latest version (2.0.2.0).


KR pcblizzard
Until the current version of the DiskSpan GUI, it is only possible to configure components when there are 2 or more GAMES tabs.
The components function was inherited from CIU in which each component is a game and is only validated if there are 2 or more games.
In other words, components are only used to create a collection of games.
For additional packages, use task settings.

In the next version of DSG it will be supported to use multiple components even if you only have a single game configured.

Quote:
Originally Posted by wareck (Post 505113)
I found the issue
It's when I use parallel tool, like mpz_mtx.
when I click on abort , there is some threads still running.
Because of that, temporay folder and archive are still in use.
So when I click on retry, diskspan can't delete conversion temporay file and make some error code.

I just need to check is there is no anymore process still runing...
was my bad

thanks !
best regards
I did a test here using mpz_mtx with random files and everything seems to be ok...
See the test in the attached video.

KaktoR 29-07-2024 02:05
Quote:
Originally Posted by wareck (Post 505113)
I found the issue
It's when I use parallel tool, like mpz_mtx.
when I click on abort , there is some threads still running.
Because of that, temporay folder and archive are still in use.
So when I click on retry, diskspan can't delete conversion temporay file and make some error code.

I just need to check is there is no anymore process still runing...
was my bad

thanks !
best regards
This is because mtx using chunks to process data. Each chunk (x MB) needs to finish before anything else happens. The more chunks you have (x cpu threads) and how big the chunks are (x MB) the more time it takes.

One solution is to taskkill all mtx processes if click on "Abort" button.

PHM2D 02-08-2024 08:22
Tasks vs. Components for Multi Languages
 
First of all, thank you for this great tool.

I have separated optional game language audio files from my main game folder and want to include them as optional components which can be installed/copied if chosen to. However it is a little bit confusing as how to achieve this goal. Should I change components to 1 for the main game data tab and then add another game data tab that would include optional language files as the required component? Or should I change it to 1 for the component tab as well as the main game tab? Is this the correct method of doing all this? I also have no idea how to use tasks.
I have already created .bin files which use the default naming "data1a-01" for the main game files and "Optional1a-01" for the component file.
I will be using ASIS as the Installer which supports components.

Cesar82 02-08-2024 08:43
components was created to install 2 or more games in a game collection. to install additional items use the tasks option (As far as I remember ASIS also supports tasks). Just use tasks like: 1, 2, etc. in both dsg and asis..


All times are GMT -7. The time now is 20:15.
Page 10 of 14 « First 89 10 1112 Last »
Show 40 post(s) from this thread on one page

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