close command prompt

[FrizzleFry]

Just add an exit after the :end label and the script will close the command prompt when it ends.

Edit: I changed the topic subject since we got split off the original thread.

[JRz]

Just add an exit after the :end label and the script will close the command prompt when it ends.

no it won't

[FrizzleFry]

Just add an exit after the :end label and the script will close the command prompt when it ends.

no it won't

It will exit if you are not using x2's console. This is one of the several reasons that I do not use it.

[JRz]

Hmm, normally it would, but on my system it won't. Even without the Exit it would have to close the command prompt when the script ends. Only if you have specified a custom preamble (szDosCmdPreamble in registry) it could behave differently.

I'll investigate at home (where I ran the script, currently at work) and let you know.

[FrizzleFry]

Hmm... my point is that if you end the batch/script file with an exit the command prompt will close when you run the script from x2's address/command bar. If you do not have an exit command the script will complete but the command prompt window will remain open.

This does not apply if you are redirecting DOS commands to x2's console.

This is my current preamble:

"szDosCmdPreamble"="cmd.exe /K "

I have adjusted this before to run 4nt instead of cmd but I think this is the standard x2 setting.

[JRz]

My bad. I had a command in the "szDosCmdPreamble" which was no longer on my system. So when a 'normal' command prompt was started by X², it generated an error.

Strangely enough it did create the folders, but didn't execute the exit at the end of the script.

Normally I do have the X² DOS window enabled, so I didn't notice this quirk on my system until now.

Case closed AFAIC

[FrizzleFry]

If you change the preamble to

"cmd.exe /c "

the command prompt exits automatically even without adding the exit to scripts.

But will this cause problems for the x2 console?