Hi Bonnie:

The workstation is an IBM with straight MS-DOS 6.0 loaded. If I try using HIMEM only--I get insufficient memory. It has been a while, but I recall that FoxPro 2.0 DOS extended is different than FoxPro 2.5 DOS extended. I need some type of memory manager to emulate expanded memory. If memory serves me correct, I don’t believe that 2.0 can use extended memory.

BTW, I’m still using 2.0 because I need to convert this application to Y2k, and I don’t want to rock the boat in converting it to FoxPro DOS 2.5. There are some serial communications in this program that are currently working. So I’m going let sleeping dogs lie and use the standard version of FoxPro2.0 and tweak the upper memory area.

Thanks All!

--Paul

>>I have tried running MEMMAKER with no change, and all possible options using EMM386 in the CONFIG.SYS--For example:
>>
>>DEVICE=C:\DOS\EMM386.EXE 4096
>>DEVICE=C:\DOS\EMM386.EXE 4096 RAM
>>DEVICE=C:\DOS\EMM386.EXE 4096 HIGHSCAN
>>
>>None of these work.
>>
>>If I try:
>>DEVICE=C:\DOS\EMM386.EXE 4096 NOEMS
>>I get: Incompatible memory manager
>>
>>Does anybody have some new ideas that I can try?
>
>Hi Paul --
>
>The statement DEVICE=C:\DOS\EMM386.EXE 4096 in your config.sys should work. Are you running this in a DOS Window, or shelling out to DOS under Windows? Or is this standalone DOS? (which version of DOS, not that is should matter). Under Windows it could be a problem and it has to do with VCPI (and I forget exactly what this is ... I'm referring to old notes that I wrote myself 8 years ago < g >). But, if you are booting straight to DOS, EMM386 should work without a problem.
>
>Have you tried no memory manager at all? (except, of course, for HIMEM) ... FoxProX should run that way as well. I've never tried QEMM or BlueMax or 386Max, but they are all supposed to work fine without any parameters (again, because of VCPI compatibility).
>
>I suppose you could resort to not running the extended version of FoxPro .... I know, it's a lot slower, but it'll still work. :-(
>
>
>HTH,
>Bonnie