jeff@drexel.UUCP (Jeff White) (02/17/88)
At one of the companies I work at, they have several DT100 terminals, which I believe are probably Liberty OEM terminals, that are connected to locally attached printers through the terminals printer port. Ocassionally, when the terminals are turned on, the login prompt (ther terminals are connected to a 6000 system running Xenix) gets sent out the printer port (and prints on the printer). Control returns immediately to the terminal keyboard, so that a user can enter their login and password (this doesn't appear on the printer, ie. local print is turned off). Has anyone else ever experienced problems like this? If so, what was the problem (and your solution). One idea I just had (but since I'm not at the system can't test) is that the clear screen sequence at the beginning of a session is causing the printer to go into local print mode. However, that wouldn't explain how the terminal got back to normal mode and allowed a login. I'm assuming, but not totally sure, that the problem is with the terminal and not with Xenix (something in the 'is' field in termcap might be the culprit). Again, I would appreciate any help. Jeff White Drexel University - ECE Dept. rutgers!bpa!drexel!jeff
leonard@bucket.UUCP (Leonard Erickson) (02/25/88)
In article <560@drexel.UUCP> jeff@drexel.UUCP (Jeff White) writes:
<
< At one of the companies I work at, they have several DT100 terminals, which
<I believe are probably Liberty OEM terminals, that are connected to locally
<attached printers through the terminals printer port. Ocassionally, when the
<terminals are turned on, the login prompt (ther terminals are connected
<to a 6000 system running Xenix) gets sent out the printer port (and prints
<on the printer). Control returns immediately to the terminal keyboard, so
<that a user can enter their login and password (this doesn't appear on the
<printer, ie. local print is turned off). Has anyone else ever experienced
<problems like this? If so, what was the problem (and your solution).
< One idea I just had (but since I'm not at the system can't test) is that
<the clear screen sequence at the beginning of a session is causing the
<printer to go into local print mode. However, that wouldn't explain how
<the terminal got back to normal mode and allowed a login. I'm assuming,
<but not totally sure, that the problem is with the terminal and not with
<Xenix (something in the 'is' field in termcap might be the culprit).
< Again, I would appreciate any help.
<
< Jeff White
< Drexel University - ECE Dept.
< rutgers!bpa!drexel!jeff
Well, I've got a DT-100 at home. From what I've been told it's a relabeled
Wyse-75.
I can only suggest a couple of possibilities:
1. the clear screen is doing a "print line" or some such
2. the termcap is flaky. (I know for a *fact* that there are at least two
errors in the 600 Xenix termcap entries for the dt-100.)
By the way, I've yet to find *any* kind of lockup that I can't clear
with shift-setup. (now if that would only clear the mis-set tabs...)
--
Leonard Erickson ...!tektronix!reed!percival!bucket!leonard
CIS: [70465,203]
"I used to be a hacker. Now I'm a 'microcomputer specialist'.
You know... I'd rather be a hacker."