Path: utzoo!attcan!uunet!cs.utexas.edu!sdd.hp.com!hp-pcd!hplsla!davidr
From: davidr@hplsla.HP.COM (David M. Reed)
Newsgroups: comp.windows.ms
Subject: Re: himem.sys 2.60 and three bugs
Message-ID: <3130023@hplsla.HP.COM>
Date: 20 Jul 90 05:12:33 GMT
References: <11416@bsu-cs.bsu.edu>
Organization: HP Lake Stevens, WA
Lines: 25

I have a different problem with HIMEM.SYS that came with MSWindows3.
I have MSWindows3 installed in a 25 MHz 80386 system with MS-DOS 4.01.
If I use HIMEM then I am unable to open a "DOS Prompt" window.  If I
do not use HIMEM, or use an older version (such as from MSWindows/386)
then I can open a COMMAND.COM window.  But with the new HIMEM (needed
for full implementation of MSWindows3 Enhanced mode), if I try to start
up COMMAND.COM (via selecting it with a mouse, or selecting "DOS Prompt"
in the Program Manager, or even after defining a PIF), the screen clears,
and then is immediately repainted with MSWindows, and MSWindows pops up
an "Insufficient memory" message.

Just going to the DOS directory in File Manager and selecting various
executables, there are some that run just fine, others generate a message
of improper usage (expecting parameters), or report "Insufficient memory"
in the cleared screen before MSWindows is repainted.  It is only with
COMMAND.COM that MSWindows reports insufficient memory.  Programs like
MAPMEM report over 525 KBytes of free memory when they run from MSWindows.

I have re-installed MS-DOS and MSWindows several times.  Generally, 
everything seems to behave properly (other MSWindows and non-Windows
programs) within MSWindows3.  ONLY COMMAND.COM has a problem.  Even when
booting with a very minimal CONFIG.SYS and AUTOEXEC.BAT.  (That is how
it was determined that the problem is related to HIMEM.SYS.)  

Suggestions?