You are not logged in. Login Now
 0-24   6-30   31-55   56-80   81-105   106-130   131-155   156-180   181-205 
 206-230   231-255   256-280   281-283       
 
Author Message
25 new of 283 responses total.
mic
response 31 of 283: Mark Unseen   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: Mark Unseen   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: Mark Unseen   Jan 9 17:55 UTC 1999

Perhaps your agora participation file is corrupt.


davel
response 34 of 283: Mark Unseen   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: Mark Unseen   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: Mark Unseen   Jan 10 00:33 UTC 1999

This response has been erased.

remmers
response 37 of 283: Mark Unseen   Jan 10 16:34 UTC 1999

The official address for reporting Backtalk problems is 
backtalk@hvcn.org .
gregb
response 38 of 283: Mark Unseen   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: Mark Unseen   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: Mark Unseen   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: Mark Unseen   Jan 11 17:01 UTC 1999

I certainly cannot complain about the phone wait, then.
orinoco
response 42 of 283: Mark Unseen   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: Mark Unseen   Jan 11 21:41 UTC 1999

We dropped two lines in November.
jiffer
response 44 of 283: Mark Unseen   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: Mark Unseen   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: Mark Unseen   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: Mark Unseen   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: Mark Unseen   Jan 12 02:16 UTC 1999

   I know that Grex has had some problems being on the net today.
davel
response 49 of 283: Mark Unseen   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.
krj
response 50 of 283: Mark Unseen   Jan 12 03:33 UTC 1999

My calls to Grex have been getting answered by a modem which does not 
respond further for about the last fifteen minutes.  Apparently the 
same problem as reported in #46 and #47.  This final time I got lucky, 
I guess.
aruba
response 51 of 283: Mark Unseen   Jan 12 04:00 UTC 1999

Yeah, I think krj and I were competing for that modem that doesn't connect
right, because all the other lines were full.  The fact that Grex answered
every few tries but didn't connect meant that my attack-dial script wasn't
very effective, and I had to keep restarting it.  Scott, is there any way to
fix that modem?  Do you know which one it is?

Before I finally got in, I tried changing the speed I was calling at from
14400 to 9600, on a lark.  I got in right after that, but I can't say if it
was on the modem that's been having problems.
n8nxf
response 52 of 283: Mark Unseen   Jan 12 12:30 UTC 1999

I was unable to log in via modem today.  It would connect then nothing.
I'm in on a telnet right now.
void
response 53 of 283: Mark Unseen   Jan 12 13:10 UTC 1999

   same here.  i'm here via backtalk.
dpc
response 54 of 283: Mark Unseen   Jan 12 14:47 UTC 1999

I dial in.  Yesterday afternoon about 4:30 I dialed -3000 and I *think*
I got no response at all.  I tried several other dialins and got busies.
        Just now, I got "modem answers but no Grex" on -3000.  Then I
got in on -4931.
scott
response 55 of 283: Mark Unseen   Jan 12 15:49 UTC 1999

OK, OK, I'll fix it.  ;)
 0-24   6-30   31-55   56-80   81-105   106-130   131-155   156-180   181-205 
 206-230   231-255   256-280   281-283       
Response Not Possible: You are Not Logged In
 

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