Xref: utzoo comp.windows.ms:9093 comp.windows.misc:1800
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!att!devildog!devildog.att.com
From: jdalin@devildog.att.com (Jimmy Dalin)
Newsgroups: comp.windows.ms,comp.windows.misc
Subject: Insufficient Memory
Message-ID: <1853@devildog.att.com>
Date: 7 Feb 91 21:38:44 GMT
Sender: jdalin@devildog.att.com
Followup-To: comp.windows.ms
Distribution: na
Organization: AT&T IMS - Piscataway, NJ (USA)
Lines: 25

Help!  I'm sure that this is an easy problem to solve, but so far it's
got me absolutely stumped.  I'm running Windows 3.0 on a 386-20 system
in 386 enhanced mode.  I started using 386MAX version 5.1 earlier this
week, but the problem existed before 386MAX, and it still continues.
I have 4 meg of memory.
 
In a nutshell: when I double click on the DOS prompt within Windows to
drop temporarily into DOS 4.01, virtually anything I try to do is
rejected with an "Insufficient memory" error message.  Even CHKDSK, for
example, will not execute.
 
Thanks to 386MAX, I can run a handy memory map routine (386UTIL.COM /M).
When I run it from Windows, it tells me that I have about 575K available
memory.  When I drop into DOS and run the same utility, it tells me that
I have only about 34K available memory.  Even stranger, when I run the
utility from DOS, the low memory numbers don't even add up to anything
like 640K!  It's as if some 540K of memory just disappeared; the utility
tells me that memory stops at 1E00, instead of going up to A000, which
is listed as the end point when I run the same utility from within
Windows.
 
I have no special drivers or TSR's running, and I installed Windows 3.0
taking all of the usual defaults.  I have colleagues with basically the
same setup as mine who are not experiencing this problem.  Thanks in
advance for any possible help.