|
|
| Author |
Message |
| 25 new of 124 responses total. |
ryan
|
|
response 61 of 124:
| 
May 4 13:29 UTC 1999 |
This response has been erased.
|
keesan
|
|
response 62 of 124:
|
May 4 17:02 UTC 1999 |
I got write failed a few times yesterday, and a new user got it the first time
he tried to send an email a few days before that.
Re 53 direct dial, problem resolved itself somehow, no hardware changes that
I know of.
Write failed both in email and in bbs yesterday.
|
keesan
|
|
response 63 of 124:
|
May 5 18:22 UTC 1999 |
Today I dialed in several times and it sounded like it was connecting, but
timed out in 45 seconds. Just got through with no trouble now. Should I set
it at 60 seconds?
|
davel
|
|
response 64 of 124:
|
May 6 00:57 UTC 1999 |
Yes.
|
keesan
|
|
response 65 of 124:
|
May 7 18:08 UTC 1999 |
I fixed the problem, which keeps recurring, by not using the dialing program
of Procomm but instead typing in atdt 7613000. This connects almost
immediately instead of a 20 second wait time. Why? I had been having this
problem for a week already. Is anything different at the grex end?
|
keesan
|
|
response 66 of 124:
|
May 7 18:31 UTC 1999 |
I found the original version of procomm plus and that dials fine and the
cursor works. The version that the grex batch file points to has some bugs
in it somewhere, I tried comparing settings and did not see any differences
in general modem options, where should I look for problems? (The arrow keys
will not work even when I connect with atdt in the bat version). I will go
back to do things the slightly longer way. I should figure out just what the
batch file Jim wrote is doing. He said Procomm will scatter copies of itself
around if you put procomm directory on the path.
|
davel
|
|
response 67 of 124:
|
May 7 18:47 UTC 1999 |
Check what terminal emulation gets chosen.
|
keesan
|
|
response 68 of 124:
|
May 7 19:12 UTC 1999 |
We fixed that, it was set to ANSI but we changed it to VT102 (I think - maybe
the change did not get made permanent? I will check again).
|
scg
|
|
response 69 of 124:
|
May 8 00:07 UTC 1999 |
I'm guessing procomm is probably sending some init string along with the
dialing, which confuses things.
|
bdh1
|
|
response 70 of 124:
|
May 8 07:11 UTC 1999 |
Most unix-es don't know ANSI from a hole in the ground. Thank-You
Micro$oft. If you use the micro$oft telnet program to telnet to a unix
host the 'negotiation' of the connection will result in a TERM of
'ANSI'. I'm so sure this was not deliberate on the part of micro$oft.
I'm so sure this was not another deliberate act on micro$oft's part to
deliberately screw things up. Unix hosts need merely symbolically link
the vt100 entry in the /usr/lib/terminfo/t directory to
/usr/lib/terminfo/a/ansi to accomidate brain dead micro$oft users.
(If you are an older version of unix you need to duplicate the vt100
stanza of /etc/termcap as ANSI|ansi).
|
jazz
|
|
response 71 of 124:
|
May 8 11:30 UTC 1999 |
ANSI is a valid termcap, and in this case it's not an inherent weakness
of Microsoft, but of most UNIX implementations, that ANSI isn't recognized.
Who uses Windows telnet anyways?
|
remmers
|
|
response 72 of 124:
|
May 8 12:03 UTC 1999 |
Lots of people use Windows telnet. Far, far too many. That's because it
comes with Windows, and most users aren't savvy enough to know how to
improve the situation.
But I agree with jazz that the weakness with ANSI is with Unix
implementations. Grex has a pretty decent ANSI termcap, but that's an
exception.
|
jazz
|
|
response 73 of 124:
|
May 8 12:20 UTC 1999 |
The program itself has a host of other weaknesses: a very poor scroll
buffer implementation, poor terminal capability support, bad colours, and a
tendency to stop responding at random intervals. If a user's not savvy enough
to go to download.com and install something better, then they really deserve
what they get - I still insist computers should not be for the stupid. :)
|
drew
|
|
response 74 of 124:
|
May 8 17:35 UTC 1999 |
/a is *still* at 100%.
|
keesan
|
|
response 75 of 124:
|
May 9 00:22 UTC 1999 |
Procomm seems to use ANSI as a default. The problem is apparently a missing
procomm .kbd file, whatever that is, in the version of it that somehow created
itself in another place on my computer when I put procomm on the path and ran
a batch file. I have no idea where this place is. The original version access
without the batch file works fine.
|
drew
|
|
response 76 of 124:
|
May 10 00:22 UTC 1999 |
In addition to #74 - and probably because of it - I found 135 brandnew items
upon entering BBS.
|
keesan
|
|
response 77 of 124:
|
May 10 21:04 UTC 1999 |
I fixed my Procomm problem by discovering a few pcplus files lurking in the
WP directory and deleting them. It now works even with pcplus on the path,
which Jim thought had been the problem. I am attempting to figure out what
is on my computer and what it does so I can learn to transfer all the useful
stuff to another computer before the last 1.4M fills up with files. (First
thing to do is eliminate Windows 3.1 and four viewer programs based on it.)
All sorts of files lurking in odd places, some came with, some added later.
The new computer is half the size and four times the HD size, and the old one
about the size of a PS/2 386 tower but on its side.
|
vanders
|
|
response 78 of 124:
|
May 11 11:28 UTC 1999 |
Unfourtunatly, i'm forced to use Windows Telnet, as my employers would not
be impressed if i started downloading & installing files onto their computers.
If i could, i'd get a nice SSH client & make use of my other shells. But i
can't. *sigh*
|
drew
|
|
response 79 of 124:
|
May 12 19:46 UTC 1999 |
Mail from my current ISP is bouncing. The message I get back says:
Hi. This is the NetZero mail server.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<drew@cyberspace.org>:
204.212.46.130 does not like recipient.
Remote host said: 553 <drew@cyberspace.org>... One generation passeth away,
and another generation cometh: but the earth abideth for ever.
Giving up on 204.212.46.130.
Huh!!??
|
dang
|
|
response 80 of 124:
|
May 12 19:48 UTC 1999 |
This is a message from Grex's spam filter. Talk to Marcus about it,
maybe he can tell you how to get it through. I'd guess that this
particular message resembles closely a common spam message. Try
changing the subject line.
|
drew
|
|
response 81 of 124:
|
May 13 20:24 UTC 1999 |
Changing the subject does not work. Perhaps all mail from this site is
rejected automatically? Seems logical - it is effectively possible for anyone
to get an account and be active without passing any kind of ID check - if only
for just enough time to spew out a single burst of spam.
Still, the message says "host doesn't like *recipient*...", and I recall a
file successfully making it here from there.
|
mdw
|
|
response 82 of 124:
|
May 14 00:09 UTC 1999 |
None of grex's anti-spam checks look at *just* the subject value, and
actually, very few pay any attention to the subject value except for
logging purposes.
The "One generation passeth away, and another generation cometh: but the
earth abideth for ever." messages indicate a mail configuration error in
the server. There is almost certainly nothing you, as a user, can do
about this problem, because it has nothing to do with any part of your
mail. Changing the subject line will definitely have no effect, because
this error is generated before grex ever sees your mail. Legitimate
mailers that properly follow the guidelines of RFC 821 and RFC 1123 will
never encounter this problem. Spam mail packages (and other PC based
mail packages) frequently encounter this problem when talking directly
to grex, for various obscure technical reasons.
You have the following options:
(1) don't use this vendor for email.
(2) if you must use this vendor for email, don't forward mail from it
to grex.
(3) if you must use this vendor, and want email forwarding to work
you will need to get their postmaster or system adminstrator
to contact postmaster@cyberspace.org .
|
blight
|
|
response 83 of 124:
|
May 14 04:06 UTC 1999 |
Is Grex having problems with the mail que? For about three
days whenever I try to use Pine to check my mail I get the
message "cannot open folder /var/spool/mail/blight --no such
folder." I sent myself some mail from another email account
and Pine is still unable to find my mailbox. The only things
I have changed are that I'm now using secure shell to login
instead of ordinary telnet and I changed my shell from
csh to bash. What can I do about this?
|
aruba
|
|
response 84 of 124:
|
May 14 13:09 UTC 1999 |
That's the wrong name for your e-mail file; it should be
/var/spool/mail/b/l/blight
You can tail that file to get your latest messages. For a longer term
solution, though, I'm not sure.
|
ryan
|
|
response 85 of 124:
|
May 14 13:27 UTC 1999 |
This response has been erased.
|
