X-Authentication-Warning: acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs Date: Tue, 12 Sep 2000 17:41:17 +0200 (MET DST) From: Hans-Bernhard Broeker X-Sender: broeker AT acp3bf To: Kalum Somaratna aka Grendel cc: djgpp AT delorie DOT com Subject: Re: Common DOS programs in DJGPP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Tue, 12 Sep 2000, Kalum Somaratna aka Grendel wrote: > On 12 Sep 2000, Hans-Bernhard Broeker spoke the following immortal words, > > > And that one is *not* a DOS compiler. It's a Win32 compiler. Neither > > the compiler itself, nor the executables it creates, will run in > > DOS. Not even Windows 3.1 with Win32s installed will do. > > Hmm...are you quite sure of this Hans, I have the 5.0 version and it does > support creating of 16-bit dos executables. The commercial version sold as 'Borland C++ 5.0' does, indeed, contain all these packages. But the freely available one contains only of 'bcc32.exe' and the relevant tools needed to use it (including 'make' and 'ilink', but no 'tasm', no debugger and no profiler). It's essentially the command-line stuff you'ld also find in C++ Builder, latest version. It's not the one from 'Borland C++' (there is no version 5.5 of that). > So even if 5.5 does not provide support for 16 bit dos apps, it may be > possible to compile 16 and 32 bit DPMI apps using the powerpack for dos > addon. If at all, only 32bit DPMI may be possible. I have the package, at home, and there definitely is no 16bit compiler in it. Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.