Unable to close v13

May 29, 2008
64
0
#1
Click on TCmds red X or file/exit achieves nothing.
If I exit every tab I am still left with an empty shell. Must close in TaskManager

running 13.00.19 x64 under win7-64
 
May 29, 2008
64
0
#2
Problem might be related to inability to write tcmd.ini file.

As a test I renamed TCMD.ini (while TCmd active) - on attempted exit a new TCmd.ini is created but remains empty.
I am not running from C:\Program Files but from c:\myapps\tcmd
 

rconn

Administrator
Staff member
May 14, 2008
10,573
97
#3
> Click on TCmds red X or file/exit achieves nothing.
> If I exit every tab I am still left with an empty shell. Must
> close in TaskManager
Not reproducible here.

Do you have any other apps (antivirus, screen managers, etc.) injecting code
into TCMD? Have you tried it with an empty TCMD.INI?

Anybody else able to reproduce this?
 
#4
TCC 13.00.19 Windows Vista [Version 6.0.6002]
TCC Build 19 Windows Vista Build 6002 Service Pack 2

I have no troubles. I can not reproduce this.

On Sat, Sep 10, 2011 at 22:40, yakir <> wrote:


> Click on TCmds red X or file/exit achieves nothing.
> If I exit every tab I am still left with an empty shell. Must close in
> TaskManager
>
> running 13.00.19 x64 under win7-64
>
>
>
>
>


--
Jim Cook
2011 Monday: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Tuesday.
 
#5
On Sun, 11 Sep 2011 11:55:05 -0400, rconn <> wrote:

|Anybody else able to reproduce this?

Not exactly, but the old problem about consoles not closing right away now shows
itself in anoother way.

I have TCMD set to remain open if it has no tabs. Whenever I "X" a tab, it
takes 4+ seconds for the TCC process to disappear from TaskMgr; if it's the only
tab it takes 4+ seconds for it to disappear from the TCMD window.
 

ron

Aug 19, 2008
146
0
#7
I'm not seeing either problem. My .ini is in ...appdata\local...

TCC 13.00.19 x64 Windows 7 [Version 6.1.7600]
TCC Build 19 Windows 7 Build 7600

But, this is a relatively clean VM. I've not migrated yet on the main box.
 
May 29, 2008
64
0
#8
Further investigation points to the problem being related to the TCSTART.ini (basically only loads aliases).
However I cannot pinpoint as it is not consistent, there seems to be some type of "memory" involved
e.g.
no TSTART - no problem
empty TCSTART - problem returns
rename TCSTART - problem remains

I don't have time now to reboot between each test.
Will keep you posted
 
#9
From: yakir
| ...
| I don't have time now to reboot between each test.

I presume "reboot" refers to restarting Windows. Typically it is enough to stop and restart TCC or TCMD. Occasionally logging out the current user and logging back in is needed. Windows restart is very rarely needed. This may speed up your testing.
--
HTH, Steve
 

rconn

Administrator
Staff member
May 14, 2008
10,573
97
#10
> I have TCMD set to remain open if it has no tabs. Whenever I "X" a tab,
> it takes 4+ seconds for the TCC process to disappear from TaskMgr; if it's
> the only tab it takes 4+ seconds for it to disappear from the TCMD
> window.
Try the test build in ftp://jpsoft.com/beta/tcmd.exe and let me know if it
changes this behavior. (And makes your old shutdown delay return?)
 
#11
On Mon, 12 Sep 2011 11:25:19 -0400, rconn <> wrote:

|---Quote---
|> I have TCMD set to remain open if it has no tabs. Whenever I "X" a tab,
|> it takes 4+ seconds for the TCC process to disappear from TaskMgr; if it's
|> the only tab it takes 4+ seconds for it to disappear from the TCMD
|> window.
|---End Quote---
|Try the test build in ftp://jpsoft.com/beta/tcmd.exe and let me know if it
|changes this behavior. (And makes your old shutdown delay return?)

It did not change the behavior described above and it did bring back the old
shutdown delay.
 
#14
On Mon, 12 Sep 2011 17:00:28 -0400, rconn <> wrote:

|---Quote---
|> It did not change the behavior described above and it did bring back
|> the old shutdown delay.
|---End Quote---
|Interesting, because there were *no* other changes in the shutdown code.
|
|Are you sure the behavior above didn't also happen in 12.1?

It does happen in 12.1.
 
#15
On Mon, 12 Sep 2011 17:28:46 -0400, rconn <> wrote:

|---Quote---
|> It did not change the behavior described above and it did bring back
|> the old shutdown delay.
|---End Quote---
|Do you get the delay with *all* tab windows, or only with TCC tabs? (Try it
|with CMD.)

TCC 11 also terminates immediately. And TCMD (v13) terminates immediately when
X'ed if TCC v11, CMD, or PS is the only thing running in a tab.
 
#16
On Mon, 12 Sep 2011 17:28:46 -0400, rconn <> wrote:

|---Quote---
|> It did not change the behavior described above and it did bring back
|> the old shutdown delay.
|---End Quote---
|Do you get the delay with *all* tab windows, or only with TCC tabs? (Try it
|with CMD.)

CMD and PowerShell (and their conhosts) both disappear from TaskMgr immediately.
 
#18
On Mon, 12 Sep 2011 20:11:44 -0400, rconn <> wrote:

|---Quote---
|> TCC 11 also terminates immediately. And TCMD (v13) terminates
|> immediately when X'ed if TCC v11, CMD, or PS is the only thing
|> running in a tab.
|---End Quote---
|Assuming that TCC 11 is running with the same configuration as 12 and 13,
|that would mean that it is a TCC issue and doesn't have anything to do with
|TCMD.

I'm pretty confident all the settings are the same. The ones that have affected
this in the past (UpdateTitles=No, TITLEPROMPT set, TCEXIT existing) are the
same. BTW, the more recent problem (tab-TCC not terminating right away goes
away if I first "UNSET TITLEPROMPT" (and I'd bet if I did any of the other
measures that affected my earlier, similar problem).

Hmmm!, it doesn't happen when TCC is running stand-alone, so it has something,
however indirect, to do with TCMD or with the mere fact that it's hidden.

What happens when the user X's a tab (or X's TCMD)? Do you send
WN_SYSCOMMAND\SC_CLOSE to the console? Are you sure it's sent right away? With
a plugin, I could have TCC send WM_SYSCOMMAND\SC_CLOSE to itself after it has
been hidden.
 
#19
On Mon, 12 Sep 2011 20:43:12 -0400, vefatica <> wrote:

|What happens when the user X's a tab (or X's TCMD)? Do you send
|WN_SYSCOMMAND\SC_CLOSE to the console? Are you sure it's sent right away? With
|a plugin, I could have TCC send WM_SYSCOMMAND\SC_CLOSE to itself after it has
|been hidden.

FWIW, I tried that ... used a plugin to send WM_SYSCOMMAND\SC_CLOSE to the
console and did that after "WINDOW HIDE & DELAY 2". TCC (13) terminated
promptly.

And (just curious) I notice that my plugin "XCLOSE OFF" (disable console's "X"
and "Close") doesn't work in a tabbed TCC, not even after it has been detached.
That's no big deal but I wonder whether you went out of your way to do that (and
if so, how you did it).
 
#21
On Mon, 12 Sep 2011 21:07:42 -0400, rconn <> wrote:

|---Quote---
|> What happens when the user X's a tab (or X's TCMD)? Do you send
|> WN_SYSCOMMAND\SC_CLOSE to the console? Are you sure it's sent right
|> away?
|---End Quote---
|Yes, and yes.
|
|Try installing build 21 (just uploaded to the ftp beta area) and see if it
|behaves any differently.

Both problems are gone in build 21.

If you've got it, please tell me ... what was it's (crazy?) dependence on
TCEXIT, UpdateTitles, and TITLEPROMPT?
 
#23
On Mon, 12 Sep 2011 22:21:00 -0400, rconn <> wrote:

|---Quote---
|> If you've got it, please tell me ... what was it's (crazy?) dependence
|> on TCEXIT, UpdateTitles, and TITLEPROMPT?
|---End Quote---
|None of the above. TCC is apparently hanging (only on your system?) in an
|OpenProcessToken call. (That's the only thing I commented out in build 21.)

Hmmm! All along I could get rid of the problems in any of a number of ways ...
get rid of TCEXIT, set UpdateTitles=Yes, UNSET TITLEPROMPT before X'ing, use the
TITLE command in TCEXIT. Is it related to the console's caption in any way?
 

rconn

Administrator
Staff member
May 14, 2008
10,573
97
#24
> Both problems are gone in build 21.
Try it one more time with the new build 21 (you'll have to uninstall first;
it takes me a couple of hours to create a new build rev) in the ftp beta
area.

I've shuffled around some of the shutdown code and added a couple of sanity
checks. I think your problem was strictly timing related; you were just
unfortunate enough to be in the wrong place at the wrong time during
shutdown.
 
#25
Email replied 10 minutes ago ... don't know what happened to that.

That one is OK too. Just to be sure ... server timestamp 9/13 02:55 (UTC) ... right?

Try it one more time with the new build 21 (you'll have to uninstall first;
it takes me a couple of hours to create a new build rev) in the ftp beta
area.

I've shuffled around some of the shutdown code and added a couple of sanity
checks. I think your problem was strictly timing related; you were just
unfortunate enough to be in the wrong place at the wrong time during
shutdown.
 
#26
On Mon, 12 Sep 2011 22:55:35 -0400, rconn <> wrote:

|---Quote---
|> Both problems are gone in build 21.
|---End Quote---
|Try it one more time with the new build 21 (you'll have to uninstall first;
|it takes me a couple of hours to create a new build rev) in the ftp beta
|area.
|
|I've shuffled around some of the shutdown code and added a couple of sanity
|checks. I think your problem was strictly timing related; you were just
|unfortunate enough to be in the wrong place at the wrong time during
|shutdown.

That one is OK too. Just to be sure ... it's the one stamped 9/13 02:55 (UTC
server filestamp) ... right?
 
May 29, 2008
64
0
#27
Re: Unable to close v13 - Solved

TCC 13.00.21 Windows 7 [Version 6.1.7600]
TCC Build 21 Windows 7 Build 7600

Problem of no shutdown solved ! Thanks