RUN COMMAND BOX

[EdK]

when i go to start/run , enter a command, a "dos box" pops up and goes away
quickly.I cannot see what happens.how can I fix this.....??

 

[Herb Martin]

when i go to start/run , enter a command, a "dos box" pops up and goes away
quickly.I cannot see what happens.how can I fix this.....??

Run CMD.exe first.

Leave the resulting Command Prompt window OPEN.

Run command prompt programs from this window.

The problem is that

 

[BobC]

when i go to start/run , enter a command, a "dos box" pops up and goes away
quickly.I cannot see what happens.how can I fix this.....??

Start > Run > then type "cmd" in the box. This opens a command window. Type
your commands in the command window.

 

[EdK]

Start > Run > then type "cmd" in the box. This opens a command window. Type
your commands in the command window.

*********
THANK YOU Herb/Bob.got it !!!

 

[Jay Somerset]

when i go to start/run , enter a command, a "dos box" pops up and goes away
quickly.I cannot see what happens.how can I fix this.....??

Another, more convenient way if you want to run the same command in the
future, is to type "CMD /K command" (without the quotes), where "command" is
the program you want to run.

 

[Herb Martin]

Another, more convenient way if you want to run the same command in the

future, is to type "CMD /K command" (without the quotes), where "command" is
the program you want to run.

The /K is unnecessary if you run this from the Start\Run (or similar place
like Task Manager)

The /K is mostly needed for Batch files or Shortcuts where you wish to run a
command prompt program AND keep the window open afterwards.

 

[Jay Somerset]

The /K is unnecessary if you run this from the Start\Run (or similar place
like Task Manager)

The /K is mostly needed for Batch files or Shortcuts where you wish to run a
command prompt program AND keep the window open afterwards.

Seems to me that was exactly what the original poster was trying to avoid.
Please reread the original post.

 

[Herb Martin]

Seems to me that was exactly what the original poster was trying to avoid.

Please reread the original post.

Nope, it was the other way around.

 

[Jay Somerset]

Nope, it was the other way around.

We are miscommunicating. If you type a command into Start>Run (such as
IPCONFIG) you will never see the output, as the winfdow closes immediately
after the command executes. In order for the output of the command (in this
case IPCONFIG) to be readible, you need to keep the command window open.
The only way i know of to do this with a single typein in to precede the
command with CMD /K. The alternative is to open a CMD window, and then type
the command into that window -- two operations instead of one, and the
method I suggested also has the advantage that it stays around for later
reuse in Start>Run.