From: "Ben Peddell" Newsgroups: comp.os.msdos.djgpp References: <3e18ff2f DOT sandmann AT clio DOT rice DOT edu> <_yYS9.19409$jM5 DOT 53659 AT newsfeeds DOT bigpond DOT com> Subject: Re: Generate real-mode 386 DOS executables? Lines: 14 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Message-ID: Date: Mon, 13 Jan 2003 13:38:50 +1000 NNTP-Posting-Host: 144.134.90.244 X-Trace: newsfeeds.bigpond.com 1042445149 144.134.90.244 (Mon, 13 Jan 2003 19:05:49 EST) NNTP-Posting-Date: Mon, 13 Jan 2003 19:05:49 EST Organization: Telstra BigPond Internet Services (http://www.bigpond.com) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hmm. Is the 32-bit real mode that Charles was talking about where the address space is 32-bit, or where the operand size is 32-bit, or both? If it's 32-bit operands, then you would have to compile it as a stand-alone, and you would be limited to 64kB of address space per segment before having to play around with them. As those who responded to my outburst pointed out, it would be better to use a compiler that isn't a stranger to Real Mode programming. If you don't want to be able to access extended memory without needing to enter protected mode, or you don't want to play martyr, then I withdraw my remark as being useless to you.