X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Subject: Re: cc1plus.exe: out of memory ...
To: djgpp AT delorie DOT com
References: <66694c0e-7f93-494b-a566-29cedaebf471 AT googlegroups DOT com>
 <b7adb439-560b-4227-8d59-84943aa33ad9 AT googlegroups DOT com>
From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Message-ID: <5c44dc6a-0da0-9cc1-c37d-f3a5c3d3fa37@iki.fi>
Date: Mon, 28 Aug 2017 21:18:55 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <b7adb439-560b-4227-8d59-84943aa33ad9@googlegroups.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 08/17/2017 10:49 PM, rugxulo AT gmail DOT com [via djgpp AT delorie DOT com] wrote:
> Hi,
>
> On Thursday, August 17, 2017 at 11:17:17 AM UTC-5, Gregg wrote:
>> Sorry if this is a repeat, but my searching is not yielding answer.
>>
>> A very simple program compiles fine on Win7 using DJGPP GCC 4.73
>> but not 7.2 (downloaded today using the zip picker).
> Haven't you already edited the registry to increase the DPMI limit?
>
> "
> Add registry entry 'DpmiLimit' with large enough value to
> Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW
> "
That should be sufficient for recent 32 bit Windows versions. No need even to reboot after doing 
registry change. I have not tried with WIn7, but it works with latest Windows Vista and Windows 10 
32 bit versions. I'm myself using 32-bit Windows 10 (running in VirtualBox VM under Fedora 26 64 
bit version) to build DJGPP port of GCC including latest versions as gcc-7.2.0 and gcc-6.4.0. So 
one can compile large enough programs for DJGPP under 32-bit Windows.

Andris

PS. Windows 10 update sometimes removes this added registry setting when updating to new build. So 
one had to re-add it to the registry