Multifunction printers generally install two printer drivers: one for the printer itself, and one for the fax capability. Often these two names are identical, except the word “Fax” is appended to one. For example, these two printers might appear in your Windows printer list:

Lexmark X5070
Lexmark X5070 Fax

The near-identical names can cause problems selecting the correct printer. The solution is to make the names less identical. Renaming the fax driver by moving the word “Fax” to the beginning of the name will take care of the problem. In the above example, you would then have these two printers:

Lexmark X5070
Fax Lexmark X5070

Please note also that any multifunction printer is likely to be a USB printer. More information on using USB printers with TinyTERM is in this knowledge base entry.

(Century Software, Inc., does not endorse particular printer brands or models, nor do we manufacture or sell printers. The use of Lexmark above is intended as an example only. No trademark infringement is intended.)

Configure TinyTERM’s transparent printing option to spool the print job. Whether set to Print on Key Press or Print on Timeout, a printout that takes a long time to generate will put extra form feeds into the print job. This happens regardless of the timeout value as well.

TinyTERM works as designed in this instance. Applications that take an arbitrarily high amount of time to generate a printout will have natural breaks in the data flow. If the break is long enough, which depends on the timeout value set or the time before key press, TinyTERM will release the print job as it should. The workaround is to print on timeout, with a timeout value equal to or greater than the job creation time. This is typically 60 seconds or more.

CR 855

The Century LPD Server does not automatically start on Windows Vista. There’s a runtime error, then the status monitor CenLPDstatus.exe closes.

This is due to security settings in Windows Vista. To bypass the problem, run CenLPDstatus.exe as an administrator:

1. Click on the Start button and select All Programs, then Startup.
2. Right-click on Cenlpdstatus.exe.
3. Select Properties from the pop-up menu.
4. Go to the Compatibility tab.
5. Check the box labeled, “Run this program as an administrator.”

The next time CenLPDstatus.exe tries to load, you will see an “Allow/Deny” message window. Allow the program to run. It can then be configured normally.

CR 847

The Wollongong TCP/IP stack included with TinyTERM Plus NFS for DOS includes an NFS client that allows a DOS PC to use UNIX printers. To print using NFS, Wollongong TCP/IP must be running. It then requires the following steps:

1. At the DOS prompt type NFS, then press Enter. If NFS has been installed correctly, the following screen will be displayed:
   

   Century Client NFS for DOS (Version 2.0)
   Copyright (C) 1990,1993 The Wollongong Group.

   If the above lines are not displayed or an error message is received, check the NFS installation guide and try again.

2. The host system must be running version 2 of the pcnfsd daemon. To confirm this, log into the host and run the following command:
   

   rpcinfo -p

   This program can usually be found in the /usr/etc directory. If you can not run this program, you may not have permissions. Talk to your system administrator to use this program. Assuming you can run the above command, you will see a screen similar to the following:

   program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
150001 1 udp 1028 pcnfsd
150001 2 udp 1028 pcnfsd
150001 1 tcp 1024 pcnfsd
150001 2 tcp 1024 pcnfsd
100003 2 udp 2049 nfs
100005 1 udp 1027 mountd
100024 1 udp 1042 status
100024 1 tcp 1025 status
100020 1 udp 1050 llockmgr
100020 1 tcp 1026 llockmgr
100021 2 tcp 1028 nlockmgr
100017 1 tcp 1027 rexd
100021 1 tcp 1029 nlockmgr
100021 1 udp 1062 nlockmgr


   Under the program column you will be looking for the number 150001. Under the vers column you will need the number 2. You must have pcnfsd version 2 in order for the NFS services to work. Versions 1 and 2 can run in conjunction. If you only have version 1 running, you will have to upgrade to version 2 on your host.

3. Determine which hosts on your network are running NFS services. To do this, type the following:
   

   mount /n

   This command may take a few seconds to process, depending on the number of servers available and the current network traffic. It will return a screen similar to the following:

   NFS SERVERS
(192.168.0.25) century
(192.168.0.13) sconfs
(192.168.0.12) scoodt
(192.168.0.10) rs6000
4 servers available on your subnet.

   If no servers are available, talk with your network administrator.

4. Next you will need to see which servers, if any, have print services available. To do this, use the /l option along with the hostname in question. For example:
   

   mount /l century

   A screen similar to the following will be displayed:

   NAME DEVICE LOCATION
---------- ------------ ---------------
sunprint Local
epson1 /dev/lp0 Local

   Note that the sunprint line above doesn’t show a device. On some systems this is normal.

5. You are now ready to mount an NFS printer. In the example above, you might enter the following at the DOS prompt:
   

   mount lpt1 century:/sunprint user passwd

   In the above example the host is century, the printer is sunprint device, the username is user, and the password is passwd. If auth had been run, it would not be necessary to add the username or password, although doing so would not cause any problems.

   If all went well, you will see a line similar to the following:

   Device lpt1 redirected to \century\/sunprint successfully

Troubleshooting Tips
If you get “permission denied” or “invalid path” when mounting the printer:

1. Using the rpcinfo command outlined above, verify that pcnfsd version 2 is up and running on the NFS server.
2. Verify that the spool directory has been exported by looking for /usr/spool/pcnfs (or higher) in the /etc/exports file.
3. From the DOS prompt, type mount /e servername. You should see /usr/spool or higher directory exported.
4. Verify that you can mount /usr/spool and that you have permissions of 777 by copying a file to /usr/spool. On some systems the directory will be /var/spool instead.
5. From the DOS prompt execute PWSETUP and select View Current Settings. Make a note of the PC’s IP address, the user id and hostname of the PC. On the server, verify that the PC’s hostname is in the /etc/hosts file.
6. Finally, if you have any logical links to /usr/spool, verify that the linked file as well as /usr/spool is also exported.

Installing LPD in Windows 95
In Windows 95, LPD is not automatically installed. To install the LPD server, follow these instructions:

1. From Control Panel, select the Network icon.
2. From the Network dialog box, click the Add button and select Service, then click Add again.
3. Click the Have Disk button and specify the directory TinyTERM was installed into (C:\Century by default), then click OK.
4. Select Century Network Services and click OK. The Windows 95 Network dialog box will then be displayed. Click OK and reboot the system.
5. Go to Control Panel and select Network. From the Network dialog box, select Century Network Services, then click the Properties button. Select printer under “Service Name,” then select Enable.
6. Make sure printer is still highlighted and click the Configure button. Click New to enter a printer name, then click OK. The printer name should be no more than 14 characters long, and should only use letters and numbers, no spaces or punctuation.
7. From the Century LPD Server Properties dialog box, highlight the new printer and select Connect. Associate the new printer with an existing Windows printer and click OK, then Apply.
8. Check the spooling directory setup. Select the Services tab, highlight the desired printer, then click the Configure tab. Select Spooling. Verify the correct spool directory is selected for the printer. To use the path specified by the Windows TEMP environment variable, check Use local machine TEMP directory. To spool print jobs to a specific directory, uncheck Use local machine TEMP directory and enter the directory path in the Path box. Remember to put a trailing backslash on the path; e.g., C:\LPD\.
9. Select the Access Rights tab and click Add. Select Any Host or specify a hostname or IP address. Click OK, then Apply. Continue clicking OK until the Networks dialog box closes. Reboot the PC.
10. Windows 95 should now display a hammer-and-wrench icon in the system tray. If it does not, add C:\Century\marlpd32.exe to the StartUp folder on the Start menu and reboot the system.

Installing LPD in Windows 3.1 and Windows for Workgroups
In Windows 3.1 and Windows for Workgroups, the Network Shared Services application provides an LPD server. To define an LPD printer, open Network Shared Services and follow these steps:

1. Select Configure Servers. A list of managed services displays.
2. Double-click printer. The Configuration window comes up.
3. Select Printer Connections.
4. Click New. The Specify Printer Name dialog appears.
5. Enter a printer name. The printer name should be no more than 14 characters long, and should only use letters and numbers, no spaces or punctuation.
6. Click OK. The new printer is added to the Printer Name listbox.
7. Select the new printer name from the Printer Name listbox.
8. Click Connect. The Specify Network Printer Connection dialog opens.
9. Select the printer you want from the list of local printers and click OK. The printer you selected now appears in brackets next to the printer name.
10. Click OK to accept the changes.

Installing LPR in Windows 95
In order for LPR to work, a printer port must be created and associated with a printer driver. There are two ways to create a printer port and associate it with a printer driver:

1. Through the Network Printing application
   1. Open the Network Printing icon in the Century program group.
   2. From the File menu select New Port. Enter a port name or select one from the list box. For example:
      

      pcsupport!testprint

      where “pcsupport” is the hostname of the computer running LPD, and “testprint” is the LPD printer name.

   3. Open Control Panel and double-click Printers.
   4. Select an installed printer, then go to the File menu and select Properties.
   5. Select the Details tab, then choose the LPD port from the Print to the following port menu and click OK.
2. Through Control Panel
   1. Open Control Panel and double-click Printers.
   2. Select an installed printer, then from the File menu select Properties.
   3. Select the Details tab and click on Add Port.
   4. Select Other, then Marathon Port Monitor.
   5. Enter the port name; e.g, pcsupport!testprint, or select one from the listbox.

Installing LPR in Windows 3.1 and Windows for Workgroups

1. Double-click the LPR icon in the Century program group.
2. From the File menu, select New Printer. The Define Network Printer dialog opens.
3. Enter the Remote machine name and Remote printer name for the printer you want to use, then click OK.
4. A new printer icon with the names you assigned appears in the Printers icon bar. Click that icon to highlight it.
5. From the Configure menu, select Misc.
6. Set the Directory for spooled files. Make note of the port specification listed below it after this is set.
7. Click Control Panel. The Control Panel Printers dialog opens.
8. Highlight a printer and click Connect.
9. Scroll down through the Ports window until you find the correct LPR port. Highlight it and click OK.
10. Click Close in the Printers dialog.

Please be aware that if you use THIRDNET.EXE, you will be unable to access remote LPR printers via Windows Print Manager. You will still be able to access them via Century Network Printing.

