Path: utzoo!attcan!uunet!samsung!usc!rutgers!rochester!uhura.cc.rochester.edu!gwni
From: gwni@uhura.cc.rochester.edu (G. Wayne Nichols)
Newsgroups: comp.os.msdos.misc
Subject: HIMEM.SYS is a dog
Summary: V2.60 eats CPU cycles
Keywords: HIMEM.SYS
Message-ID: <10025@ur-cc.UUCP>
Date: 24 Oct 90 15:47:33 GMT
Organization: University of Rochester - Rochester, New York
Lines: 17

Last night I installed Windows 3.0 for the first time,
and among the new goodies to stuff in your CONFIG.SYS,
they supply a new version of HIMEM.SYS, version 2.60.
After rebooting (but before running Windows),
I happened to check the Landmark speed of the system.

Now my 20 MHz 0 wait state 386SX usually rates a 25.0
while using HIMEM.SYS 2.06.
With the new HIMEM.SYS, the rating dropped to 16 point something!!
(Yes, replace with the old one -- back up to 25).
What is happening -- is the new HIMEM.SYS forcing wait states or something?
Does it eat CPU cycles for lunch?

I don't want to lose 1/3 of my CPU power *before* running Windows!
Who knows how bad it will be *inside* Windows.

Any insights, folks?