Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!aries!mcdonald
From: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Newsgroups: comp.windows.ms
Subject: Re: himem.sys
Message-ID: <1990Jul28.212853.8561@ux1.cso.uiuc.edu>
Date: 28 Jul 90 21:28:53 GMT
References: <1990Jul27.154843.21611@ux1.cso.uiuc.edu>
Sender: usenet@ux1.cso.uiuc.edu (News)
Reply-To: mcdonald@aries.scs.uiuc.edu (Doug McDonald)
Organization: School of Chemical Sciences, Univ. of Illinois at Urbana-Champaign
Lines: 23

In article <1990Jul27.154843.21611@ux1.cso.uiuc.edu> I wrote:
>I sort of like Windows 3.0, but it has one terribly irritating flaw -
>fatal, in fact: it won't run in extended 386 mode, the only useful way
>to run it, without the himem.sys that comes with it. With himem.sys
>installed, none of my other 386 programs will run.
>
>
>IS there a way around this? Somebody surely could make a himem.sys program
>that can be turned off. Qemm for example, can be turned off. OR
>make one that can be removed?
>
>
>Is anyone at Microsoft listening??????????????
>

I discovered a new piece of info: If I include himem.sys (the win 3.0 one)
in my config.sys file but not smartdrive, then I CAN run my 386 programs
(with the Phar Lap extender) happily all day - UNTIL I run Windows 3.0
itself. After that, the 386 programs won't run until I reboot. Could
it be that himem.sys is not completely releasing memory when it is no
longer used?

Doug McDonald