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
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Environment Variables in Vista
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 08, 2009
09:53 AM
Environment Variables in Vista
We are running into a problem where environment variables set within a command prompt are not defined for the installer when the installer is invoked from that command prompt. This is only happening when run on Vista.
For example, if we run the following from a command prompt on Vista:
set CONFIG_FILE=c:\custom_install.properties
setup.exe
The environment variable CONFIG_FILE is not defined when we try to access it during installation. We rely on this to know when the user wants to run in configuration mode, where they can create a custom install properties file.
Has anyone else seen this and have a workaround? We are using InstallAnywhere 8.0.1
For example, if we run the following from a command prompt on Vista:
set CONFIG_FILE=c:\custom_install.properties
setup.exe
The environment variable CONFIG_FILE is not defined when we try to access it during installation. We rely on this to know when the user wants to run in configuration mode, where they can create a custom install properties file.
Has anyone else seen this and have a workaround? We are using InstallAnywhere 8.0.1
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 10, 2009
08:43 AM
If you want your installer to read from the properties file you mentioned, the simplest way would be to launch your installer like this:
setup.exe -f c:\custom_install.properties
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 10, 2009
07:30 PM
We're actually not trying to read from an existing properties file, we are trying to generate a properties file. Our installer has a configuration mode, where we ask the user questions about the type of custom installer properties file that they would like to create. For example, we ask them which components they would like to be available, enabled, selected, etc. Based on their answers, we write out a custom install properties file to be used later as you suggested (setup.exe -f custom_install.properties). Our installer relies on the existence of an environment variable to know to run in configuration mode, rather than the normal installation mode. For some reason, when running on Vista, if the installer is run in a command prompt where the environment variable has been defined, it is not defined in the installer's environment.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 20, 2009
01:08 PM
We ran into the same problem on Vista and Windows 2008. The work around is to set it in the Windows "Environment Variables" screen instead.
But if anybody figure out how to make it work setting it in the command prompt, I would like to know.
But if anybody figure out how to make it work setting it in the command prompt, I would like to know.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)