|
|
| Author |
Message |
| 25 new of 124 responses total. |
ec
|
|
response 50 of 124:
| 
Apr 18 03:51 UTC 1999 |
I'm not very back and never ceased to be on-line... but it's good to see
you're here too.
There's lovely connectivity and lately very nice weather up here in
Edmonton, Alberta!
The only problem I've ever had with mailers is that the M$ variety
thinks it's appropriate to quote all special characters with single
quotes... including single quotes. :-P
|
mary
|
|
response 51 of 124:
|
Apr 18 11:48 UTC 1999 |
Howdy, Iain. How are Jennie and Chris? I've often wondered
how it went for you three when you moved to Canada. Was that
community accepting of your unusual (threesome) relationship?
|
keesan
|
|
response 52 of 124:
|
Apr 22 02:53 UTC 1999 |
We are getting a badly scrambled screen, intermittently, lower ASCII, using
bbs, pine and lynx (the response I am typing is okay though). Has been
happening off and on for a few hours. I cannot read other responses after
the first five lines or so. (Wonder if the problem is this computer).
|
bdh1
|
|
response 53 of 124:
|
Apr 25 07:47 UTC 1999 |
Were you on a local dialup modem or telneted in? What is 'lower ASCII'?
'(Wonder if the problem is this computer)' if you mean yours not grex,
I'd bet on it. If telneted in does your screen size and TERM variable
match what you negotiated? (If you are using a Micro$oft telnet program
the answer is usually 'no' and there's your problem. Sigh.) Of course,
it is now four days later, how they hangin' now?
|
hhsrat
|
|
response 54 of 124:
|
Apr 26 01:07 UTC 1999 |
Telnetted in just now, could not run the "uptime" command
|
tsty
|
|
response 55 of 124:
|
Apr 26 04:32 UTC 1999 |
new item for specific sys problem. deserved NOT to take up space here,
as it did tehlast time <i learned, see?>
ec - dude, welcome back ... both b0xes?
|
davel
|
|
response 56 of 124:
|
Apr 27 10:41 UTC 1999 |
Re 54: there was a discussion of the uptime problem in the current system
announcements item, resps 51-55.
|
janc
|
|
response 57 of 124:
|
Apr 29 16:20 UTC 1999 |
Hi Iain. Thanks for the Backtalk bug reports. I think both of those
bugs are pretty fixable.
|
krj
|
|
response 58 of 124:
|
Apr 30 20:18 UTC 1999 |
/c and /a are full, or almost so
|
dpc
|
|
response 59 of 124:
|
May 4 13:12 UTC 1999 |
Here's what I got when I quit the mail program just now:
& q
/a: write failed, file system is full
/a: write failed, file system is full
Saved 1 message in mbox
!
So. /a is full.
|
jazz
|
|
response 60 of 124:
|
May 4 13:14 UTC 1999 |
Bad guests, over super-soft quota. :P
|
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%.
|
