mikef@portia.Stanford.EDU (Michael Fallavollita) (09/07/89)
Has anyone experienced problems using NCSA Telnet under windows? I've
been running Telnet under windows, then stopping Telnet and running an
editor. When I try to go back to Telnet, it closes all my connections.
I'm using a Model 80 with qemm and smartdrive both loaded. I'm guessing
there is some sort of memory conflict and something important is getting
overwritten, but that is only a guess.
If anyone else is using Telnet under Windows, please let me know what
kind of memory configuration you are using. (EMS drivers, etc.)
Thanks in advance.
Mike
_____________
| |
| Mike's |
| 386 |
|____ _____| Michael Fallavollita
| | mikef@portia.stanford.edu
----------------------
| [ ] [ ]|
| [ ]|
----------------------meyer@s.cs.uiuc.edu (09/14/89)
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."davidr@hplsla.HP.COM (David M. Reed) (09/22/89)
Telnet must remain 'active' or the connection closes. This is why I use DESQview instead of MSWindows. (Even the 386 version of MSWindows will usually not allow telnet to stay active in a background window because it is not a 'true', or pre-emptive multi-tasking environment like DESQview.) You can run MSWindows in a DESQview window if you really need to (such as running a specific MSWindows application like Excel).