Basic question, I know - but I can never get CH's "Search" to find if things have been answered before...

I have a simple .BAT file. I'd like the CMD window to be open and active (i.e., ready for another command, even if it's just "Exit", after it runs).

If I USE
Code: [Select]pauseof course, it keeps the window open until I tap any key, then it closes.

If I use
Code: [Select] cmd /k before my first command, the window stays open, but is essentially "dead" and won't allow for more commands... I have to manually close the window. Same as if I put just simply Code: [Select]cmd as my last line.

My Googling skills are not up to this task. I keep getting the same answers no matter how I ask. I just want a command prompt after the END of my batch file!

ThanksWhy wouldn't you put CMD /K at the end of your batch file? You said you put it before your first command.Sorry, should have mentioned I tried that too. Same results.

I get a blinking underscore, but it's not a command prompt. The only command I type that works is "exit".

What I'd like is for it to be able to then treat the window as a "normal" CMD window once the BAT runs.

When you execute cmd.exe that is a normal console window. cmd /k works for me at the end of a test batch file. After the batch file completes I get a standard command prompt:

Code: [Select]@echo off
echo doing important work. Please standby
ping 127.0.0.1 -n 6 > nul
echo Critical tasks completed.
pause
cmd /k
(The ping obviously is just to make it pretend to do something!)Quote from: Squashman on March 09, 2018, 09:05:21 PM

When you execute cmd.exe that is a normal console window.

cmd /k works for me at the end of a test batch file. After the batch file completes I get a standard command prompt:

cmd /k works for me at the end of a test batch file. After the batch file completes I get a standard command prompt:

A "normal" console window is some sort of c:\ prompt.... Yes?

When I run your file, I get a c:\ prompt. Hm. Will start from scratch tomorrow and re-report....