TERM for UnixWare installes from the /termunix/u3 directory on the TinyTERM/TERM CD. As it installs, it asks which UNIX you are installing to. Choose INTERACTIVE.

In order for TERM to use a serial port, the port must be set up for bidirectional access. (More information on this is in the Setup and Configuration of the UnixWare manual.) The script below should work:

pmadm -r -p ttymon3 -s 01d
pmadm -a -p ttymon3 -s 01d -s login -fu -v `ttyadm -V` -m "`ttyadm -b -h -r0 -t 60 -d /dev/term/-1s -1 9600NP -s /usr/bin/shserv -m ldterm -p "tty01 login: "`"

Change the lockfile format within the TERM setup under communications to:

/var/spool/locks/LK.%m

You must now connect to /dev/ttyxxx, not /dev/term/ttyxxx.

The NFS Server may be set up for individual users or groups and may be used to set up directories to be exported, including permissions for files included. The server itself must be set up, as well as the users and groups for the server. Detailed explanations follow for each item on the NFS Server main screen.

Getting Started
To initiate NFS Server, select the Network Shared Files icon from the Century program group. The following steps are required for initial setup of the NFS Server. Detailed explanations for each of the options are in the “Guided Tour” section of this document:

1. Set up the Log File that will record NFS Server events. This includes startups and transfers. From the NFS Server main screen, go to the Options menu and select Log File Setup.
2. The server itself may be customized for various options. These options include turning the server on, starting the server minimized, packet size of transfers, whether or not the files will be transferred in UNIX format and whether or not the server will act as an authenticator for the network.
3. The group(s) that will be allowed access to the NFS Server must then be set up. When users are set up, the group the user belongs to must be entered as a valid NFS Server group. The user as well as the group the user belongs to will determine permission rights to files exported using the NFS Server. From the Options menu, select Setup Groups.
4. Set up the individual users that will have access to the NFS Server. From the Options menu, select User.
5. The directories to be exported must then be entered. These directories may be changed as often as necessary. In addition, user permissions for the directories may be changed as necessary. From the Options menu, select Setup Exports.

Guided Tour
After initializing NFS Server, the following selections are available:

• Log to File
• Log File Setup
• Setup Server
• Setup Users
• Setup Groups
• Setup Exports

Log to File
This item works as an on switch for the Log File. If a check is placed on this item, events occurring on the NFS Server will be recorded in the Log File. Without a check mark, events will not be recorded. To have the ability to change this option, the Log File must be set up first.

Log File Setup
This option sets up the file where events in the NFS Server are logged. After selecting this option, enter the desired directory and file. If the name of the file or the path name is not known, click Files. You can then browse for the file.

Usually a .tmp (temporary) file is used for log files. This file will need to be maintained by manually clearing the entries to the file.

Events logged to this file include such items as file transfers, startups of the server, daemon functions and other NFS functions. The history may then be reviewed as required.

Setup Server
Changes may be made to server operation here. The following are detailed descriptions of each of the options available:

• Server On
  This checkbox will turn the server on and off. Click this box if the server should be initialized on startup.
• Start Minimized
  This option determines whether the server will be initialized as a full window display or if it will be minimized at startup. Place a check in this box if the server should be minimized at startup.
• Preferred Transfer Size
  The size of the read/write blocks may be changed as required. Select the desired size from the pull down list.
• Export Mounts in UNIX Style
  If the files exported from the erver should be formatted for UNIX, place a check in this box. When files are viewed in UNIX format, clients will see the exported directory as /c/tmp rather than C:\tmp, for example.
• PCNFS Daemon On
  Place a check in this box if the server should act as an authenticator for the network.
• Port Mapping Daemon On
  This checkbox must be selected as on if the Server On option is checked. This determines if the server is running on a port.

Setup Users
Users must be set up on the server to be allowed access. Select Options | Setup Users to display the Setup User dialog box:

• User Name
  Type the username that will be allowed access. To delete a user, click the Remove button after selecting the username.
• Password
  Type the password for the user. This will be required when the user is attempting to access the server.
• UID
  Type a User Identification (UID) number, or click Create Unique ID to have the UID created automatically. The UID will be used when transferring files to or from a UNIX machine. UNIX determines read, write and execute privileges from the UID. If the UID entered for the user does not allow privileges to the files specified to transfer, the transfer will not complete.
