delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/04/21/12:30:03

Date: Thu, 21 Apr 1994 11:49:22 -0500 (EST)
From: "WONKOO KIM, EE, U. OF PITTSBURGH" <WKKST AT vms DOT cis DOT pitt DOT edu>
Subject: Re: 2 questions about readme.dj
To: babcock AT cfa DOT harvard DOT edu
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu

>Date: Thu, 21 Apr 1994 10:16:43 -0400 (EDT)
>From: peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
>Subject: RE: 2 questions about readme.dj
>
>> >How can I tell if I *may* need to use the 16-bit gcc driver on OS/2 2.0?
>> 
>> I think the size of free system memory will determine this.  With enough
>> size of system memory (8MB ?), regular 32-bit gcc.exe worked just fine. 
>
>Have you tried multiple compilations in the same window with 32-bit gcc?  My
>experience was that it would crash around the 14th compilation.  The problem
>goes away with the real-mode gcc.

Maybe you are right, as I haven't tried so many compiling under the same OS/2
dos session.  If so, 32-bit gcc leave some garbage in memory after every
execution and eat up all dos memory after many executions??
If this really happened under DPMI, what about under Windows(non-OS/2) dos box?
Do you experience the same thing? (Maybe after a lot many # of execs)

Wonkoo Kim
wkim AT vms DOT cis DOT pitt DOT edu


- Raw text -


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