I tested all three variants of the SET commands (SET, SETL, and SETM) just to confirm the results. All but SETM work as expected with the newer releases.
Not shown in my example above was the statement:
shell "cmd.exe /c set > /temp/test.txt"
which dumped the Kix current environment. As expected, it had the "T=two" value.
I've performed the test multiple times with 4.01, 4.12, and 4.20, clearing the registry keys each time.
Only the SETM appears to be broken, writing the value to the CURRENT_USER environment instead of the SYSTEM environment. (In other words, SETM mimics SET). A typo in the command/function name parser sending the SETM request to the SET function??
Glenn
_________________________
Actually I
am a Rocket Scientist!
