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: <1990Jul29.022443.610@ux1.cso.uiuc.edu>
Date: 29 Jul 90 02:24:43 GMT
References: <1990Jul27.154843.21611@ux1.cso.uiuc.edu> <1990Jul28.212853.8561@ux1.cso.uiuc.edu> <8661@ur-cc.UUCP>
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: 26

In article <8661@ur-cc.UUCP> ttak@uhura.cc.rochester.edu (Timothy Takahashi) writes:
>In article <1990Jul28.212853.8561@ux1.cso.uiuc.edu> mcdonald@aries.scs.uiuc.edu (Doug McDonald) writes:
>>
>>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)
>

Ah ---- 

I tried it on a gen-u-ine IBM PS/2 Model 80. 100% true blue. Tried
IBM DOS 3.3 and IBM DOS 4.01.


Same problem.

Doug McDonald