Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!ucsd!rutgers!gatech!hubcap!ncrcae!ncr-sd!ncrlnk!ncrwic!ksuvax1!eecea!gordon
From: gordon@eecea.eece.ksu.edu (Dwight Gordon)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Background Communications under Desqview
Message-ID: <380@eecea.eece.ksu.edu>
Date: 4 Aug 88 18:23:55 GMT
References: <595@unh.UUCP> <2706@bgsuvax.UUCP> <7804@cup.portal.com>
Reply-To: gordon@eecea.UUCP (Dwight W. Gordon)
Distribution: na
Organization: Kansas State University, Manhattan, KS USA
Lines: 23


Kermit 2.30 contains TopView detection/manipulation code.  If you run it
as a stand-alone program under DesqView, there is no problem with it on
either of the two systems on which I've used it.  However, if you use it
in a DOS shell and run another DesqView-aware program in that same shell
(at a later time), you may find out that one or more lines on the screen
have acquired an "invisible" attribute (i.e. the line is always blank).
There is a slight difference between TopView compatibility (Kermit) and
DesqView compatibility.

Secondly, there are times when DesqView zero's out the Com1/2/3/4 pointers
at 40h:0h.  Kermit makes the associated ports "unavailable."  I have not
been able to find a specific set of sequences under which this will occur.
I have seen it enough to know that it is not an isolated occurrence.

I have had to patch my version of Kermit 2.30 to fix these problems.

Dwight W. Gordon
Kansas State University
Department of Electrical and Computer Engineering
Durland Hall
Manhattan, KS 66506 
gordon@eecea.eece.ksu.edu
dwgordon@ksuvm.bitnet