ctr/c nop in attached consoles in tcmd 10 under vista sp1

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
G

gwmacdonald

Guest
#1
Two environments for comparison:

TCC 10.00.76 Windows Vista [Version 6.0.6001]
TCC Build 76 Windows Vista Build 6001 Service Pack 1

TCC 9.02.155 Windows Vista [Version 6.0.6001]
TCC Build 155 Windows Vista Build 6001 Service Pack 1

Under TCMD 10 in an attached TCC or CMD console, if I run a continuous ping (e.g., ping -t x.x.x.x) or a simple btm file consisting of the single command "delay 999", ctrl/c will interrupt neither. Nothing is displayed when ctrl/c is pressed. However, shift/ctrl/c will interupt both the ping and the btm file as expected. But, if the TCC or CMD consoles are detached, then ctrl/c works as expected.

Under TCMD 9, ctrl/c works as expected in both attached and detached consoles.

I only experience this problem in Vista SP1. I have only one Vista installation, so I don't know if this problem is machine specific. However, this problem does not occur under Windows 7 RTM or XP SP2.
 
G

gwmacdonald

Guest
#2
TCC 11.00.21 Windows Vista [Version 6.0.6001]
TCC Build 21 Windows Vista Build 6001 Service Pack 1

This problem does not occur in TCMD 11.
 

rconn

Administrator
Staff member
May 14, 2008
10,100
85
#3
Two environments for comparison:

TCC 10.00.76 Windows Vista [Version 6.0.6001]
TCC Build 76 Windows Vista Build 6001 Service Pack 1

TCC 9.02.155 Windows Vista [Version 6.0.6001]
TCC Build 155 Windows Vista Build 6001 Service Pack 1

Under TCMD 10 in an attached TCC or CMD console, if I run a continuous ping (e.g., ping -t x.x.x.x) or a simple btm file consisting of the single command "delay 999", ctrl/c will interrupt neither. Nothing is displayed when ctrl/c is pressed. However, shift/ctrl/c will interupt both the ping and the btm file as expected. But, if the TCC or CMD consoles are detached, then ctrl/c works as expected.

Under TCMD 9, ctrl/c works as expected in both attached and detached consoles.

I only experience this problem in Vista SP1. I have only one Vista installation, so I don't know if this problem is machine specific. However, this problem does not occur under Windows 7 RTM or XP SP2.
Not reproducible here. You probably have Ctrl-C defined as an accelerator key in your TCMD 10 configuration -- try right clicking on the TCMD menu and go to the Customize dialog.