On Wed, Apr 2, 2025 at 4:59 PM Eric Auer via Freedos-devel <freedos-devel@lists.sourceforge.net> wrote: > > Hi Jim, as the error messages are about exception 07, > device not available, all refer to basically the same > code address and one of them shows the machine code > to be DB E3 which stands for FNINIT, this does indeed > look very much like an app which blindly assumes some > FPU (floating point unit) to be available, instead of > at least testing for presence first and exiting with > an error message if necessary. This makes me wonder > whether we include any good FPU emulators yet :-) > [..] > > > I also tried rebooting & compiling the C program with i16gcc. I forgot > > to save the output with Logger, but I took a photo. It has this error: > > > > Exiting due to signal SIGNOFP > > Coprocessor not available at eip=008acd60 > > > > ..and then the eax, ebx, ecx, edx, esi, edi, ebp, esp register values. > > The program was CC1.EXE > > You mean I16GCC also blindly assumes a FPU to be present? That is odd. >
Yes, that's what happened. I tried using 'i16gcc -c hello.c' and that took *forever* but eventually failed with "Exiting due to signal SIGNOFP" and "Coprocessor not available". I can't attach photos to the email list, but maybe a WEBP will be small enough to make it. I'll send that as a follow-up. I'll also send you (Eric) the photo off-list. _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
