> There is no "standard Windows method" for setting custom console colors; it's (completely) different in every version of Windows.
From a user point of view, the properties dialog for console apps is pretty much unchanged since Windows 3. You get 16 colors corresponding to the 16 colors...
TCC.exe version 12.0 and 12.10 ignore any custom console colors set via a Windows shortcut.
Is this a bug by design?
I hope it's the former, because I'd be disappointed if you no longer support the standard Windows methods for setting console dimensions, fonts sizes and colors using...
Additional info.
The problem is in the running of the encrypted btm file, not in the encryption itself.
Proven by running encrypted scripts created by v11 and v8, using v8.
One of two of my old script are getting output truncated using TCC 11.00.33 x64. Happening where I'm using '()' brackets in the output. Works ok if I use '{}' brackets instead.
Is this limitation by design?
Here's an example ("ss" is a variable in my original script)...
I'm getting an 'Invalid batch file' error whenever I use batcomp to encrypt a script using TCC 11.00.33 x64. Also failed for TCC 11.00.32 x64.
Works fine if I use 4NT 8.02.106.
I'm running Win 7 64 bit.
Example:
[M:\Dev\BTM]batcomp hello.btm hello_comp.btm
Compressing...
I sometimes run 4NT full screen, i.e. start it up and press Alt-Enter. Works fine.
TCC has a problem with this mode because the history windows are graphical, not part of the console.
Is there a workaround? I couldn't see a setting for this in the help file.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.