Build 144 Installation Bug?

[edlipson]

I hit a similar problem to one one reported in the support forum (old) about not being able to execute scripts. There may be something wrong with ftype in the installation when you relate bat and cmd to TCC.

In a build 129, the ftype are
---- CON
batfile="C:\Program Files\JPSoft\TCMD9\4nt.exe" /c "%1" %*

---- CON
cmdfile="C:\Program Files\JPSoft\TCMD9\4nt.exe" /c "%1" %*

In 144
--- CON
cmdfile=C:\Program Files\JPSoft\TCMD9\4nt.exe "%0" "%$

---- CON
batfile="%1" %*

Repairing 144 returns the system to how it was before
---- CON
batfile="C:\Program Files\JPSoft\TCMD9\4nt.exe" /c "%1" %*

--- CON
cmdfile="C:\Program Files\JPSoft\TCMD9\4nt.exe" /c "%1" %*

 

[Charles Dye]

I see it too, after installing TCC/LE built 145 and letting the installer create file associations. The installer is creating keys named:

HKCR\JP Software.TCC LE 9.02.BAT\shell\&Open\command\
HKCR\JP Software.TCC LE 9.02.BTM\shell\&Open\command\
HKCR\JP Software.TCC LE 9.02.CMD\shell\&Open\command\

The default (unnamed) value in each "command" key is correct. However, the installer is also creating a value named "command" within each key, of type REG_MULTI_SZ and containing gribble. That item appears to be confusing Explorer; deleting it (from all three keys) fixes Explorer's handling of these file types.

I haven't tested, but I suspect that running TCCBATCH.BTM would also fix the issue because it uses different registry keys.