www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/02/10/09:24:27

Xref: news2.mv.net comp.os.msdos.djgpp:934
Newsgroups: comp.os.msdos.djgpp
From: peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock)
Subject: cwsparam parameter meanings
Message-ID: <DMFz1K.J3q@cfanews.harvard.edu>
Sender: news AT cfanews DOT harvard DOT edu
Reply-To: rbabcock AT cfa DOT harvard DOT edu
Organization: Smithsonian Astrophysical Observatory, Cambridge, MA, USA
Date: Thu, 8 Feb 1996 05:24:55 GMT
Lines: 20
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

After reading the docs for CWSPARAM, I'm not sure I understand two of
the parameters.  I get my DPMI services from OS/2, but my users may need
to use CWSDPMI, so I need to advise them on proper settings.

> Minimum application memory desired before 640K paging ? [256Kb]
>   This parameter determines the threshold which CWSDPMI
>   should start using DOS memory as DPMI memory.

What is it that is crossing a threshold?  Does the default 256K value mean
that DOS memory will be used as DPMI memory if unused extended memory drops
below 256K?

> Paragraphs of DOS memory to reserve when 640K paging ? [3840]

If a program has a shell-to-dos function, does this parameter control how
much memory is available in the shell?

In general, how should I advise my users to set these options for a program
which is relatively small (~200K), but may require arbitrarily large amounts
of memory for data and may want to spawn a DOS program or DOS shell?

- Raw text -


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