Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!hplabs!hpfcso!hpldola!ppa
From: ppa@hpldola.HP.COM (Paul Austgen)
Newsgroups: comp.sys.ibm.pc
Subject: Re: QEMM 5.0 Slo-o-o-o-ws system DMA
Message-ID: <11250141@hpldola.HP.COM>
Date: 28 Jun 90 20:52:59 GMT
References: <3863@trantor.harris-atd.com>
Organization: HP Elec. Design Div. -ColoSpgs
Lines: 57

> / hpldola:comp.sys.ibm.pc / shim@zip.eecs.umich.edu (Sam Shim) / 11:51 am  Jun 26, 1990 /
> In article <11250139@hpldola.HP.COM> ppa@hpldola.HP.COM (Paul Austgen) writes:
> >I just started using Desqview 2.2 on my 386, and I noticed that
> >the screen display is pretty slow.  When I use MORE and also do
> >directory listings, it seems to paint and stop, and continue on
> >again.  This surprised me, since I gave the foreground 99 tics,
> >and the background only 3 tics.
> 
> First, you should not set the forground to 99 ticks and the backgroud
> 3 tics since you are multitasking with a ratio of about 5 seconds to
> 1/6 of a second.  I hope you were doing that only for testing.  I keep
> my ratio at 1:1.
  
  I am doing this because I am not really that interested in
multi-tasking.  I am interested primarily in the performance of
the foreground task.  In this case, I am running Microsoft Word,
and the mouse sprite seems a little jerky with the recommended
ratio of 9 to 3.  My main motivation for using DV was to keep
alive my communications program to keep a telnet connection to my
Unix cluster server.  Even this 99 to 3 ratio seems to keep the
connection alive just fine.



> Screen updates are fast and smooth, both for the
> foreground app and the background apps.  This might help.  If not, turn off
> direct writes to screen if you running programs that do not do direct
> writes.  Turn of virtualization when you don't need/want it.
Turning off virtualization cured the problem.  Excellent point.

> Make sure
> you are using the proper graphics driver.

I'm not sure what you mean here.  I believe that DV selected it
from its bag of tricks during installation.

> Take out ansi if you are using
> it.
> 
Why?  I have ansi.sys installed in the main memory (pre-DV
invocation).  For the dos window (BigDos), I use dvansi, since
ansi doesn't seem to survive through to the DV windows.  

> Hopefully one of these will fix it.
> 
 Thank you for your reply.  The virtualization seems to have done
the trick.
> 
>  -----------------------------------------------------------------------------
> | Sam Shim                                 | Bart:  Your succumbing to        |
> | EECS Departmental Computing Organization |        mob mentality, Dad.       |
> | University of Michigan                   | Homer: Don't be ridiculous, son. |
> |                                          |        I'm hopping on the        |
> | internet: shim@zip.eecs.umich.edu        |        bandwagon!  Get with      |
> | Compuserve: 72371,1277                   |        the winning team!         |
>  -----------------------------------------------------------------------------
> ----------