Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

eset PATH does not take effect

Jun
25
0
If I alter the PATH variable with eset, it does not take effect immediately:

:: view the path
C:\Program Files\JPSoft\TCMD31]path
PATH=C:\Users\ericp\enp\bat;c:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem; [other stuff deleted...]

:: A batch file at the head of the path is not found, backslash prepended to filename
[C:\Program Files\JPSoft\TCMD31]areacode 312
TCC: Unknown command "\areacode.btm"

:: although the batch file exists where it should
[C:\Program Files\JPSoft\TCMD31]dir /b c:\Users\ericp\enp\bat\areacode.btm
areacode.btm


What did I do wrong?
 
If I alter the PATH variable with eset, it does not take effect immediately:

. . .
Unfortunately, I cannot reproduce this behavior myself, even though I copied the above sample correctly. And when I type an unknown command that does not exist (like "nocmd"), I get a response without a backslash prepended:

TCC: Unknown command "nocmd"

Must be gremlins . . .
 

Similar threads

Back
Top