Yet more problems with Clipper apps running on Intel 3.0Ghz 1

[GAstrada]

Years ago I thought that the __wait_b.obj, linked with the program stuff, was the final solution for high speed machines.
And it was.
But now, in genuine Intel 3.0 Ghz (NOT in AMD architecture), new problems arises: the well known "CPU hogging" was pretty resolved by Ted Means's excellent IAmIdle() function, available from Nanfor lib (last version in NFPAT1A.zip).
But now, in such kind of machines running XP pro in Intel 3.0Ghz, y have new problems:

- Unexpectedly a Clipper apps "freezes" during a "menu to", (a finger pushing continuosly a cursor key) or inside a "dbedit()".
The machine isn't hung: if you wait 2-3 minutes: it processes the pending keystrokes, and continue. Assumed that the __wait_b.obj and Iamidle.obj were linked in the app,: occurs anyway randomly. If you see the CPU usage, tipically isn't more than 2%, (not hogging). What happens ???

- Quitting a Clipper app is surprisingly random: assume you launch it from an inofensive shortcut, it can quit now, .... or in a few minutes !! What happens ???

Technical: - Clipper 5.2e
- Rtlink
- Clipper.lib, extend, nanfor, cpmi

Any help will be appreciated !!!!!!!!!!
Regards
Gustavo

 

[TonHu]

General advise:
I would suggest to 'upgrade' your app and dev-environment to xHarbour (either the free/open source version at

http://www.xharbour.org,

or the commercially supported version, but based on the same sources, at

http://www.xharbour.com

that also offers extra tools and libraries)
I'm experiencing similar problems, just running a commandline (4Dos 7.x) and using several non-Clipper tools, both on Intel and AMD CPU's, and it's IMHO just one way of MS telling us' developers to upgrade to real Windows based tools instead of the old and trusted DOS tools. (Just downloaded the Visual C# 2005 Express Edition ;-))

Real suggestion:
Switch from RT-Link to Blinker (3.30 and up should be rather Ok, latest offering is the best I guess) the 7.x version has been enhanced to resolve specific problems like these. AFAIK RT-Link hasn't been updated in a _very_ long time, surely not the Clipper specific version that came with CL5.2.
Could be you're using the MENU TO enhancements of nanfor? maybe you (as I did) enhanced it in some way, that is now degrading performance, like a wrong INKEY() function call?
The rest of the stuff you're using shouldn't hinder normal performance of any Clipper app.

BTW: You could try to install a Win98se on the system, just to see if the processor or the OS is the culprit, but a side by side install isn't possible out of the box in XP and then '98 order. An extra harddisk (temporarily installed instead of the current) can get you testing :-D

HTH
TonHu