Those variables are included in GetEnvironmentStrings() WinAPI call. Documentation http://msdn.microsoft.com/en-us/library/windows/desktop/ms682653(v=vs.85).aspx does not show there are such variables, still it's easy to check =c: alike variables are included in the result. There are no WinAPI function to split returned string into key-value pairs, thus every application (i.e. JVM) should implement it.
It looks this environment variable contains current directory for each drive. You may check it in cmd.exe:
Those variables are included in GetEnvironmentStrings() WinAPI call.
Documentation
http://msdn.microsoft.com/en-us/library/windows/desktop/ms682653(v=vs.85).aspx
does not show there are such variables, still it's easy to check =c: alike variables are included in the result.
There are no WinAPI function to split returned string into key-value pairs, thus every application (i.e. JVM) should implement it.
It looks this environment variable contains current directory for each drive. You may check it in cmd.exe:
c:
cd some\path
echo Value of %=c:%
There is a good blog post describing the case
http://blogs.msdn.com/b/oldnewthing/archive/2010/05/06/10008132.aspx
In the agent side we use JVM proveded System.getenv() call
Thanks.
Sam