In article <02cf01c667e2$8b637a20$6500a8c0 at BILLING>,
"Jay West" <jwest at classiccmp.org> writes:
You wrote....
Actually this is *exactly* what I'm trying to
do.
Ohhhh from your previous email, I thought you were hoping to use the term
server to hook up terminals to classic/vintage computers that did not have
an ethernet port (capability) in which case a term server isn't really what
you want.
The end goal is to have some way of driving a significant number of
terminals all at once without having one PC per terminal. I'm
thinking the VAXserver could handle this, the only question is if the
OpenVMS license would allow for multiple logon sessions. In some
alternative reality I would like to reproduce a midrange timesharing
system, probably something PDP-11 based. But those didn't have
ethernet back in the day, I don't know how well they would work with a
terminal server. Our PDP-11/70 had gobs of serial ports on it, I
think.
However, its my understanding that you could use the terminal server
"in reverse" to connect from the TCP/IP enabled machine to a port on
the terminal server and from there talk to the RS-232 style monitor
port on an older machine like some S-100 bus based machine. While
this is not my use case, I thought you could do this as people on the
net talk about using terminal servers to monitor the serial console
port on a Sun.
--
"The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
<http://www.xmission.com/~legalize/book/>
Pilgrimage: Utah's annual demoparty
<http://pilgrimage.scene.org>