|
|
| Author |
Message |
| 25 new of 181 responses total. |
scg
|
|
response 140 of 181:
| 
Nov 17 02:46 UTC 1998 |
Right. You only get all the lines if you dial in on 761-3000. That's why
people should dial in on 761-3000.
|
hhsrat
|
|
response 141 of 181:
|
Nov 17 16:19 UTC 1998 |
11am-1pm is a pretty busy time to telnet in
|
tsty
|
|
response 142 of 181:
|
Nov 18 11:40 UTC 1998 |
i started out as #87 in line... 2.5 hours ago...
|
krj
|
|
response 143 of 181:
|
Nov 18 16:48 UTC 1998 |
I started item:128 for whining about the telnet queue.
(Yes, I'm one of the whiners.)
|
keesan
|
|
response 144 of 181:
|
Nov 18 22:39 UTC 1998 |
I have been unable to reach grex for two days, after changing to dialing 3000
instead of 5159. Jim set Procomm up to time out after 30 sec, I have not been
able to figure out how to make this longer, anyone happen to know? I finally
dialed 5159 again and got connected immediately. Sent a couple of files via
M-Net and they don't seem to support x or y modem. Is there some way to set
up the trunk thing so that if the last couple of numbers are busy it goes back
to the beginning?
|
davel
|
|
response 145 of 181:
|
Nov 19 02:48 UTC 1998 |
Sindi, is this DOS Procomm Plus? It's been a long time, but I might be able to
check ...
|
davel
|
|
response 146 of 181:
|
Nov 19 02:53 UTC 1998 |
(If it's Windows Procomm, change it thus: open the dialing directory. In the
menu bar at the top, click on Options, then on Call Settings. But I think
I remember that you're using DOS Procomm ... vague memory says to me that it's
somehow through the dialing directory in that, too; could be wrong.)
|
bean
|
|
response 147 of 181:
|
Nov 19 04:11 UTC 1998 |
20 waiting, 26 remote, 4 local users, 72 max remote users, 6735 head
Okay, I give up, why are 20 waiting if only 26 are on?
|
scott
|
|
response 148 of 181:
|
Nov 19 11:55 UTC 1998 |
If DOS, try hitting the End key while it is dialing.
|
keesan
|
|
response 149 of 181:
|
Nov 19 18:21 UTC 1998 |
I hit the end key while dialing, but also had to hit return key in order for
the count to resume. Reset to 60 sec, it still timed out on both 3000 and
5141 at 9600. After five or so tries, I finally tried 3000 at 2400 and
connected in 12 sec total. The attempt at 9600 gave me a high-pitched squeal
at about 25 seconds that continued to 60 sec. (5059 gets a recording, this
number no longer in service). This problem started two days ago. I dialed
M-net okay and got through to 3000 at 9600 yesterday, so assume my modem ok.
Can anyone explain why the lower speed will connect but not 9600?
|
keesan
|
|
response 150 of 181:
|
Nov 19 23:29 UTC 1998 |
Changing the wait time with end is only temporary, it seems.
Again I could not get through at 9600, should I wait more than 60 sec?
2400 bps worked in exactly 12 sec. Is there a bad line from here to there?
They fixed a break in it in August when it went dead.
|
scg
|
|
response 151 of 181:
|
Nov 20 01:52 UTC 1998 |
You might also try a different modem.
|
mcnally
|
|
response 152 of 181:
|
Nov 20 07:24 UTC 1998 |
I agree.. Sounds like your modem doesn't negotiate well with at least
one of the early trunk modems. Given that you presumably have access to
a pool of cheap used modems at Kiwanis, why not try another for a while?
|
keesan
|
|
response 153 of 181:
|
Nov 20 22:33 UTC 1998 |
But why did my modem connect okay to Arbornet at 9600 bps in 19 seconds, but
not in 60 sec to Grex 3000 or 5041, and just fine at 2400? And why did it
work until three days ago? I will try another modem and report back.
(Or maybe grex should replace the problem modem? What is the high-pitched
squeal that I got after 25 seconds on grex at 9600?
|
mdw
|
|
response 154 of 181:
|
Nov 21 02:42 UTC 1998 |
That's the pig.
|
scg
|
|
response 155 of 181:
|
Nov 21 04:14 UTC 1998 |
There are standards for how modems are supposed to communicate at various
speeds. If all manufacturers stuck exactly to the standards, all modems would
talk to eachother. In practice, that's not the case. Many, perhaps most,
modems deviate from the standards in one way or another, but have generally
been tested carefully to make sure that they will still talk to modems that
do adhere to the standards. However, when you get two modems that deviate
from the standards in opposite directions, you start having trouble.
|
valerie
|
|
response 156 of 181:
|
Nov 22 01:39 UTC 1998 |
This response has been erased.
|
other
|
|
response 157 of 181:
|
Nov 22 13:22 UTC 1998 |
8:22am up 3 days, 18:31, 3 users, load average: 0.22, 0.14, 0.00
|
keesan
|
|
response 158 of 181:
|
Nov 23 01:02 UTC 1998 |
Jim suggested a dirty contact, unplugging and replugging, but just in case
we switched modems and connected with a Compudyne in 22 sec. If it had been
modem incompatibility I would not have been using grex for the past six months
with the other modem.
|
scg
|
|
response 159 of 181:
|
Nov 23 01:59 UTC 1998 |
That's not quite true. Grex has two different kinds of modems in its hunt
group. That is, they're the same brand and model and everything, but they
made some changes at some point so the newer ones are different from the older
ones. It's possible that when you started dialing into the beginning of the
hunt group instead of somewhere near the end, you started using a different
version of the modem on Grex's end than you had been using before.
|
keesan
|
|
response 160 of 181:
|
Nov 24 19:23 UTC 1998 |
I was dialing to both 5159 and 3000 and connecting fine. My new modem does
not put garbage on the screen in random places like the old one seems to have
been responsible for doing (a screenful when I logged off).
|
senna
|
|
response 161 of 181:
|
Nov 26 09:27 UTC 1998 |
Okay, I'm going to be picky and bring up my text droppage problem again. The
difficulty appears to originate from my computer at some point, but it's still
annoying. When I recieve text, random parts (in substantial portions) get
left out. This includes all characters, including enters or line breaks, so
large amounts of text like bbs or party are very difficult to read. If
possible, this is even worse when I dial into mnet. It only occurs when I
dial in, which is when I'm using hyperterminal. Any ideas?
|
remmers
|
|
response 162 of 181:
|
Nov 26 12:13 UTC 1998 |
Sounds like a flow control problem. Check your modem and hyperterminal
settings.
|
mcnally
|
|
response 163 of 181:
|
Nov 27 06:11 UTC 1998 |
It does sound like a flow-control problem. But rather than check your
Hyperterm settings I recommend that you junk it entirely. Even if it
has nothing to do with your current problem it's practically a no-lose
move..
|
rtg
|
|
response 164 of 181:
|
Nov 29 06:08 UTC 1998 |
What do you suggest as a freely-available replacement communications
program for Win95/8?
BTW - has anyone noticed that hyperterm is distributed on the WIN98 CD,
but the installation program doesn't download it? I've been trying to get
it, or something better, loaded for a friend this week.
|
