Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsm!cbnewsk!cbnewsj!rudy
From: rudy@cbnewsj.att.com (avram.r.vener)
Newsgroups: comp.os.msdos.desqview
Subject: Re: vi under Desqview -- is it possible?
Message-ID: <1991Jun6.021549.9505@cbnewsj.att.com>
Date: 6 Jun 91 02:15:49 GMT
References: <1991Jun3.153008.20350@mips2.ma30.bull.com>
Organization: AT&T Bell Laboratories
Lines: 27

In article <1991Jun3.153008.20350@mips2.ma30.bull.com> anderson@mips2.ma30.bull.com (Dave Anderson) writes:
>>   I have recently purchased Desqview, and I am pleased with it except for
>> the fact that my favorite editor will not run under Desqview in any way.
>>   Symptoms: 
>>     When VI attempts to run, the screen is blanked, and then the console 
>> starts beeping relentlessly as the cursor marches majestically across the
>> screen to the rhythm of the beeps.
> 
   [ stuff deleted ]
>    Maybe we should create a support group here.  I got Desqview a few
>  weeks ago and had precisely the same problem.  I tried MKS vi, as well
>  as "calvin" (another freeware vi-clone) -- both by themselves, as well
>  as from Big DOS.  I eventually gave up trying, and for that reason never
>  use Desqview.  (What good is it if you can't bring up a simple editor?)
>  Windows 3.0 handles vi with no problem.
>
>  I thought perhaps I also just wasn't setting the magic Desqview parameters
>  for vi, but now I wonder if _anybody_ out there has configured it correctly?
>  Help us out, somebody...

I have no problem running vi.  I always do it from a Big Dos window. The only
problem I recall having is a 'nglob' error if I tried to call vi from one of my
extended disks logical drives.  Installing a /tmp directory in every logical
drive fixed that problem.  

--
Rudy Vener  AT&T BTL  uucp: att!mtqua!rudy  internet: rudy@mtqua.att.com