Hi Pete
Thanks for your prompt reply.
I've been through the rounds with this. I can see in windows task manager that fs is utilising approx 95% & upwards of the cpu when running. The numbers jump about a bit but its taking most of the cpu. The only other process consuming is Explorer.exe and the rest of the background processes are just sitting there apparently not doing much. When RC is running it takes 2 or 3 % momentarily but mainly sits at 0%.
Moving all the sliders to minimum in FS results in frame rates at my set limit of 20 fps, fs continues to draw 95%+ of the cpu and there is no noticeable improvement in the delay problem. Killing many of the non-essential processes (the extent of RC support's suggestions so far) has no effect either.
Right clicking then in the window does, as you suggest, halt, or rather slow fs - its cpu consumption drops and whilst rc "speaks" the "system idle process" takes up the bulk of the cpu %tage - not rc. Once the rc voice has finished but before I left click in the AdvDisp to re-activate FS the cpu split between fs and rc goes to about 60/40 in fs's favour (the numbers do move about a bit) it seems to stay there until I left click. After left clicking fs returns to consuming most of the cpu with rc returning to 0% most of the time. So to summarise the halt on fs by right clicking does reduce its cpu consumption but this isn't taken up by rc immediately - the system idles, although the rc menu & voice responses continue rc doesn't take cpu until after its spoken and it is waiting for me to take the action I've agreed to at which stage it consumes 30 to 40% of cpu with fs taking the rest. Reactivating fs returns it to taking most of the cpu.
I've tried re-setting the priorities of these processes - setting rc to high and fs to low in an attempt to allow rc to get the cpu it needs when it needs it but this does not appear to have any effect on either the problem or the cpu allocations.
The solution may well be to do with halting some of fs's activity - but I'm not convinced it's a cpu capacity problem. The symptoms suggest something more akin to removing a "blockage" or hold which then allows rc to continue.
Hmmmmm!
Yes, both rc and fs are on the same machine which has a single processor.
Ian