I'm running the latest version of TCC 11.00.44 64-bit under Win7 and I've encountered a problem that I have never seen before (and I've been a registered users since the early days of 4DOS). If I type in one or more characters in the tcc console window and hit the TAB or F9 key and there are no files in the current directory that start with the characters I typed, the command line freezes and the only option is to close the tcc window. For example, if I type in "xyz" and hit tab, and there are no files in the directory matching "xyz*" it freezes. If I run the 32-bit version on the same machine with the same options and aliases, I do NOT get the same behavior. The window allows me to continue editing the command line. I suspect the problem may be that the command line wants to "beep" when the expansion fails, and the normal beep isn't supported in 64-bit windows. If I try to use the beep command, I get the same lockup, which suggests that TCC's directsound implementation of beep may have a bug.