FileForums - [CIUv3] Custom Installer Ultimate v3

FileForums (https://fileforums.com/index.php)

- Conversion Tutorials (https://fileforums.com/forumdisplay.php?f=55)

- - [CIUv3] Custom Installer Ultimate v3 (https://fileforums.com/showthread.php?t=102510)

is there a way to fix inno script with xtool when used with cls-diskspan.dll
when asked to enter setup.002 or 003 ect..
if you press cancel (the one inside) the setup just hang with xtool at 0%

function MyDiskRequest(APath, AFilename: String): String;
var
MsgResult: Integer;
begin
Result := APath;
if not FileExists(AddBackSlash(Result) + AFilename) then
repeat
MsgResult := MsgBox(GetMessage(1, AFilename,''), mbConfirmation, MB_OKCANCEL);
if MsgResult = mrCancel then
WizardForm.CancelButton.OnClick(nil);
if (MsgResult = mrOk) and (FileExists(AddBackSlash(Result) + AFilename) = False) then
if MsgBox(GetMessage(2,'',''), mbConfirmation, MB_YESNO) = mrYes then
if GetOpenFileName('', Result, Result, AFilename + '|' + AFilename, AFilename) then
Result := ExtractFileDir(Result);
until (FileExists(AddBackSlash(Result) + AFilename) = True) or (ISDoneError = True);
end;

:confused:

not the cancel button for the installer...
i'm talking about cancel button inside the browser when you asked to insert setup.002...
xtool.exe reamin in taskmanager the main cancel button work normally...
i think something to do with
if MsgResult = mrCancel then
WizardForm.CancelButton.OnClick(nil);

Quote:

Originally Posted by Simorq (Post 479317)

Hi Cesar82
http://s8.picofile.com/file/8351426642/Bug.jpg

In the "Setup requires" section there is a bug.
It should be 14 GB, not 140 gb

CIU 3.0.0.0 UPDATE 1 - HOTFIX 4

https://i.imgur.com/WxG8I5v.png

The value is correct.
GameSize key is in Mb.
14000 Mb = 13.67 (The MbToGb conversion used in CIU is around to 14.0 GB)
During the MbToGb conversion in CIU the division of the GameSize value is made by 1000, not by 1024 that would be correct
14000 Mb ~ 14.0 GB

Seems to be a problem with the font then.

few bugs found in last update Hotfix.4

[PercentLabel] , [PercentLabel] -> MoveY=50 still in original position rather then moving to setting

default {pf} is Program Files rather then old Program Files (x86)

When selecting Cancel after install has started leaves the install folder behind & doesnt delete it, when it did in earler versions. Also have to cancel 2-3 times before it actually does stop the install process.

Quote:

Originally Posted by pakrat2k2 (Post 479332)

default {pf} is Program Files rather then old Program Files (x86)

Code:

{pf}

Program Files. The path of the system's Program Files directory. {pf} is 

equivalent to {pf32} unless the install is running in 64-bit mode, in which 

case it is equivalent to {pf64}.

ive know that but it still sets it to Program Files rather then Program Files (x86) when it used to in earlier versions.

First image Hotfix 4

second image is from Update 1

they are BOTH in 64 bit mode!

Quote:

Originally Posted by pakrat2k2 (Post 479335)

Isnt it supposed to work this way? I mean, if you set x64 mode it should install to Program Files folder as its x64 only, with x64 mode disabled it should go to x86 folder as x86 can be used for both versions.

Quote:

Originally Posted by pakrat2k2 (Post 479332)

few bugs found in last update Hotfix.4

[PercentLabel] , [PercentLabel] -> MoveY=50 still in original position rather then moving to setting

It's working perfectly here.
NOTE: The progress bar label PercentLabel during uninstallation is fixed (it gets centralized and MoveX, MoveY is disabled in the uninstall bar)
https://i.imgur.com/IjDF7az.png

Quote:

Originally Posted by pakrat2k2 (Post 479332)

default {pf} is Program Files rather then old Program Files (x86)

If the 64BitOnly=1 option in Setup.ini
{pf} = Program Files
If the 64BitOnly=0 option in setup.ini
{pf} = Program Files (x86)

All other variables that have double paths (32 and 64 bits) are also changed using 64BitOnly=1.
Variables such as ComomFiles ({cf}) and others.
Using 64BitOnly=1 registry keys like HKEY_LOCAL_MACHINE\SOFTWARE are created in HKEY_LOCAL_MACHINE\SOFTWARE (Not in more at: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node)

Quote:

Originally Posted by pakrat2k2 (Post 479332)

When selecting Cancel after install has started leaves the install folder behind & doesnt delete it, when it did in earler versions. Also have to cancel 2-3 times before it actually does stop the install process.

I've already created an executable to do the deletion of the folder, which will be overwritten by the current Clean.bat that runs when exiting the installer.
The .bat file does not support special characters such as ™.

The delay when exiting the installer may be because when you cancel the installation, the uninstall process is done in silent mode (Does not display progress).
Depending on the number of files already installed that need to be erased, it may take some time before you quit the installer. (Erase files one by one)
Then I'll check the process of deleting folders better.
Maybe I put that when starting the files removal the cancel button is set to disabled, to avoid clicking it again.

Quote:

Originally Posted by Cesar82 (Post 479334)

The RequestDisk function in the CIU script is not valid for .002, .003, etc. files.
The RequestDisk window displayed while searching for .002, .003, etc. files is done inside the DiskSpan.dll library (not in CIU script).

[I]I did not quite understand his problem.
From what I understand the process XTool.exe is running if you cancel the search for the .002, .003, etc. file.
.

yes.
when used with xtool it just hang in the proccerss at 0% cls-lolz and cls-srep close but the installer remain stuck i need to press on cancel (installer) to exit but does not delete the files that installed...
i tested other script the same problem with xtool/ztool...
DiskSpan.dll

In InstallerScript_3.0.0.0.u1 [2019.02.05].iss the line numbers you said & what I extracted are 1 line different ?

@Cesar82
OnlyLabel=1 does not work on [SmallButton] ??

@Cesar

[CMDCommands], are they always executed from {app} folder or from {tmp} folder (working dir)?

Quote:

Originally Posted by pakrat2k2 (Post 479342)

In InstallerScript_3.0.0.0.u1 [2019.02.05].iss the line numbers you said & what I extracted are 1 line different ?

In the update1.hotfix4 script on the previous page, it's exactly lines 6024 and 6030. You may have inserted a line somewhere before line 6024 in the script.
--------------------------

Quote:

Originally Posted by houcine80 (Post 479344)

@Cesar82
OnlyLabel=1 does not work on [SmallButton] ??

Fixed in Hotfix 5.
--------------------------

Quote:

Originally Posted by KaktoR (Post 479348)

@Cesar
[CMDCommands], are they always executed from {app} folder or from {tmp} folder (working dir)?

I do not know if this was the question...
But the bat file (.cmd) is created inside the {tmp} directory.
An is-XXXXX.cmd file (XXXX, are randomly generated characters) is created.
TmpFile: = GenerateUniqueName(ExpandConstant ('{tmp}'), '.cmd');

found what was wrong by your image. You have to have values in PercentLabelSI as well.
I was just using PercentLabel, works as I wanted now.

thanks