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

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.

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*************************

1. Make sure that Windows for Workgroups is installed correctly and that a connection can be made to other Windows for Workgroup machines using the NetBEUI protocol.
2. Ensure that Windows for Workgroups is installed for Real and/or Enhanced mode NDIS.
3. Check the CONFIG.SYS file. No Protocol Manager or MAC driver should be included.
4. Now install PathWay Runtime using PWSETUP, specifying C:\Windows as the directory containing the driver and related files.
5. PWSETUP will prompt you for a modification of CONFIG.SYS. Respond with No. This will avoid having to modify it later. If this was missed for some reason, remark out or delete the Wollongong Group section of that file.
6. In AUTOEXEC.BAT add the bolded lines to the Wollongong section as indicated:

SET PATH=C:\PATHWAY;%PATH%
PWCONFIG -N:65
C:\WFW3.11\NET INIT ;this loads the device driver
NDIS -I:X -D:Y ;this loads the NDIS driver interface
C:\WFW3.11\NET START NETBIND ;this completes the binding process
PWTCP

Make sure that the NET START command is not executed at the beginning of AUTOEXEC.BAT.

The -I: parameter on the NDIS line refers to the IRQ level of the 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.

The -D: parameter on the NDIS line refers to the bracketed section in your protocol.ini file which contains your card name and settings. For example, if the sixth section in your protocol.ini contains this information, the NDIS line should read -D:6. Errors which indicate “unable to bind” or “incomplete binding” can be resolved by double-checking this value and/or verifying that the protocol.ini contains the proper information for your network card.

Once you have installed Pathway, reboot the machine. Watch for any errors. If no errors occur, first try to ping at 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.

Century Software, Inc., has had a request for IBM 5250e emulation. This has not been implemented thus far.

CR 93

TinyTERM for Windows has a Display DIM attribute as option for Wyse50 and Wyse60 emulations. Century Software, Inc., has had a request to add this functionality to TERM for UNIX/Linux.

CR 842

In TinyTERM’s Session Properties, check the Use custom emulation size box and set the Columns to 132. Text will remain on screen that should be cleared, depending on how the host application clears the screen. The same thing will work properly without a custom emulation size.

CR 839

TERM for Linux does not communicate through the Digi PortServer at all. It connects to the tty port generated, but there’s no response after that. The remote system doesn’t see anything you type in TERM, and TERM doesn’t echo anything back from the host.

CR 838

Century Software, Inc., has had a request to display the status of Caps Lock in the emulator window. The most likely place for such a feature would be the Status Bar at the bottom of the TinyTERM window.

CR 834

Program a mouse button to the string “%o%p”, which will copy selected text and paste it at the current cursor location. Select some text near the top of the TinyTERM window, then click the programmed mouse button. The selected text is pasted at the prompt normally.

Hit Enter a few times to move the selected text off screen. Right-click again without selecting new text. The area of the screen you originally selected will be copied, instead of just pasting in what should be on the clipboard. TinyTERM actually picks up the current text at the previously selected location.

CR 833