delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1994/03/24/01:33:23

Date: Thu, 24 Mar 94 14:40:21 JST
From: Stephen Turnbull <turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp>
To: FIXER AT FAXCSL DOT DCRT DOT NIH DOT GOV
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: cannot exec go32

I'm not sure what's going on with your make problem.  Since you use
QEMM and presumably are pretty amazingly optimized, I assume you're
not having the "too many GO32s running at once" problem (I think thereGO32.
should be three in your case, for a total of approx 480KB free
program space required under 640KB).  This of course is DJ's case 2.
    QDPMI and GO32 don't like each other much.  In particular, if (1)
you have QDPMI running *and* (2) you have some of QEMM's memory
protection features turned on (as in DV/X) *and* (3) you are using
either edebug or GO32=topline ..., then QEMM objects to attempts to
write to screen memory (this may only be in a DOS window under DV/X, I
don't recall having it happen under DOS, I almost never run under DOS
alone).  However, this should give you an "illegal access" message
from QEMM, not a GO32 failure.
    Still, I would try turning off QDPMI.
    Yet another possibility (but unlikely if you have lots (> 500KB)
of free DOS program space before running make), is that some of the
methods of passing long args to DJGPP programs use environment
variables, and this could up the needed space enough to trash your
third GO32.
    --Steve


- Raw text -


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