Re: [Bug 586] Changed - int3d: unknown/not implemented parameters - endless loop + err:int:INT_Int3dHandler

[admiral coeyman]

wine-bugs(a)winehq.com wrote:
> http://bugs.winehq.com/show_bug.cgi?id=586
>
> *** shadow/586  Thu May 23 12:32:36 2002
> --- shadow/586.tmp.2333 Thu May 23 12:51:14 2002
> ***************
> *** 120,122 ****
> --- 120,128 ----
>   Robert, could look at this?
>   What does this interupt and its parameters mean?
>   Do we want to implement it?
> +
> + ------- Additional Comments From andi(a)rhlx01.fht-esslingen.de  2002-05-23 12:51 -------
> + Everybody knows that Ralf Brown's Interrupt List tells you what it is ;-)
> +
> + Int 0x3d is floating point emulation interrupt.
> + Unfortunately I currently don't know whether we need to implement it or not.

The endless loop must be handled.  
	It looks like these interrupts are a hook into a floating point emulator and
this interrupts acts as the 'fwait' instruction.  All that this interrupt
should do is wait for the last operation assigned to the [emmulated] fpu to
signal that it has completed.  
	The operating systems that support wine will run with chips that do not have
the built in fpu, however, there shouldn't be that many of them out there.  It
wouldn't hurt to emmulate the interrupt.  This is part of a block of interrupts
that appears to start at 0x39 and run up to 0x3e .
	God Bless,
		--Robert 'Admiral' Coeyman



-- 
---
May you live as long as you wish and age but a single day.
http://www.dotguy.net/                 admiral(a)corner.net
Webmaster/ Linux Administrator         Computer Co-Op/CornerNet