Noclose.pif not called for CMD files

[Flint]

Valid for NT-based Windows versions only - NT/2000/XP/2003/Vista. In Win9x CMD files aren't supported.

1. Create any CMD file (for example with one command DIR inside it).
2. Press Shift+Enter on this file.
3. The console window closes immediately after the batch file is executed (noclose.pif is present and working; Shift key on the keyboard is not broken ).

If you just rename the same CMD file into BAT, Shift+Enter immediately begins to work correctly (that is - remain the console window till manual close).

I performed some investigations and found that for CMD files noclose.pif is not called at all (can be easily checked by replacing the noclose.pif with e.g. calc.exe: when you press Shift+Enter on a BAT file, the Calculator appears; when you press Shift+Enter on a CMD file the black console window just quickly appears and closes).

[iNSiDE]

Confirmed

[ghisler(Author)]

I'm sorry, you cannot use cmd files with noclose.pif. They are executed by cmd.exe and do not work with command.com.

[Flint]

I'm sorry, you cannot use cmd files with noclose.pif. They are executed by cmd.exe and do not work with command.com.

Many users are already using various replacements for this in-highest-degree-out-of-date noclose.pif, either by simply replacing command.com with cmd.exe in the noclose.pif properties, or using my NoClose Replacer. Could you please add possibility of running CMD files via Shift+Enter? You could make it optional, even turned off by default.

The better idea, of course, would be normal support for cmd.exe, but I'm afraid, it's too late for this request in 7.0...

[karlchen]

I'm sorry, you cannot use cmd files with noclose.pif. They are executed by cmd.exe and do not work with command.com.

Ever since Windows NT, command.com has been an anachronism.
There is no good reason to use command.com on NT-based Windows versions.
Please, consider preferring cmd.exe over command.com on NT-based systems, or rather use %comspec%.

For the time being, I recommend replacing noclose.pif by NoClose Replacer 1.2.

Oh yes, NoClose Replacer will launch .BAT .and CMD script files using cmd.exe.

Ciao,
Karl

[ghisler(Author)]

Unfortunately .pif files only work with DOS programs like command.com, but not with Win32 programs like cmd.exe. Any ideas?

[Flint]

Unfortunately .pif files only work with DOS programs like command.com, but not with Win32 programs like cmd.exe. Any ideas?

That's why I said about options. If the user has replaced noclose.pif with anything that allows executing Win32-programs (NoClose Replacer for example is a usual Win32 program, not a PIF file, and of course it can run any other Win32 programs including cmd.exe), he can set the option to tell TC that CMD files can now be started with noclose.pif without any problem.

[petermad]

Unfortunately .pif files only work with DOS programs like command.com, but not with Win32 programs like cmd.exe

Maybe I misunderstand you, but here on my Win XP SP2 noclose.pif works with both cmd.exe and %COMSPEC% set as the command.