>>>Is there anything special that has to done to run a FoxPro 2.5 app. under NT Workstation. I know, you're probably saying to yourself, "FoxPro 2.5????"
>>>
>>
>>You need to avoid using the Extended Edition, which isn't compatible with the NT memory manager.
>
>I use the extended edition FPD 2.6 all the time with NT4. However, I must say sometimes it totally kicks me out. Don't know the cause. Could this be because the fast CPU problem that I hear about? Or perhaps the memory manager incompatibility that you talk about ?
>
>Anybody know?
>
>Alex

I have several FoxPro 2.6 for DOS apps running on 15 NT 4.0 machines. I set up the NT memory management like this to get the FoxPro extended version to run. Using the Memory tab on the properties dialog of the FoxPro application icon set...
- Extended Memory to 4 Meg or more
- DPMI Memory to 4 Meg or more
- Conventional Memory 630K
Don't use the Auto setting for any of these memory types.
Here is what I imagine happening inside the computer when the app starts.
The FoxPro runtime loads and starts up. NT waits a fraction of a second to see how much memory the application is going to use. At this point, the FoxPro runtime is still checking for available memory and not using much, so NT allocates a small amount. FoxPro sees the small amount and runs the standard mode. If you specify memory amounts, *including conventional memory*, it is there when FoxPro checks for available memory and the extended version runs.

By the way, the "fast machine problem" does not affect FoxPro for DOS, only 2.6 for Windows.
David.