by to which replies are impossible, someone caused to appear as though
"Barry" had uttered:
If this is the same type of cable that you would use to connect aQuote:> I've gotten my hands on an HP 700/92 dumb terminal...
> [commendable amount of detail on software setup]
> ...
> my ttys file entry:
> ...
> my termcap file entry:
> ...
> output from stty -f /dev/ttyd0 -e:
> ...
> getty process
> ...
> The terminal's datacomm port is connected to my PC's first serial
> port (com1) by means of a Male DB25 to Female DB9 RS-232C cable...
> The terminal works in local mode, but nothing pops up in remote mode.
modem to a PC, then you must deal with the following situation:
(1) The PC expects to talk to a modem at the other end of the cable.
(2) The terminal *also* expects to talk to a modem at the other end
of the cable.
Note that both devices want to talk to a modem. You must do something
to satisfy this yearning.
What you need, therefore, is little item called a "null modem".
The null modem consists of a small plastic block with a female
connector on one end and a male connector on the other end, with
some tricky wiring inside. You can buy a null modem at a Radio Shack
store, or from various vendors such as BlackBox or Digikey. They are
available in either 25-pin or 9-pin styles.
(Pedantically speaking, the 9-pin D-shell connector is a DE-9, but
this detail is usually fudged.)
Attach the null modem to one end of the cable between the PC and the
terminal. (For a simple asynchronous terminal, it probably doesn't
matter which end of the cable.)
Then see if the terminal can communicate better with your FreeBSD Unix
system.
------------
For other information on using character-cell video terminals, see:
http://www.cs.utk.edu/~shuford/terminal_index.html
...RSS