Solved

Keyboard is not working properly

Posted on 2000-02-23
5
341 Views
Last Modified: 2013-12-23
I have installed SCO Unix 5.0.5 in a IBM Netfinity P-III server and network is on ethernet and using TCP/IP protocol. We ahve successfully connected the DOS 6.22 workstation with SCO system via third party telnet software. But when we try to run Foxpro for Unix version from the terminal the key BACKSPACE, DELETE, CTRL+T/Y does not work and the graphics screen of the foxpro looks shattered. When log in prompt shows on the terminal at that time if we press BACKSPACE to delete any character the cursor goes to next line and one column wider than the prevoius line.
For your information terminal type is VT-100.
Can anyone solve these problems.
Thanks
0
Comment
Question by:tauhid_bd
  • 3
  • 2
5 Comments
 
LVL 20

Expert Comment

by:tfewster
ID: 2553109
Terminal type doesn't get set (at the Unix end) until you've logged in, so you can expect some odd results from BACKSPACE etc. If you log in to a Unix shell, does BACKSPACE work then? Does "clear" clear the screen?

If not, do "echo $TERM" while logged in to check the terminal type set at the Unix end & double check the setting for the terminal emulator.

You can set BACKSPACE up manually with
stty erase BACKSPACE (& include it in your startup files).

Which telnet/terminal emulator software are you using?
0
 

Author Comment

by:tauhid_bd
ID: 2557195
When I logged on on Unix from the terminal BACKSPACE key does not work properly and 'clear' commands does not clear the screen.

I will try with this "echo $TERM" command.
I am using NSCA's telnet for DOS and sometime NUPOP. Nupop is mailing software under DOS>
0
 
LVL 20

Expert Comment

by:tfewster
ID: 2557763
OK, if the BACKSPACE key & "clear" command don't work at the Unix command line, there's a mismatch in the terminal type. I'm not familiar with the NSCA utilities, so I can't tell you how to check/set the emulation type at the PC  end - if you don't have the manuals it may be easier to experiment at the Unix  end.

Set the terminal type in Unix with "TERM=vt100;export TERM" (Or "setenv TERM  vt100" if you  use the c-shell).

Once we've got the right terminal type, we need to make sure it gets set correctly when you log in.

2 other things that would be worth trying (if possible); If you have a VT100 terminal, try connecting that in place of the PC. If you have a Win95/98/NT PC, try telnet on that and see if you get the same results.

Let me know how you get on
Tim
 
0
 

Author Comment

by:tauhid_bd
ID: 2560726
Let me try on to export the VT-100 terminal. I will let you know within few days.
By the way do you any other software in your knowledge which can connect a DOS machine to a windows machine ?
0
 
LVL 20

Accepted Solution

by:
tfewster earned 50 total points
ID: 2606372
As you haven't come back to me, I assume setting the terminal type resolved the problem.

You can set this automatically when the user logs in by putting the command in their .profile or .cshrc file.

If the user uses other terminals, or if other people use that terminal, you may need some additional code in these files to test the terminal type before resetting it, e.g.

if [ $TERM = "unknown" ]
then
  TERM=vt100;export TERM
fi

To give you a more definite answer I need to know:
- What shell the user(s) use;
- What "echo $TERM" reports on that terminal and others.

Regards, Tim
0

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Let’s list some of the technologies that enable smooth teleworking. 
I had an issue with InstallShield not being able to use Computer Browser service on Windows Server 2012. Here is the solution I found.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

831 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question