Re: Hardware Interrupts

["Carroll-Tech" <andrew@carroll-tech.net>]

> From: tmoran@acm.org
> Subject: system calls, was Re: Hardware Interrupts
>
> > task Interrupt_handler is
> > ...
> > I want to call the BIOS interrupt (INT11h) to get the equipment list
[snip]
>   BTW, what machine has a BIOS INT11h call?
Good question!  I'm just going by the information in Kip R. Irvine's book
"Assembly Language For Intel-Based Computers", third edition.
I also found the same information in a book called "DOS 5: A Developer's
Guide" by Al Williams (page 163).  This book does say 80286 - 80486.
So...it must be pretty old.

> ------------------------------
> From: sk <noname@myob.com>
> Subject: Re: Hardware Interrupts
>
> andrew@carroll-tech.net:
>
>  > procedure getequipment is
[snip]
> I don't know any answers to your questions. What I do
> remember about any assembly calls to BIOS interrupts
> is that you have to set up the registers with parameters
> etc.
Okay, I understand that regarding "assembly" but not going
through Ada.

> You are using GNAT from your examples. Which version
> and platform ?
Gnat 3.15p on a FreeBSD Unix 5.1

> If it is an Intel compiler running in "protected" mode,
> that is 32-bit address space etc, the physical address
> "16#11# does not corespond to the interrupt 11. Once
[snip]
> entering protected mode.
Basically I've made my own bootloader and it will boot programs
that I create.  So there is no kernel loaded or anything like that.  The
bootloader loads the program I want right after the BIOS is done.  In
fact, I am trying this "stuff" out because I want to learn more about
kernels (other than reading in a book) and how to do PIC programming
and stuff like that.

> If you are still determined to go into never-never land,
> you need to look at Ada's machine code insertions.
Links?  References?

>The code you posted looks potentially fatal to your machine.
Hey, how else am I going to learn?  If I make a mistake at least it's not
while I'm working for some client or something.  I'm just doing some
of my own research.

> Sorry, not much help, but I am hoping that you don't
> trash your system by being determined to call a
> possible inaccessible BIOS.
I'll look into this before I continue.  I don't really wan't to format the
disk
either, even though it's not imperitive at this point if it happens.

Thanks!