2 Jun
1999
2 Jun
'99
12:02 p.m.
On Wed, 2 Jun 1999, Marvin wrote:
I have frequently used the PC as a terminal for the
machines that require
one. So far, there have been no problems ... except for the minor details of
knowing how the serial port was hardwired configured (baud, data bits,
parity, stop bits), and if a nul modem cable is required. And of course,
that problem remains regardless of what is connected to the serial port.
But how do I lobotomize that silly "HYPER-TERMINAL" app in Windoze95 to
convince it that I do NOT want it to dial, wait for carriertone, etc.?
Those are the kind of "extra variables" that I was trying to avoid, since
they'll add another 20 minutes onto the task. Connecting one of the
Televideo 920s or DEC VT100s would let me move forward to the next part of
the task.
But figuring out how to do simple stuff with needlessly complicated
"tools" is just one more thing that we all need to get around to doing
occasionally. And I certainly will eventually need to figure out how to
do local terminal stuff with that Windoze95 app.
The advice here has been great. The parameters do, indeed, seem to be set
with some headers. The headers are, of course, unlabelled. But there's
the remains of a piece of tape near one of the connectors with a hand
scribble of "9600", so I'll start off by assuming that that's the
current
baud rate setting.
The first time that I did any serial interfacing (in the 70s) it was a
nightmare. Now, it's just one more trivial hassle along the way. But it
shouldn't take but 20 minutes.
Allison's comment that it won't start talking to the terminal until it
sees the disk means that there's not much point in continuing that part of
it until I find or get a system diskette for it.
--
Grumpy Ol' Fred cisin(a)xenosoft.com