Mail Archives: djgpp/1995/06/03/00:22:40
> Date: Fri, 02 Jun 95 22:21:30 -0400
> From: peprbv AT cfa0 DOT harvard DOT edu
> To: wkim+@pitt.edu
> Reply-To: rbabcock AT cfa DOT harvard DOT edu
> Subject: Re: DJGPP in DOS session under OS/2 Warp?
>
> > The current djgpp's gcc may not crash in a OS/2 DOS session after many
> > compilations since we've had many updates in djgpp so far.
>
> It looks like it may have been fixed. I was able to compile a very short
> routine 20 times, and I'm now building something real and have gotten most of
> its 100 or so routines compiled.
>
> > I think that the magic number 14 (if exist) should depend on the assigned
> > DPMI memory size of a DOS session, if there is any such magic number to
> > crash.
>
> I just checked; I've got that window set to 24MB (it didn't use to be that
> high). Djgpp doesn't need that much, but the program I'm compiling may when
> I stress test it. I've also got video_mode_restriction set to cga to give a
> 720K window which means I don't have to tell OPUS MAKE to page itself out for
> each compile. OS/2 and djgpp have been updated. At least 4 things have
> changed, and one of them fixed it.
I thought I sent my previous message to djgpp list, but only to you...
I also did a small test. With default settings (4MB DPMI, etc.) of
an OS/2 Warp DOS session, djgpp's regular gcc didn't crash even after
30 recompilations in one window. So, I assume that djgpp does not
have any problems with OS/2 Warp's DOS session. FAQ listed the crash
problem (#2.2), but I think the problem has been fixed in OS/2 Warp.
My djgpp version is 1.12.maint3. I think djgpp's memory requirement
has been also improved. I recall that 4MB DPMI was not enough for
old djgpp (5MB required), but now djgpp can run with small memory.
//--------------------------------------------------------------------
// Wonkoo Kim
// wkim+@pitt.edu
- Raw text -