Hi,
On 27/05/2011 15:12, Gabor Szabo wrote:
I am not sure what do I have to look for but in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
I have a row:
Path REG_EXPAND_SZ C:\Program Files\CollabNet\Subversion
Client;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\strawberry\c\bin;C:\strawberry\perl\site\bin;C:\strawberry\perl\bin;
If the problem previously described was present, then you would see
Path REG_SZ
not
Path REG_EXPAND_SZ
For info, until something calls SendMessageTimeout to broadcast that
stuff like the environment has changed, already running progs will have
the environment that was present when started. There's even more fun
with services where the ability to reload the environment etc without a
reboot varies across windows versions (hurrah!).
When you were having the problem, the environment that explorer / the
desktop had, which allowed it to launch cmd.exe, isn't necessarily the
same as the environment that the launched shell would receive nor what
you could actually see in the registry.
As Toby pointed out, installation routines that just bang a few entries
in the registry and change the environment usually cause problems that
are likely difficult to trace and may disappear on a reboot or some
subsequent installer 'fixing' your machine state as a side-effect. (if
you're lucky).
Anyhow, good to hear it works now.
Mark
