Mail Archives: djgpp/2000/12/05/14:06:49
ftp://clio.rice.edu/djgpp/eatmem.exe
ftp://clio.rice.edu/djgpp/eatmem.c
This allows you to arbitrarily consume some amount of DOS memory and > 1Mb memory.
It was designed for use with an EMM provider (EMM386, etc) and requires linking
with the CWSDPMI build directories. I have an equivalent someplace which works
with raw and/or XMS, but I couldn't find it (it called XMS directly if HIMEM was
present, and hooked both int 15's for memory size if not). If you could wait
several days I might be able to find it...
This is one of the little utilities tossed together to test CWSDPMI under various
memory environments.
> I use dos that comes with Win95 OSR2. Can himem.sys be used to control
> amount of memory used by DPMI? Or should I just hack CWSDPMI and rebuild it?
> May be somebody can suggest a patch to CWSDPMI (or at least function
> name/filename to hack in)?
You can either write a program which makes an XMS call before calling your
program to consume some of the memory, or modify valloc.c in cwsdpmi to
override the memory size returned from XMS.
> And IMO it seems that limiting amount of RAM is a general purpose task, so
> support for it can be added to cwsparam.exe/cwsdpmi.exe (or solution added to
> FAQ).
I was planning to eventually release my QC suite with the utilities, and that
would be one of them.
- Raw text -