It involves interacting with window's registry. I haven't tried it but looks promising. One note, each process of windows opens it's own copy of the current environment. If a process is running in window 'A' and the registry later changed in window 'B', window A will not acknowledge the changes unless the program running in that window requests an update. If you're just after temp changes to subprocesses within your process and subsequent spawned/forked processes, you can always modify %ENV.
Did a quick test under WinXP and observed that while you can change ENV{PATH} within the program, it reverts back to what the parent process has defined as ENV{PATH} once the program exits. The goal of the registry hack would be to alter subsequent spawned processes. My intent was to use this as a cheap way to pass information between otherwise non-friendly programs.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.