|
|
| Author |
Message |
| 25 new of 364 responses total. |
scg
|
|
response 225 of 364:
| 
Aug 2 07:15 UTC 1997 |
SunOS 4.something is the old SunOS that Grex is running. SunOS 5.5 is
Solaris, if I'm remembering correctly. Will SunOS 4 binaries run on Solaris
without doing something special?
|
remmers
|
|
response 226 of 364:
|
Aug 2 12:45 UTC 1997 |
Re #223 and preceding: Since you asked for a fix, I took the
liberty of editing your .login file to replace the line
eval `tset -s vt102`
by
tset vt102
Seems to have fixed things. Problem may have been that
tset has been re-defined as a global alias.
|
valerie
|
|
response 227 of 364:
|
Aug 2 13:07 UTC 1997 |
This response has been erased.
|
valerie
|
|
response 228 of 364:
|
Aug 2 13:11 UTC 1997 |
This response has been erased.
|
remmers
|
|
response 229 of 364:
|
Aug 2 15:47 UTC 1997 |
Right, I think that with 'tset' defined as a global alias the
way we've done it, you don't want the 'eval'. Either that, or
precede the tset with a backslash, as in
eval `\tset -s vt102`
to make the shell use the 'real' tset instead of the alias.
|
valerie
|
|
response 230 of 364:
|
Aug 3 22:58 UTC 1997 |
This response has been erased.
|
kaplan
|
|
response 231 of 364:
|
Aug 4 03:48 UTC 1997 |
Re 225: SunOS 4.x binaries do run in a special compatability mode on SunOS
5.x (aka Solaris 2.x) but in my expirence, it is not 100% stable. It is
probably worth seeking out a native Solaris 2.x version of Netscape.
|
remmers
|
|
response 232 of 364:
|
Aug 4 12:00 UTC 1997 |
Re #230: The 'tset' alias we set up does an 'eval' and sets the
TERMCAP variable.
|
valerie
|
|
response 233 of 364:
|
Aug 4 13:44 UTC 1997 |
This response has been erased.
|
valerie
|
|
response 234 of 364:
|
Aug 5 04:30 UTC 1997 |
This response has been erased.
|
omni
|
|
response 235 of 364:
|
Aug 5 19:15 UTC 1997 |
Thank you. I was stuck at #62 a few nights ago. I stayed.
|
tsty
|
|
response 236 of 364:
|
Aug 6 05:55 UTC 1997 |
....hmmm, re #234. happens that way....doesn't it.
|
aruba
|
|
response 237 of 364:
|
Aug 6 12:53 UTC 1997 |
I haven't been able to get in when dialing 761-3000 or 761-3411, but 761-3451
works fine. What happens on the other two is, my modem makes all the noises
that I expect from a successful connection, but then doesn't ever finish the
connection. I have my script set to time out if it doesn't receive CONNECT
back from the modem in 30 seconds - should I make that higher?
It has been like this for several day; possible longer.
|
richard
|
|
response 238 of 364:
|
Aug 6 22:44 UTC 1997 |
*arg* I was number 53 in the wait que a while ago. Is the idle time
zapper zapping properly? I really think there needs to be a max cap on the
que
Grex shouldnt ever beholding more than twenty or twenty five people in
line atanyone time.
\.
|
senna
|
|
response 239 of 364:
|
Aug 6 23:06 UTC 1997 |
That would remove the purpose of the queue, richard, becuase then we'd still
be vulnerable to telnet attacks and the like.
|
tsty
|
|
response 240 of 364:
|
Aug 7 02:40 UTC 1997 |
i've quit using -3000; i have had zero problems since the change.
|
srw
|
|
response 241 of 364:
|
Aug 7 02:46 UTC 1997 |
I am experiencing the same problems as mark. I can no longer connect to
any of the available dialups. The modems won't negotiate a connection.
Obviously some people are able to. I am using a rather vanilla 28.8
modem. I'm no longer suppressing MNP. I think the problem is with Grex's
modems.
|
tsty
|
|
response 242 of 364:
|
Aug 7 05:01 UTC 1997 |
are yuo all getting the same 'pretty pictures' as i was getting? <g>
|
scg
|
|
response 243 of 364:
|
Aug 7 08:48 UTC 1997 |
The first time I tried to dial up tonight the modem started negotiating, and
then went back to making the high pitched noise as if it had just answered.
I hung up and tried again and it worked. The number I was dialing was
761-4931, so it was something above that in the hunt group. If it weren't
for all the other stories here, I would have been ready to blame my modem for
it, but it sounds like it might have been one of Grex's modems.
|
senna
|
|
response 244 of 364:
|
Aug 7 13:56 UTC 1997 |
I've recieve zero problems when I'm not dialing 3000.. which is to say when
I dial 5041 which is only at off hours when it's actually free
|
i
|
|
response 245 of 364:
|
Aug 7 22:31 UTC 1997 |
Similar here - I started dialing -9671 (first 9600 line) and my problems
have vanished (and I've always gotten through!).
|
scott
|
|
response 246 of 364:
|
Aug 7 23:27 UTC 1997 |
(I'm planning on doing something about the modems in the next day or
two)
|
scott
|
|
response 247 of 364:
|
Aug 8 00:30 UTC 1997 |
OK, the modems are now historically accurate again (no more groupie lines).
One change: 761-4931 is now the first fast line.
|
srw
|
|
response 248 of 364:
|
Aug 8 06:09 UTC 1997 |
Thanks, Scott. I'll have to see if I continue to get problems with
negotiating. Another night maybe.
|
tsty
|
|
response 249 of 364:
|
Aug 8 06:15 UTC 1997 |
i did try -3411 a few days ago.... either garbage or pretty pictures,
depending on your term type ...<g>.
thahkxx for the modem changes.
|
