TC uses noclose.pif when you press Shift+Enter for keeping the shell window open, so you can read the output of executed commands or batches.
But this shell is no longer active and allows no further working with it.
In WinXP you can use cmd.exe /k what keeps the shell open and active.
My suggestion for taking advantage of this feature within TC is adding 2 new settings to wincmd.ini.
They are meant to modify what Shift+Enter in TC does:
UseNoclosePif=(1/0)
=1 means TC uses noclose.pif from %WinDir% (current behavior). This would be standard in TC and the choice for Win9x users. Novices would not have to bother with it.
=0 is for more experienced users of WinXP/2k/NT and means TC ignores noclose.pif and is forced to execute the command with a preceded {VarText} defined in the 2nd setting:
ShiftEnterLine={VarText}
{VarText} could be cmd /k (or %comspec% /k or d:\4NT\4NT.exe /c).
For example: When you type in TC command line DoThis.bat and press Shift+Enter, TC would execute cmd /k DoThis.bat.
With this realized in TC, WinXP/2k/NT users would have the chance to get rid of this obsolete noclose.pif while TC would be downwards compatible to Win9x.
Please discuss the suggestion here and vote for it there(click).
Should TC make "cmd /k" usable with Shift+Enter
Moderators: Hacker, petermad, Stefan2, white
The proposal has been made several times already, nice that you bring it up again. In case you are interested in one of the old threads check it out here:
http://www.ghisler.ch/board/viewtopic.php?t=3435
If you don't know, you can do a workaround if you prefer cmd /k, the solution was born or at least mentioned in that thread above:
Create a batchfile called noclose.bat with the following content and save it in %windir%:
cmd.exe /k %2 %3 %4 %5 %6 %7 %8 %9
Now edit noclose.pif and enter noclose.bat as command. Shift-Enter will call cmd and console will stay open.
Icfu
http://www.ghisler.ch/board/viewtopic.php?t=3435
If you don't know, you can do a workaround if you prefer cmd /k, the solution was born or at least mentioned in that thread above:
Create a batchfile called noclose.bat with the following content and save it in %windir%:
cmd.exe /k %2 %3 %4 %5 %6 %7 %8 %9
Now edit noclose.pif and enter noclose.bat as command. Shift-Enter will call cmd and console will stay open.
Icfu
This account is for sale
Yes, I knew about the older thread. But noclose.bat is just a limping workaround of the workaround noclose.pif. 
Test the following: Type cmd /k set c in TC command line and press Enter, you will be shown the variables with first letter c. That is how it should be.
When you check the taskmanager, only cmd.exe is active for this real 32bit console.
Now type set c in TC command line and press Shift+Enter using your batch workaround. Error "variable c is not defined" will appear.
The console window title shows MS-DOS. In taskmanager you can find ntvdm.exe in addition to cmd.exe. NT-VDM is a virtual DOS machine for 16 bit programs.
Does anyone really want to keep alive obsolete technic with limping workarounds?
Users of TC on a USB-stick could be happy too, if they could get rid of noclose.pif instead of adding a second file (noclose.bat) to %windir%.
All I want is a clean and up to date solution in TC for its command line
This is min. 4 years overdue!
Test the following: Type cmd /k set c in TC command line and press Enter, you will be shown the variables with first letter c. That is how it should be.
When you check the taskmanager, only cmd.exe is active for this real 32bit console.
Now type set c in TC command line and press Shift+Enter using your batch workaround. Error "variable c is not defined" will appear.
The console window title shows MS-DOS. In taskmanager you can find ntvdm.exe in addition to cmd.exe. NT-VDM is a virtual DOS machine for 16 bit programs.
Does anyone really want to keep alive obsolete technic with limping workarounds?
Users of TC on a USB-stick could be happy too, if they could get rid of noclose.pif instead of adding a second file (noclose.bat) to %windir%.
All I want is a clean and up to date solution in TC for its command line
This is min. 4 years overdue!Well, I agree wholeheartedly but that's not enough unfortunately. 
TC command line support is really bad, that's why I only use it for simple commands right now. I am completely addicted to TypeAndRun aka TAR console meanwhile and don't miss the command box anymore.
In case you don't know it, you should really give it a try:
http://galan.dogmalab.ru/tmp/tar470b3.zip
A decent yahoo group where all releases and plugins are announced you can find here:
http://groups.yahoo.com/group/typeandrun
HTH (a little
)
Anyway, I sincerely hope that ghisler will one day change his mind and drop that ugly noclose.pif so we can at least use it with a little more comfort.
Icfu
TC command line support is really bad, that's why I only use it for simple commands right now. I am completely addicted to TypeAndRun aka TAR console meanwhile and don't miss the command box anymore.
In case you don't know it, you should really give it a try:
http://galan.dogmalab.ru/tmp/tar470b3.zip
A decent yahoo group where all releases and plugins are announced you can find here:
http://groups.yahoo.com/group/typeandrun
HTH (a little
)Anyway, I sincerely hope that ghisler will one day change his mind and drop that ugly noclose.pif so we can at least use it with a little more comfort.
Icfu
This account is for sale