My problem is that in Windows, there are command line windows that close immediately after execution. To solve this, I want the default behavior to be that the window is kept open. Normally, this behavior can be avoided with three methods that come to my mind:
- Putting a
pauseline after batch programs to prompt the user to press a key before exiting
- Running these batch files or other command line manipulating tools (even service starting, restarting, etc. with
net start xyor anything similar) within
cmd.exe(Start – Run – cmd.exe)
- Running these programs with
cmd /klike this:
cmd /k myprogram.bat
But there are some other cases in which the user:
- Runs the program the first time and doesn't know that the given program will run in Command Prompt (Windows Command Processor) e.g. when running a shortcut from Start menu (or from somewhere else), OR
- Finds it a little bit uncomfortable to run cmd.exe all the time and doesn't have the time/opportunity to rewrite the code of these commands everywhere to put a pause after them or avoid exiting explicitly.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\AutoRun HKEY_CURRENT_USER\SOFTWARE\Microsoft\Command Processor\AutoRun
(The AutoRun items are
cmd /d /k as a value of it to give it a try, but this didn't change the behaviour of the stuffs mentioned above at all… It just changed the behaviour of the command line window when opening it explicitly (Start-Run-cmd.exe).
So how does it work? Can you give me any ideas to solve this problem?