Path: utzoo!utgpu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!ists!yunexus!rreiner
From: rreiner@yunexus.YorkU.CA (Richard Reiner)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: DESQview 386 & communications programs
Message-ID: <20774@yunexus.YorkU.CA>
Date: 19 Jan 91 16:03:53 GMT
References: <3790@ryn.mro4.dec.com> <20558@yunexus.YorkU.CA> <4728@vela.acs.oakland.edu>
Organization: York U. Computing Services
Lines: 27

w8sdz@vela.acs.oakland.edu (Keith Petersen) writes:

>>When I run communications software in DESQview 386 2.31 with text
>>screen virtualization turned on, screen updates are very jerky (lines
>>are written in increments).

>This has something to do with the task switching in DESQview.  I've
>found the simple solution is to run the DESQview "MS" (memory status)
>program in one window.

>I use MS-Kermit which has an excellent VT102 emulator and is also
>DESQview aware - which means it gives up time slices to other tasks

I was encountering this problem with MS-Kermit.  I had to use screen
virualization because of a Kermit bug: it apparently violates
DESQview-awareness and writes data directly into the physical frame
buffer when executing the vt200 insert-character escape sequence in
the vt320 emulator, producing corrupted screen displays if running
without virtualization, but correct ones if running with it.

The best workaround I've found is to tell my host I'm using a vt100.
I can then turn the virtualization off.

I have reported this bug to the Kermit people at Columbia, but have not
yet received any response.

--richard