On Thu, 17 Oct 2002, Stas Sergeev wrote:
> 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.
if ((_LO(bx) >= 0xe0) && (REG(cs) < 0xf000)) { /* avoid hardreboot!! */
I should add that this test is more bogus than it used to be because these
high vectors are initialized to 0 in development versions of DOSEMU and no
longer point to the DOSEMU BIOS interrupt trampoline.
It looks a lot like something that was added to do some custom sanity
checking while debugging some DOS program, but the person forgot to remove
it later.
The comment is puzzling: hardreboot of what? Linux?
Bart
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
