Path: utzoo!utgpu!watmath!att!chinet!mcdchg!ddsw1!ddsw1!point!wek
From: wek@point.UUCP (Bill Kuykendall)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Desqview 386 Problems
Message-ID: <[1326.2]comp.ibmpc;1@point.UUCP>
Date: 6 Aug 89 13:00:03 GMT
References: <632@dtix.ARPA> <36300056@iuvax>
Lines: 29

>   I have a Nec PowerMate Portable 386sx with an Intel AboveBoard with
>   4Mb of RAM.  The Nec has a full 640K base RAM and VGA. I also
>   have a 3COM Etherlink II board running Sun's PC-NFS, and a 
>   Microsoft BUSS Mouse.

>   the largest block size is 430K!!!  The DesqView manual says that
>   there should be 550K for the largset block!!!

The problem is almost certainly the that your LAN software and mouse driver
are loaded in conventional ( <640k) memory.  The memory taken up by any
device drivers or TSRs is subtracted from the amount of memory
available in *each* window.

Fortunately, Quarterdeck supplies a program and a driver with QEMM that
allows you to put device drivers and TSR's in the free memory available
between 640K and 1 MB.  There are usually a couple of substantial chanks of
memory in there you can use.  The main limitation is that the programs you
load must each fit into a *contiguous* chunk of mappable memory.  

Install QEMM.SYS with the RAM parameter.  Then use QEMM.COM (or is it .EXE?)
to look at your memory map.  Those portions labeled 'Mappable' can be used
by LOADHI.COM or LOADHI.SYS to load your MOUSE.SYS and LAN software in.  See
your QEMM documentation for details.  With luck, you should be able to get
575K or better in each window.  Ventura will work fine with that.  If you
*do* still have a problem, you can reduce Ventura's memory requirement by
stealing some of its graphics and text buffer space.  This is done by adding
the parameter 'a=n' where 'n' is a number up to around 30, to your vp.bat
file.