Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!agate!shelby!portia!dhinds
From: dhinds@portia.Stanford.EDU (David Hinds)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Desqview on AMI 386-25 with shadowing
Keywords: dv desqview ami cache shadow shadowing problem
Message-ID: <8427@portia.Stanford.EDU>
Date: 20 Jan 90 21:07:39 GMT
References: <25b336f3:4213comp.sys.ibm.pc@vpnet.UUCP>
Sender: David Hinds <dhinds@Portia.stanford.edu>
Organization: Stanford University
Lines: 39

In article <25b336f3:4213comp.sys.ibm.pc@vpnet.UUCP>, akcs.amparsonjr@vpnet.UUCP (Anthony M. Parson, Jr.) writes:
> In trying to get DV set up to allow several large programs to run, I can't
> get even one large program, on the order of, say, Ventura Publisher to
> run.  DV error message says only 402K available, and Ventura needs 460K
> plus 9K overhead.  Similar message if I try Generic Cadd ("needs 400K
> plus 9K overhead") under DV.  With only MS (the DV memory status program)
> running under DV, I show the following:
>  
>                 Common Memory   17408   13936   13926
>                 Convent. Mem     402K    394K    394K       386, 3+ meg EXT
>                 Expandd. Mem    2960K   2960K    400K
>  
> The above is using the "normal" DV driver, DV.EXE, and QEMM.with defaults.
>  
> HERE IS PART OF THE PROBLEM: The manual refers to DV.COM and DV.EXE
> and to XDV.COM and XDV.EXE. (see page 10 of DV manual, vs page 139
> in appendix B of same manual) I only have DV.EXE and XDV.COM !  [My
> manual says you can use only up to 8 meg with EMS, but that's another
> story]
    Desqvview looks in the current directory for its files, so before
running DV you must move to c:\dv, or whatever.  I assume from your results
that you have the desqview directory in your path, which is not good enough.
If you run XDV from another directory, letting the path find it, it will
look for DV.EXE in the current directory and fail to find it.  You need
to rename XDV.COM to DV.COM.  Then, if you are in the dv directory, typing
'dv' will cause DOS to load DV.COM, and DV.COM will load DV.EXE into
expanded memory and memory mapped above 640K.  Depending on how much high
memory has been mapped by QEMM above 640K, XDV can map all of desqview out
of the lower 640K.
    I found that turning off all sorts of hardware shadowing, and using
QEMM to shadow ROM's, is a good thing to do.  My system (a 386SX with an
Intel/Zymos chipset) shadowed ROM's in 128K blocks, regardless of their
actual size.  QEMM recovered all the empty space the board was mindlessly
shadowing.  I have lots of drivers and things mapped above 640K using
'loadhi', so there isn't that much room for desqview, but according to 'MS'
my largest windows can be about 530K.

 -David Hinds
  dhinds@portia.stanford.edu