NewsArchive
04-19-2010, 01:48 AM
Hi Friedrich,
if my setup detects, that it runs on a terminal server, it checks wheter
the terminal server is in installation mode. If not, it switches the
server in installation mode and restarts itself. If the installation has
finished, it switches back the terminal server in execution mode.
But if the user cancels the setup (via cancel button on a dialog) or if
the setup fails, the terminal server remains in installation mode.
For this purpose (and a lot more), I would need a possibility to run
some script actions, if the setup is aborted.
I would suggest the following:
1.) A new #pragma ABORT = "1". This marks an include script as a special
script, which is executed, if the installation ist aborted, a liitble
bit like the unsinstall pragma.
2.) If the user cancels the installation in the dialog loop, the
%_SB_NEXTDIALOGID% holds a special value, so the abort script can
detect, wheter the user aborts the installation in the dialog loop or
anywhere else.
What do you think?
Markus
if my setup detects, that it runs on a terminal server, it checks wheter
the terminal server is in installation mode. If not, it switches the
server in installation mode and restarts itself. If the installation has
finished, it switches back the terminal server in execution mode.
But if the user cancels the setup (via cancel button on a dialog) or if
the setup fails, the terminal server remains in installation mode.
For this purpose (and a lot more), I would need a possibility to run
some script actions, if the setup is aborted.
I would suggest the following:
1.) A new #pragma ABORT = "1". This marks an include script as a special
script, which is executed, if the installation ist aborted, a liitble
bit like the unsinstall pragma.
2.) If the user cancels the installation in the dialog loop, the
%_SB_NEXTDIALOGID% holds a special value, so the abort script can
detect, wheter the user aborts the installation in the dialog loop or
anywhere else.
What do you think?
Markus