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
- :
- Re: Target system minimum RAM requirement
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
‎Jun 29, 2015
09:42 AM
Target system minimum RAM requirement
Hello all,
Using Installshield 2014 Pro, creating an Installscript project. I want to be able to check to make sure the target system has at least 8GB of RAM before installing. How can I do this?
Thanks,
David
Using Installshield 2014 Pro, creating an Installscript project. I want to be able to check to make sure the target system has at least 8GB of RAM before installing. How can I do this?
Thanks,
David
(8) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2015
10:11 AM
Does this help any?
http://helpnet.installshield.com/installshield18helplib/IHelpBuildCondition.htm
PhysicalMemory >= 8192
I am assuming that you are creating a basic MSI project. You did not specify the project type.
http://helpnet.installshield.com/installshield18helplib/IHelpBuildCondition.htm
PhysicalMemory >= 8192
I am assuming that you are creating a basic MSI project. You did not specify the project type.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2015
10:36 AM
It's an InstallScript project. I don't see anything about install conditions on the General Information tab.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2015
10:55 AM
You are correct about the General tab; but you can add to the OnBegin event I suspect to perform your check. Just make sure that it only runs on first run or you may get behavior you do not like when trying to uninstall a product if a consumer has modified memory at all. I realize this is a corner case but it is good to be aware of it.
You will want to use GetSystemInfo I believe.
http://helpnet.installshield.com/installshield18helplib/mergedProjects/installshield18langref/LangrefGetSystemInfo.htm
You will want to use GetSystemInfo I believe.
http://helpnet.installshield.com/installshield18helplib/mergedProjects/installshield18langref/LangrefGetSystemInfo.htm
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2015
11:23 AM
Thanks Dan, I think this is getting me on the right track. I have added the OnBegin function, but it looks like the prereqs are running before that gets called. Is there a way to check before any of the prereqs start?
Thanks,
David
P.S. I'm still very new with Installshield, I appreciate your patience.
Thanks,
David
P.S. I'm still very new with Installshield, I appreciate your patience.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2015
12:13 PM
Ouch! I wish I could give you some tips there. Back when I was handling pure InstallScript installations I was scripting all of my 'prerequisites' during the product install; I don't even think they had a concept like 'prerequisites'. Hopefully someone from Flexera can chime in and provide guidance or someone who handles this more frequently.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2015
12:32 PM
I'm looking into possibly running a powershell script that can return the physical memory as the first prerequisite. We'll see how that goes. Thanks for all of your help Dan!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2015
12:41 PM
Are you comfortable with creating a C++ EXE That does the check for you using the GetPhysicallyInstalledSystemMemory? It would avoid any problems with executing scripts on systems that do not have PowerShell activated, although perhaps InstallShield has a way around this problem. Just a thought.
Here is a code example: https://msdn.microsoft.com/en-us/library/windows/desktop/aa366589%28v=vs.85%29.aspx
Here is a code example: https://msdn.microsoft.com/en-us/library/windows/desktop/aa366589%28v=vs.85%29.aspx
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2015
03:13 PM
Here's what I did to solve the problem...
1. Created a powershell script that checks for at least 8gb of RAM. If more than 8gb, it writes a text file to the CommonFiles folder.
2. Created a prerequisite that looks for the text file. If the file isn't there, it runs the powershell script. If that fails, the install terminates.
I include powershell.exe AND the script file in my prerequisite. I tested disabling Powershell on a Win 8.1 VM and it still runs fine.
Thanks for all the help Dan!
1. Created a powershell script that checks for at least 8gb of RAM. If more than 8gb, it writes a text file to the CommonFiles folder.
2. Created a prerequisite that looks for the text file. If the file isn't there, it runs the powershell script. If that fails, the install terminates.
I include powershell.exe AND the script file in my prerequisite. I tested disabling Powershell on a Win 8.1 VM and it still runs fine.
Thanks for all the help Dan!
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)