Setting Environment Variables - Revision history

Anders: Added EnVar_plug-in link

2018-11-27T23:36:27Z

Added EnVar_plug-in link

â† Older revision		Revision as of 23:36, 27 November 2018
Line 1:		Line 1:
	{{PageAuthor\|KiCHiK}}		{{PageAuthor\|KiCHiK}}

	<div style="background-color:#ff9999; color:#f00; border:2px solid #f00; padding:1em;"><font size="+1"><b>WARNING:</b> Strings longer than ${NSIS_MAX_STRLEN} will get truncated/corrupted. Do NOT use this function to update %PATH%</font></div>		<div style="background-color:#ff9999; color:#f00; border:2px solid #f00; padding:1em;"><font size="+1"><b>WARNING:</b> Strings longer than ${NSIS_MAX_STRLEN} will get truncated/corrupted. Do NOT use this function to update %PATH%, use the [[EnVar_plug-in]] instead.</font></div>

Drmarbuse: /* Exisiting Variables */ relativated the obsolitedness of the function described in this section.

2016-10-21T17:23:13Z

Exisiting Variables: relativated the obsolitedness of the function described in this section.

â† Older revision		Revision as of 17:23, 21 October 2016
Line 22:		Line 22:
	=== Exisiting Variables ===		=== Exisiting Variables ===

	The WriteEnvStr and un.DeleteEnvStr functions in this page have been obsoleted by EnvVarUpdate.		The WriteEnvStr and un.DeleteEnvStr functions in this page have been obsoleted by EnvVarUpdate for path settings and other variables for path lists. For simple one-value environment variables however, the following does apply.
	The un.DeleteEnvStr function can corrupt the contents of the PATH variable if the path being removed happens to be a subset of another path. For example, if PATH contains "C:\Windows\system32\wbem" and you remove "C:\Windows\system32" the result is "\wbem". WriteEnvStr does not prevent the duplication of entries if the user runs the installer multiple times (and the installer code does not otherwise check for duplicates). However, these routines are retained for Windows 9x and ME in the next section since EnvVarUpdate does not support the update of variables in the autoexec.bat file.		The un.DeleteEnvStr function can corrupt the contents of the PATH variable if the path being removed happens to be a subset of another path. For example, if PATH contains "C:\Windows\system32\wbem" and you remove "C:\Windows\system32" the result is "\wbem". WriteEnvStr does not prevent the duplication of entries if the user runs the installer multiple times (and the installer code does not otherwise check for duplicates). However, these routines are retained for Windows 9x and ME in the next section since EnvVarUpdate does not support the update of variables in the autoexec.bat file.

Drmarbuse: /* Your own variable */ correction of current user-addition

2016-10-21T17:20:31Z

Your own variable: correction of current user-addition

â† Older revision		Revision as of 17:20, 21 October 2016
Line 38:		Line 38:
	WriteRegExpandStr ${env_hklm} MYVAR MYVAL		WriteRegExpandStr ${env_hklm} MYVAR MYVAL
	; and current user		; and current user
	WriteRegExpandStr ${~~hkcu~~} MYVAR MYVAL		WriteRegExpandStr ${env_hkcu} MYVAR MYVAL
	; make sure windows knows about the change		; make sure windows knows about the change
	SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000		SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000
Line 46:		Line 46:
	; delete variable		; delete variable
	DeleteRegValue ${env_hklm} MYVAR		DeleteRegValue ${env_hklm} MYVAR
			DeleteRegValue ${env_hkcu} MYVAR
	; make sure windows knows about the change		; make sure windows knows about the change
	SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000		SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000
Line 55:		Line 56:

	{{PageAuthor\|KiCHiK}}		{{PageAuthor\|KiCHiK}}

	=== Functions for Windows 95, 98, and ME ===		=== Functions for Windows 95, 98, and ME ===
	If you want to set an environment variable that will stick for every other process and after reboots too you should use the functions below. To use them either save them as a .NSH file and include them in your script, or just copy paste them in your script. If you choose to save them as a .NSH file use:		If you want to set an environment variable that will stick for every other process and after reboots too you should use the functions below. To use them either save them as a .NSH file and include them in your script, or just copy paste them in your script. If you choose to save them as a .NSH file use:

Drmarbuse: added curent user in code snipplet

2016-10-21T17:19:08Z

added curent user in code snipplet

â† Older revision		Revision as of 17:19, 21 October 2016
Line 35:		Line 35:
	!define env_hklm 'HKLM "SYSTEM\CurrentControlSet\Control\Session Manager\Environment"'		!define env_hklm 'HKLM "SYSTEM\CurrentControlSet\Control\Session Manager\Environment"'
	!define env_hkcu 'HKCU "Environment"'		!define env_hkcu 'HKCU "Environment"'
	; set variable		; set variable for local machine
	WriteRegExpandStr ${env_hklm} MYVAR MYVAL		WriteRegExpandStr ${env_hklm} MYVAR MYVAL
			; and current user
			WriteRegExpandStr ${hkcu} MYVAR MYVAL
	; make sure windows knows about the change		; make sure windows knows about the change
	SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000		SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000

Anders: /* Setting Environmental Variables Temporarily */

2015-09-03T20:22:44Z

Setting Environmental Variables Temporarily

