Is the "File Associations" installer dialog working?

[Charles Dye]

The last few times I've updated Take Command, I've let the installer do its default thing:

But my old association from ... uh, 2016 remains untouched:

C:\>ver

TCC  24.00.27   Windows 7 [Version 6.1.7601]

C:\>echo %_cmdspec
C:\Bin\TCmd24\TCC.EXE

C:\>assoc .btm
.btm=btmfile

C:\>ftype btmfile
btmfile="C:\Bin\TCmd19\TCC.EXE" /c "%1" %*

C:\>

It's as if it doesn't want to overwrite an existing association.

 

[rconn]

This appears to be a Windows Installer x86 issue (x64 is working). I'll try to get a workaround into the next build.

 

[Charles Dye]

Not urgent for me. Just something I thought you should know about.

 

[vefatica]

This appears to be a Windows Installer x86 issue (x64 is working). I'll try to get a workaround into the next build.

After reading Charles's original post, I checked "BTM files" (for the first time with v24) when I updated to build 27 on Win7/x86. It worked.

 

[Charles Dye]

Works as expected for me in build 30:

C:\>ver /r

TCC  24.00.30   Windows 7 [Version 6.1.7601]
TCC Build 30   Windows 7 Build 7601  Service Pack 1
Registered to COE-DDPTMHQ1

C:\>assoc .btm
.btm=TCC.Batch

C:\>ftype tcc.batch
tcc.batch="C:\Bin\TCmd24\tcc.exe" /c "%%1" %%*

C:\>