X-Authentication-Warning: delorie.com: mail set sender to opendos-bounces using -f
X-Recipient: opendos AT delorie DOT com
Message-Id: <201004191419.o3JEIQXp004585@mr3.ash.ops.us.uu.net>
Date: Mon, 19 Apr 2010 10:13:52 -0400 (New York)
X-Mailer: 4DOS v8.00 SEND.BTM 07-10-09
From: Gary Welles <gary AT wellesway DOT com>
To: OpenDos <opendos AT delorie DOT com>
Subject: Re: 256Mb Extender Problems
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii;
	format=flowed; delsp=no
Reply-To: opendos AT delorie DOT com

My problems with GO32 and QDPMI went away.  Perhaps as a 
result of changes to DESQview/X's Virtual Memory Manager.

As a result I only need to exclude one 4Kb block from 
QEMM386's management for CLOAKING, the only DOS extender to 
complain of too much memory:

NoUseRAM=262132K-256M ;4K for CLOAKING v2.01

> I recently increased memory to 256Mb, only to encounter DOS 
> extender problems (details below).  CLOAKING reported 
> "Memory configuration too large", QDPMI "Paging Violation" 
> and GO32 hung without complaint.
>
> On the verge of asking your help, I discovered a fix by 
> excluding up to three 4Kb blocks from QEMM386's management:
>
> NoUseRAM=262124K-256M ; 4K for CLOAKING v2.01
>                       ; 8K for GO32 v1.12.special1
>                       ;12K for QDPMI v1.10

-- Gary