Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!mikes@iuvax.cs.indiana.edu
From: mikes@iuvax.cs.indiana.edu (Michael Squires)
Newsgroups: comp.os.msdos.desqview
Subject: Re: Communication programs
Summary: NCSA Telnet
Keywords: comm telnet
Message-ID: <1991May21.094107.3897@news.cs.indiana.edu>
Date: 21 May 91 14:40:28 GMT
References: <1991May19.113245.19970@cs.umu.se> <13127@pt.cs.cmu.edu> <1880@csource.oz.au>
Organization: Computer Science, Indiana University, Bloomington.
Lines: 25

In article <1880@csource.oz.au> david@csource.oz.au (david nugent) writes:

>This shouldn't be the case.  DV revectors the IRQ and manages the hardware
>interrupts.  I can't believe that it wouldn't also know which particular 
>task "owns" an IRQ vector and has enough intelligence to know that a task
>is swapped or not.

The received wisdom from Clarkson on using NCSA or CUTCP Telnet with the
Clarkson packet drivers is that (1) the packet driver must be loaded in
the session that runs Telnet (not before DesqVIEW starts) and that the
session must be non-swappable.

There is a note packed with the packet drivers that describes the installation
of NCSA Telnet + packet drivers under DesqVIEW, at least in the v8.0 version.

I did drop back to the v7.0 packet drivers as the v8.0 WD8003E driver tries
to run in 80[123]6 mode, and that seemed to cause trouble.  The v7 packet
driver did not.  There's probably a switch to turn off that feature, but
it was not immedidately obvious.

-- 

Mike Squires (mikes@iuvax.cs.indiana.edu)     812 855 3974 (w) 812 333 6564 (h)
mikes@iuvax.cs.indiana.edu          546 N Park Ridge Rd., Bloomington, IN 47408
Under construction: mikes@sir-alan.cica.indiana.edu