中国DOS联盟

In the CMD environment of 2000/XP, is there a command similar to the WAIT.COM command in pure DOS? That is, wait for 10 seconds and then continue running, and press ESC to run immediately. Similar to:
c:\>wait 10

Search for "sleep" and "timeout" using Google. The Windows 2000/2003 Resource Kit contains these commands.

Setting a time value with CHOICE will do the trick. If there is a choice, GOTO; if there is no choice, continue execution after the specified time has passed

Surprised! Even Comrade gmy has posted a CMD-related question in the DOS section! I believe it's definitely not that Comrade gmy can't distinguish, but that everyone gradually becomes confused after using it for a long time. It shows to what extent CMD has corrupted DOS! Still, Comrade gmy should move it himself.

It can be seen to what extent CMD has corrupted DOS

Hehe, let's coexist. Why still distinguish enemies and us? We are all one family

No! We can't think they are from the same family just because the command lines are similar. It's not just about similar command lines; it's a matter of principle between the two systems. Moreover, from a commercial perspective, only MS-DOS and CMD are from the same family, but not from a technical perspective.

I don't object to using CMD, but I absolutely won't allow CMD to encroach on the territory of DOS. I'm not trying to draw lines between us, but mainly, I won't allow the conspiracy of Windows command lines gradually replacing DOS to succeed. Unless one day CMD can be started independently like DOS to solve problems, then we'll include it in the DOS family, heh heh!

Originally, these are all Microsoft things. Also, we learn DOS or CMD to solve problems. Don't learn DOS just for learning DOS. Don't think DOS is very profound (the bad mentality of showing that you are superior to others) to learn DOS. In short, we should correct the learning purpose.

Always remember: Any operating system serves applications. A cat that can't catch mice is not a good cat.

Originally, these were all Microsoft things.
——
DOS was not originally created by Microsoft, and it was not the only one, nor was it the best from their family.

Moreover, we learn DOS or CMD to solve problems. Don't learn DOS just for the sake of learning DOS, and don't think that DOS is very profound (the bad mentality of showing that you are superior to others) to learn DOS. In short, we should correct the learning purpose.
——
Originally, it was like this at the beginning, but as the practicality of DOS decreases, I think it's not bad to learn DOS even just for fun. DOS can be said to be profound or not profound, mainly depending on the level you apply it to. Learning DOS makes you seem superior to others??? Haha

Always remember: Any operating system is for application services. A cat that can't catch mice is not a good cat.
——
Yes, this sentence is correct. But even if this cat is old and can't catch mice anymore, it can still do other things, and we will never abandon it because of that.

I said that if it's for pragmatism, then this forum doesn't need to be opened. Or there's no need to sell dog meat under the wolf's head.

The Boundary Between DOS and CMD

The boundary is in people's minds, and the boundary in each person's mind is different.

Microsoft's products focus on user-friendliness, and technically, they simplify as much as possible, so many technical concepts and definitions are very vague.

So probably we can seek common ground while reserving differences. As long as everyone finds out the similarities and differences between DOS and CMD, maybe we can know how to draw the boundary. Of course, it doesn't have to be viewed from a technical perspective.

Similarities Between DOS & CMD

1. Both have a command-line interface and kernel
So, the way they handle problems is the same, and the way they communicate with users is the same
So, they both support batch processing

2. Both are Microsoft products (of course, excluding other versions of DOS and CMD)
So, in many commands and features, they are the same, and even some basic codes are similar.

Differences Between DOS & CMD

1. DOS is a type of operating system, while CMD is a component of an operating system;
So, DOS usually relies on itself to achieve expansion, while CMD usually relies on Windows to achieve;

2. DOS has multiple memory modes, while CMD probably only has protected mode;
So, DOS can execute 16-bit and 32-bit programs, while CMD can execute 32-bit and 64-bit programs(?)

3. Their development teams and subsequent support personnel are different
So, in many commands and features, they have great differences.

How did we get off track... I also want to know what commands can solve this problem

Delay can be used for about 5 seconds. The number at the end can be modified by yourself.
ping 1.1.1.1 -n 4

Quick jump out can be done with CTRL+C

ping -n 10 127.0.0.1 >nul

This!!!

Great, I'm just looking for it

Which one is less resource-intensive among wait, sleep, and ping methods?