Path: utzoo!attcan!uunet!cs.utexas.edu!rutgers!sunybcs!uhura.cc.rochester.edu!ttak
From: ttak@uhura.cc.rochester.edu (Timothy Takahashi)
Newsgroups: comp.windows.ms
Subject: Re: himem.sys
Message-ID: <8661@ur-cc.UUCP>
Date: 28 Jul 90 22:57:01 GMT
References: <1990Jul27.154843.21611@ux1.cso.uiuc.edu> <1990Jul28.212853.8561@ux1.cso.uiuc.edu>
Reply-To: ttak@uhura.cc.rochester.edu (Timothy Takahashi)
Organization: University of Rochester
Lines: 18

In article <1990Jul28.212853.8561@ux1.cso.uiuc.edu> mcdonald@aries.scs.uiuc.edu (Doug McDonald) writes:
>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
>
>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?

Definately, somethings up here. Before I run Windows 3.0, the Dos 4.0 MEM
command reports extended memory available. After I run Windows 3.0, squat.

My setup : 386sx clone (Phoenix BIOS, C&T NEAT, MFM Hard Drive), IBM PCDOS 4.0
            Windows 3.0 (bought the day it was released)

tim