This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Conditional Reboot
Started by
cherukus
, Jul 01 2004 16:39
7 replies to this topic
Posted 01 July 2004 - 16:39
I am using Basic MSI - Installshield Developer 8.0.
I want to prompt the user to Reboot his PC after he installed MSDE & APP.
I don't want to invoke the reboot when when he uninstalled the APP and also when he re-installed the APP.
I tried setting a flag in the ScheduleReboot in the Install Execute Sequences, but seems NO effect.
Schedule Reboot
Condition : ISSCHEDULEREBOOT Or MSDEInstalled
MSDEInstalled flag is set to Yes when the user installs MSDE, if not by default it is set to NO.
Appreciate any ideas !!!
I want to prompt the user to Reboot his PC after he installed MSDE & APP.
I don't want to invoke the reboot when when he uninstalled the APP and also when he re-installed the APP.
I tried setting a flag in the ScheduleReboot in the Install Execute Sequences, but seems NO effect.
Schedule Reboot
Condition : ISSCHEDULEREBOOT Or MSDEInstalled
MSDEInstalled flag is set to Yes when the user installs MSDE, if not by default it is set to NO.
Appreciate any ideas !!!
Posted 02 July 2004 - 08:47
If the value of property MSDEInstalled is either Yes or No, then use this condition:
ISSCHEDULEREBOOT Or MSDEInstalled~="yes"
The ~ performs a case insensitive string comparison
ISSCHEDULEREBOOT Or MSDEInstalled~="yes"
The ~ performs a case insensitive string comparison
Stefan Krüger
InstallSite.org twitter facebook
Posted 02 July 2004 - 17:34
Unfortunately after I made this change, it is never invoking the Reboot.
I am not quite sure why it's behaving differently.
I am not quite sure why it's behaving differently.
Posted 05 July 2004 - 15:39
In which sequence are you setting the MSDEInstalled property? Since it has lower case characters in its name it's a private property, its value is only available in the sequence where it was set. So if you set it in the UI sequence you cannot read it in execute sequence.
Stefan Krüger
InstallSite.org twitter facebook
Posted 06 July 2004 - 20:13
Yep..you are right. I was not aware that it would be a private property.
How do I make this a public property so that I would be able to access the value in the Execute Sequence.
How do I make this a public property so that I would be able to access the value in the Execute Sequence.
Posted 07 July 2004 - 08:51
Public properties must be in all capital letters
Stefan Krüger
InstallSite.org twitter facebook
Posted 15 July 2004 - 04:33
Just a note: if your setup is run by a regular user with elevated rights not all public properties are sent to the execute sequence, only the properties enumerated in the SecureCustomProperties property. In other words I would add your custom property to this list:
Example: SecureCustomProperties: MYUPGRADE;MSDEINSTALLED
Info: http://msdn.microsof...es_property.asp
Example: SecureCustomProperties: MYUPGRADE;MSDEINSTALLED
Info: http://msdn.microsof...es_property.asp
Regards
-Stein Åsmul
-Stein Åsmul