In the meantime, I resorted to using this little snippet as a workaround for this limitation. This may be useful to others who may use earlier versions of TCC which which may be affected by this bug. It also has the advantage(for me) that the input history is available with CMD's SET /P...

INPUT or SET /P fails if the entered text contains pair of square brackets. [C:\]INPUT Enter text: %%myvar Enter text: Sample text [ to fail input ] TCC: Not an array variable "myvar" [C:\] The documentation does not mention anything about this behavior so Its not clear to me if it is...

Thanks for the replies guys. I appreciate that. Specially for the comments/recommendations about detecting the Comspec at run time. Yes, TCC is superior to CMD in every aspect. there is no doubt about that. TCC is capable of performing very complex tasks that are not imaginable to doing them by...

When using windows cmd.exe, if we want to know whether an existing File System Object(FSO) is a file or a directory, all we have to do, is to append a BackSlash at the end of the object name and then check for its existence: if exist example ( if exist example\ ( echo This is a...

Is there any particular reason that the digital signatures of tcmd16 x86 installer and files are not time stamped but the x64 files are?

This problem does not occur if you run the normal installation of tcc with Sandboxie. As I mentioned in my first post : "If Take Command be installed under Sandboxie..." To reproduce the error, run Take Command "installation" file with Sandboxie, and then run tcc from sandbox...

Windows XP SP3 Take Command v10.0.73 - TCC/LE v10.0.73 Sandboxie v3.38

Incompatibility with Sandboxie If Take Command be installed under Sandboxie (http://www.sandboxie.com) it cant be used, because upon start of tcc.exe, it reruns itself repeatedly. this is also true for TCC/LE. This may be a rare case that some one installs TCC under Sanboxie and face this...