delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:4392 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: \windows\emm386 broken, \dos\emm386 works |
Date: | Mon, 15 Jan 1996 08:48:09 CST |
Organization: | Rice University, Houston, Texas |
Lines: | 13 |
Message-ID: | <30fa6929.sandmann@clio.rice.edu> |
References: | <4dd0br$6mg AT leonard DOT anu DOT edu DOT au> |
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 |
> _excrutiatingly slowly_ under dos 6.2. Eventually I discovered that using > the \dos\emm386.exe instead of \windows\emm386.exe solved the problem. The DOS 6 EMM386 pools XMS and EMS memory. The Win 3.x (and DOS 5) would have fixed allocations of memory between EMS and XMS, with the default being 256K EMS. Since GO32 uses VCPI/EMS memory, you only get 256K of memory under the stupid fixed allocation of the earlier EMM386 versions. There are workarounds for the earlier EMM386 versions, but the easiest fix is to change to something else, like you did. Checking the memory that DJGPP sees as available with the GO32 command should be the first thing you do before trying any real work on a box. If it's not at least 3Mb, you need to see if you can find some more.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |