ASIS: Advanced Simple Installer Script

[L33THAK0R]

Alright got 2 more questions for you lads and then I promise I'll stop spamming 'em.

So I've got a repack with a few optional components and I was wondering if its possible for the setup once launched to have a look to see if the component file is present, and if it comes back false, can the setup disable the user from selecting that component?

like changing

Component1.Enabled=1

to

Component1.Enabled=0

My second question kinda builds off this first one, by which I mean can you have multiple CRC check files for different combinations of components selected and tell ASIS which one to select based of the selected components?


(like checksums1.md5 for main files & checksums2.md5 for main files + ost)

[KaktoR]

Originally Posted by L33THAK0R

Alright got 2 more questions for you lads and then I promise I'll stop spamming 'em.

So I've got a repack with a few optional components and I was wondering if its possible for the setup once launched to have a look to see if the component file is present, and if it comes back false, can the setup disable the user from selecting that component?

like changing

Component1.Enabled=1

to

Component1.Enabled=0

My second question kinda builds off this first one, by which I mean can you have multiple CRC check files for different combinations of components selected and tell ASIS which one to select based of the selected components?


(like checksums1.md5 for main files & checksums2.md5 for main files + ost)

code change is neccessary for this

Originally Posted by L33THAK0R

Also a super small question, if I have a compressor that is name differently to how it is named in ASIS, is it possible to change this in ASIS? in this case I'm using "afr_019" but this isn't recognised by ASIS.

In latest version asis will use whatever you put inside setup.dll.

asis itself doesn't have any compressor settings anymore.

[L33THAK0R]

Originally Posted by KaktoR

code change is neccessary for this



In latest version asis will use whatever you put inside setup.dll.

asis itself doesn't have any compressor settings anymore.

Hey so this is a bit of a dumb question but where do you put setup.dll when you've generated it

[Cesar82]

Originally Posted by L33THAK0R

Hey so this is a bit of a dumb question but where do you put setup.dll when you've generated it

Setup.dll is a ".arc" file (compressed -m0..-m8 and renamed to .dll) that contains the compressors that must be placed next to Setup.exe.
If you rename the Setup.exe file for example to Install.exe, you must also rename the Setup.dll file to Install.dll.
The Setup.dll file is automatically generated by DiskSpan_GUI when compressing the game, but you can include different compressors as long as you also create the settings in the INI files.

In the COMPRESSOR folder on DiskSpan_GUI you have a ".bat" file called "_Compress Optional DLL (Drop Folder or Setup.dll) .bat" that is especially useful for this situation.
You just create a folder and put compressors, cls libraries and .ini files
After placing all decompressor files in a folder just click on the folder and drop the folder on the .bat file to create Setup.dll file.

The standard INI file names are:

- ARC_Optimal_x64.ini / ARC_Standard_x64.ini / CLS_Optimal.ini for when installation is done on 64-bit systems.
- ARC_Optimal_x64.ini / ARC_Standard_x64.ini / CLS_Standard.ini for when installation is done on 64-bit systems.

and

- ARC_Optimal_x86.ini / ARC_Standard_x86.ini / CLS_Optimal.ini for when installation is done on 32-bit systems.
- ARC_Optimal_x86.ini / ARC_Standard_x86.ini / CLS_Standard.ini for when installation is done on 32-bit systems.

P.S: Arc.ini/CLS.ini is also compatible and will be read if the ones mentioned above do not exist.

[L33THAK0R]

Originally Posted by Cesar82

Setup.dll is a ".arc" file (compressed -m0..-m8 and renamed to .dll) that contains the compressors that must be placed next to Setup.exe.
If you rename the Setup.exe file for example to Install.exe, you must also rename the Setup.dll file to Install.dll.
The Setup.dll file is automatically generated by DiskSpan_GUI when compressing the game, but you can include different compressors as long as you also create the settings in the INI files.

In the COMPRESSOR folder on DiskSpan_GUI you have a ".bat" file called "_Compress Optional DLL (Drop Folder or Setup.dll) .bat" that is especially useful for this situation.
You just create a folder and put compressors, cls libraries and .ini files
After placing all decompressor files in a folder just click on the folder and drop the folder on the .bat file to create Setup.dll file.

The standard INI file names are:

- ARC_Optimal_x64.ini / ARC_Standard_x64.ini / CLS_Optimal.ini for when installation is done on 64-bit systems.
- ARC_Optimal_x64.ini / ARC_Standard_x64.ini / CLS_Standard.ini for when installation is done on 64-bit systems.

and

- ARC_Optimal_x86.ini / ARC_Standard_x86.ini / CLS_Optimal.ini for when installation is done on 32-bit systems.
- ARC_Optimal_x86.ini / ARC_Standard_x86.ini / CLS_Standard.ini for when installation is done on 32-bit systems.

P.S: Arc.ini/CLS.ini is also compatible and will be read if the ones mentioned above do not exist.

I understand all this but what I mean is where physically should "setup.dll" be present when making the .exe with ASIS, or is it not included inside of the .exe generated by ASIS?

[Cesar82]

Originally Posted by L33THAK0R

I understand all this but what I mean is where physically should "setup.dll" be present when making the .exe with ASIS, or is it not included inside of the .exe generated by ASIS?

I had already answered before...
Setup.dll must be next to Setup.exe (Same folder) when starting the decompression using ASIS.

Complementing the answer, for those who did not understand:
Setup.dll is not needed before build Setup.exe.
ASIS will check if there is a file with the same name as the executable, but with a .dll extension and will extract it using UnArc.dll/IsDone.dll.
Only these 2 libraries are included in ASIS and are required prior to build Setup.exe.
Nothing else is needed inside Setup.exe during the build of Setup.exe.

[L33THAK0R]

Originally Posted by Cesar82

I had already answered before...
Setup.dll must be next to Setup.exe (Same folder) when starting the decompression using ASIS.

Complementing the answer, for those who did not understand:
Setup.dll is not needed before build Setup.exe.
ASIS will check if there is a file with the same name as the executable, but with a .dll extension and will extract it using UnArc.dll/IsDone.dll.
Only these 2 libraries are included in ASIS and are required prior to build Setup.exe.
Nothing else is needed inside Setup.exe during the build of Setup.exe.

Ah alright, sorry was just hoping that'd it'd be possible to put the needed resources inside of the ASIS generated .exe, as was possible with v7.2.0.0, guess I won't be using v7.2.2.0+ lol