CPU hogging (again!)

Hi..

I have an old clipper 5.2 app that I use only occasionally. It was
hogging CPU. So I put in some code like this:

ft_onIdle( { || ft_iamidle(30, .T.) } )

It worked like magic. NTVDM CPU utilisation dropped to around 25%.

Then, to deal with a non-clipper DOS app which was hogging the CPU, I
installed a trial of TameDOS, which would work for about 5 minutes and
then lock cmd.exe altogether. So I decided to live with that one and
remove TameDOS.

The problem is that, now, my clipper 5.2 app which was working prior
to the TameDOS eval, (with the help of ft_onIdle & ft_iamidle from
NFPAT1A), now hogs 100% of the CPU ... regardless of the intensity
parameter passed to ft_iamidle .. a range of values from 1 to 100 ..
the app now hogs the CPU.

I'm running XP SP2.

Has anyone encountered this before? Any suggestions appreciated!

Thanks

Richard

Dear rl:

"rl" <rl@raluke.com> wrote in message
news:1187861276.492151.24830@r23g2000prd.googlegroups.com...
...
> Any suggestions appreciated!

www.xharbour.org, depending on what third party libs you are
using.

David A. Smith

On Aug 23, 12:27 pm, rl <r...@raluke.com> wrote:
> Hi..
>
> I have an old clipper 5.2 app that I use only occasionally. It was
> hogging CPU. So I put in some code like this:
>
>     ft_onIdle( { || ft_iamidle(30, .T.) } )
>
> It worked like magic. NTVDM CPU utilisation dropped to around 25%.
>
> Then, to deal with a non-clipper DOS app which was hogging the CPU, I
> installed a trial of TameDOS, which would work for about 5 minutes and
> then lock cmd.exe altogether. So I decided to live with that one and
> remove TameDOS.
>
> The problem is that, now, my clipper 5.2 app which was working prior
> to the TameDOS eval, (with the help of ft_onIdle & ft_iamidle from
> NFPAT1A), now hogs 100% of the CPU ... regardless of the intensity
> parameter passed to ft_iamidle .. a range of values from 1 to 100 ..
> the app now hogs the CPU.
>
> I'm running XP SP2.
>
> Has anyone encountered this before? Any suggestions appreciated!
>
> Thanks
>
> Richard

Hi,

Read the following url

http://support.citrix.com/article/CTX846521

Download clip2f.exe

I've been using it for years now, dropping the cpu-load to around
2-10% on all of my clipper 5.2e apps. Be warned I havn't tested on
Vista yet.

Lasse

Hi all.

Solution provided by David Thomas of TameDOS :

Tame changes the idle sensitivity in the _default.pif. When you
uninstall Tame it doesn't reset it. Changing the Idle sensitivity
slider in the Misc tab in the WINDOWS\_default.pif fixes the problem.

Thanks David and Lasse for your responses.

Richard

On Aug 23, 7:27 pm, rl <r...@raluke.com> wrote:
> Hi..
>
> I have an old clipper 5.2 app that I use only occasionally. It was
> hogging CPU. So I put in some code like this:
>
>     ft_onIdle( { || ft_iamidle(30, .T.) } )
>
> It worked like magic. NTVDM CPU utilisation dropped to around 25%.
>
> Then, to deal with a non-clipper DOS app which was hogging the CPU, I
> installed a trial of TameDOS, which would work for about 5 minutes and
> then lock cmd.exe altogether. So I decided to live with that one and
> remove TameDOS.
>
> The problem is that, now, my clipper 5.2 app which was working prior
> to the TameDOS eval, (with the help of ft_onIdle & ft_iamidle from
> NFPAT1A), now hogs 100% of the CPU ... regardless of the intensity
> parameter passed to ft_iamidle .. a range of values from 1 to 100 ..
> the app now hogs the CPU.
>
> I'm running XP SP2.
>
> Has anyone encountered this before? Any suggestions appreciated!
>
> Thanks
>
> Richard