Edit C:\windows\system32\config.nt and change the Files= value at the end to a reasonable number. Make sure that you have a solution in place for the CPU hogging, have a look at
Thanks Bozz, I have already given the appropriate value for files in config.nt. I also have checked the linked that you gave. Can you please further clarify the solution for CPU hogging? Using the same CPU and Windows 98, the program works fine but with Win2k it doesn't work. Is there anything I have to re-configure. I could not upgrade to Clipper 5.2e because I think the source codes are incomplete.
CPU hogging is a problem with native Clipper on newer versions of Windows (2k/XP).
When a Clipper program gets to a 'read' situation it completely swamps the processor on the PC with requests for keyboard info. On my machine here it gets to over 50% CPU usage on it's own (peaking at 100%) at that's a 3.2Ghz P4!
Most of the time, when not in a 'read' it behaves quite nicely.
If you don't have the full source code, I'm not sure what you can do about it.
Do you get any error messages? The CPU hogging will not stop the program running on 2000/XP but it slows everything else down. If you look at the performance in task manager (alt-ctrl-del) and it's 100% or near all the time then you have a problem. The problem is Clipper does not release the CPU in wait states and this affects 2000/XP more than 95/98.
Are you able to recompile the program, if so then you can add a couple of lines and a library to fix it. If not then there is a patch programme that may work of your exe's are not compressed by the linker (Blinker).
Have you come across any other methods for previously compiled .exe files - this one seems to have been very well thought out (by an Australian company working with Citrix).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.