X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Received: by 10.50.62.49 with SMTP id v17mr6580619igr.1.1445037397374;
        Fri, 16 Oct 2015 16:16:37 -0700 (PDT)
X-Received: by 10.182.116.130 with SMTP id jw2mr203702obb.4.1445037397352;
 Fri, 16 Oct 2015 16:16:37 -0700 (PDT)
Newsgroups: comp.os.msdos.djgpp
Date: Fri, 16 Oct 2015 16:16:37 -0700 (PDT)
In-Reply-To: <562168C6.5050001@gmx.de>
Complaints-To: groups-abuse AT google DOT com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=78.45.223.56; posting-account=Q0wMHAoAAADjYrghh94FTf6YnbpTqZgp
NNTP-Posting-Host: 78.45.223.56
References: <5611566C DOT 4020507 AT iki DOT fi> <561A4BCE DOT 7050606 AT iki DOT fi>
 <56213FE2 DOT 7090409 AT iki DOT fi> <562168C6 DOT 5050001 AT gmx DOT de>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <10a472e0-63c3-45e8-abe9-ee5cae5f2b72@googlegroups.com>
Subject: Re: Random compile errors under WIndows (32 bit Windows Vista and
 Windows 10)
From: "RayeR (glaux AT centrum DOT cz) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Injection-Date: Fri, 16 Oct 2015 23:16:37 +0000
Content-Type: text/plain; charset=ISO-8859-1
Bytes: 2278
Lines: 14
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t9GNU1Jo025553
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

Sorry that I cannot help you with it. I can only say that my largest project, that I compiled with DJGPP is my FFMPEG DOS port consist of tens MB of source file and I never experienced any random errors described here. I use WXP SP3 for this task. I have newer Windows installed but only in VMs, just for testing. I can see that NTVDM is more and more crippled with every newer Windows version - simple because MSDOS is out of MS scope now and if something breaks then nobody will fix it because MS allocated developers for improving people spying and enforcing W10 upgrade to everybody so no resources left for fixing NTVDM :P
I guess they will completly drop it soon. Esp. in Win10 I found some NTVDM bugs that didn't present in Win 7/8.x. I really wouldn't wonder if there happens some random DPMI corruption that was mentioned above... But I don't knoh how it's linked with change to nmalloc, if such errors happen without it too.
I wish you enough power to release 2.05 :)