Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!spool.mu.edu!uunet!microsoft!philba
From: philba@microsoft.UUCP (Phil BARRETT)
Newsgroups: comp.windows.ms
Subject: Re: himem.sys problem
Message-ID: <71472@microsoft.UUCP>
Date: 23 Mar 91 18:39:10 GMT
References: <103523@unix.cis.pitt.edu> <1991Mar18.191709.4270@zeus.mgmt.purdue.edu>
Reply-To: philba@microsoft.UUCP (Phil BARRETT)
Distribution: usa
Organization: Microsoft Corp., Redmond WA
Lines: 31

I missed the first article (vacation, y'know) so I didn't see all the detailed
description of the problem and this may have been tried already, forgive me
for chewing up net bandwidth if so.  

Have you tried the different machine options that himem supports?  Use the
/m: option.  The readme goes into some detail.

The Himem line would look like:
device=c:\himem.sys /M:1    (for example, using machine type 1, see the readme)

also, this may not be a popular suggestion but product support does know
pretty much about this and can often answer this question quickly.

good luck
phil

In article <1991Mar18.191709.4270@zeus.mgmt.purdue.edu> landers@zeus.mgmt.purdue.edu (Chris Landers) writes:
>In article <103523@unix.cis.pitt.edu> pjp23@unix.cis.pitt.edu (Paul J Pival) writes:
>>My himem.sys is incompatible with my machine (a clone 286 12mhz).
>>Is there a substitute out there I can access?  Thanks in advance.
>
>Make sure that you are using the himem.sys shipped with Windows 3.0, not 
>versions that came with various DOS distributions, or Windows 2.x.
>
>Also, himem.sys will only install if you have only extended memory, not
>if you have expanded memory only.
>-- 
>   <================================><===============================>
>   || Christopher Landers           || PURDUE UNIVERSITY - KRAN 708 ||
>   || Krannert Computing Center     || West Lafayette, IN  47907    ||
>   <=================== landers@zeus.mgmt.purdue.edu ================>