www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/08/28/05:49:19

Xref: news2.mv.net comp.os.msdos.djgpp:7958
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: oy. =) this is a quick and easy question I'm sure..
Date: Sun, 25 Aug 1996 12:14:17 CDT
Organization: Houston Supernet& Tulsa Supernet
Lines: 11
Message-ID: <322089e9.sandmann@clio.rice.edu>
References: <4vpuff$rqo AT tor-nn1-hb0 DOT netcom DOT ca>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: dmccbk.dmccorp.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

>     Okie, I'm a long time borland programmer who is just making his
> move to DJGPP..  I was frightened to discover a problem during
> compilation that goes something like "cannot compile 16 bit apps."

The messsage is "Can't handle 16 bit apps, sorry!" and comes from CWSDPMI.
The problem is you are trying to run a 16-bit DPMI application while CWSDPMI
is loaded.  This is probably due to having Borland's bin directory in your
path before DJGPP, and it picks up one of the apps from BCC instead.  
Either remove the Borland executables from your path (best bet) or put them
in the path after the DJGPP bin directory.  Don't try to mix the protected
mode makes or CPP's, or you will just cause yourself problems.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019