Subj : Re: Opinion Question - is there a preference for the various versions?
To   : borland.public.cpp.borlandcpp
From : Sebastian Ledesma
Date : Tue Oct 05 2004 06:16 pm

To add to Ed info:

The BC5.0x allows to create Win32 console apps, that looks very same as DOS
apps and can acces 32bit RAM
(but they need Win9x or above to run).
Also there was a trick (but dont remember right now if it was for BC4.5 or
BC5.0x) that allow to use Borland Power Pack DPMI extender
and create 32 bit DOS apps (apps that run over DOS like freeDOS and can
access 32 bit RAM). I managed to create 32 bit
Turbo Vision applications (http://tvision.sourceforge.net/) with that
combination.

Saludos
Sebastian

"Ed Mulroy [TeamB]" <dont_email_me@invalid.com> escribió en el mensaje
news:4162ef88@newsgroups.borland.com...
> Borland C++ 3.0 supported Windows 3.0 and its VCPI method of handling
> memory above the 640K limit, a scheme which limits what is up there to
> only one program.  Windows 3.1 and above as well as DOS itself often
> only mimic VCPI with difficulty.  Borland C++ 3.1 and above use the
> DMPI method of handling that memory as does DOS and all Windows
> versions from 3.1 up along with most debuggers, some printer drivers
> and other things.  There is significant advantage to developing DOS
> applications under BC++ 3.1 over using BC++ 3.0.  As I recall, and I
> was deeply into this at the time, the BC++ 3.1 DOS development
> facilities were, depending upon the item in question, either equal to
> those in 3.0 or superior to them.  If you have problems developing for
> DOS using Borland C++ 3.0 the source of the problem will stare back at
> you from the mirror when you are shaving.
>
> The facilities of Builder are facilities using the advantages of 32
> bit Windows.  You cannot have them or get them under DOS.
>
> When I have a need to develop for DOS and am near a machine on which
> it is installed, I use BC++ 5.02 to do it.  If I have significant
> source to type, then I use the IDE and debug via Tools|Turbo_Debugger,
> which fires up the same debugging tool I use from the command line.
>
> .  Ed
>

.