Posted 05 November 2011 - 01:30 PM
I am rather curious about the correct way to use environment variables on Windows, and I have some questions regarding what some terms mean. I find it much quicker to get things done via the command line some times, but the big stopper is having to type in really long path names. For instance, I just followed some instructions for an application server I've been looking at and the first thing it asked me to do after extracting and moving the files is to populate the home environment variable at machine level with the relevant files in my case using the SETX program name>file location -M command. What exactly did that do? And then I tried to set an environment variable for the .net framework tool InstallUtil.exe for Windows services since I use it quite often, and I hate having to call the program folder followed by the .net framework location plus the InstallUtil.exe with the service name being installed tacked on the end. That did not work, yet the setting of the first variable did. What is the difference between the two? And also, what is the difference between using the GUI versus using the command line SETX? and when looking at a list of the system variables and user environment variables from the GUI, I find it hard to figure out which each is and what they do. Some clarification would be wonderful. Thanks.
The AccessCop Network is just me and my crew.
Some call me The Queen of Cambridge