On 9 Jan 00 at 11:47, Bernie wrote:
>>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).
I have had no complaints about MemMaker and I certainly have no
complaints about doing it "by hand" ;) and I would hardly consider
myself a memory guru. Of course for a typical pre-Windows DOS user it
was probably OK, but of course many, most, or all of the memory
manager programs I have used include some type of memory optimizer
program to "simplify" their installation and setup, so there
certainly is or was a demand for such programs, or I doubt the
software publishers would have spent their resources developing them.
Regards,
Dale Mentzer
It's hard to make a comeback when you haven't been anywhere
This mail written by a user of Arachne, the DOS Internet Client
WWWWW World Wide Web Without Windows
http://home.arachne.cz Arachne DOS Browser Home Page
