Installer sets BTM associations wrongly

[vefatica]

On two machines, the installer leaves the likes of this.

v:\> ftype tcc.batch
tcc.batch="G:\tc24\tcc.exe" /c "%%1" %%*

And BTMs can't be run from Explorer.

Running TCCBATCH.BTM gives something a bit different.

v:\> ftype tcc.batch
tcc.batch="G:\tc24\TCC.EXE" /c "%1" %*

and that's OK with Explorer.

I think the installer is still not setting the association correctly.

When I started to compose this post I was on build 30. Now I'm on build 31 and the problem is the same.

 

[Charles Dye]

I saw this the other day, and convinced myself it was my own damn fault....

The file association for .BTM was set to "TCC.Batch " with a trailing space. Is that what you're seeing, Vince?

 

[vefatica]

I saw this the other day, and convinced myself it was my own damn fault....

The file association for .BTM was set to "TCC.Batch " with a trailing space. Is that what you're seeing, Vince?

I didn't notice a trailing space (I wasn't looking there). I only noticed the extra "%"s in the "open" command.

I also noticed a difference between Win7/32 and Win10/64. After an update and before any fixes ... on Win7, 2-clicking on a BTM brought up a a dialog: "Explorer doesn't know how to ..."; on Win10, I got a momentary console with no BTM in it. An extra space on Win7 (no such file type) and not on Win10 (bad args to TCC) might explain that difference.

 

[rconn]

CMD bug - fixed in build 32 (already uploaded).

 

[vefatica]

CMD bug - fixed in build 32 (already uploaded).

It's now OK on both my machines.