Archive: about timer


about timer
It is possible to force the user to wait 2 sec before clicking next

the reason is simple, my installer check if access RT is intall, if not --> then i popup the install msi of access RT. Depending the speed of the computer Access RT pop fast or slowly. IF it pop slowly the user can press next next next next and do my instllation before the access rt pop up

in that case my installation is ruine :-(

So with a small time of 2 sec i force tnhe pop-up to show and hide my screnn (user cant do next) :-)


So it is possible

Olivier from the city of Québec !


You could use ExecWait, and then your installer will wait till the MSI is finished. You might need to use a switch on the MSI command-line if that does not work.

-Stu


I try to call the other setupe.exe with ExecWait

but that change nothing..


So the NSIS installer does not wait for the MSI installer to finish?
If so, then try ExecWait "file.msi /wait"

-Stu


that interesting because.. it work, my install freeze duing the execution of my msi... butwhen my msi finish, my install start to blink and quit....


.......


that interesting because.. it work, my install freeze duing the execution of my msi... butwhen my msi finish, my install start to blink and quit....
The freezing is common because it's like the Sleep command with a timer that doesn't "wake up" the installer until the other program is closed.

About the "start to blink and quit", probably somewhere in script there is an Abort or Quit command or you did specify AutoCloseWindow to true or a custom page being skiped due to wrong INI file.

If it continues not to work, I'm suggest you to attach the script as a file.

EDITED

I only have the problem when i put the "wait " command

and i dont have any quit ...


The freezing you can't solve, but the other one involving the installator being closed after that, yes.