S
Steve Kingsland
This has been bugging me for years now, and I'm finally getting around
to asking a group of people whom should know: I change an environment
variable in Windows 2000 via System Properties | Advanced |
Environment Variables | System variables, open a DOS window and type
"set", and I don't see the change I just made. As soon as I log out
and back in, or restart, I see my change. If I go back to the
Environment Variables window, I see the change there, but in order for
any programs to pick up on the change, I need to at least log out.
This frustrates me, because I know several other people who use Win2K
who DON'T have to log out for it to take effect. I think I'm now on
my 3rd or 4th computer with NT or 2000 where this has been the case!
Why, WHY, WHYYYY is this happening to me, and can anyone explain or
offer a shortcut to avoid logging out and back in? (I frequently have
lots of windows open, servers running, etc. that I don't want to close
& re-open) I recall deleting the ComSpec env. variable in NT was a
short cut for restarting... does that still work in 2000?
Thanks in advance for your help.
Steve
to asking a group of people whom should know: I change an environment
variable in Windows 2000 via System Properties | Advanced |
Environment Variables | System variables, open a DOS window and type
"set", and I don't see the change I just made. As soon as I log out
and back in, or restart, I see my change. If I go back to the
Environment Variables window, I see the change there, but in order for
any programs to pick up on the change, I need to at least log out.
This frustrates me, because I know several other people who use Win2K
who DON'T have to log out for it to take effect. I think I'm now on
my 3rd or 4th computer with NT or 2000 where this has been the case!
Why, WHY, WHYYYY is this happening to me, and can anyone explain or
offer a shortcut to avoid logging out and back in? (I frequently have
lots of windows open, servers running, etc. that I don't want to close
& re-open) I recall deleting the ComSpec env. variable in NT was a
short cut for restarting... does that still work in 2000?
Thanks in advance for your help.
Steve