|
|
| Author |
Message |
| 25 new of 283 responses total. |
russ
|
|
response 25 of 283:
| 
Jan 9 01:36 UTC 1999 |
There is a problem with sz; it appears to fail on longer files due
to some problem with flow control. It starts dying at about 5K,
and will transmit files up to about 7k but not 10k.
|
jshafer
|
|
response 26 of 283:
|
Jan 9 01:37 UTC 1999 |
Am having trouble "forgetting" items in Backtalk. (I'm using Pistachio,
and of course am registered.) I just checked a quite a list of Agora
items to forget, and when I clicked the "Forget selected items" button
only about half of the items ended up being forgotten. I have tried
re-forgetting the remaining items several times with no effect.
Suggestions?
|
mic
|
|
response 27 of 283:
|
Jan 9 01:58 UTC 1999 |
Hmm, I don't use backtalk a lot, but you might want to query srw and janc -
the designers I believe.
|
orinoco
|
|
response 28 of 283:
|
Jan 9 02:02 UTC 1999 |
I have a problem that may or may not be related to jshafer's - I use picospan,
and every once in a while it will forget that I've forgotten an item. THat
is, it'll show me the item again as new, even though I've forgotten it.
|
jshafer
|
|
response 29 of 283:
|
Jan 9 02:31 UTC 1999 |
Mic: I thought of mailing janc about it, but I thought I'd mention it here in
case anyone else was having trouble...
|
mrmat
|
|
response 30 of 283:
|
Jan 9 04:12 UTC 1999 |
All I've been getting on my screen is gibberish when I've been dialing in the
last few days. I'm not sure this is getting through.
.
|
mic
|
|
response 31 of 283:
|
Jan 9 05:06 UTC 1999 |
Re: # 29 - John, that's cool - that's what this conference item is for (:
|
jshafer
|
|
response 32 of 283:
|
Jan 9 09:55 UTC 1999 |
Update: I quit backtalk, telnetted in and forgot about 7 items.
Upon my return to agora via backtalk later this morning, 4 of those
items were still on my "current items" list!
I tried going into one of the items and using that forget button, but
it just reset the current page without even attempting to connect to
grex. (I did, later, succeed in forgetting that particular item.)
Did I somehow get a corrupted config file? It didn't seem to loose
track of which responses I've read.
|
deblack
|
|
response 33 of 283:
|
Jan 9 17:55 UTC 1999 |
Perhaps your agora participation file is corrupt.
|
davel
|
|
response 34 of 283:
|
Jan 9 18:08 UTC 1999 |
I don't know off hand what happens if you close your telnet session without
either exiting Picospan or at least going to another conference, but it seems
possible that your participation file doesn't get updated.
(There is a command - I think it's "set autosave" which, for your current
session, causes Picospan to update your participation file as you deal with
each item. That might fix your problem.)
|
orinoco
|
|
response 35 of 283:
|
Jan 9 19:01 UTC 1999 |
That sounds like it might be what's happening to me, since I usually don't
quit picospan before I quit. Hmm...
|
valerie
|
|
response 36 of 283:
|
Jan 10 00:33 UTC 1999 |
This response has been erased.
|
remmers
|
|
response 37 of 283:
|
Jan 10 16:34 UTC 1999 |
The official address for reporting Backtalk problems is
backtalk@hvcn.org .
|
gregb
|
|
response 38 of 283:
|
Jan 11 15:29 UTC 1999 |
Re. 24: That's an assumption, not a fact. And you know what they say about
assuming... 8-)
|
keesan
|
|
response 39 of 283:
|
Jan 11 16:42 UTC 1999 |
I got busy signals for a few minutes at a time three times with week, at 4
and 7 pm on a weekday and about 6 last night (Sunday). This is tolerable,
but I would not want to see another phone line dropped. It took only about
5 minutes wait to finally get connected. How long do telnetters wait?
|
steve
|
|
response 40 of 283:
|
Jan 11 16:47 UTC 1999 |
The telnet queue is such that on the average, 3 people a minute can
get in. I've been #75 in the queue a couple of times now, and it took
just under half an hour to get in.
|
keesan
|
|
response 41 of 283:
|
Jan 11 17:01 UTC 1999 |
I certainly cannot complain about the phone wait, then.
|
orinoco
|
|
response 42 of 283:
|
Jan 11 21:35 UTC 1999 |
Yeah, I've been noticing the busy signals too. Of course, this is just more
evidence that you notice what goes wrong, not what goes right - what I
should've found curious was the half-year without any busy signals. Did the
number of people dialing in drop and then rise again, or did we add more lines
a while ago that are just now being filled up, or what?
|
aruba
|
|
response 43 of 283:
|
Jan 11 21:41 UTC 1999 |
We dropped two lines in November.
|
jiffer
|
|
response 44 of 283:
|
Jan 12 00:19 UTC 1999 |
Grex is very laggie today,a nd is sropping people left in right who telnet
in.
|
scg
|
|
response 45 of 283:
|
Jan 12 00:32 UTC 1999 |
cisco1.detroit#sho ip bgp 204.212.46.130
BGP routing table entry for 204.212.44.0/22, version 4394286
Paths: (3 available, best #1)
4239 6347 1239 2914 234
209.142.234.74 (metric 85) from 209.142.192.90 (209.142.226.220)
Origin incomplete, localpref 100, valid, internal, best
1225 234, (suppressed due to dampening)
207.57.10.109 from 207.57.10.109 (131.103.0.30)
Origin IGP, localpref 100, valid, external
Dampinfo: penalty 2711, flapped 96 times in 06:51:18, reuse in 00:27:50
1225 234, (received-only)
207.57.10.109 from 207.57.10.109 (131.103.0.30)
Origin IGP, localpref 100, valid, external
|
cmcgee
|
|
response 46 of 283:
|
Jan 12 01:37 UTC 1999 |
I've had trouble dialing in to Grex several times today. Each time my
computer would signal that I'd connected (sounded right from the modem sounds,
too) but then I would sit for over a minute waiting for the "welcome to grex,
it may take a few minutes to log on" announcement. I never got it, 'cause
I gave up after 90 seconds. This was happening on 3000, 4931, 5041.
|
i
|
|
response 47 of 283:
|
Jan 12 01:44 UTC 1999 |
Similar here, but tried only the first & last of those #'s, waited about a
minute after getting the connection, then telnetted.
|
steve
|
|
response 48 of 283:
|
Jan 12 02:16 UTC 1999 |
I know that Grex has had some problems being on the net today.
|
davel
|
|
response 49 of 283:
|
Jan 12 03:20 UTC 1999 |
I also just encountered my first busy signal in a long time (calling Grex,
I mean). Retry a minute later got me in. So we are at the point when the
available lines are occasionally saturated. Not a big problem, at this point.
|