• Group
  Type the Group name or select the correct group for the user from the pull down list. The group the user is assigned to will be used in conjunction with the actual user name to determine read, write and execute privileges.
• Secondary Groups
  The user may be assigned to Secondary Groups to allow additional permissions for the individual. Implement Secondary Groups by clicking the Change button. Highlight the desired Secondary Group from the list displayed and click the Accept button.

Setup Groups
Groups must be set up prior to setting up users. The group name and group ID entered in this option will determine the privileges allowed to users assigned to the group. Select Options | Setup Groups:

• Group Name
  Type the group name to be added, changed or removed. If the group name entered should be removed, click on the Remove button.
• Group ID
  Type the Group ID for the name entered. The group ID entered will determine file privileges allowed to users assigned to this group. The group ID should be consistent with the group ID of files that will be transferred to or from the UNIX machine. If the group ID does not match the permissions set for the file(s) transferred, the transfer will not be completed.

Setup Exports
Entire directories or specific files within the directories may be specified for export. Select Options | Setup Exports:

• Directory/Files
  Type the full directory path to export or select the desired directory from the pull-down list.
• Owner
  Select the username from the pull-down list. The permissions for the user, the group the user has been assigned to, as well as the permissions for Other will be displayed. The permissions may be changed as necessary for the export.

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.

Plus[NFS] and Simply[NFS] include an NFS client capable of mounting any NFS server. It runs on both Windows 3.1 and Windows 95.

Windows 3.1 or Windows for Workgroups 3.11
To access the NFS capabilities from Windows 3.1 or Windows for Workgroups, run File Manager. From the Disk menu, select Network Connections and click the Browse button. You are then able to add an NFS server, after which the mountable directories will be displayed.

Multiple Networks with Windows 3.1 or Windows for Workgroups 3.11
Windows 3.1 allows only one network driver to run at a time. Windows for Workgroups allows only two. If you need to run a network s) such as Novell NetWare or Windows NetBEUI in addition to Century NFS, you must run the THIRDNET.EXE program found in the Century directory:

1. Make sure the other networks are set up and running correctly. Make a backup copy of the SYSTEM.INI file in your Windows directory.
2. Load Century NFS and allow the installer to replace the Network in Windows 3.1, or the Secondary Network in Windows for Workgroups.
3. Edit the SYSTEM.INI in a text editor such as Notepade. Replace the Network.drv= line with the driver indicated in the backup SYSTEM.INI. In Windows for Workgroups, replace the Secondnet.drv= with the indicated driver.
4. Create an icon for the application C:\CENTURY\THIRDNET.EXE and put it in the StartUp program group.
5. Restart Windows. The Century Thirdnet dialog will appear. Check the Show this message only once box and click OK. Double-click the Century Thirdnet icon and click Connect. Follow the prompts to connect to NFS drives. You will need to close and re-open File Manager before you can see newly mounted drives.

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.

Windows 95
In Windows 95, the NFS client is not automatically installed. To install the NFS client, install TERM Professional, Simply[NFS] or Plus[NFS]. Make sure you install the following components: “Century File Sharing (NFS),” “Terminal Emulator,” and “TCP/IP Network Applications.” After the machine reboots, follow these instructions:

1. From Control Panel, select the Network icon.
2. From the Network dialog, select the Add button, then click Client.
3. Select Century Software, Inc. from the Select Network Client list. Click the Have Disk button.
4. Specify the directory where Century software was installed, or click Browse to find the directory, then click OK. You will then be returned to the Windows 95 Network dialog.
5. Select Century NFS, Century Software, Inc. and click the Properties button. Type your username, password and PCNFSD host name in the indicated boxes. This step allows your PC to be recognized by NFS servers on your network.
6. Type the name of an NFS server in the New Server box and click Add Server. Click OK until you exit the Network dialog, then reboot the machine. You may be asked to insert Windows 95 disks during this process. The indicated files may already be installed, in the C:\Windows and C:\Windows\System directories, so it may not be necessary to use the Windows 95 disks.
7. Once the system has rebooted, open Network Neighborhood. Go to Entire Network and open NFS Servers. Select the NFS server to mount. Highlight the desired export directory. From the File menu, select Map Network Drive.

Message Explanations

