Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!yale!cmcl2!lanl!nmsu!opus!ghenniga From: ghenniga@nmsu.edu (Gary Hennigan) Newsgroups: comp.windows.ms Subject: Re: himem.sys Message-ID: Date: 29 Jul 90 04:54:35 GMT References: <1990Jul27.154843.21611@ux1.cso.uiuc.edu> <1990Jul28.212853.8561@ux1.cso.uiuc.edu> <8661@ur-cc.UUCP> <1990Jul29.022443.610@ux1.cso.uiuc.edu> Sender: news@NMSU.edu Organization: NMSU Computer Science Lines: 24 In-reply-to: mcdonald@aries.scs.uiuc.edu's message of 29 Jul 90 02:24:43 GMT Well here's my two cents! I don't know exactly how himem.sys works but I believe it's intended function is a full memory manager and that Microsoft decided that as such it has full control over memory. This means that it ties up all the memory and allocates portions of it to applications as they request or have need of it. This works fine in windows where, through a PIF, you can tell windows how much extended memory to give an application on startup, at least in 386e mode. What I'm not sure of is what this means if you chose to exit windows and startup applications straight from DOS. Does himem.sys still portion out the memory or does it only function in the Windows environment? Maybe some MS person reading this could answer? Anyway that's the extent of my knowledge, at least as it pertains to MSW, well maybe most other things too! -- Gary Hennigan +---------------------------------------------------------------------------+ + e-mail: ghenniga@NMSU.Edu, henninsf@maxwel.NMSU.Edu + + Department of Electrical Engineering, Grad Student + + Physical Science Laboratory (ASS)istant systems programmer + +---------------------------------------------------------------------------+