ASIS: Advanced Simple Installer Script

[L33THAK0R]

Is it possible to call the "UnpackDLLFiles" function early, ideally at the initialisation of the wizard? I recently switched to using a VCLStyle skin instead of CJStyle skin (as CJStyles arent able to modify some GUI elements and aren't quite as versatile), however the DLL size difference between the two is alarmingly large (2.98MB vs 385KB). However, applying some very basic compression, such as the parameters used to pack a given "Setup.dll" significantly reduces the VCLStyle DLL to ~700kb, unfortunately though it seems I'm not able to get the wizard to extract the DLL before loading it, despite having the commands ordered to do so.

function InitializeSetup(): Boolean;
begin
  Result := True;
  ExtractTemporaryFile('SplitLib.dll');
  ExtractTemporaryFile('Settings.ini');
  #if VCL
    FileCopy(ExpandConstant('{src}\VclStylesInno.dll'), ExpandConstant('{tmp}\VclStylesInno.dll'), False);
    ExtractTemporaryFile('VclStylesInno.dll');
    ExtractTemporaryFile('{#VCLName}');
    LoadVCLStyle(ExpandConstant('{tmp}\{#VCLName}'));

I can't quite decipher the errors I get either as they simply say:

Runtime error (at 368:722):
Could not call proc.

&

Runtime error (at 400:5):
Could not call proc.

Am I missing something or is this sort of extracting and loading DLLs a bit too finicky for Inno Setup to handle?

[KaktoR]

Originally Posted by L33THAK0R

Is it possible to call the "UnpackDLLFiles" function early, ideally at the initialisation of the wizard? I recently switched to using a VCLStyle skin instead of CJStyle skin (as CJStyles arent able to modify some GUI elements and aren't quite as versatile), however the DLL size difference between the two is alarmingly large (2.98MB vs 385KB). However, applying some very basic compression, such as the parameters used to pack a given "Setup.dll" significantly reduces the VCLStyle DLL to ~700kb, unfortunately though it seems I'm not able to get the wizard to extract the DLL before loading it, despite having the commands ordered to do so.

function InitializeSetup(): Boolean;
begin
  Result := True;
  ExtractTemporaryFile('SplitLib.dll');
  ExtractTemporaryFile('Settings.ini');
  #if VCL
    FileCopy(ExpandConstant('{src}\VclStylesInno.dll'), ExpandConstant('{tmp}\VclStylesInno.dll'), False);
    ExtractTemporaryFile('VclStylesInno.dll');
    ExtractTemporaryFile('{#VCLName}');
    LoadVCLStyle(ExpandConstant('{tmp}\{#VCLName}'));

I can't quite decipher the errors I get either as they simply say:

Runtime error (at 368:722):
Could not call proc.

&

Runtime error (at 400:5):
Could not call proc.

Am I missing something or is this sort of extracting and loading DLLs a bit too finicky for Inno Setup to handle?

You have to call function UnpackDLLFiles directly in function InitializeSetup

Originally Posted by L33THAK0R

Sorry to fill up this thread with questions, but could anyone please tell me where abouts the logic is for the transition between CompactMode's Main-Window and the CRC-Window?

I use QuickSFV for CRC validation and was hoping to add a 3rd & 4th state to the "WizardForm.NextButton" (or whatever the label is for the CompactMode Install button), to allow it to launch a given Batch script, while displaying "Verify"/"cm:Verify", and then function as a Finish/Continue button after the script concluded.

Currently I've got the latter functionality working just fine, I'm just trying to figure out how to discard the separate CRC window to move it all to the one screen.

If you want to use quicksfv instead of the crc page in compactmode you have to disable the crc page creation and call quicksfv instead.

[L33THAK0R]

Originally Posted by KaktoR

You have to call function UnpackDLLFiles directly in function InitializeSetup

Ah alright I'll give that a shot!

Originally Posted by KaktoR

If you want to use quicksfv instead of the crc page in compactmode you have to disable the crc page creation and call quicksfv instead.

Would you happen to know by any chance what the label/function is that calls the crc page post-install, I cant for the life of me seem to figure it out!

[KaktoR]

Originally Posted by L33THAK0R

Would you happen to know by any chance what the label/function is that calls the crc page post-install, I cant for the life of me seem to figure it out!

If you search for "#if CheckCRC" you will get all things related to crc check.

The crc page is a custom created page, "CurPageID = CRCPage.ID"

This page will be created here

    #if !CompactMode //if NOT compactmode (= normal mode)
      CRCPage := CreateCustomPage(wpInstalling, '', ''); //crc page will be created after wpInstalling page
    #else // if compact mode
      CRCPage := CreateCustomPage(wpInfoAfter, '', ''); //crc page will be created after wpInfoAfter page (compactmode works a bit different due to 1 page installer)
    #endif

Use Exec or Exec2 funtion on ssPostInstall step to start quicksvf.exe. You can search there for "#if UseBatch" to get an idea how it should look like with quicksvf.exe.

Originally Posted by L33THAK0R

Sorry again to seemingly never run out of queries, I'm a bit of a brainlet, if it's at all alright would you be able to walk me through the values/arguments I should be attaching to "UnpackDLLFiles", I'm not too sure about the

(UnpFile: String): Boolean;

side of things, with trusty Dr. Google not really making clear what a "UnpFile" designation is.

Example

function InitializeSetup(): Boolean;
begin
...
UnpackDLLFiles;
...

UnpFile is a custom string designated to UnpackDLLFiles function and is only valid inside this function.