www.delorie.com/archives/browse.cgi | search |
Date: | Sun, 20 Feb 2000 11:35:12 +0200 (IST) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | Florian X <dos DOT fire AT aon DOT at> |
cc: | djgpp AT delorie DOT com |
Subject: | Re: real mode & protected mode |
In-Reply-To: | <38ad822a$0$72090@SSP1NO17.highway.telekom.at> |
Message-ID: | <Pine.SUN.3.91.1000220113442.25009h-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | dj-admin AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Fri, 18 Feb 2000, Florian X wrote: > PROTECTED MODE: > > You can use all ram and flat memory, have no interrupts, so you need an DPMI > surver which switch back to realmode to start a interrupt. Not true: protected mode can use interrupts exactly as real mode can. The only difference is that instead of the real-mode Interrupt Vector Table, where each entry is a real-mode seg:off address of the interrupt service routine, in protected mode there's the Interrupt Descriptor Table, where each entry is the selector:offset address of an interrupt gate.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |