The “STD 1250 Windows Latin 2” transmit code page has the á (a acute) character unassigned. It was properly assigned to position 225 in TinyTERM 4.20.

CR 155

TinyTERM 3.x and TERM 7.x for Windows allow the user to select a language during install. The install then copies the appropriate resource files for that language only. It applies to all TinyTERM or TERM menus and dialog boxes. Available languages include English, French, Spanish and Hungarian.

TinyTERM 4.00-4.05 only have an English-language menu system. French and German were added in TinyTERM 4.10. More languages were added in TinyTERM 4.31: Italian, Spanish, Polish and Portuguese. They can be changed on the fly from the View menu. Again, these languages apply to the menus and dialog boxes in TinyTERM.

The language within the emulator window is handled through code pages. The host system and TinyTERM must be using the same code pages, or the display will be incorrect.

CR 11, Italian, German
CR 213, split into CRs 264, 265 and 266
CR 214, version 4.21 has language selector during install
CR 264, Spanish
CR 265, Polish
CR 266, Portuguese

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.

Using TinyTERM 3.3 and PCTERM emulation on Windows 3.1, some keys give extra characters, such as:

pressing a key gives ad
x gives xx
l gives l_

To fix this, change the primary code page to “STD 437 MS-DOS Latin US.”

When using SCOANSI, AT386 or other ANSI-series emulations, screens that should have lines or boxes drawn may not. Or the lines may draw as letters instead.

To fix that, open the Session Properties and go to the Code Page tab. Click the Advanced button. The top two lines of that dialog are SCOANSI alternate character sets. Set both to “STD 437 MS-DOS Latin US”. That should correct the line draw problem.

You can also go to the Attributes tab and check the “Use Non-Font Based line draw characters” option. This will use Windows graphics instead of text characters to draw the lines.

Restoring the code pages to the alternate character sets will also fix character alignment problems. For example, if the screen goes out of alignment when you minimize TinyTERM, check the SCOANSI alternate character sets.

CR 281, default.tpx
CR 360, added to all included .tpx files