ASIS: Advanced Simple Installer Script

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

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

[Masquerade]

Originally Posted by L33THAK0R

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.

Why are you not using xtool?

[L33THAK0R]

Originally Posted by Masquerade

Why are you not using xtool?

Best I can get with xtool (zlib codec, version 0.3.20), with srep and lolz, is ~9gb output (I forgot if thats with preflate or reflate, but I tried both), pzlib v3 is able to squash the input down to ~3gb, I know it's possible (and likely at this point) that the outputs from pzlib v3 may be corrupt, however they're in-line with results claimed by other users on this forum.

[:( Sad8669]

Try this thread.

Most probably caused by different versions of PZlib.

[KaktoR]

The Cesar update

v7.3.1
_____________________________________________________
- ASIS is now fully compatible with DiskSpan GUI v2.0+ (thanks to Cesar82)
  > Old DiskSpan GUI versions aren't compatible anymore
  > You can still use your own archives with ASIS (make Setup.dll manually!)
  > ASIS is now x64 ONLY!
- Remade the Redists code part (thanks to Cesar82)
  > You can now use theoretical unlimited items for your Redists
- Added options for InternalDLL and PasswordDLL inside Script.iss (thanks to Cesar82)
  > Putting Setup.dll next to the script will compress the DLL file into the Setup.exe file
  > Same password used in DiskSpan_GUI to extract decompressors from Setup.dll files
- Changed components (thanks to Cesar82)
  > The components are now exclusive for game collections
- Added Tasks (thanks to Cesar82)
  > With tasks you can define optional content to install for your installation, such 
    as languages, soundtrack, wallpapers, ... (this was the former components)
- It is now possible to use TXT and RTF files for EULA (thanks to Cesar82)
- Changed the time remaining label (thanks to Cesar82)
  > It will now be visible with more then one archive.
    Progress is now calculated according to the size of the arc generated by DiskSpan GUI.
    Example: If DiskSpan GUI generates 2 archives, the first 400 mb and the second 100 mb means 
    that the first archive will occupy 80% and the second 20%.
    So when extracting arc1, 0.80 will be passed in the second parameter (PctOfTotal) of IsDone's 
    IsArcExtract function. For the second file 0.20 will be sent.
    If you don't have the sizes in Records.ini, it will be divided by the number of files, which is 0.50/0.50.
    If you don't use DiskSpan GUI for generating records.ini, you can do it manually (like with records.inf)
- Updated BASS.dll library (thanks to Cesar82)
- Updated some other things (thanks to Cesar82)

I did many tests with this, but maybe I didn't test all 100%. If you encounter any bugs, let us know.

First post updated with new images.

[Cesar82]

Fix ASIS error on disable task page:
Change text in script line 4063.

#ifdef UseTasks

change to:

#if UseTasks

[L33THAK0R]

Would it be possible to add some of the changes to the CheckCRC section of ASIS v7.3.1 to v7.2.0? Specifically line 5527 under the [Custom Messages] section:

english.label2={#if CompactMode}Overall progress:{#else}Total files: %1  Files processed: %2    Ok: %3  Missing: %4  Bad: %5{#endif}

I attempted to do so myself but was met unsucessful.