|
![]() [ View full size screenshot ] |
| Version | Date Released | Status | Release Notes |
| TCC/LE 13.03.39 | Jan 23, 2012 | New Release | · The batch debugger editor and command input editor have been upgraded to a major new version. · Added the feedback tab to the web help pages. · BDEBUGGER - Added the Ctrl-F3, F3, and Shift-F3 keys (find next / find prev). |
| TCC/LE 13.03.38 | Jan 9, 2012 | New Release | · The batch debugger editor and command input editor have been upgraded to a major new version. · Added the feedback tab to the web help pages. · BDEBUGGER - Added the Ctrl-F3, F3, and Shift-F3 keys (find next / find prev). |
| TCC/LE 13.03.36 | Jan 5, 2012 | New Release | · The batch debugger editor and command input editor have been upgraded to a major new version. · Added the feedback tab to the web help pages. · BDEBUGGER - Added the Ctrl-F3, F3, and Shift-F3 keys (find next / find prev). |
| TCC/LE 13.02.36 | Dec 29, 2011 | New Release | · The batch debugger editor and command input editor have been upgraded to a major new version. · Added the feedback tab to the web help pages. · BDEBUGGER - Added the Ctrl-F3, F3, and Shift-F3 keys (find next / find prev). |
| TCC/LE 13.02.35 | Dec 21, 2011 | New Release | · The batch debugger editor and command input editor have been upgraded to a major new version. · Added the feedback tab to the web help pages. · BDEBUGGER - Added the Ctrl-F3, F3, and Shift-F3 keys (find next / find prev). |
| TCC/LE 13.01.33 | Dec 13, 2011 | New Release | · The local help (tcmd.chm) has a number of new display options. · Take Command and TCC now have the option to use either the new Web Help or the local help (tcmd.chm). The web help has some additional features, including the ability to add comments to help topics. · The search algorithm for the popup windows has changed slightly. TCC will append a * to the search string unless the last character of the string is a wildcard (?, *, or ]), or if the search string is a regular expression (the first two characters of the string are ::). · MKLINK - The /X option no longer requires two arguments. · Take Command/LE has been discontinued. Existing Take Command/LE customers have been sent a free update to the full Take Command version. |
| TCC/LE 13.01.29 | Nov 16, 2011 | New Release | · Take Command/LE and TCC/LE are now available in 32-bit and 64-bit versions. · Removed the (non-Windows) limits on filename and argument size. The maximum filename size (dictated by Windows) and single argument size is now 32,767 characters. · The maximum (input) command line is now 65,535 characters. · The maximum expanded command line size is now 131,072 characters. · Fuzzy directory (jpstree.idx) updates (in MD, RD, DEL /S/X, etc.) are twice as fast as v12. · The Take Command (and Take Command/LE) toolbar has a new button "V" that will call the new file viewer VIEW (see below). |
| TCC/LE 13.00.28 | Oct 31, 2011 | New Release | · Take Command/LE and TCC/LE are now available in 32-bit and 64-bit versions. · Removed the (non-Windows) limits on filename and argument size. The maximum filename size (dictated by Windows) and single argument size is now 32,767 characters. · The maximum (input) command line is now 65,535 characters. · The maximum expanded command line size is now 131,072 characters. · Fuzzy directory (jpstree.idx) updates (in MD, RD, DEL /S/X, etc.) are twice as fast as v12. · The Take Command (and Take Command/LE) toolbar has a new button "V" that will call the new file viewer VIEW (see below). |
| TCC/LE 12.11.74 | Aug 17, 2011 | New Release | · TCMD.INI file parsing (and thus the startup time) is faster. · Changed the dialog fonts from MS Sans Serif to Tahoma. · File read operations are slightly faster. |
| TCC/LE 12.11.71 | Jul 19, 2011 | New Release | · TCMD.INI file parsing (and thus the startup time) is faster. · Changed the dialog fonts from MS Sans Serif to Tahoma. · File read operations are slightly faster. · CMDVariables=yes|NO - Requires environment variables in TCC to be delineated by leading and trailing %'s. For those of you who just can't get enough of CMD compatibility, and the consistent way it handles variables. Which have to be enclosed in %'s, like "%varname%". Unless it's a batch variable, which only has a leading %. Or a FOR variable, which only has a leading %. Or sometimes two leading %'s. |
![]() Desktop Collection everything for convenient computer operation & control into 1 economical pac |