|
|
| Author |
Message |
| 25 new of 234 responses total. |
dpc
|
|
response 175 of 234:
| 
Aug 18 18:27 UTC 1998 |
Yesterday and today I got a bizarre result when I dialed in.
Instead of getting "grex.cyberspace.org login:" I got
"grex.cyberspace.org ". There was a blank space
where "login:" should have been. The cursor was in the correct
place, and when I typed "dpc" it took the login and all the
"login:" reappeared when I entered my password.
|
mdw
|
|
response 176 of 234:
|
Aug 19 00:59 UTC 1998 |
That sounds like a problem with your computer or terminal software,
not with grex.
|
valerie
|
|
response 177 of 234:
|
Aug 19 13:35 UTC 1998 |
This response has been erased.
|
senna
|
|
response 178 of 234:
|
Aug 19 14:19 UTC 1998 |
That happens to me on occasion, I believe it's just an echo error.
I've decided that my text droppage problem is local to my system, since it
happens on mnet just as much.
|
scott
|
|
response 179 of 234:
|
Aug 19 16:43 UTC 1998 |
It's a non-repeatable peculiarity. Happens to me to.
|
dpc
|
|
response 180 of 234:
|
Aug 20 18:57 UTC 1998 |
I'm running ClarisWorks for the Mac. The reason I mentioned this oddity
is that I have *never* seen it before, on Grex or M-Net.
|
mdw
|
|
response 181 of 234:
|
Aug 21 01:40 UTC 1998 |
If the "login:" message came back when you entered your password, that's
not grex - the login program on grex simply doesn't have the smarts to
move the cursor up & rewrite the login: prompt on a previous line. It's
far more likely that your terminal software remembered the "login:"
message, but somehow forgot to actually write it out to your screen
memory. When you entered your password, it probably had to scroll the
display or do something more major, thus causing it to refresh the
screen, and incidently to display the "login:" message it had
remembered. Chances are that if you had done something else that would
cause the local display window to be refreshed, such as temporarily
placing another window in front of the terminal window, or using any
local scrolling/windowing screen controls, that this would have caused
the "login:" message to be displayed as well. Some terminal programs
are more brain damaged than others. The stock windows terminal and
telnet clients seem to be particularly brain dead. Probably MicroSoft
has a corporate theory that you should be using local gui driven
software, rather than remote TTY interface software. From a business
perspective, it makes perfect sense.
|
scott
|
|
response 182 of 234:
|
Aug 21 10:46 UTC 1998 |
I think the problem is that the connecting-to-terminal-server process
occasionally barfs, causing modem junk to happen. Sometimes the
terminal-server-to-Grex connecting process generates some junk. In either
case just dialing again gives a good connection, and I've seen no data
indicating any particular dialin line has a problem.
|
rs1
|
|
response 183 of 234:
|
Aug 22 08:38 UTC 1998 |
One guy, on an old obsolete cumputer with something that he doesn't
understand in the way of software to connect to grex and he has problems
with m-net and he says its grex's problem....
Yeah, I buy it. OJ was framed. And Clinton didn't get blowjobs from
Monica.
Yeah.
|
jazz
|
|
response 184 of 234:
|
Aug 23 14:14 UTC 1998 |
I'm not SunOS literate enough to answer, but that kind of delay sounds
like a wrappers problem associated with hosts that do not have working reverse
DNS (which requires DNS to time out, usually around ten seconds, but not
necessarily so) and telnet.
Another possibility is that it's got something to do with the modem
handshaking at the beginning of a session. Non-error-correcting modems often
encounter delays after beginning to train with error-correcting modems (which
GREX does have).
|
cybot
|
|
response 185 of 234:
|
Aug 24 12:24 UTC 1998 |
View hidden response.
|
dpc
|
|
response 186 of 234:
|
Aug 25 18:03 UTC 1998 |
I dialed in this morning and read a few items in Agora. Then just
now I logged in again. My problem: The responses that I read this
morning were *still* new. This is the first time I've seen this
happen. Howcum?
|
toking
|
|
response 187 of 234:
|
Aug 25 18:28 UTC 1998 |
I've had that happen when I drop carrier....usually, to avoid it, I quit
out of pico span <to the login prompt> and quit from there to disconnect
|
scott
|
|
response 188 of 234:
|
Aug 25 21:20 UTC 1998 |
What toking said. You have to quit Picospan for your participation file to
be saved.
|
tpryan
|
|
response 189 of 234:
|
Aug 25 23:07 UTC 1998 |
In my .cfonce file, I have added the command
set autosave
it forces picospan to save your participation after each item. If you
disconnect or get disconnected, only the last items shows up as new
again.
Wish I could remember what 'set edalways' is in their for.
'set stay' returns you to a respond or pass prompt after you respond
(or forget).
|
davel
|
|
response 190 of 234:
|
Aug 26 00:53 UTC 1998 |
"set edalways" causes text entry - your entry of an item or response -
to bring up your designated editor instead of using Picospan's builtin
text collector. For most people, these days, the editor in question is
gate (thanks again to Jan!!!).
|
davel
|
|
response 191 of 234:
|
Aug 26 10:20 UTC 1998 |
Hmm. Grex seemed pretty slow.
/a/d/a/davel$ uptime
6:02am up 16 days, 16:33, 72 users, load average: 59.73, 37.22, 22.41
It's a little better now.
|
davel
|
|
response 192 of 234:
|
Aug 26 19:41 UTC 1998 |
I dialed in, and the modem connected but after that nothing responds.
Still sitting there connected to the modem after 8 minutes. (I'm
telnetted in to enter this. I have problems if I telnet in, so I
avoid it.)
|
coyote
|
|
response 193 of 234:
|
Aug 27 04:25 UTC 1998 |
I've had that problem too, twice, but the 761-3000 number works fine, and both
times I've just tried the 761-5041 number again a few minutes later and have
connected fine.
|
drew
|
|
response 194 of 234:
|
Aug 27 17:03 UTC 1998 |
The outgoing mail limiter, upon getting a message exceeding the intended
limit, *both* sends the mail anyways *and* bounces a copy back to me. I do
not think that this is what's intended.
|
dpc
|
|
response 195 of 234:
|
Aug 28 15:48 UTC 1998 |
Re #186 et seq--I *did* properly log off the first time. If I'd been
disconnected, I would have expected the problem.
|
valerie
|
|
response 196 of 234:
|
Sep 2 13:59 UTC 1998 |
This response has been erased.
|
drew
|
|
response 197 of 234:
|
Sep 3 00:55 UTC 1998 |
I'll send them a note.
|
senna
|
|
response 198 of 234:
|
Sep 3 15:20 UTC 1998 |
Grex appears to be suffering from massive processory slowdowns at the moment.
Or it did, when I was getting on.
|
valerie
|
|
response 199 of 234:
|
Sep 9 16:31 UTC 1998 |
This response has been erased.
|
