delorie.com/archives/browse.cgi | search |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: a.out.h |
Date: | Thu, 28 Nov 2002 13:16:43 CST |
Organization: | Rice University, Houston TX |
Lines: | 15 |
Message-ID: | <3de66b9b.sandmann@clio.rice.edu> |
References: | <3de640b6$0$8306$9b622d9e AT news DOT freenet DOT de> <as5fuf$mld$1 AT antares DOT lu DOT erisoft DOT se> |
NNTP-Posting-Host: | clio.rice.edu |
X-Trace: | joe.rice.edu 1038511313 15295 128.42.105.3 (28 Nov 2002 19:21:53 GMT) |
X-Complaints-To: | abuse AT rice DOT edu |
NNTP-Posting-Date: | 28 Nov 2002 19:21:53 GMT |
X-NewsEditor: | ED-1.5.9 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> : And why did aout.h come with DJGPP v1? > > Perhaps _that_ was an a.out system? V1.09 was a.out, and did not support DPMI (Windows) at all. V1.09d was a patched version of 1.09, supported DPMI (Windows 3.1, OS/2, etc), but the a.out format required lots of wasted memory. The smallest images took a minimum of 5Mb of memory (each) to run. V1.10 or V1.11 moved to COFF format for better debugging and DPMI memory layout support. So early DJGPP V1.x releases were a.out format, the later ones were coff.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |