ASIS: Advanced Simple Installer Script

[L33THAK0R]

Hi all,

Is it possible to rename a series of files extracted OR all files with a given extension, post-extraction, or would this require a rewrite of the script?

[Masquerade]

Originally Posted by L33THAK0R

Hi all,

Is it possible to rename a series of files extracted OR all files with a given extension, post-extraction, or would this require a rewrite of the script?

Simply include a bat file in your archive with the required commands then use Exec2 to run the bat file in the "ssPostInstall" phase.

[L33THAK0R]

Originally Posted by Masquerade

Simply include a bat file in your archive with the required commands then use Exec2 to run the bat file in the "ssPostInstall" phase.

I completely forgot about using the redistributables function! Argh, sorry for the silly question, thank you for your assistance!

[Masquerade]

I assume

ISDoneStop;

will stop the install timer?

[Cesar82]

Originally Posted by Masquerade

I assume

ISDoneStop;

will stop the install timer?

In the ISDone documentation it says:

1)
function ISDoneStop: boolean;

During a test pass, it calculates all data by checkpoints and writes to the file specified in the initialization, clears some variables, etc.

2)
Stopping internal library timers, freeing memory from library variables, writing the records.inf file during a test run, etc.

Original information:
1)
при тестовом проходе рассчитывает все данные по чекпоинтам и записывает в файл, заданный в инициализации, очищает некоторые переменные, и т.д.

2)
остановка внутренних таймеров библиотеки, освобождение памяти от переменных библиотеки, запись файла records.inf при тестовом прогоне, и т.д.

I think it's a deinitialization function (like IsDoneUnInit).
But if you call IsDoneInit and after the procedure calls ISDoneStop it is necessary to call UnloadDLL(<isdonedllpath>) to be able to initialize the IsDoneInit function again (If you don't call UnloadDLL you will get an error message).

I can say this because I had to do this in order to extract the decompressor files from DLL Setup.dll in CIU.
Initially CIU extracts only Records.ini to check the installer type information, then Isdone is rebooted to extract the decompressor files and finally if everything is ok, reboots again to perform game extraction.

[Masquerade]

I am mainly trying to pinpoint when the installer timer is stopped so I can move this point to further in the script to keep the timer running despite all archives finishing extraction.

[Cesar82]

Originally Posted by Masquerade

I am mainly trying to pinpoint when the installer timer is stopped so I can move this point to further in the script to keep the timer running despite all archives finishing extraction.

As far as I could understand, ISDoneStop is always between the begin end of ISDoneInit.
Maybe you shouldn't call IsDoneStop without successfully initializing it.
Other than that you can initialize and finalize whenever you want (You can initialize in InitializeWizard and Finalize in DeinitializeSetup if necessary (Just placing a globar variable to receive the result of the ISDoneInit function.

[L33THAK0R]

Hi all,

Does anyone know how to force the redists box for ASIS to be ticked? I'm currently using the redists to force some scripts to run and don't want there to be any chance of the end-user mucking up the install.

Another question I have is does anyone know why, in v7.2.0 compact mode, the redists box remains unavailable, however in v7.2.2a compact mode, the redist box is selectable?

EDIT: After editing the v7.2.0 script a bit I got the redists to work, however I'm yet to figure out the answer to my first question.

[Masquerade]

L33THAK0R

Why not go to the ssPostInstall part of the setup and write an Exec2 statement to run your script?

This way, the script will be ran instantly after the files are extracted, Regardless of whether the user opts to install redists or not.

[L33THAK0R]

Originally Posted by Masquerade

L33THAK0R

Why not go to the ssPostInstall part of the setup and write an Exec2 statement to run your script?

This way, the script will be ran instantly after the files are extracted, Regardless of whether the user opts to install redists or not.

Honestly I investigated your suggestion and using the redists seems like the easiest solution. Did about 5 minutes of looking through the script (I posted my question rather hastily, as I was excited to finish my repack of the series this method is required for, and was caught up in the moment talking to some lads and a quite skilled re-packer about it.), and figured out the function/call/whatever its classified as that's responsible for checking if the redists are selected is "UseRedists" (for anyone looking for a similar solution in the future) on line ~4918 (I've modified ASIS v7.2.0 a fair bit to suit my needs better so the line number might not be exact), and it works perfectly.

[L33THAK0R]

Originally Posted by Masquerade

L33THAK0R

Why not go to the ssPostInstall part of the setup and write an Exec2 statement to run your script?

This way, the script will be ran instantly after the files are extracted, Regardless of whether the user opts to install redists or not.

Just wanted to update and say yeah you're right ssPostInstall is heaps cleaner to organise than a redist, decided to take your advice, thanks for the help!

[L33THAK0R]

Hi all,

Does anyone know how to add additional commands/options to srep for unpacking with ASIS? I'm currently using pzlib v3 (xtool doesn't inflate the files as well) + srep + lolz/rz (experimenting with different combinations right now) for the 2015 title "Mad Max" and I always seem to get either a -1 or CRC fail error at some point when unpacking. According to this thread using the "-hash" command to ignore bad CRC checks, may resolve this bug, and if not then I'll just have to investigate a different method. Would it be as simple as editing the arc.ini to include a srep header or would I need to add/edit something in the script? Thanks for taking the time to read this post.

[Masquerade]

Originally Posted by L33THAK0R

Hi all,

Does anyone know how to add additional commands/options to srep for unpacking with ASIS? I'm currently using pzlib v3 (xtool doesn't inflate the files as well) + srep + lolz/rz (experimenting with different combinations right now) for the 2015 title "Mad Max" and I always seem to get either a -1 or CRC fail error at some point when unpacking. According to this thread using the "-hash" command to ignore bad CRC checks, may resolve this bug, and if not then I'll just have to investigate a different method. Would it be as simple as editing the arc.ini to include a srep header or would I need to add/edit something in the script? Thanks for taking the time to read this post.

I had no issues decompressing mad max when using profrager's cls-srep.

If you are using srep.exe to decompress, try with cls-srep

[L33THAK0R]

Originally Posted by Masquerade

I had no issues decompressing mad max when using profrager's cls-srep.

If you are using srep.exe to decompress, try with cls-srep

Darn, might be the version of pzlib I'm using then! I've been using the stock standard cls-srep that ASIS v7.2.0 ships with, time to test out some older versions of pzlib me thinks.

[:( Sad8669]

Try this thread.

Most probably caused by different versions of PZlib.