You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-249   250-274   275-299   300-324   325-349   350-364     
 
Author Message
25 new of 364 responses total.
srw
response 175 of 364: Mark Unseen   Jul 23 06:06 UTC 1997

I can certainly detect the speed increase due to the extra memory. I'd 
have been shocked if it failed to be noticeable, since 32MB is a 
pitifully small amount of memory for a system running as much load as we 
are.
scg
response 176 of 364: Mark Unseen   Jul 23 07:17 UTC 1997

Yeah, Grex now feels much more pleasant.
tsty
response 177 of 364: Mark Unseen   Jul 23 07:49 UTC 1997

View hidden response.

remmers
response 178 of 364: Mark Unseen   Jul 23 09:15 UTC 1997

The problem may to some extent be at your end. I dial the
"advertised line" a lot (I'm connected that way now), and it
doesn't usually happen to me. When it does, sending BREAK
characters fixes it - I usually have to send only one or two
BREAK's to get a readable login prompt.
janc
response 179 of 364: Mark Unseen   Jul 23 13:17 UTC 1997

I'd love to know what is happening.  But it doesn't happen to me with any of
the computers/modems I dial in with and I don't know squat about what TS uses.

I thought the "byebyebaby" screen was especially artistic.
dang
response 180 of 364: Mark Unseen   Jul 23 15:32 UTC 1997

It happenes to me occasionally when I dial in from home, but that terminal
won't even hang up my modem, so something is wrong on my end at least. 
However, busying out that line allows me to dial in.
richard
response 181 of 364: Mark Unseen   Jul 23 18:16 UTC 1997

TS, grex lags bad enough without you dumping those screens...
you could have emailed that garbage to staff without forcing
everyone else to read it.
senna
response 182 of 364: Mark Unseen   Jul 23 18:51 UTC 1997

3000 is working fine for me now, but I was getting some garbage last night.
My settings are fine, though.
valerie
response 183 of 364: Mark Unseen   Jul 23 20:50 UTC 1997

This response has been erased.

i
response 184 of 364: Mark Unseen   Jul 24 01:57 UTC 1997

I usually have to dial -3000 about 5 times to get a good connection, but the
problem I generally see is a very short (3-25 characters) burst of high-bit-
set ASCII garbage (then no response) or a session that freezes before getting
all the way to the login prompt.  Once into the .profile, etc. stuff, I
VERY seldom have any problems.  Sending BREAK doesn't seem to do any good;
I'm not confident that none of the fault is my modem's.
tsty
response 185 of 364: Mark Unseen   Jul 24 02:27 UTC 1997

i have expurgated #177, but you *can* see it if you want s'nifty
graphics.
  
valerie said it was causing some ppl's terminals to, ummm, uhhhh......
go bonkers (?). nothing like that happened to mine so i didn;'t 
consider it a problem. however, since it is , it is expurgated.
  
as for the specific problem, the breaks (long, short, longer, any)
generate 'more of the same.'
  
i strongly (!) suspect that IF the actual -3000 modem is busy (and
this connection is on tty h7 after having dialed -3000) the connection
works ok. 
  (tty h4 is busy at the time of this login)
  
lots of good discussion at tnight's board meeting.
valerie
response 186 of 364: Mark Unseen   Jul 24 04:32 UTC 1997

This response has been erased.

scg
response 187 of 364: Mark Unseen   Jul 24 04:44 UTC 1997

On 761-3000, I tend to get a good connection about half the time.  The other
half it's usually just a blank screen.  This is usually with a USR Sportster
28.8 modem, but occasionally with an Acer 33.6 modem as well.  I'm not sure
if I've seen it with my IBM PCMCIA (People Can't Memorize Computer Industry
Acronyms) modem or not.

I'm using Hyperterminal (mostly because I'm too lazy to download a real
terminal program), so I cna't send breaks and don't know whether that will
help or not.
davel
response 188 of 364: Mark Unseen   Jul 24 17:48 UTC 1997

The last 3 times I've been on, things have seemed fine (if sometimes a bit
slow - better now) - and then Grex just stopped responding.  I finally gave
up & disconnected (at least one was over the internet, at least one was a
dialin).  Didn't have time to call back & see whether Grex was up if I tried
again.  Modem did *not* disconnect all by itself ... but since dialins are
now apparently telnets from groovy, that may not prove Grex didn't completely
crash any more.
richard
response 189 of 364: Mark Unseen   Jul 24 19:37 UTC 1997

Interesting...Agora hasnt been telling me lately how many newresponses
I have to read.  Mybookmark is still in place and there are always
new messages to read but Agora isnt telling me how many.  The other
confs I read are fine.n  It is only Agora that wont give4 me a
status report on how many nitems/responses I have to read.
senna
response 190 of 364: Mark Unseen   Jul 24 21:06 UTC 1997

Pleasantly, 3000 worked for me today
remmers
response 191 of 364: Mark Unseen   Jul 24 21:18 UTC 1997

I haven't encountered the problem that TS is having on the -3000
lines -- I can just about always get connected, get a login
prompt, and get sensible-looking output from Grex.

When I leave my modem in "smart" mode -- error correction and
data compression turned on -- most of the time I still have the
buffering problem I mentioned earlier: When Grex pauses for
input, the last one or two characters of output aren't displayed
until I actually type something. Does anybody else experience
this problem?

If I dumb down my modem a bit by turning off error correction
and data compression, and set both the modem and serial port to
talk at 2400 baud, things generally work fine.

Also, things work fine when I'm connected at 14.4 through
groupie.
dang
response 192 of 364: Mark Unseen   Jul 24 21:27 UTC 1997

I got the garbled modem stuff again and I persisted in sending more breaks
than I had in the past, and lo and behold, the junk magically cleared into
a login prompt. :)
tsty
response 193 of 364: Mark Unseen   Jul 24 21:53 UTC 1997

just a question... about the modei... weren't we all told that the old
2400 (beaten to death but still merry) supra modei on the -3000 queue had
been replaced with the newer/faster/better/v.XXX stuff and now we could
forget about dumbing down our -3000 calls?
  
it should be noted, actually, that when #117 was entered (GASP!!!) it was
entered not only from -3000, but also tty h4! (aren't intermittants such
fun<G>)

this particular connnection at the moment is a -3000 dial ending up
on tty h9, with all v.xxxx working fine.  oh, well.
remmers
response 194 of 364: Mark Unseen   Jul 24 23:53 UTC 1997

Yes, the assertion was made that we didn't have to dumb down
anymore. Doesn't seem to work reliably, though.
senna
response 195 of 364: Mark Unseen   Jul 25 02:33 UTC 1997

I've gotten the same problem John has.
albaugh
response 196 of 364: Mark Unseen   Jul 28 17:11 UTC 1997

Last night around 1am I twice got a modem answer on the fast number for the
first time in ages, but in both cases no "real" connection was established,
as after the modem-to-modem chit-chat ended, my dialer kept counting seconds,
and there was no "CONNECTED 9600" or whatever message.  Then I tried the slow
number, and the first connection at 2400 did not result in a grex session.
At this point my fast modem is totally useless for contacting grex.  :-(
senna
response 197 of 364: Mark Unseen   Jul 28 20:07 UTC 1997

For some reason picospan is ignoring the spaces between responses. 
Everything's sandwiched in.
valerie
response 198 of 364: Mark Unseen   Jul 28 20:45 UTC 1997

This response has been erased.

valerie
response 199 of 364: Mark Unseen   Jul 28 20:48 UTC 1997

This response has been erased.

 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-249   250-274   275-299   300-324   325-349   350-364     
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss