For some weird reason, non-ADMIN, the IF fails to compare correctly if not compared with a ZERO and thus the GOTO is wrongly taken (ie: it says a NEG# is GE a POS#): C:\Windows\System32>h:\d\tools\myprogs\dostips1.bat 4 req=4, ERRORLEVEL via DSNTODAY and EL NOT(!) CHECKED PATHSET DSNTODAY,0,E,"...

For some reason, using this command: for /f "usebackq tokens=1,2* delims= " %%i in (`type COUNTER.txt`) do set COUNTERrc3=%%i against file COUNTER.txt which contains: 0x0000020A 0586 6.1 2 ????## where '????' is 0A020000h and '##' is 0D0Ah (CRLF) the FOR fails to parse the 1st field correc...

My simple .BAT ain't so simple now, but I narrowed it down: specifically, using a VAR with a number OTHER THAN ZERO only works, apparently, for ERRORLEVEL: [code] C:\Windows\System32>h:\d\tools\myprogs\dostips1.bat 4 req=4, ERRORLEVEL via DSNTODAY and EL NOT(!) CHECKED PATHSET DSNTODAY,0,E,"&qu...

In Win7, I have a .BAT that tries to process a negative ERRORLEVEL, but does so rather poorly, and I was hoping that a better way could be found. I have a program that can do an INT3 which forces an rc of -2147483645; 80000003h. My .BAT can only seem to handle this correctly by doing this after the ...