Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!sics.se!fuug!mcsun!hp4nl!alchemy!nevries
From: nevries@cs.ruu.nl (Nico de Vries)
Newsgroups: comp.lang.c
Subject: Re: Intel 386 C
Message-ID: <1991Jun12.113801.27306@cs.ruu.nl>
Date: 12 Jun 91 11:38:01 GMT
References: <1234@ocsmd.com>
Organization: Utrecht University, Dept. of Computer Science
Lines: 22

In <1234@ocsmd.com> glenn@zeus.ocs.com (Glenn Ford) writes:


>Has anyone used INTEL386 C?  It is supposed to make 386 executables
>that don't need a DOS extender!  It apparently wraps its own
>DOS extender into the executable!  Sounds too good to be true?!
>Let me know of any evaluations people have if they have tried
>doing this..thanks..
>
>glenn
>glenn@zeus.ocs.com
What is so special about that? Even the public domain GNU C++ compiler
for 386 processors has this feature. I personally would advice you
to use Watcon C 8.0 and a PharLap DOS extender supporting virtual
memory. This combination is VCPI compliant (which INTEL-C isn't)
which allows it to run under DesqView and the upcomming DescView/X
MS-DOS X-Windows environment.
I have to admit that INTEL supports DPMI (from Windwoes 3.0) but
I suppose you want to use a 386 compiler for the speed and than
seems Windows not to be the best solution.

Nico de Vries