From: Kbwms AT aol DOT com Message-ID: <6e6be1f9.366f9867@aol.com> Date: Thu, 10 Dec 1998 04:46:15 EST To: Eli Zaretskii Cc: djgpp-workers AT delorie DOT com Mime-Version: 1.0 Subject: Fwd: Error incurred with djlsr202.zip Content-type: multipart/mixed; boundary="part0_913283175_boundary" X-Mailer: AOL 3.0 16-bit for Windows sub 38 Reply-To: djgpp-workers AT delorie DOT com This is a multi-part message in MIME format. --part0_913283175_boundary Content-ID: <0_913283175 AT inet_out DOT mail DOT aol DOT com DOT 1> Content-type: text/plain; charset=US-ASCII Dear Eli Zaretskii, In response to your conjecture regarding the topic "DJGPP 2.02 fails immediately on FPU-less machine !" K.B. Williams --part0_913283175_boundary Content-ID: <0_913283175 AT inet_out DOT mail DOT delorie DOT com DOT 2> Content-type: message/rfc822 Content-transfer-encoding: 7bit Content-disposition: inline Return-Path: Received: from rly-za01.mx.aol.com (rly-za01.mail.aol.com [172.31.36.97]) by air-za04.mail.aol.com (v53.20) with SMTP; Wed, 09 Dec 1998 20:11:15 -0500 Received: from delorie.com (delorie.com [208.7.170.162]) by rly-za01.mx.aol.com (8.8.8/8.8.5/AOL-4.0.0) with ESMTP id RAA18328 for ; Wed, 9 Dec 1998 17:23:08 -0500 (EST) Received: from envy.delorie.com (IDENT:dj AT envy DOT delorie DOT com [208.7.170.171]) by delorie.com (8.9.1/8.9.1) with ESMTP id RAA30499 for ; Wed, 9 Dec 1998 17:22:21 -0500 Received: (from dj AT localhost) by envy.delorie.com (8.8.7/8.8.7) id RAA07322; Wed, 9 Dec 1998 17:22:20 -0500 Date: Wed, 9 Dec 1998 17:22:20 -0500 Message-Id: <199812092222 DOT RAA07322 AT envy DOT delorie DOT com> From: DJ Delorie To: Kbwms AT aol DOT COM In-reply-to: <2e0414b6 DOT 366ee85e AT aol DOT com> (Kbwms AT aol DOT com) Subject: Re: Error incurred with djlsr202.zip References: <2e0414b6 DOT 366ee85e AT aol DOT com> Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit > I did that almost immediately after sending the letter. I changed the > global definitions of DJDIR and DJGPP and picked up from where the make > had quit. It went to the end. Later, I started from the top, used the > shell script to change the global definitions, and it quit by hanging my > entire system. TWICE. > > After some annoying restarts, I discovered that if I work without Windows > 3.1 the make goes from front to back. This is a Microsoft problem. Their DPMI servers leak, and there's nothing we can do to work around it. It leaks too fast for a full build to succeed; you just have to keep restarting it until it makes it through. cwsdpmi doesn't have this problem, of course, so it works under DOS. --part0_913283175_boundary--