Take Command 10.0.66 beta test

rconn

Administrator
Staff member
May 14, 2008
11,242
103
I've uploaded a test build of Take Command 10.0.66 to the ftp beta area (ftp://jpsoft.com/beta/tcmd.exe).

This build has a (hopefully final) fix for the Windows API bug that causes (usually rarely) a Ctrl-Break or (even more rarely) a Ctrl-C to terminate TCMD. If you've experienced problems with Ctrl-Break or Ctrl-C terminating TCMD, please try this build and let me know if you still have any problems.

I've run this build overnight (8+ hours) on three computers with weights holding down the Ctrl and Break keys and haven't been able to make it terminate.
 
Mar 9, 2009
28
0
On Fri, Apr 17, 2009 at 02:27:32PM -0500, rconn wrote:

> I've uploaded a test build of Take Command 10.0.66 to the ftp beta
> area (ftp://jpsoft.com/beta/tcmd.exe).
>
> This build has a (hopefully final) fix for the Windows API bug that
> causes (usually rarely) a Ctrl-Break or (even more rarely) a Ctrl-C to
> terminate TCMD. If you've experienced problems with Ctrl-Break or
> Ctrl-C terminating TCMD, please try this build and let me know if you
> still have any problems.
Although I never had this problem, I had hoped that the new version
might also help with mine (Ctrl-C being blocked from an attached SFU
tcsh shell tab). It doesn't. :-)
 
May 20, 2008
603
0
Sammamish, WA
TCC 10.00.66 Windows XP [Version 5.1.2600]
TCC Build 66 Windows XP Build 2600 Service Pack 3
TCMD v10.00.66

(Running 9.02.154, I could not duplicate any of the below problems.)

.) I have not had any failures while manually pressing Ctrl-C. I'm
only a hundred or so in, however.

.) I also noticed that the Ctrl-C is not being passed through to an
application that does getch().

.) Running stand alone (not in TCMD), and typing EXIT, I get a fault
that does not generate a .GPF file:
---------------------------
tcc.exe - Application Error
---------------------------
The instruction at "0x02d43d5e" referenced memory at "0x02d43d5e". The
memory could not be "written".


Click on OK to terminate the program
---------------------------
OK
---------------------------


.) Running inside TCMD, the following command terminates TCMD and
orphans the two TCC windows. Running this same command in TCC
stand-alone does not cause trouble.
for /l %h in (1,1,100) do (echo %h %+ keystack Ctrl-c)

---------------------------
tcmd.exe - Application Error
---------------------------
The instruction at "0x0213c042" referenced memory at "0x0213c042". The
memory could not be "written".


Click on OK to terminate the program
---------------------------
OK
---------------------------


On Fri, Apr 17, 2009 at 1:11 PM, Emilio III <> wrote:

> On Fri, Apr 17, 2009 at 02:27:32PM -0500, rconn wrote:
>
>
> ---Quote---
>> I've uploaded a test build of Take Command 10.0.66 to the ftp beta
>> area (ftp://jpsoft.com/beta/tcmd.exe).
>>
>> This build has a (hopefully final) fix for the Windows API bug that
>> causes (usually rarely) a Ctrl-Break or (even more rarely) a Ctrl-C to
>> terminate TCMD. *If you've experienced problems with Ctrl-Break or
>> Ctrl-C terminating TCMD, please try this build and let me know if you
>> still have any problems.
> ---End Quote---
> Although I never had this problem, I had hoped that the new version
> might also help with mine (Ctrl-C being blocked from an attached SFU
> tcsh shell tab). *It doesn't. :-)
>
>
>
>
>


--
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.
 

rconn

Administrator
Staff member
May 14, 2008
11,242
103
Emilio III wrote:

> On Fri, Apr 17, 2009 at 02:27:32PM -0500, rconn wrote:
>
>
> ---Quote---
>> I've uploaded a test build of Take Command 10.0.66 to the ftp beta
>> area (ftp://jpsoft.com/beta/tcmd.exe).
>>
>> This build has a (hopefully final) fix for the Windows API bug that
>> causes (usually rarely) a Ctrl-Break or (even more rarely) a Ctrl-C to
>> terminate TCMD. If you've experienced problems with Ctrl-Break or
>> Ctrl-C terminating TCMD, please try this build and let me know if you
>> still have any problems.
> ---End Quote---
> Although I never had this problem, I had hoped that the new version
> might also help with mine (Ctrl-C being blocked from an attached SFU
> tcsh shell tab). It doesn't. :-)
Completely unrelated issue.

Rex Conn
JP Software
 

dim

Dimitry Andric
May 31, 2008
205
1
Netherlands
On 2009-04-17 21:27, rconn wrote:

> This build has a (hopefully final) fix for the Windows API bug that causes (usually rarely) a Ctrl-Break or (even more rarely) a Ctrl-C to terminate TCMD. If you've experienced problems with Ctrl-Break or Ctrl-C terminating TCMD, please try this build and let me know if you still have any problems.
FWIW, I didn't have any problems before with Ctrl-C or Ctrl-Break, and none with this build either.

What is funny though, with build 64, a Ctrl-C only took effect on the key up event, not on the key down. With build 66, this seems to have changed.
 

rconn

Administrator
Staff member
May 14, 2008
11,242
103
dim wrote:

> On 2009-04-17 21:27, rconn wrote:
>
>
> ---Quote---
>> This build has a (hopefully final) fix for the Windows API bug that causes (usually rarely) a Ctrl-Break or (even more rarely) a Ctrl-C to terminate TCMD. If you've experienced problems with Ctrl-Break or Ctrl-C terminating TCMD, please try this build and let me know if you still have any problems.
> ---End Quote---
> FWIW, I didn't have any problems before with Ctrl-C or Ctrl-Break, and none with this build either.
>
> What is funny though, with build 64, a Ctrl-C only took effect on the key up event, not on the key down. With build 66, this seems to have changed.
WAD.

Rex Conn
JP Software
 
May 20, 2008
9,634
64
Syracuse, NY, USA
On Fri, 17 Apr 2009 14:27:39 -0500, rconn <> wrote:

|I've uploaded a test build of Take Command 10.0.66 to the ftp beta area

Was there a build 65?
--
- Vince
 
Jun 26, 2008
38
1
On Fri, Apr 17, 2009 at 21:27, rconn <> wrote:


> This build has a (hopefully final) fix for the Windows API bug that causes (usually rarely) a Ctrl-Break or (even more rarely) a Ctrl-C to terminate TCMD. Â*If you've experienced problems with Ctrl-Break or Ctrl-C terminating TCMD, please try this build and let me know if you still have any problems.
It is apparently working fine. "Apparently" in the sense that I
haven't been able to make it crash in the use cases where it often did
before.

Juanma