Actually, you don't have to log out and back in again. You can make the changes in the Registry however you like. Then go to the Control Panel -> System (-> Advanced) -> Environment. Click OK. Now the Explorer shell has been told to pick up the new environment settings (but the Service Control Manager hasn't, but that shouldn't matter for most cases). Now open a new Command Prompt window and the environment should reflect the changes. Command Prompt windows opened before the changes won't see the changes.
Update: Regarding
clicking OK and/or Apply in the System CP has no effect on any current (no surprise there) or new command prompt windowsIt sounds like you may not have followed the directions. You have to select the "Environment" tab (in WinNT) and then click "OK" ("Apply" won't be an option). In Win2K, you have to select the "Advanced" tab, open the "Environment" dialog, then click "OK".
One more thing, you can't start a new command prompt from an old command prompt or it will inherit its environment from that command prompt instead of from the Explorer shell.
I've just reverified this behavior for both WinNT and Win2K (starting the new command prompt window from the "Start" menu).
- tye (but my friends call me "Tye")In reply to (tye)Re2: Evironment variable on Win32 machines
by tye
in thread Evironment variable on Win32 machines
by RayRay459
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |