Path: utzoo!attcan!uunet!microsoft!jimmat
From: jimmat@microsoft.UUCP (Jim MATHEWS)
Newsgroups: comp.windows.ms
Subject: Re: himem.sys woes - fix???
Message-ID: <56224@microsoft.UUCP>
Date: 1 Aug 90 16:11:48 GMT
References: <1990Jul31.010650.2060@ux1.cso.uiuc.edu>
Reply-To: jimmat@microsoft.UUCP (Jim MATHEWS)
Organization: Microsoft Corp., Redmond WA
Lines: 29

In article <1990Jul31.010650.2060@ux1.cso.uiuc.edu> mcdonald@aries.scs.uiuc.edu (Doug McDonald) writes:
>I have posted several articles flaming the Win 3.0 himem.sys program.
>It refuses to let me run my 32-bit 386 programs that use the Phar Lap
>extender. I have a kludge around the problem which I am going to be
>rash enough to post. Please folks: this is for running programs with said
>Phar Lap extender. (There are commercial programs that use it.)
>It has not been tested for anything else. Caveat emptor. I have tested it
>extensively for two days for my work, including writing a program that
>zeroed all the extended memory it could malloc up.
>
   ...

>Again, caveat emptor.
>
>Doug McDonald


This is a very dangerous thing to do!  Hacking up himem.sys this way can 
cause your system's extended memory to be allocated to several programs
at the same time.  This would be extremely bad if you were using the
smartdrv.sys or emm386.sys drivers that come with Windows 3.0.  This
patch could easily cause someone to lose their hard disk.  smartdrv.sys 
is not the only disk cache that uses XMS memory allocation.  I strongly 
recommend that people do not apply this patch--it's too easy to forget
that it's been applied and do something very very bad to your system.

Jim Mathews

I seldom speak for myself, much less my employer.