On Tue, Oct 07, Alexandre Julliard wrote:
> Well, the patch is doing a kind of lazy initialisation, since it falls
> back to the global vector if the task one is 0. We could possibly set
> the task vector at that point, but it's not clear to me that it would
> be necessary.
Now that you mention it
Jukka Heinonen <[EMAIL PROTECTED]> writes:
> However, I can't see why this would cause a crash because as far as
> I know, int 0 vector is never called by Wine. It doesn't really matter
> but I'm just curious... (Perhaps they handle int 0 as a call chain?)
It never gets called, but in order to ch
Mike McCormack wrote:
> Two 16bit programs launch, one after the other. Each program hooks INT
> 0, however since our interrupt tables are global to all tasks, the
> second task retrieves the interrupt vector that the first task set.
>
> The first task exits, and restores the original INT 0 vecto
Hi All,
I've run into an interrupt related problem with Quicken 2002's installer.
Two 16bit programs launch, one after the other. Each program hooks INT
0, however since our interrupt tables are global to all tasks, the
second task retrieves the interrupt vector that the first task set.
The fi