Invalid PCNFSD Host
To resolve this problem, set the authentication server must be set to the server’s hostname, not its IP address. If there is no name server or DNS, create a hosts file in the windows directory.

Also, check that the PCNFSD Version 2 is running on the server.

Incorrect Function
This is usually an authentication issue. One or more of the following suggestions shouuld resolve this error:

• The user name and password in the Century NFS Client Properties must be a valid user name on the system that is to be mounted.
• If the user name is “root,” try a different user. Some PCNFSD daemons consider root permissions the same as “nobody”.
• If the PCNFSD authentication server is different than the server that is to be mounted, verify that the user id for the authentication user is the same on both servers.
• If the exports file on the server is listing only some nodes with permission to mount, verify that the PC is listed.
• If the user name and password is left blank in the Century NFS Client Properties, verify that the Primary Network Logon is set to Century NFS (Windows 95 only).
• Verify that PCNFSD Version 2 is running on the server with the udp protocol.
• Make sure the user is not cancelling the Windows login. If the user name and password are not entered when Windows is started, there will be an authentication problem. Windows has not been told who the user is or the password for the user.

Invalid Function
Make sure the user name and password are correct. If the name or password has been changed, Windows will need to be restarted.

Unable to see exported Directories/Drives
Use the hostname, not the IP address for the server in the NFS setup. Then verify the server name. Also, verify that the directories have been exported.

Also, check the hosts file to make sure that there are only entries for the IP address and the hostname. Any other alias, etc., should be removed from the file.

The Local Device type and Network resource type are not the same
Open Windows Explorer and double-click the NFS export. Do not attempt this in Network Neighborhood.

Updating Century NFS in Windows 95
If you are installing an updated version of Century NFS in Windows 95, we recommend that you follow these steps:

1. Go to Control Panel | Network and remove Century NFS.
2. 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 Windows in DOS mode and delete the files there.
3. Reboot the PC, then install the new version. Once the system has restarted after the install, check the C:\Windows\System directory. Verify 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 NFS in Windows 95” above.

Before using mscreen, FacetTerm or other multiple session software, you will need to know the following:

• Which terminal emulation will you be using?
• How many sessions will you need?

The rest of this document will address mscreen only.

Setup Procedures

1. Set the number of screen pages. In TERM or TinyTERM, this will be an option in your terminal emulation setup. For TinyTERM 4.x, go to the Edit menu and select Preferences.
2. Connect to the UNIX host as normal.
3. By default mscreen will check the file /etc/mscreencap for the terminal capabilities. If you are using a different file, set the MSCREENCAP environment variable to the file you will be using.
4. At a shell prompt, enter this command:
   

   mscreen -n 6

   The number can be less than 6, but it must not be less than the number of screen pages configured in step 1. TERM and TinyTERM support up to six screen pages.

   On some connections you will need to add the -t option to the above command line. This is particularly necessary for terminal devices that start with “ttyp”.

5. If all went well, you should see a screen similar to the following:
   

   mscreen rev VII
who is S-F7
help is S-F8
stop is S-F9
quit is S-F10
ttyp0 is S-F1
ttyp1 is S-F2
ttyp2 is S-F3
ttyp3 is S-F4
ttyp4 is S-F5
ttyp5 is S-F6

   The actual keys may be different, but some key assignment should be shown. You can then use the specified keys to switch between screens. Shift-F2 in the above example would take you to the second screen, ttyp1.

ANSI emulation may not have an entry in /etc/mscreencap. If this is the case, you can append the following entry to that file, or create a new file with the entry and set the MSCREENCAP environment variable to point to this file:

ansi|term63:\

