Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!munnari.oz.au!bruce!sol6!maurice
From: maurice@sol6.cs.monash.edu.au (Maurice David Castro)
Newsgroups: comp.sys.ibm.pc
Subject: Re: EMM386.EXE slows down Hyperdisk
Message-ID: <4481@bruce.cs.monash.OZ.AU>
Date: 24 Jun 91 09:38:33 GMT
Article-I.D.: bruce.4481
References: <25639@well.sf.ca.us>
Sender: news@bruce.cs.monash.OZ.AU
Distribution: comp
Lines: 34

From article <25639@well.sf.ca.us>, by al@well.sf.ca.us (Alfred Fontes):
> I followed the directions in Chaper 12 of my spiffy, new DOS 5.0 manual
> about loading everything into high memory.  Unfortunately, EMM386.EXE
> seems to slow Hyperdisk down, on the order of 50%.
> 
> Has anybody else had this problem?  What can I do about it?
> 
> Al Fontes, Jr.
> -- al@well.sf.ca.us --
> -- uunet!apple!well!al --

I make no use of hyperdisk, however, my 386sx has a bios which supports
so called "extended features", the memory manager provided with the 
machine has served me well and is LIM4.00 standard so I took the path of 
least risk and used the built in EMM. 

I think that you will probably be able to use the original memory manager
you were using before DOS5 came along provided it is compliant with either
LIM3.2 or LIM 4.0 compliant (quoting the DOS 5.00 manual). Apart from being the
standard for LIM there seems to be no advantage in using EMM386.

The memory savings gained by DOS 5 are dependent on high memory not on 
Extended/Expanded (I can never remember which one is which) so are
not dependent on EMM386

WARNING: If you suspect that your original memory manager is going to 
cause problems, then do NOT attempt what I have outlined! Merely because
it appears to work safely in one circumstance does not guarantee safe
operation for all.

Maurice Castro
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
maurice@bruce.cs.monash.edu.au
(Disclaimer: All care taken, but no liability accepted)