Path: utzoo!utgpu!watmath!att!bellcore!rutgers!usc!cs.utexas.edu!uunet!crdgw1!sungod!davidsen
From: davidsen@sungod.crd.ge.com (ody)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Desqview 386 Problems
Message-ID: <1537@crdgw1.crd.ge.com>
Date: 8 Aug 89 17:40:31 GMT
References: <632@dtix.ARPA>
Sender: news@crdgw1.crd.ge.com
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Distribution: na
Organization: General Electric Corp. R&D, Schenectady, NY
Lines: 21

In article <632@dtix.ARPA> jmoore@dtix.navy.mil (Jim Moore) writes:
| PROBLEM :
|    It almost works.  I have installed DesqView, rename xdv.com to dv.com,
|    execute dv, the open a window and run the memroy status program.
|    It tells me there is 3300K of available extended memory and
|    the largest block size is 430K!!!  The DesqView manual says that
|    there should be 550K for the largset block!!!

  I ran DV and QEMM until I could get a reasonable UNIX for the 386 (I
got my 386 in 1986 when they were new and shiny). I had a bit over 600k
free, more than if I ran just DOS. I don't remember all the details, but
I had all of the device drivers out, and no TSR's in before starting DV.
I had one session which only ran TSR's, and that worked reasonably well.

  You might check how much junk gets loaded before DV, since I think you
have to keep it.

  Let us know how you make out.
	bill davidsen		(davidsen@crdos1.crd.GE.COM)
  {uunet | philabs}!crdgw1!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me