ASIS: Advanced Simple Installer Script

[gen40]

this is cool epic i will use this when i do my next repack

[L33THAK0R]

hey so I'm pretty dumb/simple/touched in the head, how can I get like an optional .bin or whatever working with ASIS? Not looking to have it as a select-able option in the GUI just want to be able to put an "optional.bin" in the root directory for the installer and it to extract it, sorry if this is a silly question.

[KaktoR]

Add a second record to Records.ini

[L33THAK0R]

Originally Posted by KaktoR

Add a second record to Records.ini

Thank you so much for your quick response, got another quick question, how can I select AFR 0.20 in the "COMPRESSOR_GUI.exe"? Using ASIS v7.2.0.0 and can only seem to select 0.19. Sorry if its a bit of a silly question.

[KaktoR]

I think you have to hold CTRL key and click on "default" if I remember right.

[L33THAK0R]

Originally Posted by KaktoR

I think you have to hold CTRL key and click on "default" if I remember right.

sick as, cheers man, works like a charm

[L33THAK0R]

Hey dunno if anyone knows how to or if it's even possible with ASIS, but is there a way to get ASIS to delete a specified file at the end of install? Got this really annoying 40mb junk temp file that isn't getting cleaned up and was wondering if there was a way I can get the installer to remove it.

[Masquerade]

Originally Posted by L33THAK0R

Hey dunno if anyone knows how to or if it's even possible with ASIS, but is there a way to get ASIS to delete a specified file at the end of install? Got this really annoying 40mb junk temp file that isn't getting cleaned up and was wondering if there was a way I can get the installer to remove it.

if CurStep = ssPostInstall then begin
    DeleteFile(ExpandConstant('{app}\<path to file>'));

[L33THAK0R]

Originally Posted by Masquerade

if CurStep = ssPostInstall then begin
    DeleteFile(ExpandConstant('{app}\<path to file>'));

fuckkk absolute legend, cheers brother

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

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

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