Page 1 of 1

MS loves Linux...continued

Posted: 29 Sep 2015, 19:26
by viking60
Well I have this newfound tolerance and found that a dialog with Microsoft would be appropriate now that we have the love for Linux in common.
There are some tangents where both Windows and Linux info is required like Samba and Python ++ so I happily danced away to the Microsoft support site because I wanted to ask a question:
namely:
Is there a way to add a folder to the windows path in the cmd window?

This can be done via the control panel but, setting it for the session only can be done directly in cmd - so I wanted this command that would make it stick from the cmd-line.
So as a said happily surfing to the Microsoft support site and....
:A
Image

Eh some love.. that is...

So Microsoft; your Boss loves Linux and your services run on Linux - you need to fix this.
And after all the "not breaching privacy marketing" how come that your site control the OS?
In the mean time you can answer here :-D
:A

Re: MS loves Linux...continued

Posted: 29 Sep 2015, 19:49
by Snorkasaurus
The answer provided in this post at SO works on Windows 7 for me. You could be asking about an earlier version of Windows, but I am pretty sure the folks at microsoft.com don't answer questions about earlier versions either. :-)

s.

Re: MS loves Linux...continued

Posted: 29 Sep 2015, 20:39
by viking60
So running cmd as admin and a

Code: Select all

setx /M PATH "%PATH%;<your-new-path>

would worK after a reboot too? If that is the case then my question is answered anyway. :s

In case of fciv it would be like this then:

Code: Select all

setx /M PATH "%PATH%;C:\fciv

Re: MS loves Linux...continued

Posted: 29 Sep 2015, 21:56
by Snorkasaurus
viking60 wrote:would worK after a reboot too?

I am very confident that it will, though I did not test a reboot. What I did was go look at the registry key quoted in the post... hmmm, it isn't in the post. Okay, so the reg key is

Code: Select all

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment\Path

I basically checked the contents of that key, ran the command, and re-checked the key. The value had been updated with the path I added in the command. It is my impression that would survive a reboot. :-)

s.