When printing the screen or running a transparent print job, the printed output may be too small to be useful. There are three ways to increase the size of the printout, all in TinyTERM’s Printer Setup options:

1) Select the “Direct to device” option. This bypasses the Windows printing system entirely, sending the output straight to an LPT or COM port. You may need to check the “Add Form Feed (FF)” box as well, depending on your printer.

This option will often fail on Windows 2000 or XP, as they handle the printer and serial ports differently. Also, most USB printers require a printer driver, so this option will fail with those as well.

2) Check the “Use Printer Fonts” box in TinyTERM 4.13, or the “Bypass Printer Drivers” box in TinyTERM 4.20 and higher. This still uses the Windows printer system to manage the printout, but doesn’t use the driver itself. This works on all versions of Windows, but still fails with most USB printers due to eliminating the required driver.

3) Click the Setup button for the selected printer. This brings up the Page Setup dialog box. In the upper left are “Lines” and “Columns” boxes, both set to 0. This allows Windows and the printer to configure the print size.

A typical page is 66 lines long and 80 columns wide. Set the Lines and Columns accordingly here, and print a test page. If it’s still too small, decrease the number of columns and lines in Page Setup. If the printout comes out too large, increase one or the other. Experiment with the numbers until you find one that works in your environment.

Any version of TinyTERM or TERM for Windows can use a USB printer, provided the driver is installed in and recognized by Windows. The specifics depend on which version of TinyTERM you have.

TinyTERM 3.x and earlier, also
Any version of TERM for Windows
The USB printer must be the Windows default printer. Set TinyTERM to use PRINTMNGR as its printing device. TinyTERM will then send all printer output to that printer.

TinyTERM 4.00 – 4.12
Select the “To Windows Printer” option in TinyTERM’s Printer Setup dialog. Then click the Setup button to choose the USB printer.

TinyTERM 4.13 and newer
Select the “To Windows Printer” option in TinyTERM’s Printer Setup dialog. Use the drop-down list to select the desired printer. Do not set the “Use printer fonts” or “Bypass printer driver” option.

Unlike parallel printers, there is no hardware port associated with a USB printer. So almost all USB printers require a printer driver to function in Windows. Bypassing the printer driver will usually cause all print jobs to be lost if that option is set.

CR 249

This error happens when using the Century FTP Client that came with TinyTERM Plus versions 4.11 and earlier over a VPN. It’s fixed with the patch available here.

To use the patch, locate the existing ftpslave.exe file on your PC. Rename it as a backup, then copy this file into the same directory. The next time you start the Century FTP Client, the patch will be in effect.

This patch does not work with SecureFT.

CR 100, fixed in TinyTERM Plus 4.12 .

This error means that the host TinyTERM or TERM contacted rejected the connection. There are several possible reasons this can happen:

1. The host isn’t configured for the connection type you used. Make sure that you used the right connection type — telnet, rlogin or SSH. Also check the host to be sure the right server application is running.
2. The default port for the connection type isn’t what the host is using. The default ports by connection type are:
   

   telnet: 23
   rlogin: 513
   SSH: 22

   If the host is configured to use a different port, change that in TERM or TinyTERM.

3. TinyTERM connected to the wrong host. There are a few possible reasons for this:
   1. Check the hostname or IP address. If the address is wrong or has a typo, make the necessary change.
   2. If the address is correct, you can test a telnet connection in Windows or UNIX. (There is no equivalent test available in Windows for rlogin or SSH connections.) Go to a command prompt. At the prompt, type:
      

      telnet hostname

      Replace “hostname” above with the correct hostname or IP address. If that also fails to connect, check the TCP/IP settings on your PC and correct them where needed.

   3. If the address and TCP/IP settings are correct, change the address TinyTERM is using. TinyTERM references hostnames and IP addresses in a different manner. So if you have an IP address in TinyTERM, try a hostname instead. If using a hostname, try the host’s IP address.If the server has no hostname assigned, edit the system’s hosts file to create a name. Instructions for doing that in Windows are available here.
4. A firewall is blocking the connection. Check the firewall settings on your desktop system first. Windows XP and Vista include firewalls. There are also third-party products such as Norton Personal Firewall. Make sure TERM or TinyTERM is in the exceptions list for each firewall installed.

Click here to watch a screencast about this and other network connection errors.

Windows 3.1

There is one special case in Windows 3.1. If you are using Novell Client32 TCP stack, TinyTERM will give this error. The 32-bit stack does not work with Windows 3.1-compatible versions of TinyTERM.

This error means the IP address of the server you are attempting to connect to is unreachable from your computer. It’s almost always due to incorrect network settings on the PC. To check your network settings, do the following:

Windows 95, Windows 98, Windows Me

1. Click Start->Run
2. Type “winipcfg” in the Open: box and then click OK

Windows NT, Windows 2000, Windows XP

1. Click Start->Programs->Accessories->Command Prompt
2. At the prompt, type “ipconfig” and press Enter

Verify that these settings are correct. If they are incorrect, contact your network administrator for assistance in properly configuring your computer.

If these settings are correct, then it is possible that your server may be down, or you may be experiencing some other problem with your network. You should contact your network administrator for assistance in this situation also.

Click here to watch a screencast about this and other network connection errors.

This error indicates that a timeout occurred before a connection could be made. There are several different situations in which this error can occur.

First, you will need to verify that you have entered the correct IP address or hostname into TinyTERM.

Once you have verified that, you will need to test the network connectivity between your PC and the server. You can do this by using the Windows utilities ping and telnet. Both utilities use the Windows command prompt.

