this was suppose to be a response to; http://www.computing.net/answers/do... But the thread was too old , still , I hope this will help someone I too had a problem with dos 6.20 and memmaker , If you don't want to read on , I fixed my emm386 crashing my program problem by replacing ver6.2 emm386 and himem.sys with the versions from dos6.22 I have a dos program that requires 540k of conventional memory , and it needs networking , I changed the network , and now that requires more memory and there isn't enough for both. I ran memmaker , and now my program locks up.. Whats odd is that if I use my original config.sys and autoexec , with no sizer or chkstate , it still locks up , no trick I have learned or manual edit will change the situation. A full restore from an image backup fixed the lockup problem , but I still couldn't free enough UMBs to load the network high. I tried memmaker again .. now my program crashes unless I rem out emm386 , and without it , I cant run my program and the network at the same time.. I tried several versions of emm386 from dr-dos and freedos , I also tried jemm...... I found they only work if you also use the himem program from the same version of dos you got emm386 from. I found all these non-MS memory managers will free more memory while using less themselves , but my network (AILANBIO) wont load high and fails saying not enough memory and wont load low .. that doesn't happen with the MS memory managers??? Wonder why? So I went back to MS and tried the himem.sys and emm386 from 95 and 98 , with the /V (verbose) switch , emm386 loads with no error and reports its providing memory , but loadhigh and devicehigh have no effect and mem /c shows that upper memory wasn't used at all (weird?). So in the end , just for Sh*!s and giggles , I tried the himem and emm386 from dos 6.22 , low and behold , it worked! .. for me I needed the noems and i=b000-b7ff parameters... highscan caused no harm So , the question not answered ... what changes (besides config.sys and autoexec.bat) , what else does memmaker do that causes programs to freeze? How , when I restore config.sys and autoexec.bat from backup, then use F8 to skip the program that freezes, how does memmaker come back to the 'press enter to restore previous settings' screen? Is that a clue?

Jeez a follow up to a 4 year old thread, Einstein? This is MS Memmaker Technet Page: http://technet.microsoft.com/en-us/... This also begs the question why you are using version 6.20 when M$ themselves issued a "stepup" to 6.22 which fixed several issues (page last updated 2002): http://support.microsoft.com/kb/119151 http://www.microsoft.com/downloads/...

For something technically complex like what you seem to be describing, I wouldn't mess with memmaker at all. Memmaker was created by Microsoft to help people who didn't have the time or inclanation to study the intricate vulgarities of DOS upper memory allocation. There is no way an automated program can set up DOS upper memory better than a patient person who knows what he's doing can. Due to the wide variations in hardware and software involved there are thousands of unique combinations possible. It takes someone examining the unique hardware and software of the particular machine in question to best determine which UMBs are really "free" and which divers/TSRs need to be loaded in what order. I've used memmaker, it is satisfactory for general use, but it does a half-assed job when things are really tight.

The final version of memmaker and its associated files can be found here: http://support.microsoft.com/defaul... in the OLDDOS.exe download. I'd think the 95 versions of himem.sys and emm386.exe would work with 6.2 also, but haven't tried them. When you run memmaker it has to reboot twice. It adds a line in config.sys and maybe autoexec.bat to keep track of where it's at. If you restored one of those intermediate versions that's why you're getting the message about restoring the previous settings. The original (pre-memmaker) versions of config.sys and autoexec.bat will be saved in your dos directory with UMB extensions. You can manually rename them and copy over the memmaker versions, if necessary.

Why don´t you try DOS7.10 that itself can be loaded in the upper memory blocks? I´m using it in my 486´s and is stable and works properly. In case you have any problem with version, it has ver command to report 6.22 version of DOS. Good luck If there is a possibility of several things going wrong, the one that will cause the most damage will be the one to go wrong.