From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stas Sergeev Subject: Re: DPMI: Interrupt vector overwritten Date: Thu, 17 Oct 2002 07:51:50 +0400 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <3DAE33D6.8010508@yahoo.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-msdos@vger.kernel.org Cc: John Elliott Hello. John Elliott wrote: > They cause > dosemu to abort if DPMI function 0x300 is used to call interrupt 0xE0 > or higher; What exactly interrupt from this range do you want to execute? > is this correct, Of course it is not. If your program installs the realmode handler for that ints, it will just crash dosemu with that code. It was even worse when this was done not only for 0x300, but also for 0x301 and 0x302, so it crashed dosemu *randomly* because bx is meaningless for those. I moved it under "if (inumber == 0x300)" rather than remove, because it was a hard times and it was nearly impossible to get included something more than an absolutely trivial patch. Removal patch would just have been ignored most likely, so the compromiss was to put it under "if". Now, as the devel branch is in progress, the things are much better. > and if so, why is it doing it? For no reasons, feel free to remove it if it hurts you, which is still strange. Why do you need that vectors?