Date: Thu, 7 Oct 1999 18:30:06 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Leonid Pauzner cc: djgpp AT delorie DOT com Subject: Re: DJGPP 2.02: redir.exe on FPU-less machine... In-Reply-To: <2.07b4.TRE1.FJ8E10@pauzner.mccme.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Thu, 7 Oct 1999, Leonid Pauzner wrote: > On December 1998 I was reporting that newly uploaded DJGPP 2.02 > had a broken emu387.dxe which became obvious on my FPU-less machine > (DJGPP 2.02 package was fixed in a couple of days). On what platform? What OS, what version? Please always supply this information. The emulator included with v2.02 and earlier has several bugs, most of them go back to the first v2.x release almost 4 years ago. I'm sending you (in a separate message) a patched version of emu387.dxe produced from the latest development sources. Please see if it makes the problems go away. > crash.log always ends with: > FPU unavailable at eip=4f19; flags=3246 > eax=00000000 ebx=00000007 ecx=37fcb98d edx=37fcb98d > esi=00098f3b edi=00001eca ebp=00098920 esp=000988e8 cs=a7 > ds=af es=af fs=8f gs=bf ss=af error=0006 This message comes from CWSDPMI, not from Make or the emulator. I have never seen anything like this before. If this problem persists after you start using the patched emulator, you will have to investigate some more. No one of the development team has access to an FPU-less machine, so all we can do is set 387=n and assume this produces the same behavior as on a machine without an FPU. One thing I would try is to set 387=n and see if the above message goes away (if it isn't solved by the patched emulator). > Please have a look on the problem before 2.03 come. I'm looking at this now. Good enough?