Mail Archives: djgpp/1999/07/23/04:53:18
Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote:
: On Thu, 22 Jul 1999 mdruiter AT cs DOT vu DOT nl wrote:
: > IIRC, CWSDPMI only supports up to 128MB of *virtual* memory. At least,
: > it doesn't give me more than that.
:
: No, it supports up to 256MB of physical and additional 256MB of paged-out
: memory, for a grand total of 512MB of vurtual memory. If this doesn't
: work for you, either you have an old version of CWSDPMI (before r4), or
: something is wrong in your setup, or some memory manager you install
: prevents CWSDPMI from giving you more.
Hmm. My lastest box (the screaming 20MHz with 4MB of RAM) seems to
think differently:
Filesystem Type 1024-blocks Used Available Capacity Mounted on
\\KANT\TMP net 2402586 2028571 374015 84% t:/
go32/v2 version 2.0 built Mar 20 1999 14:47:50
Usage: go32 coff-image [args]
Rename this to go32.exe only if you need a go32 that can run v2 binaries as
well as v1 binaries (old makefiles). Put ahead of the old go32 in your PATH
but do not delete your old go32 - leave it in the PATH after this one.
Set GO32_V2_DEBUG=y in the environment to get verbose output.
DPMI memory available: 3414 Kb
DPMI swap space available: 129818 Kb
cwsdpmi -p -st:\cwsdpmi.swp
CWSDPMI V0.90+ (r4) Copyright (C) 1997 CW Sandmann ABSOLUTELY NO WARRANTY
And doing a simplistic "b = (char *)malloc(A_LOT); for(i=0; i < A_LOT;
i += 4096) { b[i] = 1; }" verifies that only ~128MB is available.
Can it be the low amount of RAM (4MB) that cause this?
Right,
MartinS
- Raw text -