TCC won't close after .btm execution

Jul 7, 2008
35
0
Texas, USA
#1
I'm testing latest TCMD version/build before upgrading and ran into a weird problem: when I double click on a .btm file it opens and runs in a TCC window, but once the batch is complete, the TCC window doesn't close.

It tried to deassociate .btm and then reassociate it, but that made no difference. Also tried to reinstall Take Command which also had no effect on the problem.

Any ideas what might cause this and how I could fix it?
 
Aug 9, 2009
133
0
#2
add EXIT to end of batch


> -----Original Message-----

> Subject: [Support-t-2529] TCC won't close after .btm execution
>
>
> I'm testing latest TCMD version/build before upgrading and ran into a
> weird problem: when I double click on a .btm file it opens and runs
> in a TCC window, but once the batch is complete, the TCC window
> doesn't close.
>
> It tried to deassociate .btm and then reassociate it, but that made
> no difference. Also tried to reinstall Take Command which also had no
> effect on the problem.
>
> Any ideas what might cause this and how I could fix it?
>
>
>
>
 

rconn

Administrator
Staff member
May 14, 2008
10,579
97
#4
> Apparently something changed between v11 and v12 that made issuing exit
> necessary to close the execution window when evoking a script by double-
> clicking on its icon..?
No - you just need to change your batch file association to say "TCC /C
...". The /C tells TCC to close when the batch file exits.

If you run the TCCBATCH.BTM file in your v12 installation folder, it will
make the changes for you.

Rex Conn
JP Software
 
Jul 7, 2008
35
0
Texas, USA
#5
No - you just need to change your batch file association to say "TCC /C
...". The /C tells TCC to close when the batch file exits.

If you run the TCCBATCH.BTM file in your v12 installation folder, it will
make the changes for you.
Running tccbatch.btm did not fix it. Apparently something had gone wrong with the association. I first ran

assoc .btm=
ftype TCC.Batch=

to deassociate .btm. However, even after that a definition still remained in the registry for .btm. Once I deleted it, I could then recreate the association correctly by running tccbatch.btm. Now it works.