Set MAAVIS_HOME on install
For integration with GPII we need to set a MAAVIS_HOME environment variable on install that poinnts to the install directory in which the executable files and media folder reside.
Leave a comment
The Inno Setup FAQ says:
Setting Environment Variables
On Windows NT/2000/XP/2003, environment variables are stored as string values in the registry, so it is possible to manipulate them using the [Registry] section. System-wide environment variables are located at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
User-specific environment variables are located at:
HKEY_CURRENT_USER\Environment
On Windows 95/98/Me, you'll need to modify AUTOEXEC.BAT to set environment variables. Inno Setup does not include any built-in feature for that, however you could write a small program to do that and execute it via the [Run] section (more info).
Setting Environment Variables
On Windows NT/2000/XP/2003, environment variables are stored as string values in the registry, so it is possible to manipulate them using the [Registry] section. System-wide environment variables are located at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
User-specific environment variables are located at:
HKEY_CURRENT_USER\Environment
On Windows 95/98/Me, you'll need to modify AUTOEXEC.BAT to set environment variables. Inno Setup does not include any built-in feature for that, however you could write a small program to do that and execute it via the [Run] section (more info).
file:cfu9DyZdmr4yVoacwqjQXA
Environment settings for GPII integration
Environment settings for GPII integration
Thanks for the patch Ross. I'll add it to trunk and then the next release.
Note however currently Maavis is a portable app which means setting environment variables for absolute paths to the installed location does not make sense in the general case. However for the sake of GPII integration we can restrict to installing to a local non-removeable device. It would probably make more sense to set these env vars in the cmd files that launch Maavis.
As being a portable App may not be the right decision I have created the related ticket #217 to discuss this.
Note however currently Maavis is a portable app which means setting environment variables for absolute paths to the installed location does not make sense in the general case. However for the sake of GPII integration we can restrict to installing to a local non-removeable device. It would probably make more sense to set these env vars in the cmd files that launch Maavis.
As being a portable App may not be the right decision I have created the related ticket #217 to discuss this.
(In maavis:268) Corrected version to 2.3 and added seting env vars for HOME and MEDIA. Fixes #216