Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!sdd.hp.com!hplabs!otter.hpl.hp.com!hpopd!richardh
From: richardh@hpopd.pwd.hp.com (Richard Hancock)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Windows 3, HIMEM.SYS and Extended Memory
Message-ID: <59630004@hpopd.pwd.hp.com>
Date: 7 Jan 91 13:20:42 GMT
References: <1991Jan4.003923.29710@hellgate.utah.edu>
Organization: Hewlett-Packard CCG-PWD, UK.
Lines: 14

/ hpopd:comp.sys.ibm.pc.hardware / dcc@hpopd.pwd.hp.com (Daniel Creswell) / 12:29 pm  Jan  7, 1991 /

> Himem.sys provides access to a 64K High Memory Area (a chunk you can't
> usually) get at. This is a small area of extended memory above 1Mbyte.

I believe that Himem provides Windows with access to ALL extended memory by
implementing the XMS specification. (Himem only accessed the first 64K-16 bytes
- the High Memory Area - of extended memory in Windows 2.x).

Windows effectively takes-over your extended memory and provides the XMS
interface to it. It's likely that your memory checking programming doesn't talk
XMS.

Richard.