[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

5076.0. "Terminal program needed to emulate TVI 925." by DNEAST::BAKER_CHUCK (Human Input Required...) Wed Sep 25 1991 13:12

    
    
    
     I need help.  The college where my wife teaches has recently made
    their computer system available via modem and she would like to be able
    to access it from our Amiga.  (So far easy enough).  The operating
    system is UNIX but that's about all she could tell me about it.  Her
    terminal is a TVI 925 .  Does anybody know anything about this
    terminal?  And does anybody know of a compatable terminal program for
    the Amiga?
    
      I use VLTjr. currently but it doesn't understand many of the special
    codes that are used.  I can talk to the computer but most of the
    software (like E-MAIL) is scrambled.
    
    Any help at all would be appreciated.
    Chuck
T.RTitleUserPersonal
Name		DateLines
5076.1What functionality does she need?TLE::ALIVE::ASHFORTHLord, make me an instrument of thy peaceWed Sep 25 1991 13:3710
Unless the some special function of the TVI is being used (e.g., a proprietary
graphics mode), you should be able to specify a vt100-style terminal emulation
using a standard tty type. If this is the case, just check with the system
administrator at the school, should be no biggie. Any Unix system I've seen is
prepared to deal with vt100 terminals.

If, on the other hand, your wife *does* need full emulation of the TVI's
proprietary functions, you got me- never hoid of 'em.

Bob
5076.2LEECHS::hiltonHow's it going royal ugly dudes?Thu Sep 26 1991 05:1514
If the UNIX machine is capable of supporting vt100, then after login,
get to the c shell:

csh
then see what it thinks the terminal is:
printenv
is TERM is not equal to vt100 then:
setenv TERM vt100

NB: UN*X is case sensitive

This works on ULTRIX in a c shell, so should be ok!

Greg
5076.3WhAt Do You MeAn CaSe SeNsItIvE/ (<- lowercase ?)DNEAST::BAKER_CHUCKHuman Input Required...Thu Sep 26 1991 07:5719
    
    
    
      Thanks to .1 I found a UNIX book and looked up some terminal type
    commands.  Late last night I tried to set the terminal type with the
    command term = (vt100).  Got a multitude of errors. Gave up.
    
      The machine does support VT100's as in several places it offers them
    in a menu list.
    
       Now, thanks to .2 I know that uNiX is case sensitive I'll try things
    again.
    
    Do we have someone in sales that could convince the University of Maine
    to switch from I*M & uNiX to DEC and VMS?  It would really make my life
    easier.8-}
    
    Thanks again
    Chuck
5076.4LEECHS::hiltonHow&#039;s it going royal ugly dudes?Fri Sep 27 1991 06:418
Chuck,

Make sure your in the C shell before typing the commands! UN*X has a
number of different shells, all of which do things differently. Your
term=vt100 command works with System V shell!


Greg
5076.5Ya,Ya,Ya... And HELP: cannot be found either.DNEAST::BAKER_CHUCKHuman Input Required...Fri Sep 27 1991 07:5314
       Aaaaarrrrggggg;   
    
    
    
      OK....  How do I get to a "C" shell and how is it different from
    whatever default I end up at when I request uNiX?   Yes I admit that
    the book I found was on the System V.
    
    
       I still think that it would be easier for them to convert to VAX + VMS
    than for me to convert to uNiX.
    
    Thanks for the help
    Chuck
5076.6More UN*X commands...BAHTAT::HILTONHow&#039;s it going royal ugly dudes?Fri Sep 27 1991 09:1125
    see 5076.2, but in case it wasn't clear. Lines starting with # mean
    ones you type in, but don't type the #!!!
    
    
    OK. Login to the beast
    Change to the c shell
    #/bin/csh
    Then find out what it thinks your terminal is:
    #printenv
    Look for the entry TERM
    If it's not vt100 then change it:
    #setenv TERM vt100
    And your off!
    
    
    For system V shell I THINK you want to do something like:
    #TERM=vt100
    #export TERM
    
    But don't quote me on that!
    
    Try the above and if it doesn't work we can do some other things.
    
    
    Greg