Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!lll-winken!ncis.tis.llnl.gov!blackbird.afit.af.mil!ewilliam
From: ewilliam@afit.af.mil (News System Account)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: v10i111: dj1bin, GNU C and C++ for 386/DOS (part 01/36)
Message-ID: <1991Feb24.201347.12868@afit.af.mil>
Date: 24 Feb 91 20:13:47 GMT
References: <NELSON.91Feb11113723@sun.clarkson.edu> <1991Feb11.233356.18585@sj.ate.slb.com> <1991Feb13.165208.2645@agora.rain.com> <1991Feb20.173743.8872@dbase.A-T.COM>
Organization: Air Force Institute of Technology
Lines: 17

tomr@dbase.A-T.COM (Tom Rombouts) writes:

>In article <1991Feb13.165208.2645@agora.rain.com> tima@agora.rain.com (Tim Anderson) writes:
>>What DOS extender dos this thing use? I am not familiar with any that would
>>hold up to GNU's Copyleft... (and how do I get ahold of it??)

>Although I have not seen the source, just because it requires a 386 does
>not imply that any DOS extender is being used, just that some 386 specific
>instructions are being generated.  

The setup uses a DOS extender (required to get the flat address space that
UN*X programs are used to).  The extender is one written by the guy who did
the port, and placed it under the Copyleft provisions -- it is a good piece
of work, but assumes a plain system -- no QEMM, DESQview, or the like.

Ed Williams
ewilliam@blackbird.afit.af.mil