Print jobs from the server may print one line, feed a page, then print the next line, and so on. This usually happens when the host application turns transparent printing on at the beginning of each line, then off at the end. TinyTERM versions 4.00 and higher include a workaround to stop this problem.

TinyTERM 4.00-4.12
In TinyTERM’s Printer Setup, check the Manually stop print jobs box. This will make the Stop on key press box available. Check it, too. The next time you print, TinyTERM will hold the print job in memory until you press a key. Then the print job will go to the printer with the correct pagination.

TinyTERM 4.13 and higher
In TinyTERM’s Printer Setup, check the Spool print jobs box. This will make two options available: Print on key press and Print on timeout. Print on key press works the same way Stop on key press does in earlier versions of TinyTERM.

Print on timeout (not available in TinyTERM 4.13) includes a timeout setting, which defaults to five seconds. If you have this option selected, TinyTERM will hold the job until the specified number of seconds go by with no new print data. Then it will release the job all at once. You can adjust the timeout based on how the print job behaves.

CR 21, spool option
CR 145, spool timeout

Thank you for coming to our Knowledge Base page. Here we provide support for older products, those we don’t officially support through telephone or email. You’ll also find support here for our newest products as well.

The Knowledge Base is set up in blog format. You can use the Search box to enter a specific term, or click a category in the list on the left to see all topics in that area.

If you can’t find what you’re looking for, please post your question as a comment in a similar topic. (You will need to register to post comments.) A support representative will answer in the comments within one business day.

That error means the TinyTERM license has already been entered into your PC’s registry. But if TinyTERM won’t start, there’s an error reading it back out.

The first thing to check is the license it’s reading. Right-click the shortcut you use to start TinyTERM. Select Properties from the pop-up menu.

On the Shortcut tab of the Properties, check the Target line. It will read something like this:

“C:\Program Files\Century\TinyTERM\tt.exe” -P52 default

The -P52 argument needs to match the first three characters of your serial number. For example, if you licensed TinyTERM with the serial number E43219876EM, you should have -E43 there.

If that argument does match, you’ll need to remove the TinyTERM license, then add it again through License Manager. If you are using Windows NT, 2000, XP or Vista, you’ll need to login as a local PC administrator first.

1. Click on Start | Run.
2. In the Run dialog, type:
   

   regedit

   then click OK. The Registry Editor will open.

3. In the Registry Editor, go to HKEY_LOCAL_MACHINE\Software\Century Software.
4. You’ll see a License1 key. You may also see License2, License3, etc., up to a maximum License9. Delete all License# keys one at a time, but don’t delete anything else.
5. When all the License# keys have been deleted, close the Registry Editor.
6. Run TinyTERM’s License Manager to re-enter your serial number and activation key.

If you go through these steps, you may still see the message, “This product is not licensed.” However, License Manager may then say the license has already been used. There are two possible reasons for this.

• You have more than one copy of the license file CenLic32.dll on the PC. Search the C: drive for that file name. For each copy that comes up, right-click on it and select Properties. Check the version number. If it does not match the version of TinyTERM you have installed, delete it. When all incorrect versions of the file are gone, the error will be as well.
• You are running Windows NT, 2000 or XP with a language requiring Unicode installed. This includes languages such as Chinese, Japanese and Korean, but other languages can cause this as well. This will not happen in TinyTERM version 4.33 or higher. The license code was rewritten in those versions to support Unicode.

For TinyTERM version 4.30 or 4.31, there is a patch. To use it, locate the existing CenLic32.dll file and rename it as a backup. Copy the patch into C:\Windows\System32 and rename it CenLic32.dll. Then go through steps 1-6 above.

There is no patch or other solution for versions prior to 4.30. A newer version of TinyTERM is required.

CR 142, Unicode licensing
CR 288, This serial number and activation key have already been used

When installing or running TinyTERM version 4.00-4.03, you may get one of several errors. They are particularly likely when you install TinyTERM over a previous install, rather than uninstalling first:

• Files failed to self-register
• License.exe is linked to missing export mfc42.dll
• Replace DCOM95.exe
• ATL.DLL or CENCOM.DLL install failure
• CLSID_tConnectionManager errors
• Get Property ‘CaptureOn’ failed: Invalid object instance

