|
Terminal type problems may vary:
-
What terminal type your software is emulating?
-
What terminal type are you specifying when logging on?
-
Is the terminal type being set correctly?
-
Is that emulation compatible with University of Maryland, College Park (UMCP) systems? (Poorly
written programs may not provide good emulations.)
- Are you using the Mac OS X terminal application? If so, please see our page on configuring terminal emulation with the OS X terminal application.
As you login to one of the Office of Information Technology (OIT) Unix systems, you may see the
prompt:
TERM = (unknown)
What should you type at that prompt? If you're just pressing the
Enter key, that can cause a problem. The program is asking you to input the
terminal type that your communications software is using. You will
need to determine this yourself, by referring to the seller or
from the documentation. Some
communication packages have multiple termtype settings, therefore, you will
need to check the configuration.
If you are sure you know what terminal type your software is
emulating and you are indeed typing the correct term at the prompt shown above,
then you need to check to make sure things are being set
correctly on the WAM side. To check this type:
rac2> set | grep term
For example, if your terminal type is vt100, you should see:
rac2> set | grep term
term vt100
You can also check your environment settings with:
rac2> printenv | grep TERM
Using vt100 terminal type (as an example), you should see something
like this:
rac2> printenv | grep TERM
TERM=vt100
TERMCAP=d0|vt100|vt102|vt100-am|dec-vt100:cr=^M:do=^J:nl=^J:bl=^G:co#80
[ TERMCAP will have several lines; deleted to save space ]
rac2>
Note the TERM is set to vt100, and the second value in the
TERMCAP variable is also vt100, this shows that everything is
set correctly.
If either the 'set' or 'printenv' commands return a value
which is NOT your terminal type, you need to determine the
reason. If you are having difficulties with this, come to the OIT
Help Desk.
One way to reset things quickly is to issue the following
three commands (assuming you are using a vt100 terminal type):
rac2> unsetenv TERMCAP
rac2> set term=vt100
rac2> tset
Erase is Delete
Kill is Ctrl-X
rac2>
If everything seems to be set correctly, the last possibility
is that the software package you're using to communicate
doesn't emulate a terminal type which is compatible with the University of Maryland, College Park
Unix systems.
If that is the case, a free
communications package named F-Secure can be downloaded (for windows)
or pickup a Getting Connected CD
at the OIT Help Desk. Macintosh users can use the Terminal program that comes
with the Macintosh Operating System (OS) called Terminal.
|
