Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!cs.uoregon.edu!akm
From: akm@cs.uoregon.edu (Anant Kartik Mithal)
Newsgroups: comp.windows.ms
Subject: Re: How to get extended mem back after a windows session?
Summary: why do we need himem at all?
Keywords: extendedmemory,  himem.sys
Message-ID: <1990Oct26.195130.17719@cs.uoregon.edu>
Date: 26 Oct 90 19:51:30 GMT
References: <90297.155820MUHRTH@DB0TUI11.BITNET>
Sender: news@cs.uoregon.edu (Netnews Owner)
Organization: Department of Computer Science, University of Oregon
Lines: 21

In article <90297.155820MUHRTH@DB0TUI11.BITNET> MUHRTH@tubvm.cs.tu-berlin.de (Thomas Muhr) writes:
>Nothing against the sophisticated memory management of himem.sys, but
>we use older software which needs extended memory and has no chance to
>communicate their needs via himem. Smalltalk V/286 for example.
>Is there a utility available which after invocation of windows, I mean,
>after leaving it, gives extended memory back for undiscplined programs?

I actually don't understand why we need himem.sys at all. After all,
both 286 and 386 systems can address extended memory without a
problem (in protected mode), so why do we need to use himem? I
understood the logic for emm, but not xms.

kartik



-- 
Anant Kartik Mithal                                     akm@cs.uoregon.edu
Network Manager, 					(503)346-4408 (msgs)
Department of Computer Science,                         (503)346-4156 (direct)
University of Oregon, Eugene, OR 97403-1202