You are not logged in. Login Now
 0-6   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.
rcurl
response 6 of 283: Mark Unseen   Dec 26 01:43 UTC 1998

I am unable to connect via compuserve. I get a login prompt, but that is
quickly dropped with a message that the connection was closed by the host.
I am now connected via a double telnet via Michnet.
janc
response 7 of 283: Mark Unseen   Dec 28 17:40 UTC 1998

Re resp:3:

  Grex actually has three MOTD files - the one with the ICNET message,
  the one with the birthday announcments, and the one with everything
  else.  I think Backtalk doesn't do the ICNET one, which is kind of
  OK, since we no longer use ICNET's connection.  Other than this, and
  formatting, they should always be the same.
steve
response 8 of 283: Mark Unseen   Dec 29 16:04 UTC 1998

   Grex ran out of space on the "/a" partition at 3:54am today.  An
idiot was FTPing an entire OS here (beos) but ran out of Grex before
it ran out of beos to FTP.  Removed it.
keesan
response 9 of 283: Mark Unseen   Dec 29 17:06 UTC 1998

STeve, when do you sleep?
steve
response 10 of 283: Mark Unseen   Dec 29 17:43 UTC 1998

   At those various off times when 1) kids 2) work 3) grex allows it.
jared
response 11 of 283: Mark Unseen   Dec 30 03:22 UTC 1998

that should have been 
when {kids, work, grex} allows it
steve
response 12 of 283: Mark Unseen   Dec 30 03:36 UTC 1998

   Hey, the kids encourage grex work--or they can't get on maybe.
aruba
response 13 of 283: Mark Unseen   Jan 4 18:18 UTC 1999

I've been unable to dial in for the last couple of hours; the modem connects,
but then I don't get any text.  I'm telnetted in now.
keesan
response 14 of 283: Mark Unseen   Jan 4 18:21 UTC 1999

I just dialed in okay, shortly before you telnetted in.
scott
response 15 of 283: Mark Unseen   Jan 4 20:36 UTC 1999

There is apparently one evil modem that is doing that "connect but no message"
bit.
gregb
response 16 of 283: Mark Unseen   Jan 4 20:45 UTC 1999

Request to all:  To help keep track of what response goes with which 
msg., please try to remember to put the original msg. # in your 
response.  Some of these confs. have a rapid turnover, which means it's 
possible to come into a conf and read msgs. that have no apparent 
meaning, unless you know which msg. was the origin.

Those that are already doing this, it's appreciated.
rcurl
response 17 of 283: Mark Unseen   Jan 4 21:32 UTC 1999

(This announcement is getting as bad as that $24,000 for $6 thing...:) )
keesan
response 18 of 283: Mark Unseen   Jan 5 02:31 UTC 1999

At least it was well meant.  I always read confs from the beginning and have
not found it a problem to figure out what was being referred to.
jared
response 19 of 283: Mark Unseen   Jan 5 02:57 UTC 1999

put "b n" in your .cfrc
i
response 20 of 283: Mark Unseen   Jan 5 04:08 UTC 1999

Got busy signals ~1 hour ago.  Then could only get through on a too-noisy-
to-use line.  (Dialed elsewhere & telnetted some, so probably not my stuff
or line.)  I'm in on a good dial-in now.
gregb
response 21 of 283: Mark Unseen   Jan 6 15:06 UTC 1999

Re. 17:  Since not everybody reads all confs., this seemed like the logical
course of action.  If you have a viable alternative that accomplishes the same
thing, let me know.
remmers
response 22 of 283: Mark Unseen   Jan 6 17:45 UTC 1999

(But that doesn't explain why you put it in multiple items in the *same*
conference.)
gregb
response 23 of 283: Mark Unseen   Jan 8 14:39 UTC 1999

Re. 22:  Wrong wording on my part.  I should have said "item," though my
previous statement still applies.
keesan
response 24 of 283: Mark Unseen   Jan 8 20:15 UTC 1999

I think just about everyone reads the first couple of items.
russ
response 25 of 283: Mark Unseen   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: Mark Unseen   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: Mark Unseen   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: Mark Unseen   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: Mark Unseen   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: Mark Unseen   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.
 .
 0-6   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