X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: "Wiktor S. (wswiktorSP AT Mpoczta DOT fm) [via djgpp AT delorie DOT com]" Newsgroups: comp.os.msdos.djgpp Subject: Re: secret DJGPP documents? Date: Tue, 13 Oct 2015 18:27:12 +0200 Organization: INTERIA.PL S.A. Lines: 23 Message-ID: References: <201405111842 DOT s4BIgrRx012234 AT delorie DOT com> <2943e$56161ee8$97d537ad$10931 AT ALLTEL DOT NET> NNTP-Posting-Host: user-46-112-47-223.play-internet.pl Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="windows-1252"; reply-type=response Content-Transfer-Encoding: 7bit X-Trace: usenet.news.interia.pl 1444753631 4770 46.112.47.223 (13 Oct 2015 16:27:11 GMT) X-Complaints-To: usenet AT firma DOT interia DOT pl NNTP-Posting-Date: Tue, 13 Oct 2015 16:27:11 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Bytes: 2167 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Charles Sandmann wrote: > 2) Under W95 they could not reliably get the 12MB(?) of memory they > needed, on a 16MB system if it had been running a while, so I > provided them a hack to page out other applications so they could > lock the memory required. It was > a stupid little thing about how W95 didn't follow DPMI > expectations, frustrated > them for weeks (commercially they must run on 16MB system, many > systems were architecturally limited to 16MB at the time). It > took me about an hour > to develop a workaround. So this is why Q1 source code is more complicated than it needs be, with arcane memory manager that directly talks to DPMI instead of doing simple malloc()... It still compiles and works with GCC 5.2.0 + DJGPP 2.05 + CWSDPMI r7 + DOSBox. -- Wiktor S.