| Thanks for the reply, Steve. I'll go back and track down exactly
| which ones are discrepant. My impression is that it's not variables
| created in a command prompt, because I do them all in the registry
| these days; but I'll check and report back.
It depends on where in the registry you create them. IIRC I created no
registry variables, and modified only TEMP and TMP. All other of my
variables are true environment variables, created using the SET command. I
regularly work on at least two systems (my dekstop and my laptop), so I have
3 definiton files - one for variables shared by all my systems, and one for
each of my individual systems. These definition files are loaded with SET /R
commands by the TCSTART.BTM program. These variables allow all my batch
files to find other batch files, data files, programs, etc. so I can use the
same command on any system to get the same job done.
| Or is there any way directly to access the environment variables that
| don't come from the registry? SET and SET /E each give 94 lines.
The /E option when displaying environment variables does not do anything. If
is useful only for registry variables.
Windows creates a number of environment variables dynamically, based on the
/s etc. registry variables. There is a hierarchy; I believe all others
override /S. For example, on my WinXP SP3 system TEMP has different
definitions for /S, /D, or /U - the /U shows up in "SET".