Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!samsung!spool.mu.edu!sdd.hp.com!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!rpi!batcomputer!cornell!uw-beaver!mit-eddie!xn.ll.mit.edu!xn!tonyb
From: tonyb@titania.juliet.ll.mit.edu ( Tony Berke)
Newsgroups: comp.windows.ms.programmer
Subject: Borland C++ target hosts
Message-ID: <TONYB.91Mar21152525@titania.juliet.ll.mit.edu>
Date: 21 Mar 91 21:25:25 GMT
Sender: usenet@xn.ll.mit.edu
Distribution: comp
Organization: M.I.T. Lincoln Lab - Group 43
Lines: 19

OK, there are probably lots of old postings on this subject, bit I'm
not sure how to get at them.

Here's the question:  A little note in the README file of my newly
acquired C++ says something to the effect of 'C++ only supports
windows protected-mode target files'.

I've noticed what appear to be follow-ups on this issue, but not the
answer to the basic question: Can I only write Windows programs that
will run on 386's ??   If that's true, I assume it has to do with
Windows' bogus memory management scheme, and Borland's desire to make
it a non-issue.  That's all very nice, but it would seem to preclude
writing mass-market applications using the product.

Please let me be wrong on this... I *really* don't want to have to
keep using the SDK and C.  Any trick workarounds (that don't look as
ugly as the real thing) ?

Thanks, Tony Berke  (email -- tonyb@juliet.ll.mit.edu)