I used only HIMEM when I ran FOXPROX.

On a separate note, Bonnie mentioned VCPI... that reminded me, there are some obscure switches to EMM386 you might be able to try, like /NOVCPI. If memory serves, you can type EMM386 /? at the command prompt to get the full command syntax.

>Hi Al:
>
>I was kind of afraid of that.
>
>What memory manager are you using when you want to use FOXPROX?
>
>Thanks!
>
>--Paul
>
>>FoxPro 2.0 /Extended uses its own DOS extender which is not compatible with MS's EMM386. You have to boot your machine with it not loaded for FOXPROX to run.
>>
>>What I had to do on my old 386 was create a boot menu in CONFIG.SYS. If I wanted to run FOXPROX, I would reboot, then select that boot option. Otherwise, it would boot regularly with EMM386.
>>
>>HTH.
>>
>>>Hi:
>>>
>>>I have a computer with 64 MB of memory. When I start FoxPro DOS 2.0--FOXPROX--I get the following message.
>>>
>>>os386:Expected page to be present
>>> CR2 = 0020 2000 CR3 = 0214 F000
>>> CR2 [Dir Page Offset] = [0000 0201 0000]
>>> CS:EIP = 000F 0000 0000
>>>Interrupt 0E at CS:EIP=000F:00000000
>>>....... address and register dump
>>>
>>>
>>>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?
>>>
>>>Thanks!
>>>
>>>--Paul