China DOS Union

It has been discovered that there is a bug in the if command of high - version 4NT / Take Command.

When the judgment condition is false, the if command will ignore the command separator in the same line after it, that is, it will treat the other multiple commands separated as part of its own conditional execution instead of commands on a new line, whether executed in the command line or in a batch file.

For example
if 1==1 echo 1 %+ echo 2
The return result is

1
2

Execution is normal.

But if
if 1==2 echo 1 %+ echo 2
No result is returned, and the second echo is never executed.

But if it is written in two separate lines in a batch file, it is not affected
if 1==2 echo 1 echo 2
Execution is normal.

This bug does not affect the statements before the if in the same line.

It has been tested that this bug only occurs in high - version 4NT / Take Command, and exists in 8.0, 9.0, 10.0, but not in 6.0, 7.0 and 4DOS.

Ask, is there any major progress in 4NT now?
I'm still using 6.01...

Now the highest version of 4NT and also the final version is 8.02 Build106, JPSoftware will no longer release subsequent versions. Starting from 9.0, JPSoftware has integrated the previous Windows command-line products into Take Command:

http://www.cn-dos.net/forum/viewthread.php?tid=40956#pid283683

Currently the latest version of Take Command is 10.0. The Take Command Console contained in Take Command can be said to be the continuation of 4NT. JPSoftware also has a completely Console-form free version: TCC LE. I tried it and found that it has many unsupported features, such as some variable functions not working, unable to set redirection in Unicode mode, etc. Well, the lite version is just to let you experience it, heh heh.

The new version of 4NT / Take Command of course has more commands, internal environment variables, variable functions than the old version, and of course some bugs have been fixed. Unexpectedly, some new bugs have appeared?! Heh heh

Just posted in the official forum, let's see what responses there will be.
http://www.jpsoft.com/forums/showthread.php?p=9427

The answer is just not to check "Duplicate CMD.EXE bugs".