At the SCO UNIX console, the sequence \033[0m resets the text attributes. It removes all bold, reverse, blink, etc., characteristics, and restores the colors to their defined defaults, normally white text on a black background.

When TinyTERM is configured for SCOANSI emulation, \033[0m restores all text attributes to normal except color. If the colors have been changed, they stay changed.

The documentation is a little ambiguous. It reads in part:

Disable all attribute modifiers (bold, underline, italic, reverse video, concealed and blinking). In the default mode, set the font back to font 0. In backwards compatibility mode, only set the font if the SGR0 control option is set . . .

There is no mention of color at all. So whether or not TinyTERM is acting correctly is not strictly defined.

CR 542

Century Software, Inc., has had a request to increase the number of available background colors. This has not been implemented in the user interface. However, through CScript you can redefine the existing colors.

CR 409

TERM for UNIX/Linux acts as a monochrome emulator only, even when the terminal type chosen can display colors.

CR 16, TERM for Linux
CR 223, TERM for UNIX

The Use non font-based line draw characters option on the Attributes tab of Session Properties creates lines in bold white only. There is no way to change this.

CR 134

When a portion of the text in the TinyTERM window is blinking, none of the text can be selected for long, even the non-blinking areas. You can select text initially, but as soon as something blinks, the selection disappears.

This was changed in TinyTERM 4.30. Selecting text temporarily disables the blink attribute until the selection is somehow canceled.

CR 354

The IBM3151 emulation in TinyTERM 4.x does not always display bold text correctly. It also does not turn off correctly in all cases. This is fixed in TinyTERM 4.30.

CR 296

Whenever something on screen should blink, it does, but it always uses the default colors for the session. If the host changes the colors, that doesn’t come through. This was fixed in TinyTERM 4.21.

CR 292

Using any terminal emulation, TinyTERM 4.00-4.13 will not always display reverse text properly. Instead, it displays as normal text. If Ignore host color sequences is checked on the Attributes tab of Session Properties, reverse works properly. This was fixed in TinyTERM 4.20.

CR 139

TinyTERM version 4 introduced much greater color and attribute flexibility for display. Not all users find the default settings to their liking, though. It’s easy to change the color pallette and other font attributes.

In TinyTERM, open the Session Properties and go to the Attributes tab. In the “Mappable attribute combinations” box are 16 different combinations: NORMAL, BOLD, REVERSE, etc. As you highlight each one by clicking on it, you can change both the foreground and background color, as well as the display attributes assigned to it. Use the “Display Attribute As” and color boxes on the right of the dialog.

Once you have configured each attribute the way you like, click the Save As button to give the new attribute scheme a name. It will be saved to the file attr.dat. If you would like to distribute the new scheme to other users, simply copy that file to their PCs in the C:\Program Files\Century\TinyTERM folder.

Once you’ve created a custom keyboard mapping, attribute scheme or other configuration in TinyTERM, you may want to distribute it to all users. There is an easier way than recreating the configuration on every single PC.

Once you’ve created a custom keyboard scheme in TinyTERM, it’s saved into the file C:\Program Files\Century\TinyTERM\keyboard.dat. To copy a scheme to another PC, you only need to copy the keyboard.dat file. Then the next time you start TinyTERM, the new scheme will be available on that PC as well.

Other custom configuration files that can be distributed the same way. There are several, all with the .dat extension:

attr.dat – contains attribute schemes: colors, etc.
codepage.dat – contains code pages for different character sets
login.dat – contains automatic login schemes

All this information is referenced by connection files, which have the .tpx extension. Those files contain all the connection information, but they also reference the .dat files. So no matter how much customizing you do in TinyTERM, you only need to distribute the four .dat files and any .tpx files you may have created.