delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/10/26/03:11:24

From: "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Q: How to make DJGPP-compiled program to be executed in a stay-alone circumstance?
Date: Tue, 26 Oct 1999 0:26:28
Organization: Aspen Technology, Inc.
Lines: 13
Message-ID: <3814f534.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 991024093556 DOT 29385P-100000 AT is>
NNTP-Posting-Host: dcloan.aco.aspentech.com
X-NewsEditor: ED-1.5.8
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> See the file CWSDPMI.DOC, it explains how to disable the swap file.

You can also use CWSPARAM to disable it in the image, or run CWSDPR0 (which
doesn't use a pagefile).

> I'm guessing that CWSDPMI didn't work because of the swap file
> problem.  Try again after you solve that problem, it might be that the
> other problems will also go away.  If not, post here the details.

No, the CWSDPMI message is just a warning - it doesn't hurt anything.  You
should just have malloc()/sbrk() return with a failure if you run out of
memory.  Nothing else should change.  Maybe there should be an option to
suppress the warning message ...

- Raw text -


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