NoClose Replacer.

[Flint]

NoClose Replacer 1.1 is ready now! Thanks to icfu for the ideas and testing.
Download (mirror)

The list of changes:

1. The parameters CommandProcessorNT and CommandProcessor9x were added.
2. When the explicit command interpreter is absent in the settings, the command cmd.exe /K or command.com /K is taken depending of the system (earlier it was always cmd.exe).
3. Added possibility to assign different programs to hotkeys in addition to ones specified in the CommandProcessorNN settings.
4. The documentation is converted into HTML-format.

[Flint]

NoClose Replacer 1.2
Download (mirror)

The list of changes:

1. Some bugs fixed that caused additional hotkeys not to work in Win9x systems.
2. Added support for environment variables.
3. Now the program can be started with empty command line (containing of spaces only). This can be useful for opening a console window without preliminary executing of any command.

[icfu]

Very nice additions, as usual.

Thank you!

Icfu

[SQUIRE]

Thanks Flint, good work.

[djorge]

Thank you.
This tiny utility is very usefull.

[karlchen]

Hi, Flint.

Just dropped in to join the crowd praising your little helper.
(... wondering why I did not start using it any earlier ... )

Karl

[X-Byte]

Very nice

Now I wish Christian Ghisler would change Total Commander's behaviour of statically executing %windir%\noclose.pif
Instead this should be configurable in wincmd.ini

Code: Select all

NoCloseApplication = %COMMANDER_PATH%\Utils\NoClose.exe

[gbo]

I will be interested to know in which context (with wich application) people are using this utility?

Just for my curiosity and hopefully I will find a usage for this after reading some "reviews" if any.

Thanks in advance

[X-Byte]

I Primarily use it with console applications that just throw some output and then terminate, without any user interaction.

My favorites:
ipconfig
tracert
ping

[karlchen]

I will be interested to know in which context (with wich application) people are using this utility?

Whenever you type a command in the TC commandline box, TC will call noclose.pif in %windir% and execute it.
TC's noclose.pif has got the following drawbacks:

• if you execute the command by pressing enter, a command box will pop up and close as soon as the command finishes. (cmd.exe will be used on NT and above, command.com on Win9x/ME)
• if you execute the command by pressing shift+enter, a "DOS box" will pop up and stay open "inactive". You cannot use it for further commands.
• even on NT and above noclose.pif will call command.com, no matter what you put in noclose.pif, when launched by shift+enter.
• There is no way to tell TC to use an alternate command interpreter for noclose.pif.

NoCloseReplacer removes the last 3 limitations.
Very likely it can do much more, but I have not found out yet.

Karl

[gbo]

@karlchen
Yes I understood that from the !ReadMe_eng.html file but my question was more about : Can someone gives examples so that I can see why it is so nice to do that inside TC.

@X-Byte
Thanks for the answer, but what is/are the advantage(s) to start those commands (ipconfig, tracert, ping) from TotalCommander ? Do you pass any parameters from TC ?

Sorry if my remarks are stupids but I just try to understand.

Anyway thank for the replies.

[karlchen]

Hi, GBO.

There is nothing which you can do using the TC commandline which you cannot do by typing the same command in a cmd.exe window.

The difference is only whether you have to open cmd.exe yourself first or whether you let TC do this for you.
Ok, one more difference: you can copy any marked file/foldername to the TC commandline by pressing ctrl+enter, you cannot copy it to a cmd.exe window this way.

If you never use(d) the TC commandline, very likely NoCloseReplacer will not make your life any easier.

Karl

[gbo]

Hi Karl,

OK I see, thank you for throwing some light on this subject.

If you never use(d) the TC commandline, very likely NoCloseReplacer will not make your life any easier.

I must admit that I don't often use the TC commandline the only exceptions are :

In conjunction with some FS plugins
(eg Secure FTP plugin -> cd \\\Secure FTP connections\Neos\apache\html\)

and

To reach some environment variables (eg cd %$FONTS%)

[karlchen]

Good evening, Gil.

I don't often use the TC commandline the only exceptions are :
[...] cd \\\Secure FTP connections\Neos\apache\html\
[...] cd %$FONTS%

These are 2 examples where using the TC commandline will definitely not invoke noclose.pif.
So NoCloseReplacer will not mean much to you. Never mind.

The praise goes to Flint because his noclose.pif - in fact an exe and not a pif at all - is more flexible than the genuine TC provided pif-file (and it will not launch the 16bit-DOS-emulator on NT-based systems).

Karl

[st]

(i really don't hav the patient 2 read the replies here)
is it safe to replace a system's file?