[CIUv3] Custom Installer Ultimate v3

[andreiutzu21]

Originally Posted by Cesar82

@andreiutzu21, let me know if the dot is displayed when unchecking the components (like: 0. MB) in the setup.exe file attached HERE and let me know.

the dot is not there after the 0 but at VRAM is the same it shows 3 gb instead of 4

[Cesar82]

Originally Posted by andreiutzu21

the dot is not there after the 0 but at VRAM is the same it shows 3 gb instead of 4

That VRAM without problem.

THE STORY:
The CIU formerly at the time of Yener90 used the get_hw_caps.dll library to detect hardware.
As some functions stopped working with this library after the release of new versions of windows, the CIU started to use the ISSysInfo.dll library (by petef1999).
However, after the emergence of GPUs with VRAM greater than 4 GB, this library began to not correctly detect the VRAM of these GPUs.
Then I searched for efficient hardware detectors for VRAM, until in "CIU 3.0.0.0_b9.u1.HF6" I made my own version in the CIU script itself getting the values in the windows registry, but using the same ISSysInfo library .dll to read GPU name
But that wasn't so efficient because as you commented the labels were smaller on "CIU 3.0.0.0_b9.u1.HF6" (see it has 2 video card names).
What happens is that in idle mode, current laptops turn off the dedicated video card using only the integrated Intel HD Graphics card.
So after that in "CIU 3.0.0.0_b9.u2" Razor12911 helped me by improving a code which he himself had shared in the debate about not having a functional VRAM detect code so that this code would not only detect Namee VRAM of all GPUs and generate a list. Now it ordered and returned only the highest VRAM value (a logic because the dedicated card would probably always have the highest VRAM).
So I inserted Razor12911's code into CIULib.dll trying to make the VRAM check faster than the script itself using my code.

Now I perfected my script code to not only get the largest VRAM, but also read the name of the current GPU that has the largest VRAM size (I hope it's not slow).
I will send you a PM soon with test file.
If possible send me by PM the original captured images of your previous post b9.u1.HF6 (the labels are illegible).
Thanks.

[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

[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