From: Martin Str|mberg <ams AT speedy DOT ludd DOT luth DOT se>
Subject: Re: Generate real-mode 386 DOS executables?
Newsgroups: comp.os.msdos.djgpp
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> <tcmhva DOT 6c4 DOT ln AT jellix DOT jlfencey DOT com>
User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (NetBSD/1.5_BETA (alpha))
Message-ID: <1042054297.215872@queeg.ludd.luth.se>
Cache-Post-Path: queeg.ludd.luth.se!unknown AT speedy DOT ludd DOT luth DOT se
X-Cache: nntpcache 2.4.0b5 (see http://www.nntpcache.org/)
Date: 08 Jan 2003 19:31:37 GMT
Lines: 25
NNTP-Posting-Host: queeg.ludd.luth.se
X-Trace: 1042054297 news.luth.se 26545 130.240.16.109
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Vinzent Hoefler <JeLlyFish DOT software AT gmx DOT net> wrote:
: 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*.

: 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.

Not quite. The problem is that as soon you restore a segment register
in real mode its big real mode properties go poff. If you're lucky you
might have fs and gs untouched (mainly because of DOZE's
8086-ness). But e. g. FreeDOS kernel compiled for 386 or higher
probably uses them, or any other 386-aware program might, so just
forget about it.


The real problem is of course what this has to do with DJGPP?


Right,

						MartinS