home *** CD-ROM | disk | FTP | other *** search
-
- NCSA Telnet Digest Friday, February 17, 1989 Volume 2 : Issue 18
- --------------------------------------------------------------------
- Subjects:
- 3C505 driver
- Problem with Kinetics EtherPort/SE
- --------------------------------------------------------------------
- Date: Tue, 14 Feb 89 17:40:35 CST
- From: timk (Tim Krauskopf)
- Subject: 3c505 driver for v2.2
-
- We have some outside contributors to thank.
-
- Bruce Orchard
- Waisman Center on Mental Retardation and Human Development
- University of Wisconsin-Madison
-
- Warren Van Houten <vanhouten@uv4.eglin.af.mil>
-
- Bruce wrote a driver for NCSA Telnet for the PC v2.1 for the 3C505
- board last summer. Warren modified it recently to fit in with the
- calling conventions of NCSA Telnet v2.2.
-
- You need to make a few mods and recompile NCSA Telnet to get this
- to work. It is "technically" unsupported by NCSA, but we would like to know
- about any problems you have with its use.
-
- The assembler source file is posted in the contributions directory
- on our server.
-
- Tim Krauskopf
- NCSA
-
- --------------------------------------------------------------------
-
- From: Stephen Sakamoto <steph@CS.UCLA.EDU>
- Subject: Problems with Telnet 2.2
-
- I am trying to use NCSA Telnet 2.2 on a MacSE with Kinetics EtherportSE
- installed. I can get connections to various machines, but, the problem is that
- all the connections will eventually hang. I can close the connection, but,
- reconnection results in a failure. I get the message 'host or gateway not
- responding'. If i quit and restart Telnet i can connect again, but, the
- connections will eventually hang again. I am using System version 6.0.2,
- with 2.5M installed.
-
- Stephen Sakamoto
- UCLA Computer Science Department
- (213) 825-2145
-
-
- [
- I am hearing a lot of reports like this, and we have duplicated it
- somewhat. Other users' experiences might help us resolve this problem.
- I am working with Kinetics right now to get them an accurate bug report
- that will get them started on the problem. I have not been able to
- trace this to any particular INIT, etc.
- We do not have any such problems on the EtherPort II, but we see it on
- the EtherSC and the EtherPort SE.
-
- Tim K.]
-
-
-