You are not logged in. Login Now
 0-24   20-44   45-69   70-94   95-119   120-144   145-169   170-194   195-219 
 220-244   245-269   270-294   295-306       
 
Author Message
25 new of 306 responses total.
senna
response 45 of 306: Mark Unseen   Mar 28 04:07 UTC 1998

That would be extremely helpful, Scott, but I'm afraid my next two weekends
are absolutely jammed with theater work.  (This one included, that is)
remmers
response 46 of 306: Mark Unseen   Mar 28 13:00 UTC 1998

Re resp:44: The # turned the line into a comment. I imagine that
removing the "set ignore" line altogether would also have worked.
keesan
response 47 of 306: Mark Unseen   Mar 28 15:53 UTC 1998

According to Valerie's comments on set ignore, this was supposed to make the
system ignore line noise.  Before the changeover, Ctl-C was not interpreted
as line noise, now it seems to be.  Why?
mdw
response 48 of 306: Mark Unseen   Mar 28 20:45 UTC 1998

"mail" on the old & new systems is identical.  Both would treat "set
ignore" as meaning the same thing - to ignore the "interrupt" character.
dpc
response 49 of 306: Mark Unseen   Mar 29 00:14 UTC 1998

Valerie, if you still remember the commands that tell "mail" *not* to
display those huge mail-routing headers, could you post them in this
item?  Thanx!!
keesan
response 50 of 306: Mark Unseen   Mar 29 00:17 UTC 1998

Valerie gave me instructions how to copy her .mailrc file, where they are all
listed with comments as to what they do.  (Be sure if you simply use her file
to get rid of set ignore).
mdw
response 51 of 306: Mark Unseen   Mar 29 00:44 UTC 1998

(You want the lines that say "discard XXX".  You don't want the line at
the end that says "alternates valerie@cyberspace.org", and you may or
may not have a preference about the other things Valerie does, such as
"set ignore".)
keesan
response 52 of 306: Mark Unseen   Mar 30 01:32 UTC 1998

Just now is the second time today that I typed Pine Return, got the
Pine screen, and was immediately disconnected before doing anything else.
(Last time I might have hit i first.)
keesan
response 53 of 306: Mark Unseen   Mar 30 03:31 UTC 1998

And when I exited Pine this time, the top 2/3 of the screen continued to show
the pine menu, and the bbs scrolled by underneath it.  (Cured this by giving
the clearing command in my commun. program (Ctl-C) followed by Ctl-L).  I
don't recall this happening before.  
keesan
response 54 of 306: Mark Unseen   Mar 30 03:34 UTC 1998

I still can't read the top two thirds of the bbs response, above 'Item 3
System problems.  Previous commands and Browse (item list), Read (new items)
and on there.  SOmething is wrong.  This is new.  But it could have something
to do with my having switched from Procomm to Procomm Plus today. (This did
not happen the last few times i logged on today, thought).
Will try existing bbs and then grex to fix the problem.  Odd.
keesan
response 55 of 306: Mark Unseen   Mar 30 03:40 UTC 1998

Hanging up and redialing fixed the problem.  (I meant 'exiting' grex. and 'are
on there'.  Hard to type with stuff scrolling away like that).
steve
response 56 of 306: Mark Unseen   Mar 30 04:55 UTC 1998

  It very much sounds to me like you've had some terminal problems,
such that addressing the cursor around the screen didn't work right.
Now, which end that was (yours or grex's) I'm not sure.
  Have you changed anything on your side of things?  Is this happening
often? How long? What kind of system and what terminal software are
you using?
atticus
response 57 of 306: Mark Unseen   Mar 30 07:29 UTC 1998

Problem with BackTalk: From the list of conferences if "Do It Yourself"
is selected, BackTalk reports that there is no such conference.
keesan
response 58 of 306: Mark Unseen   Mar 30 18:33 UTC 1998

Do-it-Yourself or DIY, must be a single word without spaces.  Or Fixit.
Now that your 'backtalk problem' is fixed, please join us at DIY.

My scrolling problem occurred after changing fromProcomm to Procomm Plus. 
COuld it be related to the setting term dialup?  Happened only yesterday, and
only once.
janc
response 59 of 306: Mark Unseen   Mar 30 21:44 UTC 1998

No, that seems to be a backtalk bug.  It doesn't seem to like dashes in
conference names.  Need to investigate that.
dpc
response 60 of 306: Mark Unseen   Mar 30 21:44 UTC 1998

Thanx for the mail instructions!
tpryan
response 61 of 306: Mark Unseen   Mar 30 23:06 UTC 1998

re 56 or so,    I had a similair problem when exiting lynx and trying
to use the rest of GREX on some occassions in the past.   I would get
a short screen effectivly.
olddraco
response 62 of 306: Mark Unseen   Mar 31 01:48 UTC 1998

Minor problem or major for the ladies..but a user not on my .yeswrite
file was able to send me a tel...twice...and I hadn't sent her one
prior to it. I DID send the userid then she was on before a tel though..
so..my question is..when you exit Grex and get to the login screen again
does grex then remember that the prior user was ok to get past the
.yeswrite file? Am I making sense?
scg
response 63 of 306: Mark Unseen   Mar 31 04:47 UTC 1998

did you have mesg ne set?
dang
response 64 of 306: Mark Unseen   Mar 31 22:20 UTC 1998

The answer is yes.  Grex doesn't know or care who is on the other end of a
tel you send, it just marks that tty as being able to send to you for x amount
of time.  If you tel someone on ttyh4, for example, and then they log off and
someone else logs on to ttyh4, they can tel you until the timeout runs out.
olddraco
response 65 of 306: Mark Unseen   Apr 1 01:48 UTC 1998

Yes mesg -ne is set and always has been. Dang do you know what you
are talking about?
Thought not.
dang
response 66 of 306: Mark Unseen   Apr 1 04:04 UTC 1998

Yes, I do know what I'm talking about.  Since you ask.
jep
response 67 of 306: Mark Unseen   Apr 1 14:34 UTC 1998

Backtalk looks kind of scary this morning, since hvcn.org seems either 
down or exceedingly slow.  The icons are (mostly) not showing up.
davel
response 68 of 306: Mark Unseen   Apr 1 15:01 UTC 1998

Re 65: olddraco, can *you* read?  scg, not dang, asked about mesg -ne.  But
before you ask, *he* knows what he's talking about, and that is *definitely*
the first question to ask if someone has a problem with this.
janc
response 69 of 306: Mark Unseen   Apr 1 16:28 UTC 1998

Steve's question is sensible, Dan's explanation is correct.  Fixing this in
write would add a lot more complexity to an already amazingly complex
algorithm to decide if user A can write user B.  It's pretty rare for it to
be a problem, and it can be a problem for at most four minutes.

Steve Weiss had rebooted HVCN, so Backtalk images should be zipping again.
I'm wondering if we should relax Grex's ban on images enough to put Backtalk
button images on Grex itself.
 0-24   20-44   45-69   70-94   95-119   120-144   145-169   170-194   195-219 
 220-244   245-269   270-294   295-306       
Response Not Possible: You are Not Logged In
 

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