How to? Strange colours

I had to reinstall Windows and TCC recently. Now colours are behaving strangely.

See the attached file. I configured black on pale yellow, which it does where where there is text, but leaves the rest of the screen a dark yellow green. Where did it get that colour from?
colours.png
 
It looks like the "bright" bit gets lost; I don't know how. But to change the background color, I suggest CLS /C:

Code:
cls /c black on bright yellow

The problem with that is you are limited to the old DOS colours, almost none of which are suitable for reading text. I can figure out how this is supposed to work, perhaps I can track down why it is not working.

My gut feeling is it may have something to do with which palette entry is selected when you pick a new colour numerically.
 

rconn

Administrator
Staff member
May 14, 2008
12,344
149
Is this in a stand-alone TCC console window, or in a Take Command tab window?

How did you configure your colors? There are multiple ways to do it :
  1. The registry
  2. The console properties
  3. The Take Command configuration dialog (Tabs / Windows)
  4. The TCC configuration dialog (OPTION / Windows)
  5. ANSI strings
Each approach has advantages and disadvantages; without knowing how you're setting your colors I can't provide an answer on how to correct it.
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
4,461
88
Albuquerque, NM
prospero.unm.edu
My gut feeling is it may have something to do with which palette entry is selected when you pick a new colour numerically.

But, looking at your screenshot, the text background is bright yellow. Therefore the palette entry for "bright yellow" is set correctly. I suspect you're somehow filling the console buffer with the wrong value, which gets overwritten with the right value as text is written to the console.

Did you try CLS /C BLACK ON BRIGHT YELLOW ?
 
Is this in a stand-alone TCC console window, or in a Take Command tab window?

How did you configure your colors? There are multiple ways to do it :
  1. The registry
  2. The console properties
  3. The Take Command configuration dialog (Tabs / Windows)
  4. The TCC configuration dialog (OPTION / Windows)
  5. ANSI strings
Each approach has advantages and disadvantages; without knowing how you're setting your colors I can't provide an answer on how to correct it.

I started in TCC OPTION. I set the 3 foreground and 3 background colours.

I then pause a running BTM file and click properties.
I then select the background colour with the number wheel.

I am using TCC only. There are no colour commands in my BTM files.

I have also tried Take Command config without joy.

I presume the palettes can be ignored. It might be that you have to get all the colours of interest into the palette, then select from it. Changing the palette will destroy earlier choices.
 
But, looking at your screenshot, the text background is bright yellow. Therefore the palette entry for "bright yellow" is set correctly. I suspect you're somehow filling the console buffer with the wrong value, which gets overwritten with the right value as text is written to the console.

Did you try CLS /C BLACK ON BRIGHT YELLOW ?

This works, but gives you very limited colour selection. Is it possible for an enhanced CLS that uses two (or six) html #rrggbb colour numbers? or is there some legacy DOS restriction? With that I could ignore the settings in the BTM properties and the palettes.

I don't want bright yellow. I was trying to get a pale yellow. However, thing I was mainly complaining about was the alternate dim yellow background.
 
I had to reinstall Windows and TCC recently. Now colours are behaving strangely.

I configured black on pale yellow, which it does where where there is text, but leaves the rest of the screen a dark yellow green. Where did it get that colour from?

I have discovered three facts that may be germane.

1. There are TWO menu items on a running BTM file, one labelled DEFAULTS and one labelled PROPERTIES.

2. When I use a colour number, I can get any 32-bit colour background I desire for the rest of the run. The problem is sticking for the next run. I still don't know if this is part of TCC or part of Windows.

3. I could not see any sign of a list of BTM files in the registry along with information about their colours.
 
May 20, 2008
11,400
99
Syracuse, NY, USA
2. When I use a colour number, I can get any 32-bit colour background I desire for the rest of the run. The problem is sticking for the next run. I still don't know if this is part of TCC or part of Windows.

It's part of Windows. A console's palette contains only 16 colors. You can change what those 16 colors are ... temporarily, as you point out above, or permanently by setting defaults. The entries in HKEY_CURRENT_USER\Console are the defaults. The entries in sub-keys are those specific to various console apps. I don't know if the app-specific ones can be changed (and remembered) from a dialog.
 
I think the trick to making this work is to define your global palette in OPTION, then select colours only from than by clicking on the palette, You are limited to that palette of 16 colours for everything.
The number selection seems to apply only for that one run. Everything I have read about colours and CMD.EXE assumes a limit of 16 colours.
Logically if Properties can insert any colours for the rest of the run, something should be able to intercept that choice and make the choice persist. I think it persists the slot number in the palette, but not the colour itself.
 
Similar threads
Thread starter Title Forum Replies Date
R strange bug? Support 7
Jesse Heines Strange Line Wrapping Behavior Support 14
F strange results Support 9
M Strange error messages from TCC in FTP copy Support 7
M Another possibly strange remote registry issue Support 5
forbin Strange handling of [nonbright] magenta background (v22) Support 2
N Fixed Strange dir behavior Support 6
vefatica REGDIR, strange error message Support 7
T WAD Strange Unexpected "features" in the Debugger Support 2
P Strange mouse behavior with list Support 2
vefatica Strange tcc.exception.log Support 7
vefatica A strange one Support 0
D Strange DO behavior with /O Support 5
Glenn Bowes Strange text at startup Support 5
Steve Pitts WAD Strange output from DEL of a non-existent directory Support 7
vefatica Big numbers, strange errors Support 1
aedthuio Strange... lpksetup Support 4
CWBillow dir /4 strange Support 2
D Strange issue with FOR loop Support 15
MikeBaas Strange prob with %@replace.. Support 4
vefatica OT: strange files in %TEMP Support 10
Dan Glynhampton Documentation v15 help: Strange links in @INT topic Support 0
R WAD Strange output from "memory" command Support 1
M Yet another strange something re something called "@TCONVERT" Support 8
M WAD Strange "Start" misbehavior... Support 10
vefatica Very strange console font corruption Support 3
Steve Pitts Strange problem with FREE Support 10
A strange error in alias Support 9
newgeekorder Debugger IDE - strange tab and parameter behaviour Support 1
Exolon Strange Prompt. Support 6
vefatica Strange folders Support 1
T Strange CPU value Support 3
J Strange error: unset /s Support 14
M Strange behavior... Support 2
CWBillow Strange happenings Support 2
B Strange handling of a .BAT file Support 5
vefatica Strange behavior reloading SHRALIAS sav files. Support 1
J ASSOC / FTYPE strange error message Support 3
D Strange crashes in @CRC32 and @MD5 Support 9
Charles Dye Strange output, here-doc redirection, TYPE, //UnicodeOutput=Yes Support 6
S Strange CHKDSK behavior Support 6
vefatica Strange results with CP 1252 Support 12
S Strange REN problem - non-English characters Support 3
dcantor Strange status in ACTIVATE command Support 0
Roedy unstable colours Support 1
Roedy where are the colours Support 1
Roedy Screen background colours Support 1

Similar threads