🚀 go-pugleaf

cluma@innet.be (Marc Van Schandevijl) wrote:
>someone@somewhere.com wrote:
>>gmcandrew@aec.env.gov.ab.ca (Gordon McAndrew) wrote:
>>>Rosemary Culley <rosemary@sndc.demon.co.uk> wrote:

>>>;>I read that you can run memmaker which will give you even more memory
>>>;>for dos sessions but five files were needed, two nowhere to be found.

>>Memmaker sucks.  I tried using it under 6.22 when I had it, and it
>>took some memory away.  The best way to maximize memory for your
>>system, without third-party solutions, is to go through your system
>>files, line by line, and change them around, rebooting and doing a
>>memory check to see what is the most effective.  Also, do a little
>>homework.  Can you add a devicehigh line here or there.  Is there a
>>switch himem.sys or emm386 that can help you out?  A little homework
>>will give you the greatest amount of memory.  I repeat, MEMMAKER
>>sucks.  Delete it and save yourself some space.

>Always be careful to give advice based on one experience. I am a
>consultant, installing a lot of computers, and most of the time
>memmaker does what it is supposed to do.
>There ARE better tools, but memmaker is free and it works. Of course
>you can try afterwards changing your config or autoexec, but for most
>of the people this is much to difficult...


Right.  Well, I'm a consultant too, and *I* say Memmaker sucks as well.

Why?  Let me count the ways:

1) Cannot recover half the time if something freezes or doesn't work right
   while optimizing.

2) Creates files in the DOS directory which often force the machine into
   non-optimal states during the next attempted optimization, especially
   if the previous optimization didn't work right.

3) Doesn't allow you to easily play with load order and so forth.

4) Doesn't support called batch files, or last time I checked, Microsoft's
   own multi-config/selective menu system.

5) Frequently results in less available memory than rudimentary hand-optimizing.

6) There are others but I can't think of them at the moment.


I haven't touched that dog-of-a-program for years.  If I need as much DOS 
memory as possible I follow the following pecking order:

Optimize by hand.   If I need more available memory, I use Helix' multimedia 
cloaking to load diskcache, DOS mouse driver, and MSCDEX in XMS memory. (good
savings for the most common memory hogs and very few compatibility/complexity
problems)  If I still need more, I install QEMM.



Phil


--
Philip J. Koenig         Computers & Communications           pjk@aimnet.com

[Notice: the contents of any unsolicited email sent to this email address
 is hereby declared public property and may be used for any purpose I deem
 necessary.  You have been warned.]