>I agree completely. We have to use a DOS version of Cosession Host 6.1 to communicate with a DOS app at our scale houses. Needless to say, the 350 mghz processor blows right past this communication program. We are using a slowdown utility and calling it from a batch file to run the communication batch file only. When it is done communicating, it sets the speed back to 350 mghz. You can set a throttle with the utility, but you really don't know the speed you are setting it. A 1 on the throttle is almost no slowing and 65,500 is as slow as the processor can be brought down. I have the throttle set at 10,000 which is pretty fast, but the DOS program works. I may be able to tweak it even a little faster.
>
>I don't want to have to use this utility with VFP, but I need to know if anyone else has VFP apps on faster machines and how fast a processor is working good. Since I am seeing the behavior at 350, but it works good at 200 - how does it work with 266 or say 300?

I routinely deploy VFP (not FPW) apps on faster machines; typical machines in our office are 350MHz PII boxes, and at home I use a dual processor box under NT at times. VFP isn't having any problems with the faster machines.

There is no issue with using the 100MHz FSB on the 440BX and GX chipsets with PII processors (any PII processor at 350MHz or above uses the 100MHz FSB.)

>
>Audie
>
>>This is a concern. We don't have any machines that fast, but we were thinking of a major upgrade in the new year. I hope this is a documented problem with a documented solution. And not "set the mainboard to run at a 66 MHz bus speed"...
>>
>>Joe