Usage Tips

• If DNS is not enabled on the network, make sure there are hosts files on both client and server sides, and that you can ping the hostnames.
• On Windows 3.1 or Windows for Workgroups, make sure the services file is in the C:\Century\etc directory on both client and server, if both are running Windows. If Network Shared Services shows all zeros in the port column, the services file is not present.
• Also on Windows 3.1 or Windows for Workgroups, LPD must be running at all times. You may wish to place a copy of the Network Shared Services icon in your StartUp group.

Message Explanations

• Host is refusing status check
  Check for services file and access rights in LPD server. Verify that remote printing is enabled on the LPD side.
• Host connection is down
  Check for services files. Verify that the host name is resolved to the correct address. Make sure LPD is up and running.
• Cannot Print
  Check for services files, printer connection and check for spooler directory.

Updating Century LPD in Windows 95
If you are installing an updated version of Century Network Services in Windows 95, we recommend these steps:

1. Open Control Panel | Network and remove Century Network Services.
2. Next, delete the following files from your C:\Windows\System directory: MAR_INET.EXE, MARLOG32.DLL, MARMON32.DLL and NCDMFCX.DLL. You may need to restart in DOS mode and delete these files manually.
3. Install the new version. Once the system has restarted, check the C:\Windows\System directory and see if the above four files are there, and make sure they’re all dated 6/19/1996. If necessary, copy them manually from the C:\Century directory.
4. Return to “Installing LPD in Windows 95” in this document.

Transparent printing is also known as slave printing, remote printing, local printing, pass-through printing or terminal printing. The following table lists the escape sequences needed to have transparent printing work. In all cases, \033 indicates the escape character, ASCII value 27.

¹The actual SCO console does not support transparent printing. However, the SCOANSI console emulation in TERM and TinyTERM has been designed with transparent print capabilities.

²The sequence used to turn transparent print on for Wyse50 (^X) is the same sequence that is used to end the file transfer for ZMODEM and WTERMCRC. To have TinyTERM or TERM accept the sequence as “transparent print on” in this emulation, change the file transfer protocol to something else, such as XMODEM.

The :PN= and :PS= entries for the emulation must be defined in the /etc/termcap file.

Example for Wyse 50: :PN=^x:PS=^t:
Example for VT100: :PN=\E[5i:PS=\E[4i:

To test transparent printing, you can do the following:

1. Create the following short UNIX/XENIX script file and name it tprint:
   

   # Test for transparent print in vt100 mode. \033 is esc.
echo "\033[5i"
cat $1
echo "\033[4i"

   Change the echo commands to match your emulation’s transparent print codes.

2. Set the permissions on the tprint file to read/write/execute:

chmod 755 tprint

3. To print a text file enter “tprint filename” at a shell prompt, replacing “filename” with the name of any text file; e.g., /etc/hosts.

For more information on transparent printing and other print options, please see this screencast. 

Things to check if this fails:

• The UNIX “TERM” environment variable doesn’t agree with TERM’s emulation.
• The proper escape sequences are not in your /etc/termcap file.
• TERM has been set to send all printer output to a disk file instead of the printer.

Transparent Print Issues

Why are the lines for boxes being replaced with characters?
The font set that the printer uses does not support those characters. Most printer have the capability of switching the font sets. The font set that TERM and TinyTERM uses is 437 MS-DOS Latin US. Many printers are setup by default to use 1252 Windows Latin US (ANSI), which does not have the line draw characters.

The printer is not capturing the LPT1 or LPT2 device in Windows 95
In the Configure menu item Printer Setup set the Device line to DEVICE, and in the Device Name field enter the port name of the printer.

With a serial connection to the server, transparent printing prints garbage or stops printing
Change the flow control to XON/XOFF. To change the flow control with TERM go to the Configure menu and select Communication. In TinyTERM, change the protocol=none line in the .tap file to protocol=xon.

Selecting Print Screen from TinyTERM’s File menu on Windows XP causes the error, “CSL Run Engine ActiveX Doc Object Server has encountered a problem and needs to close.” The customer who reported this can transparent print once, but after that transparent printing gives the same error.

Changing the printer did not help, nor did upgrading TinyTERM. This could only be duplicated on the original PC, no other on the customer’s network. Century Software, Inc., has also been unable to duplicate this.

CR 841

Configure a Century LPD printer to print to the Adobe Acrobat PDF print driver. LPD jobs sent to that printer disappear. There are no errors or other indications Acrobat saw the request.

CR 830

Configure TinyTERM to print to a Windows printer, with Bypass Printer Drivers and Spool Print Jobs set. Send a transparent print job that includes form feed characters (^L, ASCII value 12). They may be ignored, depending on the print job.

CR 823, fixed in TinyTERM 4.53 (May 2007)
CR 831, A4 overlap fixed in TinyTERM 4.53 (May 2007)

Configure a Century LPD printer on Windows XP. Send a print job to it. The job files  are created and stored in the specified spool directory on the PC. But they stay there, never actually going to the printer. This only happens on Windows XP, though not in every case.

CR 821