[CIUv3] Custom Installer Ultimate v3

[Cesar82]

Originally Posted by Proxson

It's me again.

Ok, after a while...ermm....cough.... I have noticed some non logical steps in the installation process. It's about the Customize and Next option at the first setup window/page whatever. If you choose Customize then you go through the steps like EULA page, info page, hardware requirements page etc. That's ok but if you choose directly the Next button then the installation promptly begins. Here comes the non logical part. If there is an EULA and by not accepting it, you can't proceed with the installation which is on the other hand bypassed when Next (prompt) is chosen. Long story short, the EULA page and info page should appear in both ways, no matter what you choose. This should be fixed by all means. Thanks guys for your great work btw. Cheers.

Something like this:

Customize --> EULA (if there) --> Info (if there) --> Hardware requirements --> Components --> Tasks --> Installation path --> Prerequisites --> Install

or

Next --> EULA (if there) --> Info (if there) --> Hardware requirements --> Install

Thank you for your opinion.

This FAST mode is used since the original project that Yener90 created, so I didn't want to change it.

You can let your installers behave without this FAST mode (So it will always show the license).
For that, try using EnableFastInstall = 0 in the [InterfaceSettings] section.

If more users find the requested behavior better, I change it.
But I particularly prefer a FAST mode as is (Perhaps with an additional ready page (not currently supported) to know what is being installed and where, like components, tasks, directory, etc.).

Perhaps a solution would be to put an additional key to activate the behavior mode you suggested.
What do you think?

[Proxson]

The fault was on my side. facepalm.jpg

Setting EnableFastInstall = 0, resolved the problem. I am so embarrassed !
Next time I should ....READ THE F***ING MANUAL ! Sorry guys.

Anyways, EnableFastInstall should be set to zero by default. Me thinks it's proper.

Originally Posted by Cesar82

Perhaps a solution would be to put an additional key to activate the behavior mode you suggested.
What do you think?

It's all up to you mate. Now it works as it should but if you catch some time you could add that additional key. Why not have both after all.

[Proxson]

*bump

@Cesar mate,

is there an option to set a custom icon for the executable shortcuts which are placed in the Group and desktop. The installer picks the default exe icon.

[Cesar82]

Originally Posted by Proxson

*bump

@Cesar mate,

is there an option to set a custom icon for the executable shortcuts which are placed in the Group and desktop. The installer picks the default exe icon.

[Executable#]

Icon={app}\myicon.ico

[Proxson]

You're quick as always.

It won't budge mate. It's still placing the default icon. Dunno.

[Executable1]

Name=Play House of Ashes
Exe=HouseOfAshes.exe
ExePath=0
ShortcutProt=1
RunAsAdmin=0
Icon={app}\HouseOfAshes.ico

Edit: If it needs some huge script rewriting then leave it as it is. It's not that important.

Edit 2: Ok, I have managed it by disabling the executable key and created the shortcuts in the custom shortcuts section. But now the 'create shortcut on desktop' box is disabled.

//[Executable1]

Name=Play House of Ashes
Exe=HouseOfAshes.exe
ExePath=0
ShortcutProt=1
RunAsAdmin=0

[CustomShortcuts]


Shortcut6={group}\Play House of Ashes; Destination:{app}\HouseOfAshes.exe; IconFile:{app}\HouseOfAshes.ico
Shortcut7={commondesktop}\Play House of Ashes; Destination:{app}\HouseOfAshes.exe; IconFile:{app}\HouseOfAshes.ico

[Proxson]

*bump

Btw, guys. Maybe it's a stupido question but how do you generate external MD5 checksum files ? Which tools do you use ? Thanks