Not difficult to slow down your pc, but the question is how to benchmark the speed, after you slowed down your pc. I would think Mark's suggestion is the one to choose.

juan

>>I've just found out that my latest greatest app that I've created on my Pentium II 350Mhz machine runs like shi* on a Pentium 90-based notebook one of the user is using. Is there a way to slow down a VFP program to mimic a slower machine? The newer computer don't come with a "Turbo" button which I used to use to slow it down for testing.
>
>Not without adding timers, bunch of code etc., throughout your app. Best suggestion is to have a second *sub-standard* computer to test on. This is great for testing installation process, apps, etc., with no fear of crapping-out your own computer. I used GHOST software to create an ititial image of my test computer and burned this onto a CD. Then, I can re-dump this image onto the test machine whenever I want to start it over with nothing but Win9x, and the basic software -- i.e., no ODBC drivers, no ODBC connections, no DCOM, no VFP runtime. That way I can find the holes after I install an app for the first time. Dumping the basic image back to the hard drive takes less than 30 minutes!