I am not sure about Foxpro but I know Clipper has a similar problem with this because Clipper constantly polls the keyboard for input causing the CPU utilization to shoot up to 100%. There are quite a few tools out there to fix this polling. We use Tamedos also but for a different reason than the polling. You might try Tamedos though.
Originally posted by bryan.tabb
Compaq Desktop, P4 1.6 , 128mb Ram, Win XP Pro, NAV 7.6
When running the Foxpro application everyting works fine. The problems start when the application is minimized and the user attempts to open other apps e.g. word , excel etc etc.
These applications run very slowly, close the foxpro app and everything runs normally.
I've tried usign the run in own memory space, adjusting the priority of NTDM, using the different compatability options. So far nothing has helped.
The high speed cpu patch has been installed.
I've checked task manager during the slow down and found fp26000.esl pretty much at 100% CPU utilisation.
Testing has been done with the application running locally and across the network.