|
|
| Author |
Message |
freek
|
|
TTY H4 SUCKS SHIT
| 
Dec 28 17:40 UTC 1996 |
Um, I propose that whatever modem it is thats FUCKED UP (TTY H4) be taken out
of Grex. The modem seems to like to make everything in all caps, and put a
\ infront of all actual caps.. like this: \WELCOME TO \GREX! I always get
this damn modem when Grex is busy, and its damn impossible to do anything.
I've tried to fix it by messing with stty, and various other things, and
nothing works. This is the 89573542897th time I've tried to tell people about
it, and noone does anything about it. Thank you and have a nice day.
|
| 16 responses total. |
ryan1
|
|
response 1 of 16:
|
Dec 28 17:52 UTC 1996 |
did you try stty -lcase?
|
popcorn
|
|
response 2 of 16:
|
Dec 29 00:11 UTC 1996 |
Freek, this is the first time I've heard you complain about this. I'm not
sure where you've been posting these things, but the best way to handle system
problems is to either post them in Agora item 3 ("system problems") or mail
them to staff.
What you're seeing is that you have an error-correcting modem. You are
connecting to a non-error-correcting modem. In the process of establishing
a connection, your modem is sending some characters to Grex's dumb modem, to
try to set up an error correcting connection. Grex's dumb modem thinks it
is already connected and that these characters are part of your login ID.
Typing capital letters at the login: prompt triggers a Really Stupid Unix
Feature, where it assumes you are on an all-uppercase terminal, so it only
sends uppercase letters to your screen. You can fix it by doing what ryan
said: typing "!stty -lcase", or by hitting some breaks and pressing enter a
few times at the login prompt, until you get another login prompt in
lowercase.
In any case, all of the non-error-correcting modems are scheduled to be
replaced in a few weeks.
|
tsty
|
|
response 3 of 16:
|
Dec 29 07:38 UTC 1996 |
good news from angst news ...not bad.
|
popcorn
|
|
response 4 of 16:
|
Dec 29 09:33 UTC 1996 |
Another idea: Someone in agora suggested hitting a few backspaces before you
enter your login ID. The backspaces should get rid of any garbage that your
modem typed for you.
|
scg
|
|
response 5 of 16:
|
Dec 29 17:12 UTC 1996 |
Maybe. It depends on whether your backspace character is set to whatever your
terminal program uses at that point. Control-U might work better.
|
dang
|
|
response 6 of 16:
|
Dec 29 19:35 UTC 1996 |
I believe that either ^H or ^? will work to backspace at a login prompt. Most
terminal programs use one of those. What your personal backspace is on grex
is irrelevent, because Grex doesn't know who you are yet.
|
scg
|
|
response 7 of 16:
|
Dec 29 19:44 UTC 1996 |
I've generally found that depending on what computer I'm logging into, either
^H or ^? will work, but never both. Grex seems to accept ^H there. Lots of
other systems I've used accept ^?. Just about anything should accept ^U or
^W, I think.
|
dang
|
|
response 8 of 16:
|
Dec 30 01:33 UTC 1996 |
(Actually, if you use ^? it doesn't erase ot from the screen, but does erase
it from the buffer.)
|
popcorn
|
|
response 9 of 16:
|
Dec 30 06:21 UTC 1996 |
Last time I tried it, only Backspace worked for backspacing at the login
prompt. But it's been a while since I typed a Delete character there.
|
janc
|
|
response 10 of 16:
|
Dec 30 06:35 UTC 1996 |
Delete doesn't work there. Wish both did.
|
freek
|
|
response 11 of 16:
|
Dec 30 07:29 UTC 1996 |
First of all, I sent tel's and mail to STeve, and scg... this the first public
attempt at bitching about it.
Second, Yes, i have tried stty -lcase, and that does not work.
Third, I will try the other things next time i get it.
|
popcorn
|
|
response 12 of 16:
|
Dec 30 14:41 UTC 1996 |
From a menu or an Ok prompt, type "!stty -lcase" instead.
(It's kinda interesting to experiment with this setting: you can run
"stty lcase" (without the - ) to switch to an all-upper-case session, and then
when you want to switch back, run "stty -lcase" to go back to a normal
session).
|
kaplan
|
|
response 13 of 16:
|
Dec 30 19:31 UTC 1996 |
I'm now on ttyh9 and getting quite a bit of line noise. Those
error-correcting modems are coming on line real soon now, right?
|
omni
|
|
response 14 of 16:
|
Dec 31 05:36 UTC 1996 |
Hopefully before the crisis in Afghanistan gets any worse ;)
|
nephi
|
|
response 15 of 16:
|
Jan 1 22:35 UTC 1997 |
(Getting secure phone lines has proved to be a bit more
of a . . . process than originally thought. It should be
done sometime this week, although dealing with a behemoth
like Ameritech can sometimes take an unpredictable amount
of time.)
|
kaplan
|
|
response 16 of 16:
|
Jan 4 05:25 UTC 1997 |
ttyh9 was bad for me again earlier today.
|