Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!m.cs.uiuc.edu!s.cs.uiuc.edu!meyer
From: meyer@s.cs.uiuc.edu
Newsgroups: comp.sys.ibm.pc
Subject: Re: NCSA Telnet under 286 Windows
Message-ID: <213400055@s.cs.uiuc.edu>
Date: 14 Sep 89 15:16:00 GMT
References: <5139@portia.Stanford.EDU>
Lines: 19
Nf-ID: #R:portia.Stanford.EDU:5139:s.cs.uiuc.edu:213400055:000:989
Nf-From: s.cs.uiuc.edu!meyer    Sep 14 10:16:00 1989



Regarding the Base note's question, It is not a good idea to run NCSA telnet
from within Windows/286.  This is because when you switch to another 
application, all processing in telnet will typically stop.  According to one of the design team, telnet must do certain tasks on the adapter on a very regular
basis.  When it cannot do this regularly, the connections close automatically.
This may be a function of the adapter, I'm not sure.

I'm also not sure if this will work, but you may want to try it under Windows
/386.   Since Windows/386 will time slice reasonably well, you may be able to
get it to work.  One problem I can foresee is one with the '386 and memory
mapping... time slicing combined with memory mapping can cause problems when
a process (such as a network routine) gains control during the wrong process's
time slice - when the '386 is workingf in the wrong block of memory.

Good Luck!
Don Meyer		meyer@s.cs.uiuc.edu

        "I'm _theory_, that's a _real_ problem."