Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!dino!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!m.cs.uiuc.edu!s.cs.uiuc.edu!jaswal
From: jaswal@s.cs.uiuc.edu
Newsgroups: comp.sys.ibm.pc
Subject: Re: MKS vi 3.1 versus Desqview 2.25
Message-ID: <213400077@s.cs.uiuc.edu>
Date: 19 Dec 89 17:30:35 GMT
References: <5643@videovax.tv.tek.com>
Lines: 14
Nf-ID: #R:videovax.tv.tek.com:5643:s.cs.uiuc.edu:213400077:000:624
Nf-From: s.cs.uiuc.edu!jaswal    Dec 18 19:34:00 1989


I don't know if you tried this already, but ...

I had a very similar problem with the old MKS and Desqview 2.x on 
an XT.  If I told DV that the application wrote directly to the screen
(or something like that) then vi would march across the top line
and beep each time.  So I changed the option to say that it didn't 
write directly to the screen and that worked. You'd think that anything
that could run under the latter option would do so under the former,
since the former is designed for ill-behaved programs.  But apparently,
vi checks for DV, assumes that the latter option is set and
(mis-)acts accordingly.

Vijay