Xref: news2.mv.net comp.os.msdos.djgpp:3284 From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: giving back dpmi memory?? Date: Tue, 30 Apr 1996 09:34:05 CDT Organization: Rice University, Houston, Texas Lines: 29 Message-ID: <318624dd.sandmann@clio.rice.edu> References: Reply-To: sandmann AT clio DOT rice DOT edu NNTP-Posting-Host: clio.rice.edu To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp > All I know is that other programs can't find free XMS/EMS memory. I'm using > cwsdpmi. When I spawn the dos program "mem", every byte of memory > (conventional, upper, and extended) is counted as used. This depends on your memory configuration. If you have a VCPI memory manager (recent emm386/qemm/etc) loaded which pools XMS/EMS memory then this works fine, since CWSDPMI asks the VCPI memory manager for pages one at a time. If you need more memory than you have, then there won't be any left. If you use an early emm386 (Win 3.x or DOS 5) it won't pool either (but you can manually fix some XMS to be saved). If you only have HIMEM, CWSDPMI will use it all (since it doesn't handle XMS fragmenting). If you need extra memory for a program, either use V1.x (which forces a swap of memory on XMS systems) or buy more ram and a decent memory manager. > When I try to run win (3.11) it swaps CONSTANTLY. This means you don't have enough RAM for what you are trying to run. Buy more, no workaround. > When I try to run other programs > which are 16-bit real mode that don't swap, and do depend on XMS or EMS, > it complains that there isn't enough free memory and I should uninstall > some drivers or buy more ram. So, the software told you the answer - the last 3 words. If software is well designed it can handle virtual memory if it's available. It seems the software you are trying to run can't, so you need to upgrade the hardware or software, one of the two.