There are patches to deal with this problem, one for each version of TinyTERM. Click on the appropriate patch to download it:

rep400.exe
rep401.exe
rep402.exe
rep403.exe

The patches are documented in this Windows WordPad document.

Some FTP servers will show an empty directory in the Century FTP Client or SecureFT. This happens when the server uses a different directory item structure than the client’s default. The following steps will change the default in the Century FTP Client:

1. Open the Century FTP Client. It displays the configuration dialog automatically.
2. Click the View/Sort tab.
3. Set the Directory Item Structure value by clicking the Set Default button.
4. Edit the Directory Item Structure value for the required format.

The steps for SecureFT are (also available as a screencast):

1. Go to the Edit menu and select Setup.
2. Click the Directory Structure tab.
3. Click the item under Active Items you want to change.
4. Click the Push button to move it to the Inactive Items. Or use the up and down arrows on the left to change the item’s position in the list.

The required format may be found by connecting to the FTP server using a command-line client, such as the one included in Windows. After connecting, type “dir” at the prompt for a directory item listing. The default format used by the graphical FTP client is:

-rwxrw-rw- 1 owner group 32 May 19 21:35 file.txt

This corresponds to Directory Item Structure:

ATTRIBUTE UNKNOWN USER GROUP SIZE MON DATE TIME FILENAME

Compare the listing on the FTP server with the listing above and change the order as needed, removing any directory items not displayed. The most common change needed is to remove the GROUP item.

In some cases, especially when you’re not using the default TERM font in TinyTERM, lines that should be drawn are odd characters instead. To change this in TinyTERM 4.x, open TinyTERM’s Session Properties and go to the Attributes tab. Check the box labeled Use Non-Font Based line draw characters. This will use graphics instead of text to draw the lines.

Please note that the color of the lines will not automatically match the text in the emulator window. The line color cannot be changed, either.

If that does not resolve the problem, your host application may be using an alternate method of drawing lines. The control characters ^N and ^O should put most terminals into graphical mode, but they are ignored by TinyTERM. This was fixed in TinyTERM version 4.65.4732.

CR 404

TinyTERM 3.2 and older versions have a “network install” option, which allows a set number of concurrent users to run it at the same time. If it’s not allowing the correct number of users, the license control file may be corrupt.

Search the TinyTERM install directory for the file tt.ser or term.ser. Rename that file as a backup, then replace it with the blank file you can download here. Rename the file to term.ser if needed.

This error means TinyTERM version 3.3 can’t locate its internal procedure for dialing a modem. It most often happens due to an inability to recognize long directory names, especially with spaces. So when it’s installed as a subdirectory of C:\Program Files, this can happen.

The error can also occur when the file WTERMUS.CMD, which contains the w_dialer_dial procedure, has gotten damaged or partially corrupted. In either case, the fix is the same.

Uninstall TinyTERM using the manual uninstall instructions. Reboot the PC, then reinstall TinyTERM. When it asks for a directory path, specify a DOS-style path, rather than a long one; e.g., C:\Century.

If you still get the error after installing, edit the WTERMUS.CMD file in the same manner described under the Incompatible TAPI Version item.

Accessing or saving files on a network drive may generate this error. It means that the NFS client driver is installed, but not licensed.

To get rid of the error, uninstall TinyTERM. Reboot the PC, then look for one or more of these files:

cennfs.sys
marnfs.sys
mar_nfs.386

They should have been removed by the uninstall. If any are left behind, delete all copies found, then reboot the PC again.

After you reboot the PC, you should not see the error any more. You can now reinstall TinyTERM. Make sure you do not install the NFS component as part of that.

CR 362

This error comes from using an older version of TinyTERM on Windows Me, 2000, XP or Vista. Windows TAPI changed considerably in those operating systems, so older versions of TinyTERM won’t understand it. The best solution is to upgrade. Or you can dial the modem manually.

You can configure TinyTERM Application Developer 3.3 to dial the modem. To do that, locate the file wtermus.cmd and open it in a text editor such as WordPad. Search it for the line:

setvar t_tapi true

For every instance of that line, change “true” to “false”. Save the changes, and TinyTERM will use its internal dialer instead of TAPI. This workaround is only available on TinyTERM Application Developer 3.3.