:who,CSF7,\E[\:\
:help,CSF8,\E[],:\
:stop,CSF9,\E[\^,:\
:quit,CSF10,\E[_:\
:,CSF1,\E[w,\E[1z:\
:,CSF2,\E[x,\E[2z:\
:,CSF3,\E[y,\E[3z:\
:,CSF4,\E[z,\E[4z:\
:,CSF5,\E[@,\E[5z:\
:,CSF6,\E[[,\E[6z:

By default these entries will work if you are using the Ctrl+Shift key combinations. No other changes should be necessary.

If you wish to use the Alt key combinations for switching between sessions for exact console emulation, you will need to append the following entry to the /etc/mscreencap file instead:

ansi|term63:\

:who,A-F7,\E[7z,:\
:help,A-F8,\E[8z,:\
:stop,A-F9,\E[9z,:\
:quit,A-F10,\E[0z,:\
:,A-F1,\E[1z,\E[1z:\
:,A-F2,\E[2z,\E[2z:\
:,A-F3,\E[3z,\E[3z:\
:,A-F4,\E[4z,\E[4z:\
:,A-F5,\E[5z,\E[5z:\
:,A-F6,\E[6z,\E[6z:

You will also need to add the following lines to your TERM.RC or TT.RC file, or make the appropriate key mappings in other versions of TinyTERM:

setkey af1 "\e[1z"
setkey af2 "\e[2z"
setkey af3 "\e[3z"
setkey af4 "\e[4z"
setkey af5 "\e[5z"
setkey af6 "\e[6z"
setkey af7 "\e[7z"
setkey af8 "\e[8z"
setkey af9 "\e[9z"
setkey af10 "\e[0z"

If you experience problems with the ANSI entries working do one of the following:

1. Move the ANSI sequences to the beginning of the /etc/mscreencap file. There is a limitation on the size of the mscreencap file. Entries past this limit are simply ignored.
2. Set the MSCREENCAP environment variable to point to a file that only has the ANSI entries. For example:
   

   MSCREENCAP=/etc/mscreen.ans
export MSCREENCAP

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.

Emulation	On	Off
Adml	\033A	\033B
AT386	\033[5i	\033[4i
SCOANSI1	\033[5i	\033[4i
TVI925	\033`	\033a
VT52	\033W	\033X
VT100	\033[5i	\033[4i
VT220
VT320
Wyse502	^X	^T
Wyse60	\033d#	^T

¹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.

If your machine can’t read the media TERM came on, there are a few things to check:

1. Verify that the correct extraction command is being used. Double-check your release notes for that information.
2. Verify that the correct device name is being used for the media being read. If you are unsure of the device name and it is not listed in the “Installation and Set up of TERM” section in the manual, you can search for the correct device name by inserting the release media in the appropriate drive and typing the following at a system prompt:
   

   # for x `ls /dev/rfd”
   > do
   > echo “Device: $x ”
   > tar xvf $x
   > done
   #

   This will cause the tar command to be used on all the selected devices until the correct one is found. In order for this to work correctly, you must loop through the right files and directory. An example of some directory specifications are as follows:

   Interactive UNIX system V/386 : /dev/rdsk/* (disks)
   SCO XENIX/UNlX : /dev/rfd* (disks)
   Sun Microsystems : /dev/rst/* (cartridge tape)
   ICL DRS : /dev/rmt/* (cartridge tape)

   Century Software, Inc., has provided TERM for UNIX releases in the following formats:

   Tan 5.25 Diskette: 36OK
   Black 5.25 Diskette: 1.2M
   Black 3.5- Diskette: 720K
   Black 3.5- Diskette: 1.44M
   Cartridge Tape: Low density
   CD-ROM: ISO 9660

3. Remove the media, reinsert it and try again.
4. If the release has multiple diskettes, try executing the extraction command on each diskette received. If all diskettes fail, reboot the system and repeat steps 1 through 4. Occasionally, UNIX drives can get messed up and require rebooting to correct. If only one diskette fails, it is an indication that the diskette is bad. Call Century Software technical support.
5. If all diskettes fail again, try using a non-Century Software diskette. If it fails to read, the diskette drive probably requires cleaning. If the non-Century Software disk works, the TERM product diskettes are damaged. Call Century Software technical support.

Cartridge Tapes
lf you are having problems reading a cartridge tape, follow the steps above. lf the above steps fall, be sure to use the blocking option with the tar command. Century Software’s tapes are usually written with a block size of 20. For example:

tar xvfb /dev/rctO 20

lf adding the block size option doesn’t help, try using the dd command as follows:

dd if = /dev/ < device > | tar xvf –

lf this command doesn’t work, try:

dd if = /dev/ < device > conv = swab | tar xvf –

There are two ways to display 132 columns: on-screen and scrolling. On-screen 132-column mode places your monitor into a mode where 132 columns appear in place of the usual 80. Scrolling 132-column mode displays 80 columns on your screen, but allows you to scroll left or right to display additional columns.

On-Screen 132-Column Mode (DOS)
TERM and TinyTERM use on-screen mode if the Video Card field in the General Setup contains an entry other than NONE. To check that, open the menu and select Configure, then General for TERM. In TinyTERM, type Alt-S and select Hardware. The following video cards are supported:

AHEAD
ATI1
ATI2
EVEREX
PARADISE
TECMAR
TSENG
VIDEO7

TERM and TinyTERM will enter 132-column mode when the appropriate sequence is received from the host application.

On-Screen 132-Column Mode (Windows)
TERM and TinyTERM automatically shift the font size when the appropriate sequence is received from the host. To be sure this is configured in TinyTERM 3.3 and earlier or TERM 7.2 and earlier, go to the Configure menu and select Fonts. Make sure the TERM font is selected and Scale to a TERM Font or Scale font to screen is checked.

Scrolling 132-Column Mode (DOS)
If the Video Card field in the General Setup is set to NONE, you will use scrolling 132-Column Mode. When in this mode use Ctrl-Right Arrow to scroll right 16 characters, and Ctrl-Left Arrow to scroll left the same amount.

Scrolling 132 Column Mode (Windows)
TERM and TinyTERM versions released prior to October 1998 use scrolling mode if the selected font will not display 132 characters across the screen, or if Scale font to screen is not selected. When TERM or TinyTERM is in scrolling 132-column mode, use the displayed horizontal scroll bar to view the rest of your text.

132-Column Mode Sequences
Terminal emulations can be divided into two groups:

Group One	Group Two
DEC VT320	Wyse WY-60
DEC VT220	Wyse WY-50
DEC VT100	TeleVideo 950*
SCOANSI	TeleVideo 925*
AT386	TeleVideo 912*

*The Televideo terminals do not support 132 column mode.

The sequences for toggling between 80- and 132-column modes are:

	Group One	Group Two
80-Column Mode	\E[?3l	\E`:
132-Column Mode	\E[?3h	\E`;

\E represents the escape character, ASCII value 27.

Network Installation (DOS and Windows 3.x)
To install TERM or TinyTERM on a network file server, run the SETUP (Windows) or INSTALL (DOS) program. When prompted for the drive on which to install TERM, specify the desired network drive; i.e., G:\apps\century.

The number of network users authorized to use TERM or TinyTERM is enforced within the software. Each user will be informed of their status with the licensing agreement. When TERM or TinyTERM loads, it will display a message similar to the following:

User 1 of 1

When users encounter the error message:

TOO MANY USERS
WAITING FOR OPENING

they must wait for a license to become available. It is important that users of a network installed version of TERM or TinyTERM exit the program gracefully. If the computer is turned off or re-booted while in TERM or TinyTERM, authorized licensees will “lose” their network license. They may then have to wait for a license the next time they attempt to access TERM or TinyTERM.

When TERM or TinyTERM are installed on a network, the sub-directory \SER installed under the TERM directory must allow all users read and write permissions to its files. Any users with insufficient rights will receive an error message and will be returned to the Program Manager or a DOS prompt.

If it becomes impossible to recover lost licenses in the manner explained above, the file TERM.SER or TT.SER may have become corrupt. Should this occur, you will need to replace the file with a fresh copy. This may be done by either installing TERM or TinyTERM again, or the file may be copied from a backup.

Adding Individual User Licenses
Use ISETUP for Windows or INSTUSER for DOS systems to install files (and a program icon on a Windows system) to user workstations. It will also brand TERM or TinyTERM with additional licenses. The serial number and activation key will be required.

Note: Century TCP/IP must be installed on each individual workstation. Install only the emulator on the network server when using Windows.

Branding
The file brand.exe is a DOS executable, so it must be run from a DOS prompt. Change to the directory where brand.exe is located, then tell “brand” which file to add new licenses to. For example, if the TinyTERM executable file is wtt.exe, the command might be:

G:\apps\century>brand wtt.exe

If you get a message that it cannot locate the file to brand, add a specific path to the file:

G:\apps\century>brand g:\apps\century\plus\wtt.exe

The serial number and activation key will then be requested. A message will then be displayed that TinyTERM has been branded.

1. Make sure that Windows for Workgroups is installed correctly and can connect to other Windows for Workgroups PCs using the NetBEUI protocol.
2. Ensure that Windows for Workgroups is installed for ODI drivers.
3. Now install PathWay Runtime using PWSETUP, specifying C:\Windows as the directory containing the driver and related files.
4. PWSETUP will prompt you for a modification of net.cfg. Respond with Yes.

Sample Files for Windows for Workgroups 3.11 and Novell 3.11

*************************AUTOEXEC.BAT*********************************

@ECHO OFF
cd \novell
lsl
smcplus
ipxodi
netx ;(or VLM for 4.x)
E:\WINWORK\SMARTDRV.EXE
PROMPT $P$G
PATH E:\NFS20\PATHWAY;E:\UTILS\UNIX;e:\norton
SET TEMP=E:\WINWORK\TEMP
SET TMP=E:\TMP
LOADHIGH DOSKEY
COPY C:\DOS\COMMAND.COM C:\ > NUL
rem #—————– The Wollongong Group ——————–#
rem # The following lines are for PathWay Runtime setup. Please DO NOT #
rem # modify or remove any of them. If you DO want to, please run the #
rem # setup program to modify or deinstall PathWay for DOS. #
PATH E:\PATHWAY;%PATH%
PWCONFIG -N:65
ODI -i:5
PWTCP
rem #——————- The Wollongong Group ——————#
NFS
mount g: \phaedra\/home/sm sm
C:\DOS\SHARE.EXE /F:4096 /L:400

**********************END OF AUTOEXEC.BAT*****************************

The -I: parameter on the ODI line refers to the IRQ level of your network card. Please verify your card setting and make sure the Pathway setting matches. Remember to use the hex value for 10 and above. Symptoms of an IRQ mismatch include slow connection speed, intermittent hanging or loss of connection, and kernel initialization failure.

Once you have installed Pathway, reboot your PC. Watch for any errors. If no errors occur, first try to ping from a DOS prompt, then make sure Windows for Workgroups loads successfully. You should then be able to use FTP, telnet or NFS to connect to your host.

***********************CONFIG.SYS************************************

DEVICE=E:\WINWORK\HIMEM.SYS
DEVICE=E:\WINWORK\EMM386.EXE noems x=d000-d3ff
DOS=HIGH,umb
files = 70
stacks=9,256
buffers = 40
lastdrive=P
DEVICE=C:\DOS\SETVER.EXE
SHELL=c:\dos\command.com /p /e:600
DEVICE=E:\WINWORK\IFSHLP.SYS

*********************END OF CONFIG.SYS********************************

**************************NET.CFG*************************************

#—————- The Wollongong Group —————-#
# The following lines are inserted for PathWay driver #
# interface setup for ODI. Please DO NOT remove them. #
Protocol IP
Bind SMCPLUS

Protocol ARP
Bind SMCPLUS
#—————- The Wollongong Group —————-#

Link Driver SMCPLUS
Port #1 300
Mem #1 000d8000
Int #1 5
Frame Ethernet_802.3
Frame Ethernet_SNAP
Protocol IPX 0 Ethernet_802.3
#—————- The Wollongong Group —————-#
# The following lines are inserted for PathWay driver #
# interface setup for ODI. Please DO NOT remove them. #
frame ETHERNET_II
PROTOCOL IP 000000000800 ETHERNET_II
PROTOCOL ARP 000000000806 ETHERNET_II
#—————- The Wollongong Group —————-#

#For 4.x Novell the Novell DOS requestors will go here.

LINK SUPPORT
Max Boards 4
Buffers 8 1514

**************************END OF NET.CFG******************************

***************************PROTOCOL.INI*******************************

[network.setup]
version=0x3110
netcard=ms$w13ep,1,MS$W13EP,4
transport=ms$nwlinknb,NWLINK
transport=ms$netbeui,NETBEUI
lana0=ms$w13ep,1,ms$netbeui
lana1=ms$w13ep,1,ms$nwlinknb

[MS$W13EP]

[NWLINK]
BINDINGS=SMCPLUS

[NETBEUI]
BINDINGS=SMCPLUS
LANABASE=0

[net.cfg]
PATH=E:\NOVELL\NET.CFG

[Link Driver SMCPLUS]
data= Frame Ethernet_SNAP
data= Frame Ethernet_802.2
data= Frame Ethernet_II
data= Frame Ethernet_802.3
data=Link Driver SMCPLUS

**************************END OF PROTOCOL.INI*************************