Dale Mentzer wrote:
>MSDOS's MemMaker figures the size of each program that it loads high and
>includes this size on the applicale LH line for each program or driver in
>the autoexec.bat file. IIRC, it loads them in memory biggest to smallest.
>Also some program use LESS memory after loading and you will be able to see
>this in the size switch that MemMaker assigns for each item.
This still doesn't explain why I under a normal MS-DOS 6.2 (that is only
using the TSRs that came with it) the free memmory was less after memmaker
had changed.
I saw in a magazine around the same time how to fix a memmory problem one
user had (when playing the latest NHL version for that year). They suggest
he should undo all the changes memmaker had done.
One doesn't have to know much (actually nothing) about memmory to do a
better job than memmaker. The rules are quite simple (once you know them):
Use these in config.sys:
device=c:\dos\himem.sys /TestMem:Off
device=c:\dos\emm386.exe noems highscan
dos=high,umb
Then just add "lh" before every line that starts a program in autoexec.bat
and change all "device=" to "devicehigh=" in config.sys (without quotes of
course).
Done, and that's much faster then memmaker who reboots a few times.
Granted if you load many (or memmory hungry) TSRs you might need to remove
a few "lh" and/or "devicehigh" to get max memmory free, but that's not that
common anyway. Besides running mem/c tells you what you need to know (as
soon as you know the diffrence between conventional and upper memmory that is).
//Bernie
http://hem1.passagen.se/bernie/index.htm DOS programs, Star Wars ...
