Glad to help! It wouldn't have occurred to me as quickly as it did, except
that I use Sysinternals' Process Explorer as a Task Mangler replacement - it
allows you to see a hierarchical list of processes, as well as the usual
sorted lists - and a week or two ago I happened to notice that CMD was
ru
Marc Tompkins wrote:
> In W2K and XP (not sure about NT), changes to environment variables made via
> the Control Panel will affect any NEW environments instantiated from the
> moment you click OK in the Environment Variables dialog.
...
> Something to be aware of, though - if CMD is being starte
Thus spake Alan G:
> > Note, these are entered in Ctrl Panel, System environment variables,
> > NOT at the command line.
>
> Umm, have you rebooted? Probably an obvious step but I don't
> think environment vars get reset in real time. They didn't used
> to on NT but that may have changed in W2K or
