Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!uwmcsd1!bbn!rochester!pt.cs.cmu.edu!b.gp.cs.cmu.edu!ralf
From: ralf@b.gp.cs.cmu.edu (Ralf Brown)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Background Communications under Desqview
Message-ID: <2611@pt.cs.cmu.edu>
Date: 5 Aug 88 21:35:55 GMT
References: <595@unh.UUCP> <2706@bgsuvax.UUCP> <7804@cup.portal.com> <380@eecea.eece.ksu.edu> <2609@pt.cs.cmu.edu>
Sender: netnews@pt.cs.cmu.edu
Distribution: na
Organization: Carnegie-Mellon University, CS/RI
Lines: 24

In article <2609@pt.cs.cmu.edu> I write:
}What DESQview does is update the screen for you when you write to the virtual
}screen.  TopView requires an explicit call to update the screen.  If DESQview
}gets this call, it will stop implicitly updating the screen and require the
}call.  Most DESQview-aware programs use the implicit screen update, since
}without explicit update calls, making the program DV-aware is about ten lines
}of code in the screen-address determination routine.
}
}There is a call to turn the implicit updates back on.  I'll see about whipping
}up a short program later tonight....

Just thought of this alternative:
On the DV 2.01 distribution disk, there is a small file named NOFF.SHR (it's
about 85 bytes).  Make sure that this file is accessible one some disk that
will be available when you load Kermit, and put the complete pathname of
NOFF.SHR (including the extension) in the "Shared Program Pathname:" field on
the advanced options screen for "Change a Program".  This file intercepts
the explicit update call so that DESQview won't see it, and won't turn off
the implicit screen updates.

-- 
{harvard,uunet,ucbvax}!b.gp.cs.cmu.edu!ralf -=-=- AT&T: (412)268-3053 (school) 
ARPA: RALF@B.GP.CS.CMU.EDU |"Tolerance means excusing the mistakes others make.
FIDO: Ralf Brown at 129/31 | Tact means not noticing them." --Arthur Schnitzler
BITnet: RALF%B.GP.CS.CMU.EDU@CMUCCVMA -=-=- DISCLAIMER? I claimed something?