in reply to ENV PATH didn't take effect

I am afraid I am not qualified for the windows support, but my best guess is, the system variables do not get propagated to all users as you suspect.

I think, that should be the normal behavior.

You can modify your own PATH variable in Perl through the %ENV hash.

$ENV{PATH} contains the PATH, and you can modify it.

Subsequent shells or cmd prompts invoked by your Perl script use that information.

Cheers, Sören

edit: strikethrough - wrong thought

(hooked on the Perl Programming language)

Replies are listed 'Best First'.
Re^2: ENV PATH didn't take effect
by anaconda_wly (Scribe) on Jun 07, 2013 at 06:32 UTC
    Thank you for the response. In fact, I changed the Path variable using Perl by TieRegistry. The system path do changed. But the click-opened command prompt didn't. If it didn't propagate to all users, I've already logged in as administrator, why I should right click opened "run as administrator" to see this change is beyond my understanding. I expect after I added the PATH env, all users can use it, no need to set it manually any more.
[reply]

      The change, if made permanent, may take effect after a logoff/logon.

      The environment on disk is copied to your live environment on logon.

      Changing the config on disk does not followup in memory right away.

      Cheers, Sören

      (hooked on the Perl Programming language)

[reply]

In Section Seekers of Perl Wisdom