Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!asuvax!mcdphx!mcdchg!att!cbnewsh!k4bnc
From: k4bnc@cbnewsh.ATT.COM (john.a.siegel)
Newsgroups: comp.sys.ibm.pc
Subject: Re: MKS vi 3.1 versus Desqview 2.25
Summary: MKS Vi under DESQVIEW  A possible solution
Message-ID: <6607@cbnewsh.ATT.COM>
Date: 14 Dec 89 14:09:42 GMT
References: <5643@videovax.tv.tek.com> <9620003@hpcilzb.HP.COM>
Organization: AT&T Bell Laboratories
Lines: 14

In article <9620003@hpcilzb.HP.COM>, bazavan@hpcilzb.HP.COM (Valentin Bazavan) writes:
> 
> I am having the same problem with MKS vi 3.1 running under Desqview
> on a Hewlett-Packard Vectra (286). I hope to be proved wrong, but I
> suspect that there is no user solution. Some change made in the new vi
> conflicts with Desqview.
> 
> Valentin Bazavan

This sounds similar to a problem I had with a somewhat earlier version of VI
running on a 80386 machine.  When the dvp option was set to virtualize the
symptoms were as described in the original article.  With this option off VI runs properly.  I suspect in this case that VI is using instructions not included
in the virtual 8086 mode.  I don't know how to relate this to a 80286 based
machine but maybe it will give someone an idea for a solution.