#1 04 Nov 2006 11:27

bspus
Member
Registered: 04 Nov 2006
Posts: 20

Permanent change to the envirronment variables?

Hi

First of all, thanks for this great forum. I've been getting answers for many problems without even having to post

I just noticed that changes to the envirronment variables done from the command line with set do not persist.
They work for as long as I use the same console instance.
If I close cmd and re open it, the envirronment variables (like %path% for example) are back to what they were and any that i had added no longer exist.
I know I can make permanent changes to them from the GUI but I was wondering why I cant do it from the command line. Is it a setting that I need to adjust?

Offline

#2 04 Nov 2006 12:15

Simon Sheppard
Super Administrator
Registered: 27 Aug 2005
Posts: 1,031
Website

Re: Permanent change to the envirronment variables?

Use SETX

If the changes need to be immediate AND permanent you may need to use both SET and SETX

Offline

#3 04 Nov 2006 18:12

bspus
Member
Registered: 04 Nov 2006
Posts: 20

Re: Permanent change to the envirronment variables?

Thanks. I missed it somehow in the command reference. It seems to be a resource kit tool too.
I dont see why MS insists on leaving some useful commands out of normal windows installations.
Its not like they take up any serious amount of space or that they charge extra for them.

Offline

Board footer

Powered by FluxBB