Mail Archives: djgpp/1996/07/06/16:45:08
Xref: | news2.mv.net comp.os.msdos.djgpp:5700
|
From: | alaric AT abwillms DOT demon DOT co DOT uk (Alaric B. Williams)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Unsupported INT 0x0d
|
Date: | Sat, 06 Jul 1996 19:41:51 GMT
|
Lines: | 29
|
Message-ID: | <836682030.7478.1@abwillms.demon.co.uk>
|
NNTP-Posting-Host: | abwillms.demon.co.uk
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Hi there... I'm writing low level stuff in DJGPP 1.12m4, in this case
a sound driver. It hooks IRQ 5, which is int 0x0D.
This works generally fine... except that occasionaly, without
provocation, it bombs out with "Unsupported INT 0x0D"
What can I do? I never call 0x0D directly; the PIC does that via
hardware. I am claiming the interrupt with both
set_real_mode_interrupt_vector (via an iret callback) and
chain_protected_mode_interrupt_vector.
P.S. Why do I have to do this? It still mucks up without, but what is
this DPMI distinction between RM and PM ints?
I don't want to use v2 since my code will not work under DPMI (the
video driver directly accesses video RAM with 0xE00A0000... there is
no DPMI-able method that fast, am I correct?)
Thanx,
ABW
--
I have become... Comfortably numb...
Alaric B. Williams Internet : alaric AT abwillms DOT demon DOT co DOT uk
<A HREF="http://www.hardcafe.co.uk/Alaric/">http://www.hardcafe.co.uk/Alaric/</A>
- Raw text -