C-c terminates Take Command

[Juanma Barranquero]

I see that build 61 included this change:

(61) Fixed a (Windows) bug with repeated ^Breaks sometimes terminating TCMD.EXE

Paradoxically, since that build ^C sometimes terminates Take Command (I'm using build 64 right now and the issue still happens).

It does not happen all the time, but quite often. For example, I have a .btm file:

@echo off
do forever
pssuspend %1
delay 60
pssuspend -r %1
delay 90
enddo

(where pssuspend is a PS Tool from Sysinternals). When that script is running, pressing ^C during one of the delays terminates Take Command most of the time (but not always). I've also had the problem ^C'ing out of list /s, etc.

 

[rconn]

Juanma Barranquero wrote:

> I see that build 61 included this change:
>
> (61) Fixed a (Windows) bug with repeated ^Breaks sometimes terminating TCMD.EXE
>
> Paradoxically, since that build ^C sometimes terminates Take Command (I'm using build 64 right now and the issue still happens).
>
> It does not happen all the time, but quite often. For example, I have a .btm file:
>
> @echo off
> do forever
> pssuspend %1
> delay 60
> pssuspend -r %1
> delay 90
> enddo
>
> (where pssuspend is a PS Tool from Sysinternals). When that script is running, pressing ^C during one of the delays terminates Take Command most of the time (but not always). I've also had the problem ^C'ing out of list /s, etc.

Not reproducible here. I tried running it 100 times with ^C and it
always gave me the prompt to terminate the batch file. I then tried it
100 times with a ^Break and that worked too.

Anybody else having a problem with ^C?

Rex Conn
JP Software

 

[Juanma Barranquero]

On Fri, Apr 3, 2009 at 03:38, rconn <> wrote:

> Not reproducible here.

I supposed as much :(

>Â*I tried running it 100 times with ^C and it
> always gave me the prompt to terminate the batch file.

I just terminated TCMD by doing "dir /p" followed by ^C. But it does
not happen all the time.

I don't know the reason, but it started just after your changes to fix
^Break. Perhaps another Windows bug.

Juanma

 

[Jim Cook]

TCC 10.00.64 Windows XP [Version 5.1.2600]
TCC Build 64 Windows XP Build 2600 Service Pack 3

I was testing this and found that ^C worked with *DIR /P flawlessly
100 times in a row.

I started then testing with ^Break and after twenty times, TCMD
vanished leaving orphaned TCC sessions.

I tried to repeat the test, but it worked flawlessly the next 100 times.

I've been trying to repeat the test, even mixing ^C and ^Break but
cannot get a failure yet.

On Fri, Apr 3, 2009 at 4:45 AM, Juanma Barranquero
<> wrote:

> On Fri, Apr 3, 2009 at 03:38, rconn <> wrote:
>
>
>
> ---Quote---
>> Not reproducible here.
> ---End Quote---
> I supposed as much :(
>
>
>
> ---Quote---
>>Â*I tried running it 100 times with ^C and it
>> always gave me the prompt to terminate the batch file.
> ---End Quote---
> I just terminated TCMD by doing "dir /p" followed by ^C. But it does
> not happen all the time.
>
> I don't know the reason, but it started just after your changes to fix
> ^Break. Perhaps another Windows bug.
>
> * *Juanma
>
>
>
>
>

--
Jim Cook
2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Sunday.

 

[Juanma Barranquero]

On Fri, Apr 3, 2009 at 16:48, Jim Cook <> wrote:

> I started then testing with ^Break and after twenty times, TCMD
> vanished leaving orphaned TCC sessions.

That's what I see (TCMD dies, the TCC sessions continue running,
though they don't have a window).

It has never happened to me with ^Break, only ^C, but that's not
unexpected, as I hardly ever use ^Break.

Juanma

 

[rconn]

Juanma Barranquero wrote:

> On Fri, Apr 3, 2009 at 03:38, rconn <> wrote:
> ---Quote---
>> Â*I tried running it 100 times with ^C and it
>> always gave me the prompt to terminate the batch file.
> ---End Quote---
> I just terminated TCMD by doing "dir /p" followed by ^C. But it does
> not happen all the time.
>
> I don't know the reason, but it started just after your changes to fix
> ^Break. Perhaps another Windows bug.

Still not reproducible here. Are you running any keyboard drivers or
background processes that monitor the keyboard?

Rex Conn
JP Software

 

[Juanma Barranquero]

On Sat, Apr 4, 2009 at 23:15, rconn <> wrote:

> Still not reproducible here. Â*Are you running any keyboard drivers or
> background processes that monitor the keyboard?

Likely, though not on purpose. This is on a HP Pavilion laptop with
Windows XP Home, BTW. There are HP-specific drivers, etc.

Programs likely to affect or monitor the keyboard:

"Quick Launch Buttons", Hewlett-Packard, c:\program files\hpq\quick
launch buttons\eabservr.exe
"TrueCrypt", TrueCrypt Foundation, c:\program files\truecrypt\truecrypt.exe
CoolSwitch,, c:\windows\system32\taskswitch.exe

plus McAfee. There's also a bunch of programs/drivers for the
Synaptics Touchpad, but I don't know whether these would affect the
keyboard.

Quick Launch Buttons is an app to support some fancy multimedia
buttons. TrueCrypt is a disk encrypter; and CoolSwitch is a nicer
Alt-Tab replacement.

None of these programs is recently installed or updated.

Juanma