This happens when TinyTERM connects via telnet, but America On-Line uses a dial-up connection. It’s due to a conflict between the TCP/IP stack for AOL and the Windows stack TinyTERM uses. TinyTERM can’t differentiate between the two.

TinyTERM versions 4.10 and higher have changes that correct for this. No patch is available for earlier versions.

When using Alt-Tab to switch between Windows applications, TinyTerm is not always active when you return to it. You have to click on the TinyTERM window to make it active.

This is a focus problem. Alt-Tab is returning system focus to tt.exe, which is the application that runs TinyTERM. What it’s not doing is returning focus to the ActiveX control that makes up the actual emulator.

This is a Windows peculiarity. The tt.exe application is really just a wrapper around the ActiveX control. It allows CenTE.ocx to run by itself, instead of in a Web browser for example. When Windows tracks the application, it normally only sees tt.exe, and so that’s where it returns focus. It’s not seeing the ActiveX piece by itself, so it doesn’t always get the focus in the right place. Unfortunately, there’s no programming we can do in TinyTERM to change that Windows behavior.

Using TinyTERM 4.02, the modem dials, but it gets a high pitched sound and the remote party disconnects. There are known TAPI connectivity  issues in that version. There is no patch. The only solution is to upgrade.

TinyTERM includes a sample script called noprefs.cs. This allows you to remove the Preferences item from the Edit menu. But what if you want to remove more items from the menus? Where are the MENUITEM numbers listed?

You don’t actually have to use the MENUITEM number to remove a menu item. If you’ll take a look at the first RemoveMenuItem() command in the script noprefs.cs, it does its work entirely by position:

RemoveMenuItem( GetSubMenu( hMenu, 1 ), 3 , 1024 );

The first parameter, GetSubMenu( hMenu, 1), is the menu number of menu index 1, the Edit menu. The menus are indexed from left to right, with the first menu (File) being index 0. So you can use GetSubMenu(hMenu,3) to indicate the Tools menu, for example.

The second parameter, 3, is the index number of the menu item. Again, these are indexed starting at 0. Item 3 in the sample script is the separator bar on the Edit menu. It’s actually a separate menu item, though you can’t click it.

The third parameter, 1024, is an internal command which tells RemoveMenuItem() to delete by position index instead of by actual number. This is required when using RemoveMenuItem() in this fashion.

Please note that removing one item reindexes every item below it. So if you remove item 3, the next item down becomes item 3, etc. When removing menu items in this fashion, it’s best to remove them from the bottom up.

This error means a serial number and activation key have already been applied to TERM. If it will not start, uninstall TERM, then reinstall it.

If that does not get rid of the error, you probably have the wrong serial number for your version of TERM. Contact Technical Support to verify your license information.

This error generally means the phone line used by the modem is in use or otherwise not working. Test it with another modem-using application, such as cu or HyperTerminal. If that gives the same or a similar error, check your phone lines. You may also need to reboot your PC.

Using TinyTERM 4.04 over a serial connection, the text can pause occasionally, then more text will display. It’s very slow in such cases.

In TinyTERM 4.05 there was a change made to the way TinyTERM buffers screen display. It smooths out the pauses and clumping of text. There is no patch.

When installing TinyTERM from a CD, you may see the error, “Drive not ready.” When this happens, try running the TinyTERM install from Start | Run. If that brings up the same error, try reading another CD in the same drive.

If other CDs will read properly, the TinyTERM CD is damaged or defective. You will need a replacement or an upgrade, depending on the version you have. Please contact our Sales department for more information.

It is possible to open multiple sessions over a single serial connection. It requires software such as mscreen or FacetTerm on the host system. Without that, only one session can run on a serial connection.

You also need to set the screen pages. That’s handled differently by different versions of TERM and TinyTERM:

• TERM: Use the TERM Script Language command PAGES:
  

  pages 4

• TinyTERM (up to 3.3) or TERM for Windows: Go to the Configure menu and select Emulation. Change the Screen Pages line.
• TinyTERM for DOS: From the main menu, select Emulation. Change the Screen Pages line.
• TinyTERM 4.00-4.20: Edit the .tpx file in Notepad or another text editor. Search for the “pages=” line. Edit the number there.
• TinyTERM 4.21 and higher: Go to the Edit menu and select Preferences. Change the Screen Pages drop-down.

Regardless of which product you’re using, accepted values for the screen pages are 1-6.

CR 26, added to user interface in TinyTERM 4.21

When switching to another Windows application from TinyTERM, your cursor may disappear. This can happen if you set a block cursor within TinyTERM. In some circumstances, this sets the cursor to block globally within Windows. It’s a Windows behavior, not something that can be controlled within TinyTERM.

In this situation, when you switch to another application, such as Microsoft Word, the global block cursor may appear as no cursor. It can’t be displayed as a block in the new application. The only fix is to use an underscore cursor instead of a block.