home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!mcsun!sunic!ugle.unit.no!nuug!nntp.nta.no!hal.nta.no!hlj
- From: hlj@hal.nta.no (Harald Ljoen FBA)
- Subject: Re: 80368/80486 exceptions & interrupts: INT 10h
- Message-ID: <1992Nov11.124211.25228@nntp.nta.no>
- Sender: news@nntp.nta.no
- Nntp-Posting-Host: rimne.nta.no
- Reply-To: harald.ljoeen@nta.no
- Organization: Norwegian Telecom Research
- References: <26759.9211101622@thor.cf.ac.uk>
- Date: Wed, 11 Nov 92 12:42:11 GMT
- Lines: 22
-
- In article <26759.9211101622@thor.cf.ac.uk>, spxtrb@thor.cf.ac.uk (Tim Barnett - programmer) writes:
- >Trivial question ...
- >I have Microsoft's 80386/80486 Programming Guide which says on page 119 ...
- >(my parentheses)
- >
- > Interrupt number Class Description
- > --------------------------------------------------
- > 16 (decimal,=10h) Fault Coprocessor error
- >
- >... but under MS-DOS I know that INT 10h traps to the EGA/VGA BIOS. Eg:
-
- When IBM designed the IBM PC *both* the hardware guys *and* the software
- guys failed to RTFM, which clearly states that interrupt vectors 00 - 1F
- are _RESERVED_ by Intel.
-
- So the INT 10 handler has to check if it was invoked by a Coprocessor
- fault. Likewise for most other BIOS calls and IRQ handlers.
-
- Neat!
-
- --
- ** Also sprach harald.ljoeen@nta.no **
-