DiskSpan GUI

[Cesar82]

Originally Posted by fabrieunko

Hello, I have 2 questions about the use of this function:

- Added independent checksum file generation

when I compact a simple game I must make the following choice:
Checksum file: MD5 Setup DLL password: hash from Setup.exe HASH (in the drop-down menu)

when is it for a compilation of several games? is the checksum file created for each game? Or for all games? if the user installs only 1 game on the compilation? moreover some installers allow the possibility to give a player name to the installation and to change the language of the game. but the ini file is modified at the end of the installation and therefore the checksum file will indicate an error. is there a possibility to exclude the .ini file (crack)?

It's like KaktoR already answered.
For each Data#.bin generated a separate hash file will be generated and depending on users' choices during installation these files will be merged and checked.

In developer mode only the "Checksum File" combobox refers to the hash.
"Setup DLL password" (Hash option) is something else, it serves to encrypt "Setup.dll" with the Hash of setup.exe.

There is no option to exclude a file from hash checking. But you can move SetIniString functions that change this ini in installer script to procedure CurStepChanged inside "CurStep = ssDone" (after hash checking)