trevisev
20th August 2002 18:25 UTC

Why no WriteEnvStr instruction ?
I tried to read and write environment variables (under Windows NT 4) with NSIS (I use the 1.99).
I found the instruction ReadEnvStr to read them, and it works very well. But there is no instruction to write it directly. :cry:

So I used WriteRegStr to set directly the variables in the Windows registry (HKCU/Environment). But Windows does not care about the changes. I have to go to the Windows environment variables dialog, then select OK to make it work. Rebooting the computer work too. But both of the solutions are not convenient... :(

Is there a way to write an environment variable and make it work with NSIS ? :D

kichik
20th August 2002 18:31 UTC

Have a look here. This script should help you understand how to do it.

trevisev
21st August 2002 20:58 UTC

Thank's a lot. It works well !

But it's boring to write code for both Windows 9x (or ME) and NT. I'll see if I can write a function to do that...

Let's sum up:
For Windows 95 or ME, to change environment variables, you have to modify autoexec.bat
For Windows NT, just modify it into the registry

kichik
21st August 2002 21:02 UTC

Yep, that's how it works... But why rewrite? Just copy my code and change "Path" to whatever variable you want to set, or better yet, make it a function variable (using the stack). Don't forget to call RefreshEnv.exe on NT so you won't have to reboot.

dbareis
22nd August 2002 10:18 UTC

Hi,

While the code is quite good (and I know given the language it took a lot of work and probably swearing) it only handles the "PATH" environment variable.

I too would like some code for this...

I need to update the PATH, some PATH like environment variables and also simpler environment variables (set text). This sort of stuff should really be in the NSIS EXE.

Bye,
Dennis

kichik
22nd August 2002 10:32 UTC

Why should it be in the EXE if you can do it with the script? It is not that complicated...

dbareis
22nd August 2002 10:49 UTC

Originally posted by kichik
Why should it be in the EXE if you can do it with the script? It is not that complicated...

kichik
22nd August 2002 10:56 UTC

Severe lack? It does exactly what you want! All you have to do is to change "PATH" to whatever you want it to be or make it a pushed argument to the function... Do you want me to write it?

Sunjammer
22nd August 2002 11:37 UTC

Hmm

Originally posted by dbareis This sort of stuff should really be in the NSIS EXE.

kichik
22nd August 2002 12:33 UTC

Here it is, enjoy :D

[edit]Attachment removed. Newer version below.[/edit]

trevisev
22nd August 2002 18:14 UTC

I meant I my first post, to write a function that accept as arguments:
- the environment variable to consider
- the action to do on it (ie: delete or write new value)
and the function would do everything needed for Windows 9x and NT OS.

Indeed, that's not very complicated from your sources...

MoNKi
22nd August 2002 20:17 UTC

kichik y think there is an error in your code but i'm not sure:

In function WriteEnvStr:

StrCpy $2 $WINDIR 2 ; Copy drive of windows (c:)
FileOpen $2 "$1\autoexec.bat" a

StrCpy $2 $WINDIR 2 ; Copy drive of windows (c:)
FileOpen $2 "$2\autoexec.bat" a
              ^

kichik
22nd August 2002 20:20 UTC

Indeed. Thank you.

YtseJam
22nd August 2002 20:27 UTC

Did you update the SourceForge thingie? I'd check by myself by I can't be arsed to do so with this Dial-up plus I'm about to go to the Air-port. (ITALY! WEE!)

See ya' next week kichik. :)

kichik
22nd August 2002 20:29 UTC

What does this script has to do with SourceForge CVS?

Have fun in Italy :D

paul_snoop
27th August 2002 14:57 UTC

Exactly what I was looking for, thanks very much Kichik :)