This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- what to set in "LaunchCondition" for windows XP SP2 config check
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 18, 2008
06:44 AM
what to set in "LaunchCondition" for windows XP SP2 config check
Hi,
Using IS 2008 to build and generate .msi for client application.
I would like to know how to give condition in DirectEditor -> Launchcondition OR Execute Sequence -> LaunchConditions so that when user clicks on .msi to install, it gives the error popup message: "windows xp service pack2 is required" if SP2 is not installed on windows XP.
If I enable condition, it should not popup when user installs the same on Windows VISTA.
can anybody suggest how to define this condition?
Regards and Many thanks.
Using IS 2008 to build and generate .msi for client application.
I would like to know how to give condition in DirectEditor -> Launchcondition OR Execute Sequence -> LaunchConditions so that when user clicks on .msi to install, it gives the error popup message: "windows xp service pack2 is required" if SP2 is not installed on windows XP.
If I enable condition, it should not popup when user installs the same on Windows VISTA.
can anybody suggest how to define this condition?
Regards and Many thanks.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 18, 2008
07:31 AM
Search in the MSI help for
"Operating System Property Values". You will get a list of operating system properties and the values they have on different operating systems. With this informations you can build your conditions. E.g. VersionNT = 501 AND ServicePackLevel = 2 will indicate WindowsXP SP2.
Barbara
"Operating System Property Values". You will get a list of operating system properties and the values they have on different operating systems. With this informations you can build your conditions. E.g. VersionNT = 501 AND ServicePackLevel = 2 will indicate WindowsXP SP2.
Barbara
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 21, 2008
10:36 AM
Thanks for the reply.
To support the installation on windows XP and VISTA systems, I set the condition as follows under LaunchCondition table:
"Installed Or (((VersionNT = 500) And (ServicePackLevel > 1)) Or (VersionNT = 600))" (without quotes)
Description: This product requires windows XP service pack level 2.
However, even after uninstalling SP2 from my XP machine, installer goes fine without any error popup 😞
Can anybody correct me where I am wrong?
Thanks a lot in advance!!!
To support the installation on windows XP and VISTA systems, I set the condition as follows under LaunchCondition table:
"Installed Or (((VersionNT = 500) And (ServicePackLevel > 1)) Or (VersionNT = 600))" (without quotes)
Description: This product requires windows XP service pack level 2.
However, even after uninstalling SP2 from my XP machine, installer goes fine without any error popup 😞
Can anybody correct me where I am wrong?
Thanks a lot in advance!!!
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 21, 2008
12:28 PM
Based on your logic, you're testing for Windows 2000 SP2 or later. See: http://msdn.microsoft.com/en-us/library/aa370556(VS.85).aspx
The only way that condition would ever be true on a Windows XP machine is if you had the product already on the machine. Have you validated the Installed value in a log file?
For more information on creating an MSI log file, please reference this article:
http://support.installshield.com/kb/view.asp?articleid=Q104807
The only way that condition would ever be true on a Windows XP machine is if you had the product already on the machine. Have you validated the Installed value in a log file?
For more information on creating an MSI log file, please reference this article:
http://support.installshield.com/kb/view.asp?articleid=Q104807