I have forgotten to cc this discussion to wine-devel. But who is interested
can catch up from this mail.
On Saturday 26 October 2002 14:07, Eric Pouech wrote:
Could somebody answer/test if calling interrupt int 0x01 is allowed
from a win32 program in WinNT environment? I would pretty
Tough all safedisc programs depend on this, I have decided not to make an
official patch. The reason is that additional info is needed for a proper
fix. Safedisc depends on that EXCEPTION_ACCESS_VIOLATION is returned on an
int 0x01 call. But it should be checked what exceptions are raised
On Saturday 26 October 2002 17:36, John K. Hohm wrote:
Tough all safedisc programs depend on this, I have decided not to make an
official patch. The reason is that additional info is needed for a proper
fix. Safedisc depends on that EXCEPTION_ACCESS_VIOLATION is returned on
an int 0x01
On Thu, Oct 24, 2002 at 12:26:15PM +0200, Zsolt Rizsanyi wrote:
But the recent interrupt changes tend to cause cvs conflicts and to break it.
This patch is supposed to work only if winver is nt40 so very probably this
applies only to NT.
...
I would like if this could be fixed properly and
Joerg Mayer [EMAIL PROTECTED] writes:
and on 28 May 2002 18:58:51 -0700, Alexandre wrote:
The main problem is that it isn't generic enough, it only applies to
the create process request but other requests have the same problem
and should be fixed too. I'll work on a more general solution.
On Friday 25 October 2002 13:46, Joerg Mayer wrote:
On Thu, Oct 24, 2002 at 12:26:15PM +0200, Zsolt Rizsanyi wrote:
But the recent interrupt changes tend to cause cvs conflicts and to break
it. This patch is supposed to work only if winver is nt40 so very
probably this applies only to NT.
Rizsanyi Zsolt a écrit :
Could somebody answer/test if calling interrupt int 0x01 is allowed from a
win32 program in WinNT environment? I would pretty like to know that!
I don't think it is
it was allowed on Win9x, and is used in this context IIRC as a ring 3 to
ring 0 transition code (how to