To open a command prompt, go to Start | Programs | Accessories. The prompt will be listed as either “Command Prompt” or “MS-DOS Prompt.”

Once you have the command prompt, ping your server. At the prompt type:

ping address

replacing “address” with the hostname or IP address of the system you’re connecting to; for example, “ping 192.168.0.1”.

If you receive multiple timeout messages, this means that your PC cannot locate the server. Contact your system administrator for help with the network setup.

If your server replies, test the connection with Windows telnet. At the prompt type “telnet address” and hit Enter; for example, “telnet 192.168.0.1”.

If you receive an error message that reads “Connection Failed”, this means the Windows telnet program is experiencing the same problem as TinyTERM. This also indicates that the problem is not related to the TinyTERM software, but rather to a connectivity problem with either the PC or the server. You will need to contact your network administrator for assistance.

If telnet connects successfully, this error may be due to the way TinyTERM handles IP addresses and hostnames. In many cases, using a hostname in place of an IP address or vice versa will get TinyTERM to connect. Check with your system administrator to get the hostname or IP address for the server, whichever you’re not currently using in TinyTERM.

If there is no hostname assigned to the server, you can edit your PC’s hosts file to give it one. Instructions for this are available here.

Click here to watch a screencast about this and other network connection errors.

Windows 95

There is one special case regarding Windows 95 and Internet Explorer 3.0. If you configure and used IE’s email, TinyTERM will give the 10060 error. To resolve this, you can either delete IE’s email, or you can upgrade to Internet Explorer 4.01 or higher.

CR 607

For versions of TinyTERM for Windows that don’t have an uninstall option, or for those that will not uninstall properly, you can remove them manually with these steps:

1. Open Windows Explorer or My Computer.
2. Delete any Century or TinyTERM folder; e.g., C:\Century.
3. Go into the Windows folder, C:\Windows or C:\Winnt.
4. Delete any files named “marathon” or “marnfs” with any extension. Close the window when done.
5. Right-click on the Start button and select Open.
6. Browse the Programs group and remove any “Century Software” or “TinyTERM” items. Close the window when done.
7. If using TinyTERM Plus, Plus[NFS] or TERM Professional, right-click the “Network Neighborhood” icon and choose Properties. Remove “Century NFS” and “Century Internet Services” if there. (They may also be listed as Marathon instead of Century.) Do not reboot when asked.
8. Click on Start | Run and enter regedit, then click OK.
9. Double-click HKEY_CURRENT_USER, then double-click Software under that.
10. Delete any “Century Software” or “NCD Software” items there.
11. Also in the registry, go to HKEY_LOCAL_MACHINE\Software and delete any Century Software or NCD Software items there, then close the Registry Editor.
12. Close all windows and reboot the PC to finalize the uninstall.

To uninstall TERM or TinyTERM for DOS, just remove the directory it’s installed in. Then edit the AUTOEXEC.BAT file to remove the directory from the PATH variable.

To uninstall TERM for UNIX/Linux, remove the /usr/term directory. Then delete these three files from the /usr/bin directory: term, callin and callout.

If you installed TERM for Linux with a package manager such as rpm, uninstall it with the same utility. Refer to the utility’s man pages for specifics.

Older versions of TinyTERM cause some applications to report a general protection fault in GDI.EXE. This is caused by the presence of the TERM fonts. To get rid of the error, delete all term*.fon files.

This will cause TinyTERM display problem, since its fonts are gone. Add a new font to TinyTERM to fix the problem. Monospaced fonts such as Courier New or Lucida Console are best.

On the other hand, if TinyTERM itself is giving the GPF error, the problem is one of two possibilities:

1. Duplicate TERM fonts. Check your Windows fonts directory. You’ll have several term*.fon files; i.e., term480.fon, term768.fon, etc. Delete all of those except the one with the highest number. The next time you start TinyTERM, the GPF should be gone.
2. Hardware acceleration. TinyTERM versions 3.0 and earlier don’t always handle fast graphics cards well under Windows 95. In Control Panel, go into the Performance applet and lower the speed of your hardware acceleration to bypass the error.

CR 118

Support for TinyTERM versions prior to 4.0 (October 1998 release) ended in July 1999. This includes all versions of TERM For Windows. Support for TinyTERM versions prior to 4.30 ended in March 2007. The only support remaining for those products is here on our website So if you have questions about our older versions, watch this forum for answers.

This also effectively means the end of support for Windows 95 as a platform for TinyTERM. Version 4.30 requires Windows 98 or higher, and versions from 4.40 on require at least Windows 98se.

TERM for DOS and TERM for UNIX/Linux are not affected by this. We will continue to support those products in the appropriate environments.

If TinyTERM doesn’t open when you try to start it, but just puts a button on the Windows taskbar, it means the window position information has gotten corrupted. To fix that, right-click the button and select Maximize from the pop-up menu. TinyTERM will open full screen. From the File menu, select Save Session. This will usually fix the problem.

If it does not, you’ll need to edit the configuration file you’re using. Close TinyTERM and edit the .tpx file being used in Notepad. Search for the following two lines, which will be one right after the other:

xwindow=
ywindow=

They’ll both be set to very high numbers, or they’ll be negative numbers. Change each to 100:

xwindow=100
ywindow=100

Save the changes and close Notepad. The next time you start TinyTERM, it will open in a normal window. It may be too small, so resize it if you need to. Then save the session to make the changes permanent.

If your version of TinyTERM is old enough to use a configuration file with the .tap extension, the correct line to adjust in that file is:

window=

Change the first four numbers in that line     they’re separated by commas     to 100. The next time you start TinyTERM, resize the window to your needs.

Watch a screencast demonstrating this process.