From: Vinzent Hoefler <JeLlyFish DOT software AT gmx DOT net>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Generate real-mode 386 DOS executables?
Date: Wed, 08 Jan 2003 12:16:13 -0500
Organization: JeLlyFish software
Lines: 19
Message-ID: <tcmhva.6c4.ln@jellix.jlfencey.com>
References: <BQ2S9.280216$a8 DOT 123208 AT news4 DOT srv DOT hcvlny DOT cv DOT net> <3e18ff2f DOT sandmann AT clio DOT rice DOT edu> <avavsl$dpf6g$1 AT ID-175126 DOT news DOT dfncis DOT de> <_yYS9.19409$jM5 DOT 53659 AT newsfeeds DOT bigpond DOT com>
NNTP-Posting-Host: firewall.mdc-dayton.com (12.161.103.180)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Trace: fu-berlin.de 1042046237 16196915 12.161.103.180 (16 [175126])
X-Orig-Path: jellix.jlfencey.com!nobody
X-Homepage: http://jlfencey.com
X-Phone: +1-937-271-7158
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Ben Peddell wrote:

[32-Bit Real Mode]
> But be warned, as soon as you call something that switches to
> protected mode, Big Real Mode goes *poof*.

Yes, but that's not the problem, you simply don't need to call such 
programs.

The main problem is, as soon as you call BIOS or something it goes 
*poof* because the called code assumes a 16-bit-code-segment. So 
probably the first timer/keyboard/harddisk/whatever interrupt would 
already crash you. That's what I said.


Vinzent.

-- 
Anything is good and useful if it's made of chocolate.