From: John Elliott <jce@seasip.demon.co.uk>
To: Stas Sergeev <stssppnn@yahoo.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: DPMI: Interrupt vector overwritten
Date: Fri, 18 Oct 2002 20:53:16 +0100 (BST) [thread overview]
Message-ID: <E182dBM-0000RS-00@seasip.demon.co.uk> (raw)
In-Reply-To: <no.id> from "Stas Sergeev" at Oct 17, 2002 07:51:50
: What exactly interrupt from this range do
: you want to execute?
INT 0xEF, the GEM API.
--
John Elliott
next parent reply other threads:[~2002-10-18 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <no.id>
2002-10-18 19:53 ` John Elliott [this message]
2002-12-16 19:19 ` increase base memory John Elliott
2002-12-16 20:01 ` Bart Oldeman
2003-03-18 20:31 ` Access denied after write to named pipe John Elliott
2002-10-17 3:51 DPMI: Interrupt vector overwritten Stas Sergeev
2002-10-17 5:08 ` Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 22:07 John Elliott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E182dBM-0000RS-00@seasip.demon.co.uk \
--to=jce@seasip.demon.co.uk \
--cc=linux-msdos@vger.kernel.org \
--cc=stssppnn@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox