中国DOS联盟

Originally posted by yangzhiyi at 2006-10-29 01:02:
Crazy, for batch commands that need to be executed step by step and also require delays, usually jumps are used. Using ping -n 1 127.1>nul for delays is even crazier.

Some commands take a relatively long time to get results, and if the next step needs to use the results, you need to delay for a while before running the next step

It's impossible to keep jumping around all the time o.o

Originally posted by zerocq at 2006-10-29 01:13:


Some commands take a long time to get results. If the next step needs to use the results, you need to delay for a while before running the next step

It's impossible to keep jumping around o.o

Generally, can start /w be used to solve the situation of waiting for results?

Usually, can starting with start /w solve the situation of waiting for the result?

Using the start command will open a new CMD window or other program windows, which is not appropriate in some cases.

And in many cases, using the ping command can play a certain role, and the time can be set arbitrarily by you, although the accuracy is not very good. In batch processing, the ping command is still used in many places to achieve the purpose of delay.

Not bad! Worth praising!~

If in the batch command, there is no need for delay at all. The result is relatively slow, but the next step偏偏 needs to use the result. The next step will not be reached until this step is not completed. If this step is completed, the next step also has the result available. DOS commands have only one pointer.
If other programs or files are called in the batch processing, start /w will do, and there is no problem of a new window.

I only know that choice is used to delay and then automatically input the value,
I really don't know how to apply this delay.
If you want multiple batch processes to run simultaneously, and the obtained results need to be used by each other, this kind of application should be wrong. Could this be multi-threading under DOS.

choice delay : choice /t 120 /d y

The delay unit is seconds, and the above is a delay of 120 seconds.

　　If a command executes relatively slowly and the next command needs to use the result of this command, you can use the command connectors "&&" and "||". For example: "command 1 && command 2 || command". In this way, if command 1 is executed successfully, command 2 is executed. If it is not executed successfully, command 3 is executed. It can also be understood that command 2 is only executed after command 1 is executed successfully.

Originally posted by lxmxn at 2006-10-29 07:46:

　　If a command executes relatively slowly, and the next command needs to use the result of this command, then you can use the command connectors "&&" and "||", uh..

But command 3 also needs to be executed after command 1 is completed.

Originally posted by yangzhiyi at 2006-10-29 08:18:


But command 3 also needs to be executed after command 1 is completed.

　　Then what is your purpose to achieve?

Hehe, I have understood what this command is for.

Win98 or pure DOS does not support >nul 2>nul. How to achieve blocking all screen output?

ctty nul

Restore with ctty con

Thanks to qzwqzw for the guidance! It solved the problem that had been bothering me for a long time.

I can't figure out why it's | directly under DOS but || is needed in BAT

Learned about >nul, , , , good stuff