â† Older revision		Revision as of 20:22, 3 September 2015
Line 7:		Line 7:

	If you want to set an environment variable only for the installer process and its sub-processes use:		If you want to set an environment variable only for the installer process and its sub-processes use:
	<highlight-nsis>System::Call 'Kernel32::SetEnvironmentVariable(t, t) i("name", "value").r0'		<highlight-nsis>System::Call 'Kernel32::SetEnvironmentVariable(t, t)i ("name", "value").r0'
	StrCmp $0 0 error		StrCmp $0 0 error
	ExecWait ProgThatReadsEnv.exe		ExecWait ProgThatReadsEnv.exe
Line 15:		Line 15:
	done:</highlight-nsis>		done:</highlight-nsis>

			To work around the NSIS_MAX_STRLEN limit when updating %Path% you can try [http://stackoverflow.com/a/32384667/3501 this function].

			{{PageAuthor\|turnec2}}

	~~{{PageAuthor\|turnec2}}~~
	== Setting Environmental Variables Permanently ==		== Setting Environmental Variables Permanently ==
	=== Exisiting Variables ===		=== Exisiting Variables ===

Anders: Added NSIS_MAX_STRLEN corruption warning

2014-02-23T19:14:45Z

Added NSIS_MAX_STRLEN corruption warning

â† Older revision		Revision as of 19:14, 23 February 2014
Line 1:		Line 1:
	{{PageAuthor\|KiCHiK}}		{{PageAuthor\|KiCHiK}}

			<div style="background-color:#ff9999; color:#f00; border:2px solid #f00; padding:1em;"><font size="+1"><b>WARNING:</b> Strings longer than ${NSIS_MAX_STRLEN} will get truncated/corrupted. Do NOT use this function to update %PATH%</font></div>


	== Setting Environmental Variables Temporarily ==		== Setting Environmental Variables Temporarily ==

Anders: Don't mix A function suffix and T type

2013-08-27T13:56:52Z

Don't mix A function suffix and T type

â† Older revision		Revision as of 13:56, 27 August 2013
Line 3:		Line 3:

	If you want to set an environment variable only for the installer process and its sub-processes use:		If you want to set an environment variable only for the installer process and its sub-processes use:
	<highlight-nsis>System::Call 'Kernel32::~~SetEnvironmentVariableA~~(t, t) i("name", "value").r0'		<highlight-nsis>System::Call 'Kernel32::SetEnvironmentVariable(t, t) i("name", "value").r0'
	StrCmp $0 0 error		StrCmp $0 0 error
	ExecWait ProgThatReadsEnv.exe		ExecWait ProgThatReadsEnv.exe

Anders: Reverted edits by 213.153.68.7 to last version by GSIJoe

2010-11-03T13:49:32Z

Reverted edits by 213.153.68.7 to last version by GSIJoe

â† Older revision		Revision as of 13:49, 3 November 2010
Line 41:		Line 41:
	SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000		SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000

	~~ATTENTION!~~
	~~if the environment variable was not known to the system before, you have to broadcast WM_SETTINGCHANGE instead of WM_WININICHANGE~~

	~~SendMessage ${HWND_BROADCAST} ${WM_SETTINGCHANGE} 0 "STR:Environment" /TIMEOUT=5000~~

	==== Function Code ====		==== Function Code ====
Line 51:		Line 47:

	{{PageAuthor\|KiCHiK}}		{{PageAuthor\|KiCHiK}}

	=== Functions for Windows 95, 98, and ME ===		=== Functions for Windows 95, 98, and ME ===
	If you want to set an environment variable that will stick for every other process and after reboots too you should use the functions below. To use them either save them as a .NSH file and include them in your script, or just copy paste them in your script. If you choose to save them as a .NSH file use:		If you want to set an environment variable that will stick for every other process and after reboots too you should use the functions below. To use them either save them as a .NSH file and include them in your script, or just copy paste them in your script. If you choose to save them as a .NSH file use:

213.153.68.7: /* Your own variable */

2010-11-03T10:43:47Z

Your own variable

â† Older revision		Revision as of 10:43, 3 November 2010
Line 41:		Line 41:
	SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000		SendMessage ${HWND_BROADCAST} ${WM_WININICHANGE} 0 "STR:Environment" /TIMEOUT=5000

			ATTENTION!
			if the environment variable was not known to the system before, you have to broadcast WM_SETTINGCHANGE instead of WM_WININICHANGE

			SendMessage ${HWND_BROADCAST} ${WM_SETTINGCHANGE} 0 "STR:Environment" /TIMEOUT=5000

	==== Function Code ====		==== Function Code ====
Line 47:		Line 51:

	{{PageAuthor\|KiCHiK}}		{{PageAuthor\|KiCHiK}}

	=== Functions for Windows 95, 98, and ME ===		=== Functions for Windows 95, 98, and ME ===
	If you want to set an environment variable that will stick for every other process and after reboots too you should use the functions below. To use them either save them as a .NSH file and include them in your script, or just copy paste them in your script. If you choose to save them as a .NSH file use:		If you want to set an environment variable that will stick for every other process and after reboots too you should use the functions below. To use them either save them as a .NSH file and include them in your script, or just copy paste them in your script. If you choose to save them as a .NSH file use:

GSIJoe: /* Setting Environmental Variables Permanently */

2009-05-08T15:35:33Z

Setting Environmental Variables Permanently

@@ Line 14: / Line 14: @@
 {{PageAuthor|turnec2}}
 == Setting Environmental Variables Permanently ==
-=== EnvVarUpdate ===
+=== Exisiting Variables ===
 The WriteEnvStr and un.DeleteEnvStr functions in this page have been obsoleted by EnvVarUpdate.
@@ Line 20: / Line 20: @@
 See [[Environmental_Variables:_append%2C_prepend%2C_and_remove_entries]] for more information.
 ==== Function Code ====