>>Interesting Idea but Foxpro doesn't show outside of
>> it's own session in the mem/c listing.
>
>I don't understand your reply, but here's the result
>of "!MEM /C | MORE" from my FoxPro 2.6a (Under
>Win95 DOS box):
>
>Modules using memory below 1 MB:
>
> Name Total Conventional Upper Memory
> -------- ---------------- ---------------- ----------------
> SYSTEM 38,976 (38K) 10,592 (10K) 28,384 (28K)
> HIMEM 1,168 (1K) 1,168 (1K) 0 (0K)
> EMM386 4,320 (4K) 4,320 (4K) 0 (0K)
> WIN 2,240 (2K) 2,240 (2K) 0 (0K)
> vmm32 50,384 (49K) 2,192 (2K) 48,192 (47K)
> COMMAND 8,176 (8K) 8,176 (8K) 0 (0K)
> FOXPRO 357,200 (349K) 357,200 (349K) 0 (0K) <--
> COMMAND 9,232 (9K) 9,232 (9K) 0 (0K)
> IFSHLP 2,864 (3K) 0 (0K) 2,864 (3K)
> SETVER 832 (1K) 0 (0K) 832 (1K)
> COMMAND 7,808 (8K) 0 (0K) 7,808 (8K)
> DOSKEY 4,688 (5K) 0 (0K) 4,688 (5K)
> Free 259,696 (254K) 259,696 (254K) 0 (0K)
>
>If necessary, you can even rename FOXPRO.EXE to other names.


That's right. You are seeing your one instance of Foxpro.exe. Try starting two instances of Foxpro.exe, run the "mem/c | more" from Foxpro (You will see it loaded once) and then it from a DOS window (No instance of Foxpro.exe is shown in memory).