When you minimize TinyTERM, then bring it back up after working in another application, the right side of the screen may have a different color than the rest of the window. That is a cosmetic issue in TinyTERM. The different color comes from the difference between the actual window size, and the amount of space the font actually fills. If 80 columns don’t take up the full width of the window, the rest is filled in the default background color.

The workaround is to adjust the TinyTERM window size so the font width exactly fills the window, then save the settings. There is no patch.

When you click on a telnet link in a browser, TinyTERM should open and make the connection. If another application opens, you can restore TinyTERM as the helper application with these steps:

1. Open My Computer or Windows Explorer.
2. From the Tools menu, select Folder Options.
3. On the File Types tab, locate the “URL:Telnet Protocol” item in the N/A portion of the list and click it to highlight.
4. Click the Advanced button.
5. Click the word “open” in the list to highlight it, then click the Edit button.
6. Under “Application used to perform action,” enter this string:
   

   “C:\Program Files\Century\TinyTERM\tt.exe” /helperapp:%1

7. Click OK several times, until the Folder Options is closed.

Like all versions of TinyTERM, the TinyTERM Web Server Client must be installed with administrator privileges on the local PC. However, unlike other versions of TinyTERM, the Web Server Client will fail with an application error for the most restricted users. It must run under at least Power User rights on Windows NT, 2000, XP or Vista.

When running Century Internet Services on Windows 95, 98 or Me, enabling the time server (either tcp or udp) causes multiple icons to appear in the Systray. Task Manager shows a separate copy of mar_inet.exe for each icon. They can be removed only by turning off the time server.

CR 247

If you have TinyTERM’s Session Properties open, and TinyTERM closes due to the “Close session on disconnect and exit” setting, the Session Properties dialog will stay open. It won’t close by clicking the OK or Cancel button, nor does the X in the upper right do anything.

To close the Session Properties, right-click on your taskbar and select Task Manager from the pop-up window. Kill any TinyTERM or tt.exe process there.

This behavior is fixed in TinyTERM 4.30. In that version and subsequent releases, the TinyTERM window will stay open until the Session Properties dialog closes. It will then respond to the automatic close.

CR 338

TinyTERM version 4 includes a DDE server and client, documented in the Programmer’s Reference Manual. The server is configured and enabled through CScript commands.

It’s possible using the DDE server to send script commands to TinyTERM from another application. However, it only accepts TERM Script Language commands in that manner, which are not documented in the Programmer’s Reference Manual. PDF documentation for TSL can be downloaded from this link.

That documentation also applies to TinyTERM Application Developer 3.3. That version of TinyTERM uses TSL exclusively, not CScript, so the notes above do not apply.

CR 499

Century Internet Services is a suite of TCP/IP server applications included with TinyTERM Plus and TERM Professional. It installs on Windows 95, 98 and Me. Once TinyTERM is installed, it starts automatically when Windows starts.

You can stop Century Internet Services from launching at startup by doing the following:

1. Click Start | Settings | Control Panel.
2. Double-click on the Network icon.
3. Click on Century Internet Services in the list, then click the Properties button.
4. Select the Options tab.
5. De-select the option “Start Century Internet Services at Windows Startup.”
6. Click OK, then click OK again.

When TinyTERM 4.x is connected via modem, some email attachments won’t open from Microsoft Outlook. In particular, documents from Microsoft Office applications such as Word and Excel are affected. As soon as TinyTERM disconnects, the documents will open. This was fixed in TinyTERM 4.30.

CR 209

TinyTERM versions 4.00-4.20 have a memory leak in the Session Properties dialog. If you change several settings at a time, eventually you’ll see a “Get property failed” error message.

When this happens, the solution is to save your settings and exit TinyTERM. When you start TinyTERM again, the error will not happen immediately. Some of your previous settings may be lost, though.

CR 254, fixed in TinyTERM 4.21
CR 401, duplicate

TERM and TinyTERM for Windows have an automated login function that can readily be extended to execute system commands as part of the connection. Under the Login setup, or the Advanced Login setup, there are four “Wait for” and “Then send” options. The first two lines are taken for the login and password prompts. The last two can be used for anything.

Note that the “Wait for” items are case-sensitive. That’s why the first letters are missing from the words “login” and “password” there. Some systems send these in upper case, others in lower. But the rest of the word is virtually always lower case, so leaving the first letter off bypasses guessing its case.

The default “Then send” strings are composed of what look like control characters. Here they are, explained:

• ^W – This causes TinyTERM to wait one second before performing the next operation.
• ^U – This sends the username from the Login dialog down the comm line.
• ^P – This sends the password. The password is stored encrypted, so it can’t be read directly from the configuration file.
• ^M – This sends a carriage return, ASCII value 13.

Any other characters entered in a “Then send” line will be sent as plain text. All characters in a “Wait for” line will be read as plain text.

Given that information, you can send any command to the host using those text boxes. For example, to wait for a $ prompt, then send an “ls” command, you would enter:

$

in the third “Wait for” line. In the accompanying “Then send” line, enter:

ls^M

The one-second wait given by ^W may or may not be necessary. Experiment with the timing to see how the commands work out. We also recommend you go through the login manually before automating it, so that you can note any differences from the defaults. Different or additional prompts are the most common changes.