Hi,
This is from Fox Wiki

Here's a couple of fixes we use to run Foxpro DOS in Win 2 K and Win XP:

QuickEdit interferes with the mouse operation.
- Run REGEDIT, search for all occurences of QuickEdit. Change the key value from 1 to 0 (which turns off QuickEdit for all DOS windows)

Foxpro consumes too many CPU cycles. This is easily fixed (once you've turned off QuickEdit)
- create a batch file with the command
START "Foxpro - MyProgram" /low foxprox
- this opens a new window running Foxpro
- the "Foxpro - MyProgram" in quotes becomes the title of the Foxpro window.
- the /low parameter sets the CPU priority of Foxpro DOS to low, so it stops hogging the CPU. This only seems to work if you start it in a new window... there is no way of running it at the reduced CPU priority in the existing window.
- foxprox is the name of the 32 bit version of Foxpro DOS

We add these changes to \WINNT\SYSTEM32\CONFIG.NT
FILES=150
shell=%systemroot%\system32\command.com /e:1024


>Hi chaps
>
>Our company has an old 2.6. application that runs in various bus companies' offices on a variety of machines and OSs.
>One operator is having problems with his version running very slowly on an XP m/c. I have little knowledge of the system and little contact with him. Someone has mentioned something about the Registry maybe contributing to the fault but I don't know. Anyone any ideas?
>
>I think I might have asked this back in Jan but can't find any messages to do with it.
>
>'ppreciate it
>
>Terry