When I use MS Memmaker.exe (selecting the Express setup) it appears to execute without fault. the following lines are written to autoexec.bat and config.sys respectively: c:\dos\memmaker.exe\session:24887 and device=c:\dos\ckstate.sys /s : fr1/24887. When I reboot I get a full page warning that memmaker.exe has terminated without completion and options are given to restart memmaker or continue. Restarting produces the same warning on the next boot, Continuing throws up no problems. Deleting the entries in autoexec & config.sys stops the warning from appearing. Can anyone shine a light on this problem please?? Thanks V...

Never seen any warnings while using memmaker. Any virus, hardware problems, incorrect configuration in CONFIG.SYS, or file corruption?

Hi Wengier - kinda hoped you would pick up this one. No recognised virus probs, pc is not conn to Internet although transfers by floppy do occur - scan with McAfee shows no infection. No known hardware probs - everything working perfectly. Config.sys shows no error message - everything loading normally. File corruption - well.. sorry, don't know about that one. The error message seems to be generated by ckstat as it appears before all other checks & loading. I will re-install Dos 7.1 and try again. Thanks V...

Valarie, You can try download the latest DOS install CD from: http://newdos.yginfo.net/dosware/dos71cd.zip This now includes Memory Maker (MEMMAKER) as a standard DOS add-on, which can be installed automatically during DOS installation if you choose to install it (of course I have already tested this MEMMAKER Add-On for many times, so it should work fine).

Thanks Wengier - unfortunately I do not have a CDR so rely on floppies. Is it possible that I have simply run out of extended memory space? The message I get on warm and cold boot up is: "Your computer was restarted before MemMaker finished optimizing your system's memory. If your computer was restarted accidentally, or if you are not sure why MemMaker was interrupted, choose 'Continue' If you restarted your computer because it was not working properly, choose 'Exit & undo changes' to restore your original system files. Then see the Troubleshooting section of the 'Making more memory available' chapter in the MS-DOS User's Guide" The message I get when re-starting MemMaker is: "MemMaker has been run on your computer before, but did not finish optimizing your computer's memory. To optimize your computer's memory choose 'Restart Optimization'. MemMaker will then restart the optimization process. To undo changes.......etc. etc." Every time I have run MemMaker it appears to terminate normally. My Config.sys file is: DEVICE=C:\DOS71\CHKSTATE.SYS /S:FR1 /22513 DEVICE=C:\DOS71\HIMEM.SYS DEVICE=C:\DOS71\EMM386.exe NOEMS BUFFERS=30,0 FILES=30 DOS=UMB LASTDRIVE=E FCBS=4,0 DOS=HIGH DEVICEHIGH /L:1,17408 =C:\DOS71\SETVER.exe DEVICEHIGH /L:1,9712 =C:\DOS71\ANSI.SYS DEVICEHIGH /L:1,18112 =C:\DOS71\DISPLAY.SYS CON=(EGA,437,1) DEVICEHIGH /L:1,11264 =C:\DOS71\VIDE-CDD.SYS /D:IDE-CD SHELL=COMMAND.COM /P /E:640 NUMLOCK=OFF STACKS=9,256 BREAK=ON SWITCHES=/W Autoexec.bat is: @ECHO OFF PATH C:\WINDOWS;C:\DOS71;\C:\DOS MODE CON RATE=32 DELAY=1 LH /L:1,14624 DOSLFN /Z:C:\DOS71\CP437UNI.TBL LH /L:1,2912 KILLER LH /L:1,6144 DOSKEY LH /L:1,27952 MSCDEX /D:IDE-CD LH /L:0;1,45584 /S SMARTDRV 1024 LH /L:0;1,3328 /S CTMOUSE LH /L:1,5536 C:\DRIVER\HERCULES\VESA REM For compatiblity purpose: CTMOUSE > NUL BREAK ON LFNFOR ON SET SOUND=C:\VIBRA16 SET BLASTER=A220 I5 D1 H5 P330 T6 SET MIDI=SYNTH:1 MAP:E SET DIRCMD=,/ON/P SET COPYCMD=/Y C:\VIBRA16\DIAGNOSE /S C:\VIBRA16\MIXERSET /P /Q setkeys.bat C:\DOS71\MEMMAKER.exe /SESSION:22513 Thanks V...

Just take out that last line from your autoexec.bat . C:\DOS71\MEMMAKER.exe /SESSION:22513 It appears memmaker has optimized your files correctly. There's no need for it to run again. HTH, Michael

Valerie, "setkeys.bat C:\DOS71\MEMMAKER.exe /SESSION:22513 So, from your AUTOEXEC.BAT, I know exactly why that happens!! Just change the second last line of AUTOEXEC.BAT from: "setkeys.bat" to: "call setkeys.bat" Then it should work!! The reason for this is: Then AUTOEXEC.BAT executes the line "setkeys.bat", it will run setkeys.bat and WILL NOT return AUTOEXEC.BAT any more, so the last line of your AUTOEXEC.BAT (i.e. "C:\DOS71\MEMMAKER.exe /SESSION:22513") will NOT be executed at all! That's why when you reboot your system next time, that full screen message will be shown (by CHKSTATE.SYS)! This is the main difference between with or without the "CALL" command!